diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2017-04-12 14:53:15 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2017-04-12 14:53:15 +0200 |
| commit | 6e306c77d3bd945dd48fd9746ac1b07610e85f36 (patch) | |
| tree | 32272d5c89367cb7df7433a02d9716cf2dfa901a /doc | |
| parent | b665dce0ea1a19c77ef522d3bfafb8210f9455b3 (diff) | |
Add support for KVM, monitoring bbot diagnostics
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/manual.cli | 19 |
1 files changed, 16 insertions, 3 deletions
diff --git a/doc/manual.cli b/doc/manual.cli index b91f6ae..2d275aa 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -199,7 +199,7 @@ While any suitable filesystem can be used, \c{ext4} is a good choice, with journaling disabled if used on a flash drive/card. For example: \ -mkfs.ext4 -L buildos.machines -O ^has_journal /dev/sdX +mkfs.ext4 -L buildos.state -O ^has_journal /dev/sdX \ \h2#config-storage-machines|Machines| @@ -423,7 +423,7 @@ build$ cd /build/machines/default/linux-gcc_6 # Make user build the owner of the machine subvolume. # build$ sudo btrfs property set -ts linux-gcc_6-1.0 ro false -build$ sudo chown build:build linux-gcc_6-1.0 +build$ sudo chown build:build linux-gcc_6-1.0 linux-gcc_6-1.0/* build$ btrfs property set -ts linux-gcc_6-1.0 ro true # Make the subvolume the current machine. @@ -450,7 +450,7 @@ build$ cd /build/machines/default/linux-gcc_6 # Make user build the owner of the new machine subvolume. # build$ sudo btrfs property set -ts linux-gcc_6-1.1 ro false -build$ sudo chown build:build linux-gcc_6-1.1 +build$ sudo chown build:build linux-gcc_6-1.1 linux-gcc_6-1.1/* build$ btrfs property set -ts linux-gcc_6-1.1 ro true # Switch the current machine atomically. @@ -505,4 +505,17 @@ Note also that on reboot the Build OS monitor examines and cleans up machine directories of any stray subvolumes. As a result, an alternative approach would be to remove the current machine symlink and reboot the build host. + +\h#machines-login|Logging into a Machine| + +A running QEMU/KVM machine (that is, one being bootstrapped or used for +building) can be accessed with a VNC client. @@ TODO + +\ +echo cont | ssh build@build socat - UNIX-CONNECT:/tmp/<toolchain>-monitor +\ + +\ +ssh -f -L 5901:127.0.0.1:5901 build@build sleep 1 && vncviewer 127.0.0.1:5901 +\ " |