hi xen-list,
i have installed xen-3.3.1 from source on a core2duo. the xen kernel
boot fine.
i create a file image with dd and a simple domU config file for windowsXP:
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
builder = ''hvm''
memory = 512
vcpus = 1
shadow_memory = 8
#vif = [ ''type=ioemu,bridge=xenbr0'' ]
acpi = 1
apic = 0
disk =
[''file:/root/xenXP.img,ioemu:hda,w'',''phy:/dev/hdc,ioemu:hdc,r'']
name = ''xenXPtest''
cdrom = ''/dev/hdc''
boot="d"
vnc=1
#vncviewer=1
vncpasswd=''test''
then i use ''xm create xenXP.cfg''
the windows cd start to boot (beginns to spinning in drive) but stop
immediately. )-:
also ''xm list'' shows for this time a domU but only some
seconds. is it a
problem to use a 64bit dom0 for 32bit domU? the xen install script have
only a 64bit binary from qemu-dm installed. i''m confused about the
error: domain xenXPtest: device model failure: no longer running; (see
log file below) here some parts from xend.log:
[2009-02-13 17:55:38 2952] DEBUG (XendDomainInfo:2036)
XendDomainInfo.constructDomain
[2009-02-13 17:55:38 2952] DEBUG (balloon:132) Balloon: 1132436 KiB
free; need 2048; done.
[2009-02-13 17:55:38 2952] DEBUG (XendDomain:449) Adding Domain: 2
[2009-02-13 17:55:38 2952] DEBUG (XendDomainInfo:2142)
XendDomainInfo.initDomain: 2 256
[2009-02-13 17:55:38 2952] DEBUG (image:300) Stored a VNC password for
vfb access
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: boot, val: d
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: fda, val: None
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: fdb, val: None
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: soundhw, val: None
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: localtime, val: 0
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: serial, val: None
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: std-vga, val: 0
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: isa, val: 0
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: acpi, val: 1
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: usb, val: 0
[2009-02-13 17:55:38 2952] DEBUG (image:743) args: usbdevice, val: None
[2009-02-13 17:55:38 2952] DEBUG (XendDomainInfo:2223)
_initDomain:shadow_memory=0x8, memory_static_max=0x20000000,
memory_static_min=0x0.
[2009-02-13 17:55:38 2952] DEBUG (balloon:132) Balloon: 1131144 KiB
free; need 542720; done.
[2009-02-13 17:55:38 2952] INFO (image:166) buildDomain os=hvm dom=2 vcpus=1
[2009-02-13 17:55:38 2952] DEBUG (image:795) domid = 2
[2009-02-13 17:55:38 2952] DEBUG (image:796) image =
/usr/lib/xen/boot/hvmloader
[2009-02-13 17:55:38 2952] DEBUG (image:797) store_evtchn = 2
[2009-02-13 17:55:38 2952] DEBUG (image:798) memsize = 512
[2009-02-13 17:55:38 2952] DEBUG (image:799) vcpus = 1
[2009-02-13 17:55:38 2952] DEBUG (image:800) acpi = 1
[2009-02-13 17:55:39 2952] DEBUG (image:801) apic = 0
[2009-02-13 17:55:39 2952] DEBUG (XendDomainInfo:1443)
XendDomainInfo.handleShutdownWatch
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
vif.
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
vscsi.
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
vbd.
[2009-02-13 17:55:39 2952] DEBUG (DevController:171) Waiting for 768.
[2009-02-13 17:55:39 2952] DEBUG (DevController:656)
hotplugStatusCallback /local/domain/0/backend/vbd/2/768/hotplug-status.
[2009-02-13 17:55:39 2952] DEBUG (DevController:670)
hotplugStatusCallback 1.
[2009-02-13 17:55:39 2952] DEBUG (DevController:171) Waiting for 5632.
[2009-02-13 17:55:39 2952] DEBUG (DevController:656)
hotplugStatusCallback /local/domain/0/backend/vbd/2/5632/hotplug-status.
[2009-02-13 17:55:39 2952] DEBUG (DevController:656)
hotplugStatusCallback /local/domain/0/backend/vbd/2/5632/hotplug-status.
[2009-02-13 17:55:39 2952] DEBUG (DevController:670)
hotplugStatusCallback 1.
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
irq.
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
vkbd.
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
vfb.
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
console.
[2009-02-13 17:55:39 2952] DEBUG (DevController:171) Waiting for 0.
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
pci.
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
ioports.
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
tap.
[2009-02-13 17:55:39 2952] DEBUG (DevController:166) Waiting for devices
vtpm.
[2009-02-13 17:55:39 2952] INFO (XendDomain:1174) Domain xenXPtest (2)
unpaused.
[2009-02-13 17:55:43 2952] INFO (XendDomainInfo:1634) Domain has
shutdown: name=xenXPtest id=2 reason=poweroff.
[2009-02-13 17:55:43 2952] DEBUG (XendDomainInfo:2402)
XendDomainInfo.destroy: domid=2
[2009-02-13 17:55:43 2952] DEBUG (XendDomainInfo:1939) Destroying device
model
[2009-02-13 17:55:44 2952] WARNING (image:472) domain xenXPtest: device
model failure: no longer running; see /var/log/xen/qemu-dm-xenXPtest.log
[2009-02-13 17:55:44 2952] DEBUG (XendDomainInfo:1946) Releasing devices
[2009-02-13 17:55:44 2952] DEBUG (XendDomainInfo:1959) Removing vbd/768
[2009-02-13 17:55:44 2952] DEBUG (XendDomainInfo:910)
XendDomainInfo.destroyDevice: deviceClass = None, device = vbd/768
[2009-02-13 17:55:44 2952] ERROR (XendDomainInfo:1966) Device release
failed: xenXPtest; None; vbd/768
Traceback (most recent call last):
File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 1960, in
_releaseDevices
self.destroyDevice(true_devclass, dev, False);
File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 924, in
destroyDevice
rc = self.getDeviceController(deviceClass).destroyDevice(devid, force)
File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 1981, in
getDeviceController
raise XendError("Unknown device type: %s" % name)
XendError: Unknown device type: None
[2009-02-13 17:55:44 2952] DEBUG (XendDomainInfo:1959) Removing vbd/5632
[2009-02-13 17:55:44 2952] DEBUG (XendDomainInfo:910)
XendDomainInfo.destroyDevice: deviceClass = None, device = vbd/5632
[2009-02-13 17:55:44 2952] ERROR (XendDomainInfo:1966) Device release
failed: xenXPtest; None; vbd/5632
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Mike Mildner
2009-Feb-14 10:38 UTC
Re: [Xen-users] device model failure: no longer running;
Fajar A. Nugraha schrieb:> On Sat, Feb 14, 2009 at 3:11 PM, Mike Mildner > <m.mildner@kleiderschrank51.de> wrote: > >> [2009-02-13 17:55:44 2952] WARNING (image:472) domain xenXPtest: device >> model failure: no longer running; see /var/log/xen/qemu-dm-xenXPtest.log >> > > And what does /var/log/xen/qemu-dm-xenXPtest.log say? > > you can try changing > > disk = [''file:/root/xenXP.img,ioemu:hda,w'',''phy:/dev/hdc,ioemu:hdc,r''] > > to simply > > disk = [''file:/root/xenXP.img,hda,w'',''phy:/dev/hdc,hdc:cdrom,r''] > > and remove the cdrom = ''/dev/hdc'' line >not really helpful informations from qemu-dm-xenXPtest.log: domid: 3 qemu: the number of cpus is 1 Watching /local/domain/0/device-model/3/logdirty/next-active Watching /local/domain/0/device-model/3/command qemu_map_cache_init nr_buckets = 10000 size 3145728 shared page at pfn 1fffe buffered io page at pfn 1fffc Time offset set 0 Register xen platform. Done register platform. thanks for the config simplifying ;-) thats all. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Feb-14 13:03 UTC
Re: [Xen-users] device model failure: no longer running;
On Sat, Feb 14, 2009 at 5:38 PM, Mike Mildner <m.mildner@kleiderschrank51.de> wrote:> not really helpful informations from qemu-dm-xenXPtest.log:> thanks for the config simplifying ;-) > thats all.So ... does your domU work now, or is it still failing? From [2009-02-13 17:55:44 2952] DEBUG (XendDomainInfo:910) XendDomainInfo.destroyDevice: deviceClass = None, device = vbd/768 and File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 1981, in getDeviceController raise XendError("Unknown device type: %s" % name) XendError: Unknown device type: None I assume it might be something related to incorrect disk config, which is why I suggested changing the config line. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Maybe Matching Threads
- HVM domain can not boot up with Qcow incremental image
- Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
- vhd format support failed on suse11 x86_64 sp2
- Centos 5.2 using LVM -> DRBD 0.82 -> Xen Problems
- Error creating vm xen3.4