[Bug 727081] New: xend domains don't work anymore since update from 12.1 beta to 12.1 RC 1
https://bugzilla.novell.com/show_bug.cgi?id=727081 https://bugzilla.novell.com/show_bug.cgi?id=727081#c0 Summary: xend domains don't work anymore since update from 12.1 beta to 12.1 RC 1 Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: i686 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas@suse.com ReportedBy: novell@kapsler.ch QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Had several domU's running with 12.1 beta just fine. I can start suse with the new kernel but domU's dont start anymore. xen seems to crash after startup, see logs dmesg: [ 547.025607] xend[15061]: segfault at 240506dc098 ip 00007f7af0e3d779 sp 00007fff506dbe38 error 4 in libxenguest.so.4.0.0[7f7af0e22000+25000] xend-debug.log: Xend started at Fri Oct 28 16:11:03 2011. Exception in thread UnixHttpServer: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 552, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 505, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 312, in run (sock, addr) = self.accept() File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 331, in accept return self.socket.accept() File "/usr/lib64/python2.7/socket.py", line 202, in accept sock, addr = self._sock.accept() error: [Errno 22] Invalid argument Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xen/xend/server/Hald.py", line 55, in shutdown os.kill(self.pid, signal.SIGINT) OSError: [Errno 3] No such process Exception in thread UnixHttpServer: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 552, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 505, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 312, in run (sock, addr) = self.accept() File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 331, in accept return self.socket.accept() File "/usr/lib64/python2.7/socket.py", line 202, in accept sock, addr = self._sock.accept() error: [Errno 22] Invalid argument Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xen/xend/server/Hald.py", line 55, in shutdown os.kill(self.pid, signal.SIGINT) OSError: [Errno 3] No such process Xend started at Fri Oct 28 16:13:53 2011. Exception in thread UnixHttpServer: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 552, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 505, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 312, in run (sock, addr) = self.accept() File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 331, in accept return self.socket.accept() File "/usr/lib64/python2.7/socket.py", line 202, in accept sock, addr = self._sock.accept() error: [Errno 22] Invalid argument Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xen/xend/server/Hald.py", line 55, in shutdown os.kill(self.pid, signal.SIGINT) OSError: [Errno 3] No such process libvirtd seems also unstable, using the virtmanager fails often, it just crashes or says, that xend is not running. Reproducible: Always Steps to Reproduce: 1. start 12.1 rc with xen-kernel 2. start a domU 3. the domU is not really booting, or something from the xen-env. is crashing -- 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=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c1
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c2
--- Comment #2 from Roman Haag
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c3
--- Comment #3 from Roman Haag
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c4
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c5
--- Comment #5 from Roman Haag
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c6
--- Comment #6 from Roman Haag
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c7
--- Comment #7 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c8
--- Comment #8 from Roman Haag
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c
Roman Haag
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c9
James Oakley
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c10
--- Comment #10 from James Oakley
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c11
James Oakley
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c12
--- Comment #12 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c13
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c14
James Oakley
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c15
--- Comment #15 from Roman Haag
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c16
Martin Jakl
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c17
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c18
Martin Jakl
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c19
--- Comment #19 from Markus Bauer
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c20
Charles Arnold
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c21
--- Comment #21 from James Oakley
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c22
Olaf Hering
I just brought up a few Xeon E3-1230 boxes on 12.1, and they exhibit the same behaviour.
I can provide full access to one of them, including IPMI, if you've been unable to replicate the issue.
James, that would certainly help. So far I have been unable to reprodce it on my testsystems. Thanks! -- 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=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c23
--- Comment #23 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c24
--- Comment #24 from Martin Jakl
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c25
--- Comment #25 from Nick Couchman
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c26
--- Comment #26 from Nick Couchman
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c27
--- Comment #27 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c28
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c29
--- Comment #29 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c30
Jan Beulich
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c31
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c32
--- Comment #32 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c33
--- Comment #33 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c34
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c35
--- Comment #35 from Ralf Müller
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c36
--- Comment #36 from Olaf Hering
Does "closing as fixed" mean that there is a patch in Tumbleweed and/or 12.1 update repository for that? No. Until an update is provided, see comment #31
-- 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=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c37
--- Comment #37 from Nick Couchman
(In reply to comment #35)
Does "closing as fixed" mean that there is a patch in Tumbleweed and/or 12.1 update repository for that? No. Until an update is provided, see comment #31
Any estimate on when this update will be out? Anything that we can do to help it along? -- 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=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c38
--- Comment #38 from Roman Haag
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c39
bartounet martin
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c40
Jan Musilek
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c41
Anton Samsonov
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c42
--- Comment #42 from Nick Couchman
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c43
--- Comment #43 from Ralf Müller
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c44
--- Comment #44 from Olaf Hering
As this bug is 'resolved' nobody seems to be interested in it anymore. It doesn't seem to be important to anyone that a default installation even with all updates still breaks. So many users of openSuSE doing their first steps with xen will run into an endless search before they possibly find the above patch. Good user impression - really. Is there something wrong with the patch above or why it is not placed in the update repository?
There is nothing wrong with the patch. An update is planned, it will happen in the next few weeks.
Maybe there should be an extra state in bugzilla for 'rolled out' with an assigned maintainer. This type of problem is not new.
Some tag for "important fix pending, update required" would help the release managers, yes. -- 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=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c45
--- Comment #45 from Ralf Müller
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c46
--- Comment #46 from Nick Couchman
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c47
--- Comment #47 from Nick Couchman
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c48
--- Comment #48 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c49
--- Comment #49 from Ralf Müller
The update is already in the queue:
Congratulations. Thank you very much. PS: I don't say anything to 'already' here. SCNR to say that I don't say it ... ;) -- 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=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c50
--- Comment #50 from Ralf Müller
https://bugzilla.novell.com/show_bug.cgi?id=727081
https://bugzilla.novell.com/show_bug.cgi?id=727081#c51
--- Comment #51 from Olaf Hering
(In reply to comment #48)
Additional Question: when a bug has come so far, that it is in a maintenance repository - what is usually done with it and how long does it usually take it to enter the official update repository?
I dont have the details for that. Perhaps asking on some of the opensuse mailing lists (factory?) can clearify the process. -- 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