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

Re: [Xen-users] Device model failure: no longer running with HVM-Guest

To: Maik Brauer <mailinglist@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Device model failure: no longer running with HVM-Guest
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Fri, 27 Feb 2009 10:05:38 +0000
Cc: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 27 Feb 2009 02:06:22 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=DShPwmeknNLtN6Furc6AOuxEIP3LZ7vZO1q4S0Fd1jU=; b=SrGn99AMYTNkEHYCU3agpRVENu6IxfW65omPbpPNkGuNnCr45yp+ShU6shS6CNPP3S 4LUoHxwOzLqGXss5BqvdRI8n28Zp5qxZJktnChvsDHdcaAhr9kJ6q6GMQKAwMJu6lICk PBhSCumQyHtIGlt3gv4etvYojOeH2WI6Iuxqs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=WKnZSOkECo7mPCvDVOkRW6EmTUVixkMhfk4y1kxMv/uf7GeFF3+zNsXdeNDkIYdNe8 bgvKGJb0av4HuBg115S125jLDjeD8VcDIwG+PXdklfbC9ci277nuedkqgJ6gwyWpN0Zd QGlvewE2PVMjbVEAPDVPVrviUa1VSjSj+S9NI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <05D3DE9E-1703-4AB9-9858-1875C57A2AEF@xxxxxxxxxxxxxxx>
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>
References: <05D3DE9E-1703-4AB9-9858-1875C57A2AEF@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Feb 26, 2009 at 1:59 PM, Maik Brauer
<mailinglist@xxxxxxxxxxxxxxx> wrote:
> Hi,
>
> I'm using the xen-3.4-unstable version with Debian Lenny.
> Next to that I use a HVM Guest.
>
> The error message from the Xend.log is:
> 2009-02-26 14:44:15 2325] INFO (XendDomain:1180) Domain ExampleHVMDomain
> (35) unpaused.
> [2009-02-26 14:44:15 2325] INFO (XendDomainInfo:1781) Domain has shutdown:
> name=ExampleHVMDomain id=35 reason=poweroff.
> [2009-02-26 14:44:15 2325] DEBUG (XendDomainInfo:2570)
> XendDomainInfo.destroy: domid=35
> [2009-02-26 14:44:15 2325] DEBUG (XendDomainInfo:2086) Destroying device
> model
> [2009-02-26 14:44:15 2325] WARNING (image:482) domain ExampleHVMDomain:
> device model failure: no longer running; see
> /var/log/xen/qemu-dm-ExampleHVMDomain.log
> [2009-02-26 14:44:15 2325] DEBUG (XendDomainInfo:2093) Releasing devices
>
>
> What about the entry that the Device model has a problem.
> Here the qemu-log:
> domid: 35
> qemu: the number of cpus is 1
> config qemu network with xen bridge for  tap35.0 xenbr0
> Watching /local/domain/0/device-model/35/logdirty/next-active
> Watching /local/domain/0/device-model/35/command
> xs_read(): vncpasswd get error.
> /vm/bfdcfd82-4ccc-c764-0a75-936f7ab9ca66/vncpasswd.
> char device redirected to /dev/pts/3
> qemu_map_cache_init nr_buckets = 10000 size 3145728
> shared page at pfn feffd
> buffered io page at pfn feffb
> Guest uuid = bfdcfd82-4ccc-c764-0a75-936f7ab9ca66
> Time offset set 0
> populating video RAM at ff000000
> mapping video RAM from ff000000
> Register xen platform.
> Done register platform.
> xs_read(/local/domain/0/device-model/35/xen_extended_power_mgmt): read error
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> cirrus vga map change while on lfb mode
> mapping vram to f0000000 - f0400000
>
>
> It says something with xen_extended_power_mgmt
>
> Who can help me ?
>
>
> Cheers,
> Maik

You need to apply this patch to qemu

http://www.nabble.com/-PATCH--ioemu:-Fix-the-segmentation-fault-on-assigning-device-without-PM-cap.-tt22094076.html

Andy

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

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

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