For what it's worth, I just did this upgrade recently. I wasn't prepared to risk breaking my 3.0.4 setup, so I cloned my entire root filesystem (I use an LVM root FS), added an extra grub entry so I could boot from the old or the new one, and only then installed the tarballs in one, keeping the other as a safety net.
I had a heck of a time getting my 3.1.0 Dom0 going. It was entirely my own fault, though -- all the problems I had were related to getting the right kernel config parameters for my hardware, and for my initrd setup supporting lvm root filesystem. In hindsight, it would have been trivially easy if I'd just done a diff of my old (
2.6.16.33-xen) kernel config versus the stock xen-patched counterpart, and then applied the same changes to the new (2.6.18-xen) kernel.
Sorry, I didn't try running 3.0.4 with the 3.1.0 tools, not 3.1.0 with the
3.0.4 kernel, so I can't tell you if these permutations work. But I'd bet money that they don't.
Good luck.
On 9/25/07, Gregory Gee
<gregory.gee@xxxxxxxxxxxx> wrote:
So I am planning on upgrading my dom0 from 3.0.4 to 3.1.0. I have
already done this for the domU's. But I need to know my backout plan if
something doesn't go right. I have a simple question.
If I install the 3.1.0 from the tarball, can I still boot the 3.0.4
dom0 kernel with the 3.1.0 Xen tools if needed? I'm not sure of the
compatibility. I had to compile my own 3.0.4 kernel because of missing
SATA drivers in 2.6.16, but I believe they are in 2.6.18, which Xen
3.1.0 is based on. I'll try and boot the 3.1.0 kernel, but if it
fails, can I boot the 3.0.4 kernel even though the xm tools are 3.1.0?
Thanks,
Greg
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users