[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Re: can't start domU


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Friedmund Lassmann <friedl@xxxxxx>
  • Date: Tue, 8 Nov 2005 11:43:58 +0000 (UTC)
  • Delivery-date: Tue, 08 Nov 2005 12:00:43 +0000
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Martin Frank <gotfried1 <at> gmx.de> writes:

> 
> Hi!
> 
> I have installed Xen version 3.0_7608-2.1 on my opensuse 10.0 system
> 
> everytime I try to start a domU the console stucks.
> I have no idea what the problem is or what I've done wrong.
> 
> Any help would be appreciated.
> 
> The console stucks after the output of this:
> xen:~ # xm create -c /etc/xen/win_config
> Using config file "/etc/xen/win_config".
> Started domain win
> ...
>
> Martin F.
> 

I've got the same problem with my xen-3.0_7608-2.1 SUSE 10 Dom0.
The funny thing is that running some RHEL 4 guest works fine,
while a SUSE 10 guest waits for some timeout then comes back with an error:

# xm create hamster -c
Using config file "/etc/xen/hamster".
Error: Error creating domain: Device 769 (vbd) could not be connected. Hotplug
scripts not working

(so this looks like if I have to patch the guest OS somehow?)

/var/log/localmessages says:
Nov  8 12:27:16 manxmaus logger: xen-vbd: vbd-2-769 up [backend/vbd/2/769]
Nov  8 12:29:16 manxmaus logger: xen-vbd: vbd-2-769 down [backend/vbd/2/769]

/var/log/messages says:
Nov  8 12:27:16 manxmaus logger: xen-vbd: vbd-2-769 up [backend/vbd/2/769]
Nov  8 12:27:16 manxmaus logger: /etc/xen/scripts/block: bind
/mnt/archive/suse10.img XENBUS_PATH=backend/vbd/2/769
Nov  8 12:29:16 manxmaus logger: xen-vbd: vbd-2-769 down [backend/vbd/2/769]
Nov  8 12:29:16 manxmaus logger: /etc/xen/scripts/block: unbind
XENBUS_PATH=backend/vbd/2/769
Nov  8 12:29:16 manxmaus logger: /etc/xen/scripts/block: Writing
backend/vbd/2/769/hotplug-status error to xenstore.
Nov  8 12:29:16 manxmaus logger: /etc/xen/scripts/block: xenstore-read
backend/vbd/2/769/type failed.

xend.log says:
[2005-11-08 12:27:16 xend] DEBUG (DevController:256) DevController: writing
{'virtual-device': '769', 'backend-id': '0', 'backend':
'/local/domain/0/backend/vbd/2/769'} to /local/domain/2/device/vbd/769.        
                                                               
[2005-11-08 12:27:16 xend] DEBUG
(DevController:258) DevController: writing {'domain': 'hamster', 'params':
'/mnt/archive/suse10.img', 'frontend-id': '2', 'type': 'file', 'dev': 'hda1',
'frontend': '/local/domain/2/device/vbd/769'} to 
/local/domain/0/backend/vbd/2/769.      
[2005-11-08 12:29:16 xend.XendDomainInfo] ERROR (XendDomainInfo:158) Domain
 construction failed 
Traceback (most recent call last):                                             
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 152, 
 in create vm.initDomain()                                                     
      
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1109,
 in initDomain self.createDevices()                                            
          
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1222, 
 in createDevices self.createDevice(n, c)                                      
             
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 893,
 in createDevice return
 self.getDeviceController(deviceClass).createDevice(devconfig)       
File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", line
 66, in createDevice
 raise VmError( ("Device %s (%s) could not be connected. "                  



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.