WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] unable to restart a domU after it ran a long time

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] unable to restart a domU after it ran a long time
From: "Sebastian Reitenbach" <sebastia@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 09 Jan 2008 18:05:17 +0100
Delivery-date: Wed, 09 Jan 2008 09:05:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: L00 bugdead prods.
Reply-to: Sebastian Reitenbach <sebastia@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I had a domU running for some weeks, and wanted to restart it, because I 
added a new partition. xm shutdown worked well, but then a xm create hang a 
long time on the console, and in the xendebug.log file, the following pyhton 
backtrace came up:

ould not perform request !<br />Traceback (most recent call last):
  File "/usr/lib64/python2.4/SocketServer.py", line 463, in 
process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib64/python2.4/SocketServer.py", line 254, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib64/python2.4/site-packages/xen/util/xmlrpclib2.py", line 
236, in <lambda>
    (lambda x, y, z:
  File "/usr/lib64/python2.4/site-packages/xen/util/xmlrpclib2.py", line 83, 
in __init__
    server)
  File "/usr/lib64/python2.4/SocketServer.py", line 521, in __init__
    self.handle()
  File "/usr/lib64/python2.4/BaseHTTPServer.py", line 316, in handle
    self.handle_one_request()
  File "/usr/lib64/python2.4/BaseHTTPServer.py", line 310, in 
handle_one_request
    method()
  File "/usr/lib64/python2.4/site-packages/xen/util/xmlrpclib2.py", line 
100, in do_POST
    self.send_response(200)
  File "/usr/lib64/python2.4/BaseHTTPServer.py", line 367, in send_response
    self.wfile.write("%s %d %s\r\n" %
  File "/usr/lib64/python2.4/socket.py", line 256, in write
    self.flush()
  File "/usr/lib64/python2.4/socket.py", line 243, in flush
    self._sock.sendall(buffer)
error: (32, 'Broken pipe')

I had to reboot the dom0 to be able to start up the domU again. Anybody can 
tell me what happened here, and how to prevent the need to reboot dom0?

I am on SLES10SP1 x86_64
Linux ppsnfs101 2.6.16.46-0.12-xen #1 SMP Thu May 17 14:00:09 UTC 2007 
x86_64 x86_64 x86_64 GNU/Linux

kind regards
Sebastian


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] unable to restart a domU after it ran a long time, Sebastian Reitenbach <=