https://bugzilla.novell.com/show_bug.cgi?id=738694
https://bugzilla.novell.com/show_bug.cgi?id=738694#c3
Charles Arnold
Yes, a reboot resolves the issue - provided you can do it. In other words, active Xen VMs must be shut down _prior_ to an update of the Xen components, or the update should abort. (exit 1 in %pre of xen component)
Your suggestion has some merit given that the host always has to be rebooted for the new hypervisor and tools to be used. However, we don't want to force a failure of the xen package just because a guest is running particularly with maintenance releases that can be enabled to happen automatically. In this case, the newer RPMs should not cause a problem with existing processes. With an OS upgrade where the ABI changes (and you run into the problem you are seeing), best practice is for the admin/user to shutdown the guests before proceeding with the upgrade. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.