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

Re: [Xen-devel] HVM guest question (was Re: [PATCH] ioemu: Cleanup the code of PCI passthrough.)


  • To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
  • Date: Mon, 23 Feb 2009 15:09:12 +0000
  • Cc:
  • Delivery-date: Mon, 23 Feb 2009 07:09:35 -0800
  • 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 :content-type:content-transfer-encoding; b=EyYTfxecLj7oAyHAUF9fF1J7ktG+lQgOpX+Y+N3iYGAsnYBCPW4gDHHvSptGfrcnUo vQlM2YXZfQnIsMTJOl/zkutCoCRYBNPFaakoBAajIdHoaWD+9WTh3yfTjai13FHsSpOi MUQ0gRWScuKpYSWX1aaEE7cT56F0Aa+8ysDJs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Mon, Feb 23, 2009 at 2:53 PM, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> Boris Derzhavets writes ("Re: [Xen-devel] Re: [PATCH] ioemu: Cleanup the code 
> of PCI passthrough."):
>>  I was under impression, that mentioned patch is supposed to support
>> loading HVM DomU (?).
>
> No, it's just code cleanup for PCI passthrough, which is for passing
> PCI devices through to guests.  If you are not doing PCI passthrough -
> ie, most ordinary HVM guests - then these changes will not affect you.
>
>>  If answer is "yes" , then my question:-
>> When http://xenbits.xensource.com/xen-unstable.hg will get this update?
>
> In this case, just now.  All changes that we make to xen-unstable,
> including the qemu-xen-unstable subsidiary tree, go through an
> automated build-and-test.  Only versions which pass the (fairly
> rudimentary) tests make it through to the main trees.
>
> The pre-testing trees (called `staging') are also available and
> published but not the `usual' case.
>
>> Looks like "make tools" is using
>> http://xenbits.xensource.com/git-http/qemu-xen-unstable.git when
>> building xen-unstable.hg/tools/ioemu-remote.
>
> Yes.  You can change this by setting the CONFIG_QEMU make variable, eg
> in a file `.config' in the xen-unstable.hg top level.
>
>> If answer is "no", i am sorry for misunderstanding.
>>
>>   Fresh Xen-Unstable Dom0 install (along with the most recent build
>> 2.6.29-rc5) still shows during attempt to start HVM DomU:-
>
> These messages are not very surprising.  Is it working ?

No, when try to start HVM on Xen unstable with pv_ops kernel I get this error:

[2009-02-22 14:01:53 3467] WARNING (image:470) domain xptest: device
model failure: pid 3735: malfunctioning (closed sentinel), killed; see
/var/log/xen/qemu-dm-xptest.log

cat /var/log/xen/qemu-dm-xptest.log

domid: 4
qemu: the number of cpus is 1
Using xvda for guest's hda
Strip off blktap sub-type prefix to /root/xp (drv 'aio')
Watching /local/domain/0/device-model/4/logdirty/next-active
Watching /local/domain/0/device-model/4/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.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

If I change the kernel to normal Xen kernel (not pv_ops) it works ok.

What can I do to debug?

Andy

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

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


 


Rackspace

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