On Thu, Aug 13, 2015 at 10:47:41AM -0400, Martin Breault wrote:
Hello,
Not sure if this is the correct list so apologies if this question is misplaced.
I tried migrating using virt-v2v a pair of Windows 2012R2 servers to oVirt using Fedora22 as a p2v server and was happy to see that it worked perfectly.
Note that Windows > 7 is not well tested. Make sure you keep backups even if the conversion appears to go normally.
I notice however that the windows icon for "safe removal" now appears on the bottom right, and when I click it, apparently I can "safely remove" my VirtIO NIC, a VirtIO serial device, and my VirtIO disk!?!?!?! I tried it on the NIC as a test and unsurprisingly, I lost all network communication to the host. I didn't try it on the VirtIO disk because I didn't want to risk crashing my OS, however this doesn't seem normal. The disk on which the system is running can't be removable?!
How can I fix this?
You probably want to ask about this on the qemu mailing list, at least that's according to: https://fedoraproject.org/wiki/Windows_Virtio_Drivers#Bugs Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/