| Hi 
List,   beneeth some debian 
domU's I tried fedoraCore3 from xen-get...   My tests are 
sucessfull bu I can't reboot this domU. The domU seem to shutdown correctly but 
doe not start again.    xm list does not 
show my fedore domU again and an manual xm create leads to:   Error: Device 2049 
(vbd) could not be connected.File /opt/xen/domains/tta/disk.img is 
loopback-mounted through /dev/loop10,
 which is mounted in a guest 
domain,
 and so cannot be mounted now.
 
 my confg file end 
(similar to my debian configs)   on_reboot   = 'restart'
 on_crash    = 
'restart'
   and xend.log 
is:    File 
"/usr/src/xen/xen-unstable/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", 
line 971, in waitForDevices_return 
self.getDeviceController(deviceClass).waitForDevices()
 File 
"/usr/src/xen/xen-unstable/dist/install/usr/lib/python/xen/xend/server/DevController.py", 
line 135, in waitForDevices
 return map(self.waitForDevice, 
self.deviceIDs())
 File 
"/usr/src/xen/xen-unstable/dist/install/usr/lib/python/xen/xend/server/DevController.py", 
line 175, in waitForDevice
 raise VmError("Device %s (%s) 
could not be connected.\n%s" %
 VmError: Device 2049 (vbd) could not be 
connected.
 File /opt/xen/domains/tta/disk.img is loopback-mounted through 
/dev/loop10,
 which is mounted in a guest domain,
 and so cannot be mounted 
now.
 
   As I'e no idea how 
to unmount my domU file I have to reboot the entiere system what's not that 
usefull...    any idea what I 
missed / forgott?   thanx   Mathias   _______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users |