I want to upgrade a Xen paravirtualized guest from 10.3 to 11.0 but I can´t figure out how to do. If I remember correctly there was earlier a Yast tool for “System update”, but I can´t find it in 10.3.
The best would of course be to boot from an ISO image, but I don´t know how to do this without converting it to a HVM guest.
I also noticed that zypper in 11.0 has a dist-upgrade option, does it work to upgrade zypper in 10.3 and use this option ??
See this thread for some methods to upgrade other than using the dvd. Upgrade to 11.0 from 10.3 using ISO image - openSUSE Forums
As far as I know a ‘System Update’ won’t bring 10.3 up to 11, or do you mean the ‘zypper dup’ (see thread).
I’m not sure what you mean by ‘converting it to a HVM guest’, but you should be able to boot your guest using the ISO (set it as first drive), and upgrade from there.
Also curios to know if this is a production machine you are using?
Cheers,
Wj
This link from the thread you posted, Upgrading openSUSE 10.3 –> 11.0 in a running system., 24/06/08, Benjamin’s blog might work for me.
The problem is with ISO images is that I can´t find a way to boot a paravirtualized machine from an image, except when I do the first installation (using Yast´s virtual machine install).
If I convert it to a fully virtualized (HVM) machine I could add the ISO image as an emulated DVD and run the normal upgrade path.
I meant “zypper dup”, but that is not available in 10.3, but according to the above link it is easy to upgrade and run using the new 11.0 repos, I will give it a shot later. And no it is just a home system, and it it easy to just snapshot th VM and roll back if anything goes wrong.
My Xen config looks like this, do you mean that I can replace the disk entries and put the 11.0 ISO image as the first disk ?
Do I need to modify the bootargs ?
I think I have tried that before without success though.
name=“Test1”
ostype=“opensuse”
uuid=“f3df5c45-b507-c4c8-fc2f-3af87bc2cb80”
memory=384
vcpus=1
on_crash=“destroy”
on_poweroff=“destroy”
on_reboot=“restart”
localtime=0
builder=“linux”
bootloader="/usr/lib/xen/boot/domUloader.py"
bootargs="–entry=xvda2:/boot/vmlinuz-xen,/boot/initrd-xen"
extra=" "
disk= ‘file:/mnt/data2/vm/xen/Test1/disk0,xvda,w’, ‘file:/mnt/data2/OS/openSUSE-10.3-GM-DVD-x86_64.iso,xvdb:cdrom,r’, ]
vif= ‘mac=00:16:3e:55:60:60,bridge=xenbr1’, ‘mac=00:16:3e:42:05:65,bridge=xenbr2’, ]
vfb=‘type=vnc,vncunused=1’]
Thanks for the links
I don’t have a Xen setup here at the moment… so can’t test.
But simply try setting the cdrom/ISO as fist drive, like so:
disk= ‘file:/mnt/data2/OS/openSUSE-10.3-GM-DVD-x86_64.iso,xvdb:cdrom,r’, ‘file:/mnt/data2/vm/xen/Test1/disk0,xvda,w’, ]
It sould let the ISO take boot priority.
If you are updating th file directly, shutdown the VM, issue a ’ xm new <serverconfigfile> ’ and then ’ xm create <serverconfigfile> '(the xm new imports the changed configuration into the xml file).
After running the update reverse the change you made.
Hope that helps,
Wj
Didn´t work with reordering the boot devices, however upgrading zypper and using “zypper dup” worked just fine.
It would be interesting to know how Yast handles the installation of VMs, it seems there is some kind of template which differs depending on which guest OS you want to install.
I guess these contains the command line sent to “xm create”, but I can´t seem to find any information on this.