When the monitor if the VM is off, you can ssh to the host machine to see if the host machine is not turn off accidentally. If the host machine is on(which means that you can ssh to it), you can check the status of the corresponding VM by : ``` lang=bash # systemctl status hmux@ecc-(Lab)-(Machine Number) $ systemctl status hmux@ecc-a-09 ``` To wake up the vm ``` lang=bash # socat - UNIX-CONNECT:/var/run/qemu/ecc-(Lab)-(Machine Number)/monitor $ socat - UNIX-CONNECT:/var/run/qemu/ecc-a-09/monitor ``` IMPORTANT: In socat, do not just quit using the {key q} or type in `quit` because that will completely shutdown the virtual machine. Use {key Ctrl C} to exit the current session. ==Qemu Host not responding to start command If the virtual machinese are not responding after the the host restated, use the unbind script with the following command with root. ``` lang=bash $ /var/qemu/unbind.sh ``` Restart the virtual machines. NOTE: ecc-a-qemu04.rd.unr.edu would mostly encounter this issue. ==Create a new Virtual Machine 1. ssh to the host machine 2. get root access by entering `$ sudo su` 3. `$ cd /var/tmp` 4. `$ ls` to make sure `win10.iso` and `virtio.iso` are within the directory 5. Remove the old volume ``` lang=bash # lvremove (volume group)/(Vm name) $ lvremove vg0/ecc-a-17 ``` 6. Create a new blank volume: ``` lang=bash # lvcreate (Size) -n (Vm name ) (volume group) $ lvcreate -L300G -n ecc-a-17 vg0 ```

When the monitor if the VM is off, you can ssh to the host machine to see if the host machine is not turn off accidentally. If the host machine is on(which means that you can ssh to it), you can check the status of the corresponding VM by : Use systemctl status hmux@ecc-a-(machine number) to check the status of the vms. Use `uptime` to check how long the machine have been running. ``` lang=bash # systemctl status hmux@ecc-(Lab)-(Machine Number) $ systemctl status hmux@ecc-a-09 ``` To wake up the vm ``` lang=bash # socat - UNIX-CONNECT:/var/run/qemu/ecc-(Lab)-(Machine Number)/monitor $ socat - UNIX-CONNECT:/var/run/qemu/ecc-a-09/monitor ``` IMPORTANT: In socat, do not just quit using the {key q} or type in `quit` because that will completely shutdown the virtual machine. Use {key Ctrl C} to exit the current session. ==Qemu Host not responding to start command If the virtual machinese are not responding after the the host restated, use the unbind script with the following command with root. ``` lang=bash $ /var/qemu/unbind.sh ``` Restart the virtual machines. NOTE: ecc-a-qemu04.rd.unr.edu would mostly encounter this issue. ==Create a new Virtual Machine 1. ssh to the host machine 2. get root access by entering `$ sudo su` 3. `$ cd /var/tmp` 4. `$ ls` to make sure `win10.iso` and `virtio.iso` are within the directory 5. Remove the old volume ``` lang=bash # lvremove (volume group)/(Vm name) $ lvremove vg0/ecc-a-17 ``` 6. Create a new blank volume: ``` lang=bash # lvcreate (Size) -n (Vm name ) (volume group) $ lvcreate -L300G -n ecc-a-17 vg0 ```

When the monitor if the VM is off, you can ssh to the host machine to see if the host machine is not turn off accidentally. If the host machine is on(which means that you can ssh to it), you can check the status of the corresponding VM by : Use systemctl status hmux@ecc-a-(machine number) to check the status of the vms. Use `uptime` to check how long the machine have been running. ``` lang=bash # systemctl status hmux@ecc-(Lab)-(Machine Number) $ systemctl status hmux@ecc-a-09 ``` To wake up the vm ``` lang=bash # socat - UNIX-CONNECT:/var/run/qemu/ecc-(Lab)-(Machine Number)/monitor $ socat - UNIX-CONNECT:/var/run/qemu/ecc-a-09/monitor ``` IMPORTANT: In socat, do not just quit using the {key q} or type in `quit` because that will completely shutdown the virtual machine. Use {key Ctrl C} to exit the current session. ==Qemu Host not responding to start command If the virtual machinese are not responding after the the host restated, use the unbind script with the following command with root. ``` lang=bash $ /var/qemu/unbind.sh ``` Restart the virtual machines. NOTE: ecc-a-qemu04.rd.unr.edu would mostly encounter this issue. ==Create a new Virtual Machine 1. ssh to the host machine 2. get root access by entering `$ sudo su` 3. `$ cd /var/tmp` 4. `$ ls` to make sure `win10.iso` and `virtio.iso` are within the directory 5. Remove the old volume ``` lang=bash # lvremove (volume group)/(Vm name) $ lvremove vg0/ecc-a-17 ``` 6. Create a new blank volume: ``` lang=bash # lvcreate (Size) -n (Vm name ) (volume group) $ lvcreate -L300G -n ecc-a-17 vg0 ```