vm from fc13 ro rhel/CentOS 5

[Gianluca Cecchi]

Hi,
what is the simpler way to "port" a vm created in current FC13 x86_64 host
to test it inside an updated rhel 5.5 x86_64 host (still with qemu/kvm)?

So source is based on
qemu-kvm 0.12.3-8.fc13
libvirt 0.7.7-5fc13

and target
kvm-83-184.el5_5.12
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?sid=1016784000&id_combo=217222%7C907818
libvirt 0.6.3-33.el5_5.1

If this is important, source vm disk is qcow2

Thanks in advance,
Gianluca

[Dor Laor]

On 07/21/2010 06:26 PM, Gianluca Cecchi wrote:
> Hi,
> what is the simpler way to "port" a vm created in current FC13 x86_64
> host to test it inside an updated rhel 5.5 x86_64 host (still with
> qemu/kvm)?
>
> So source is based on
> qemu-kvm 0.12.3-8.fc13
> libvirt 0.7.7-5fc13
>
> and target
> kvm-83-184.el5_5.12
> https://rhn.redhat.com/rhn/software/packages/details/Overview.do?sid=1016784000&id_combo=217222%7C907818
> libvirt 0.6.3-33.el5_5.1
>
> If this is important, source vm disk is qcow2

It depends. If it's Linux, most chances you're safe, unless you have 
specific scripts that tied into specific pci slot / ethX enumeration.
The above issue is cause because the pci slots might change between the 
two code bases.

That's mainly because you move from new (f13) to rhel5.5. Move to 
rhel6.0 will be easier.

Windows guest might ask for re-activation.

The safest way for you to discover is use a qcow2 external backing file 
(snapshot). This way no harm will happen if you'll revert the change.
> Thanks in advance,
> Gianluca
>
> virt mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/virt