Restoring Virtual Machines

[LimeCenter]

Dear sir or madam,

Kindly I would like to inform you that for no particular reason (to my knowledge) my two virtual machines disappeared after a basic reboot; windows 7 and a Ubuntu VM. The vdisk.img files seem to exist perfectly fine however no VM's appear. I must admit that have not made any back-ups of the XML files something that I will do from now on seeing that unRAID is not as stable as I though it would be.

Since I was unable to find documentation on how to restore the the VM I was wondering if anyone had recommendations how to restore VMs (rebooting again did not help).

[althoralthor]

I just upgraded to 6.5 and my VM's are gone as well.  VM's are enabled, but they are gone.  Has anyone else seen this?

[althoralthor]

right...besides you i guess. 

[althoralthor]

In fact, I do not even see anything on the VM's page.  No option to start existing, no option to create new VM

 

[Squid]

In VM settings are all the entries pointing to a valid share and is the location for libvirt.img pointing to the file and not a folder. If in doubt post diags

[althoralthor]

Thanks Squid- thats just it.  I can't even view the settings any longer.   Diags are attached.  Any help is appreciated!

 

emperor-diagnostics-20180412-1144.zip

[Squid]

Edit config/domain.cfg on the flash drive (use Notepad++ if using windows -> not Notepad), and give it a valid path for VIRTIOISO (say /mnt/user/system) or where ever the virtio image is stored.  Also change MEDIADIR to be /mnt/user/system  and you **should** be in business.

[althoralthor]

Squid- you are the MAN.  I am able to start my windows VM.   thank you sir!

 

there is one issue that I'm still trying to figure out.  I have a Mac VM as well that has always worked.  I get an error (screen shot below) when trying to start it.   Here are the logs.  If you need more diags, etc. please let me know.

 

2018-04-12 18:19:13.072+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: Emperor
2018-04-12 18:19:13.072+0000: Domain id=1 is tainted: high-privileges
2018-04-12 18:19:13.072+0000: Domain id=1 is tainted: custom-argv
2018-04-12T18:19:13.097941Z qemu-system-x86_64: -machine pc-q35-2.3,accel=kvm,usb=off,dump-guest-core=off: unsupported machine type
Use -machine help to list supported machines
2018-04-12 18:19:13.149+0000: shutting down, reason=failed
2018-04-12 18:21:06.816+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: Emperor
2018-04-12 18:21:06.816+0000: Domain id=2 is tainted: high-privileges
2018-04-12 18:21:06.816+0000: Domain id=2 is tainted: custom-argv
2018-04-12T18:21:06.841592Z qemu-system-x86_64: -machine pc-q35-2.3,accel=kvm,usb=off,dump-guest-core=off: unsupported machine type
Use -machine help to list supported machines
2018-04-12 18:21:06.861+0000: shutting down, reason=failed
2018-04-12 18:21:56.013+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: Emperor
2018-04-12 18:21:56.013+0000: Domain id=4 is tainted: high-privileges
2018-04-12 18:21:56.013+0000: Domain id=4 is tainted: custom-argv
2018-04-12T18:21:56.038205Z qemu-system-x86_64: -machine pc-q35-2.3,accel=kvm,usb=off,dump-guest-core=off: unsupported machine type
Use -machine help to list supported machines
2018-04-12 18:21:56.089+0000: shutting down, reason=failed

 

Below is the error window...  Any help is appreciated!

 

Edited April 12, 2018 by althoralthor

[Squid]

Q35-2.3 is no longer a supported machine type.  Edit the VM, and you should be able to change it.  No idea of the ramifications though.

[althoralthor]

Now that...is a bummer.  I'm sure you can guess the ramifications....the VM won't boot now.  Has anyone else out there gotten their Mac VM to run with 6.5?

[1812]

1 hour ago, althoralthor said:

Now that...is a bummer.  I'm sure you can guess the ramifications....the VM won't boot now.  Has anyone else out there gotten their Mac VM to run with 6.5?

i'm on 6.5 rc3 and run 2 osx vm's no problem using pc-q35-2.11

 

 

[althoralthor]

So I probably need to reinstall Mac OS i would imagine?

 

 

So recreating the VM (rebuilding the xml, etc.) worked just fine.  My VM is back.  Thanks 1812, and thanks Squid.  You guys rock!

Edited April 13, 2018 by althoralthor
Fixed issue

[ICPete]

On 4/12/2018 at 10:06 AM, Squid said:

Edit config/domain.cfg on the flash drive (use Notepad++ if using windows -> not Notepad), and give it a valid path for VIRTIOISO (say /mnt/user/system) or where ever the virtio image is stored.  Also change MEDIADIR to be /mnt/user/system  and you **should** be in business.

Thank you Squid! This suggestion worked for me as well. I was having trouble starting a Ubuntu VM for the first time, the desktop version with GUI, so that I had to provide my graphics adapter to the VM. My VIRTIOISO path setting turned out to be /mnt/user/system/libvirt/. Bingo, the Ubuntu installation fired right up, I completed the installation process to the virtual drive, and I can run the Ubuntu desktop just like it's on bare metal. You're the best!