This wont work.
>From the Xen docs:
###################
Using older Xen versions is known to be problematic, for example Xen 4.0.0 
libraries have problems with recent 2.6.32.x kernels, making xend fail to start 
due to evtchn/gntdev device node creation issues. Using Xen 3.4.2 or older 
won't work at all, since old hypervisor versions lack the new required IOAPIC 
setup hypercall and boot will fail with IRQ related issues.

It's recommended to run the latest Xen 4.0.x version, at least Xen 4.0.1.
###################

So step 1 would fail, because my hardy does "only" got a xen 3.3.0  or xen 
3.2.x one; but those one would already fail to boot on this new kernel.
So i'll have to update to xen 4.0.1+ first, but there is no such paket for 
hardy *uggggh* - so still a "broken" upgrade path.

What now? Do you really want to tell me that i am stuck at hardy and
have to do a complete reinstall of my host to get to a supported LTS
release with Xen dom0 support?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/517060

Title:
  hardy->lucid upgrade using "linux-image-xen" breaks systems running in
  PV mode under xen/xenserver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/517060/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to