On Thu, 22 May 2008 10:26:32 -0700 Matthias Saou wrote:
I assume this is again due to the Xen version rebase, same as with the 5.0 to 5.1 update : After updating a Xen server (dom0) to RHEL 5.2 without rebooting on the newer kernel, some Xen related operations start to fail. Currently, I'm unable to start any guests (domU), and the behavior is not really helpful : "xm create -c foo" just hangs for a while and exits with the error : Error: Device 0 (vif) could not be connected. Hotplug scripts not working. ... This is quite annoying, as it causes problems which might go undetected for months (years?) and will bite at the worst possible moment : When a guest crashes and needs to be restarted... I wouldd really like to see some improvements to Xen is backwards compatibility regarding the kernel/userspace duo in dom0, as to "fix" this issue, if a reboot isn't possible (as other critical domUs might be running), a simple downgrade of the userspace xen tools might do the trick. So how hard would it be for the new tools to have the old behaviour if the old kernel is found?
Just a head's up to the unwary, this is also(still) the case for 5.2 to 5.3. I just had a domU go down on a box that got updated to 5.3 and had to reboot the whole box to get things back up. Of course, this required unplanned outages on other domU's that happened to be on the same box.
Now I know to only take the xen updates manually, when I can schedule it. -Bill -- Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 [email protected] Cell: 603.252.2606 http://www.bfccomputing.com/ Page: 603.442.1833 Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
