Hi.
I use suse linux 11 SP2 + Xen4.1 + HA to create a para-virtualisation VM. VM OS is suse linux SP2. the kenel is vmlinuz-3.0.13-0.27-xen. then i change this VM from para-virtualisation VM to full-virtualization VM. I do below steps.
install a new kernel with the suse linux SP2 CD by YST. new kernel is vmlinuz-3.0.13-0.27-default. /boot/grub/menu.lst is update accordingly.
2)chage the /etc/fstab file. update all fields with xvda to hda. same thing for the xvdb …
3)in Dom0. change the VM startup config files. from
[COLOR="#FF0000"]builder=“linux”
bootloader="/usr/bin/pygrub"
bootargs=""
extra=""[/COLOR]
to
[COLOR="#FF0000"]builder=“hvm”
device_model="/usr/lib/xen/bin/qemu-dm"
kernel="/usr/lib/xen/boot/hvmloader"[/COLOR]
also change all xvdN to hdN.
then startup the vm using xm create .
VM startup successfully. I check the kernel is changed to vmlinuz-3.0.13-0.27-default.
is this method correct? did i missed something?
is there any potential issues to running the legacy software already installed?
Please post questions in the forums. No support provided via email.[/QUOTE]
’
I am doing regression test and i just want to know from the expert viewpoint if there is potential
problem. we use the suse HA extension for the HA. i create two VMs for HA backup and they are para-visualisation.