Re: [Users] VM Crash at end of disk move

Hi Markus, Relevant logs you can look at are: on the hypervisor: under /var/log/libvirt/.. The vdsm log under /var/log/vdsm/vdsm.log and on the engine host: under /var/log/ovirt-engine/engine.log hope this helps, Yeela

----- Original Message ----- > From: "Markus Stockhausen" <stockhausen(a)collogia.de&gt; > To: users(a)ovirt.org > Sent: Wednesday, September 11, 2013 7:48:22 PM > Subject: Re: [Users] VM Crash at end of disk move > >> Von: Markus Stockhausen >> Gesendet: Dienstag, 10. September 2013 21:43 >> An: users(a)ovirt.org >> Betreff: VM Crash at end of disk move >> >> Hello, >> >> Thanks for the assistance to get this all running. But now >> I'm working on the next error on my new ovirt cluster. >> >> I migrated a Windows 7 64Bit VMware VM into ovirt using >> virt-v2v. VMWare tools were deinstalled in advance. After >> two boots on ovirt everything seems fine. Just for curiousity >> I moved the boot disk to another storage domain. At the >> end the machine crashes without any indication of the >> reason. ovirt webinterface log reads: >> >> 2013-Sep-10, 21:32 User admin@internal have failed to move disk >> colvm40_1IB_win7x64_Office2010_Test_Disk to domain NAS3_IB. >> 2013-Sep-10, 21:32 VM colvm40_1IB_win7x64_Office2010_Test is down. Exit >> message: Lost connection with qemu process. >> 2013-Sep-10, 21:19 User admin@internal moving disk >> colvm40_1IB_win7x64_Office2010_Test_Disk1 to domain NAS3_IB. >> 2013-Sep-10, 21:19 Snapshot 'Auto-generated for Live Storage Migration' >> creation for VM 'colvm40_1IB_win7x64_Office2010_Test' has been completed. >> 2013-Sep-10, 21:18 Snapshot 'Auto-generated for Live Storage Migration' >> creation for VM 'colvm40_1IB_win7x64_Office2010_Test' was initiated by >> admin@internal. >> 2013-Sep-10, 21:17 VM colvm40_1IB_win7x64_Office2010_Test started on Host >> colovn1 >> >> After this crash VM can be started again. The disk image is >> taken from the target storage domain. So it seems as if the >> move was successful. Another (SLES 11 SP3) VM that was >> newly created inside the cluster does not show this problem. >> >> As I did not find qemu logs, what would be the best place to >> start analysis with. >> >> Best regards. >> >> Markus > > Memo for myself: Install ALL Windows VIRTIO drivers. virt-v2v > only does the basics to get the VM up after the migration. > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users