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] problem starting full virtualized guest on SLES10

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] problem starting full virtualized guest on SLES10
From: Stefan Berner <Stefan.Berner@xxxxxxxxxxxxxxx>
Date: Mon, 19 Mar 2007 16:43:09 +0100
Delivery-date: Mon, 19 Mar 2007 08:42:35 -0700
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.10 (X11/20060911)
Hi,

I have a big problem starting a full virtualized guest on a SLES10 system.
I installed to package from
http://developer.novell.com/wiki/index.php/Special:Downloads/xenpreview/SUSE~~~Linux~~~Enterprise~~~Server/10/x86-64/Latest/SLES10-x86-64-changeset13138-15.tar.bz2
. This worked fine, but if try to start a guest i get the following message:

Error: Device 768 (vbd) could not be connected. Hotplug scripts not working

and from the xend.log

[2007-03-19 16:33:21 xend.XendDomainInfo 4202] DEBUG
(XendDomainInfo:786) Storing domain details: {'console/port': '3',
'name': 'sles10', 'console/limit': '1048576', 'vm':
'/vm/1e94be17-4c9d-0fea-4c84-2edf3e5c84b4', 'domid': '9',
'cpu/0/availability': 'online', 'memory/target': '524288',
'store/ring-ref': '131070', 'store/port': '2'}
[2007-03-19 16:33:21 xend 4202] DEBUG (DevController:524)
hotplugStatusCallback /local/domain/0/backend/vbd/9/768/hotplug-status.
[2007-03-19 16:35:01 xend.XendDomainInfo 4202] DEBUG
(XendDomainInfo:1545) XendDomainInfo.destroy: domid=9
[2007-03-19 16:35:01 xend.XendDomainInfo 4202] DEBUG
(XendDomainInfo:1553) XendDomainInfo.destroyDomain(9)
[2007-03-19 16:35:01 xend 4202] DEBUG (image:585) hvm shutdown watch
unregistered
[2007-03-19 16:35:01 xend 4202] DEBUG (image:624) hvm reboot feature
watch unregistered
[2007-03-19 16:35:15 xend 4202] DEBUG (DevController:524)
hotplugStatusCallback /local/domain/0/backend/vbd/9/768/hotplug-status.
[2007-03-19 16:35:15 xend 4202] DEBUG (DevController:538)
hotplugStatusCallback 1.
[2007-03-19 16:35:15 xend 4202] DEBUG (DevController:524)
hotplugStatusCallback /local/domain/0/backend/vbd/8/768/hotplug-status.
[2007-03-19 16:35:15 xend 4202] DEBUG (DevController:538)
hotplugStatusCallback 1.

and from xend-debug.log

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')

The first thing I though was, that I have not enough loopback device,
and I created more loopback devices, but error didn´t disappear.

Thank you very Much.

Bye

Stefan

Attachment: stefan.berner.vcf
Description: Vcard

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] problem starting full virtualized guest on SLES10, Stefan Berner <=