[Bug 738694] New: xen: cannot interact with xend after upgrade
https://bugzilla.novell.com/show_bug.cgi?id=738694 https://bugzilla.novell.com/show_bug.cgi?id=738694#c0 Summary: xen: cannot interact with xend after upgrade Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: jdouglas@suse.com ReportedBy: jengelh@medozas.de QAContact: qa@suse.de Found By: Beta-Customer Blocker: --- After upgrade from 11.4 to 12.1 via zypper dup (the system is still running in its old state), I can no longer issue xm commands. 18:31 mz38:/var/log # strace -e connect xm list connect(3, {sa_family=AF_FILE, path="/var/run/xend/xmlrpc.sock"}, 27) = -1 ECONNREFUSED (Connection refused) Error: Unable to connect to xend: Connection refused. Is xend running? /var/log/xen/xend.log contains: [2011-12-27 18:30:01 7351] INFO (SrvDaemon:227) Xend stopped due to signal 15. [2011-12-27 18:30:10 7455] INFO (SrvDaemon:332) Xend Daemon started [2011-12-27 18:30:10 7455] INFO (SrvDaemon:336) Xend changeset: 21452. [2011-12-27 18:30:10 7455] ERROR (SrvDaemon:349) Exception starting xend ((13, 'Permission denied')) Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xen/xend/server/SrvDaemon.py", line 341, in run servers = SrvServer.create() File "/usr/lib64/python2.7/site-packages/xen/xend/server/SrvServer.py", line 261, in create root.putChild('xend', SrvRoot()) File "/usr/lib64/python2.7/site-packages/xen/xend/server/SrvRoot.py", line 40, in __init__ self.get(name) File "/usr/lib64/python2.7/site-packages/xen/web/SrvDir.py", line 84, in get val = val.getobj() File "/usr/lib64/python2.7/site-packages/xen/web/SrvDir.py", line 52, in getobj self.obj = klassobj() File "/usr/lib64/python2.7/site-packages/xen/xend/server/SrvNode.py", line 30, in __init__ self.xn = XendNode.instance() File "/usr/lib64/python2.7/site-packages/xen/xend/XendNode.py", line 1220, in instance inst = XendNode() File "/usr/lib64/python2.7/site-packages/xen/xend/XendNode.py", line 94, in __init__ self.other_config["xen_pagesize"] = self.xeninfo_dict()["xen_pagesize"] File "/usr/lib64/python2.7/site-packages/xen/xend/XendNode.py", line 1126, in xeninfo_dict return dict(self.xeninfo()) File "/usr/lib64/python2.7/site-packages/xen/xend/XendNode.py", line 1069, in xeninfo info['xen_scheduler'] = self.xenschedinfo() File "/usr/lib64/python2.7/site-packages/xen/xend/XendNode.py", line 1057, in xenschedinfo sched_id = self.xc.sched_id_get() Error: (13, 'Permission denied') -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=738694 https://bugzilla.novell.com/show_bug.cgi?id=738694#c1 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |carnold@suse.com InfoProvider| |jengelh@medozas.de --- Comment #1 from Charles Arnold <carnold@suse.com> 2012-01-09 15:36:10 UTC --- You must reboot when upgrading from 11.4 to 12.1. Is this still a problem after rebooting? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=738694 https://bugzilla.novell.com/show_bug.cgi?id=738694#c2 Jan Engelhardt <jengelh@medozas.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jengelh@medozas.de | --- Comment #2 from Jan Engelhardt <jengelh@medozas.de> 2012-01-09 16:10:08 UTC --- Yes, a reboot resolves the issue - provided you can do it. The problem is that when attempting to reboot, shutting down the Xen VMs no longer works due to the same reason `xm list` is not functional, and bringing down VMs the hard way is not nice. 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) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=738694 https://bugzilla.novell.com/show_bug.cgi?id=738694#c3 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfehlig@suse.com --- Comment #3 from Charles Arnold <carnold@suse.com> 2012-01-09 20:25:08 UTC --- (In reply to comment #2)
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.
https://bugzilla.novell.com/show_bug.cgi?id=738694 https://bugzilla.novell.com/show_bug.cgi?id=738694#c4 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |FIXED --- Comment #4 from Charles Arnold <carnold@suse.com> 2012-01-25 15:22:58 UTC --- The requirement to shutdown guests on OS upgrade has been added to the README. New packages for Xen should show up in the channel in a couple weeks. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com