Re: [ovirt-users] win 2008 kvm import
thank you - will wait and check that out thanks and regards, grant pasley. xtranet. On 6/4/2015 5:02 PM, Michal Skrivanek wrote: On 30 May 2015, at 05:03, Grant Pasley wrote: thank you daniel, i will play around with this and see how it goes before trying it on a production machine. thanks and regards, grant pasley. xtranet. On 5/29/2015 10:44 AM, Daniel Helgenberger wrote: On 29.05.2015 02:53, Grant Pasley wrote: hi all, Hello Grant, i am going to migrate a production windows 2008 image that is currently running on kvm over to ovirt 3.5.2 this weekend. are there any tips, any do's and dont's i should be aware of before doing this? Well, if waiting for 3.6 is not an option (there, v2v integration is a note that file-based kvm import probably won't be in 3.6 at GA time, possibly a bit later, so just a little bit more waiting:-) 3.6 GA will have VmWare vCenter only command line can do whatever it could do before, including what you say below major new feature [1]) you can use manual v2v command line [2] just as well. This is non destructive and leaves the original VM intact. Basically: # virt-v2v -o rhev -osd storage.example.com:/exportdomain --network rhevm vm-name The trick is '-o rhev'. It basically drops the VM from libvirt on your export domain; it worked quite well for me. It also takes care of installing virtio dirvers in the image. There where some pitfalls, though - I can't remember all of them. But one is of course your old host needs have NTFS write support in some way; and (at leat a year back) there was no package for the virtio drivers on CentOS; but they just need to be put in the right place. should i install the windows guest tools before moving over or once done? what about having to install the virtio drivers when doing and new windows vm in order to see the disks, how is this achieved with an already created kvm image? it's a kvm-to-kvm migration, nothing extra's needed in the guest, it should work just fine I wonder if it would even need to write/read anything from that NTFS volume (dunno, check v2v/guesttools docs) Post-conversion I'd recommend to install the guest tools (to get spice features, perhaps newer drivers, ovirt guest agent integration/reporting) Thanks, michal [1] http://www.ovirt.org/Features/virt-v2v_Integration [2] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization_for_Servers/2.2/html/Administration_Guide/virt-v2v-scripts.html --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] win 2008 kvm import
On 30 May 2015, at 05:03, Grant Pasley wrote: thank you daniel, i will play around with this and see how it goes before trying it on a production machine. thanks and regards, grant pasley. xtranet. On 5/29/2015 10:44 AM, Daniel Helgenberger wrote: On 29.05.2015 02:53, Grant Pasley wrote: hi all, Hello Grant, i am going to migrate a production windows 2008 image that is currently running on kvm over to ovirt 3.5.2 this weekend. are there any tips, any do's and dont's i should be aware of before doing this? Well, if waiting for 3.6 is not an option (there, v2v integration is a note that file-based kvm import probably won't be in 3.6 at GA time, possibly a bit later, so just a little bit more waiting:-) 3.6 GA will have VmWare vCenter only command line can do whatever it could do before, including what you say below major new feature [1]) you can use manual v2v command line [2] just as well. This is non destructive and leaves the original VM intact. Basically: # virt-v2v -o rhev -osd storage.example.com:/exportdomain --network rhevm vm-name The trick is '-o rhev'. It basically drops the VM from libvirt on your export domain; it worked quite well for me. It also takes care of installing virtio dirvers in the image. There where some pitfalls, though - I can't remember all of them. But one is of course your old host needs have NTFS write support in some way; and (at leat a year back) there was no package for the virtio drivers on CentOS; but they just need to be put in the right place. should i install the windows guest tools before moving over or once done? what about having to install the virtio drivers when doing and new windows vm in order to see the disks, how is this achieved with an already created kvm image? it's a kvm-to-kvm migration, nothing extra's needed in the guest, it should work just fine I wonder if it would even need to write/read anything from that NTFS volume (dunno, check v2v/guesttools docs) Post-conversion I'd recommend to install the guest tools (to get spice features, perhaps newer drivers, ovirt guest agent integration/reporting) Thanks, michal [1] http://www.ovirt.org/Features/virt-v2v_Integration [2] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization_for_Servers/2.2/html/Administration_Guide/virt-v2v-scripts.html --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] win 2008 kvm import
On 29.05.2015 02:53, Grant Pasley wrote: hi all, Hello Grant, i am going to migrate a production windows 2008 image that is currently running on kvm over to ovirt 3.5.2 this weekend. are there any tips, any do's and dont's i should be aware of before doing this? Well, if waiting for 3.6 is not an option (there, v2v integration is a major new feature [1]) you can use manual v2v command line [2] just as well. This is non destructive and leaves the original VM intact. Basically: # virt-v2v -o rhev -osd storage.example.com:/exportdomain --network rhevm vm-name The trick is '-o rhev'. It basically drops the VM from libvirt on your export domain; it worked quite well for me. It also takes care of installing virtio dirvers in the image. There where some pitfalls, though - I can't remember all of them. But one is of course your old host needs have NTFS write support in some way; and (at leat a year back) there was no package for the virtio drivers on CentOS; but they just need to be put in the right place. should i install the windows guest tools before moving over or once done? what about having to install the virtio drivers when doing and new windows vm in order to see the disks, how is this achieved with an already created kvm image? [1] http://www.ovirt.org/Features/virt-v2v_Integration [2] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization_for_Servers/2.2/html/Administration_Guide/virt-v2v-scripts.html -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
