Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

> I've also tried Xen 3.4 with the fix applied 
> for "pci device without power management"
Is it possible to share "How to apply this patch" ?

Boris.

--- On Sun, 2/22/09, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:

From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Subject: Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip
To: Ian.Jackson@xxxxxxxxxxxxx, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Date: Sunday, February 22, 2009, 9:20 AM

On Sat, Feb 21, 2009 at 3:53 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
wrote:
> Andrew Lyon wrote:
>>
>> I've also tried using 3.3.1 with the
 backported patches as above,
I
>> still get a device model failure error but this time there is no
>> mention of power management:
>>
>> [2009-02-21 12:32:33 3486] WARNING (image:472) domain xptest: device
>> model failure: pid 3766: malfunctioning (closed sentinel), killed; see
>> /var/log/xen/qemu-dm-xptest.log
>>
>
> IanJ would have more of an idea about this stuff than me.

I've now tried Xen 3.3.1 and 3.3.2 both with the backported patches
from xen-unstable for pv_ops dom0 support, and I've also tried Xen 3.4
with the fix applied for "pci device without power management", with
all 3 a existing VM which works under a non pv_ops Xen kernel fails to
start under pv_ops kernel, I've also tried different disk backends
(tap:io, file:/) the error is always the same:

[2009-02-22 14:07:25 3467] WARNING (image:470) domain xptest: device
model failure:
 pid 4224: 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

Andy


>
>   J
>
>>
>>  cat /var/log/xen/qemu-dm-xptest.log
>>
>> domid: 1
>> qemu: the number of cpus is 2
>> Watching /local/domain/0/device-model/1/logdirty/next-active
>> Watching
 /local/domain/0/device-model/1/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.
>> medium change watch on `hdc' (index: 1):
>> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
>> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
>>
>> Which logfiles do I need to post to investigate this problem?
>>
>> Andy
>>
>
>

_______________________________________________
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