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
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_Virtuali...
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com