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] device model failure: no longer running;

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] device model failure: no longer running;
From: Mike Mildner <m.mildner@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 14 Feb 2009 08:11:34 +0000
Cc:
Delivery-date: Fri, 13 Feb 2009 23:13:02 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1234595491; l=6478; s=domk; d=kleiderschrank51.de; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH:DomainKey-Signature; bh=lIr2+FeeWA2B1U5uK7BtURd2IE+J92R+wmh8dA2hCRI=; b=NGmk3WyWmsvJ7ezO6tvsYma/mwnvkEFzfeQvRwR75X4XdTsa/lbnCaY73L8wvUVhL3O 5XupP7HQOA7dQHybALGp8umO5jC62Ui7ASuvwSCytEjmlAmAMoE+kMb/9ErVx+Lt3BbNg bEMHes04DjAmfYvtX6BW7lPaDL6/9P/qpUM=
Domainkey-signature: a=rsa-sha256; s=domk; d=kleiderschrank51.de; c=nofws; q=dns; h=X-RZG-AUTH:X-RZG-CLASS-ID:Date:From:MIME-Version:To:Subject: Content-Type:Content-Transfer-Encoding; b=re8OVgxEpEAsLhJa/Rev2wKs7c9HmgNYwSz5yTn/M4NqsDQ0dduvEkkyPEp3jDe3eBx H8lNydpJwPev1u7+XTHleX/D44EP6M2x1iH0M3LsgOfh+NjdLBjKlAmzBLGzCO9jIB8Ew srhjSODo4bDGWnl2M7YRtxvt5OtQ3oQ0IVg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.17 (X11/20080927)
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>