From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Derzhavets Subject: Re: Build vmlinuz-2.6.29-rc5-tip Date: Sun, 22 Feb 2009 09:13:11 -0800 (PST) Message-ID: <259762.11615.qm@web56102.mail.re3.yahoo.com> References: Reply-To: bderzhavets@yahoo.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0846398391==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andrew Lyon Cc: Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" , Ian.Jackson@eu.citrix.com List-Id: xen-devel@lists.xenproject.org --===============0846398391== Content-Type: multipart/alternative; boundary="0-790121922-1235322791=:11615" --0-790121922-1235322791=:11615 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Thank you for explanation, i would try a script (pseudo code) Check for pid of download process after start.=20 Modify script kind of bellow afterwards and start monitor in another terminal window PID_DOWNLOAD =3D XXXX while [ 1 =3D=3D 1] do var=3D`file=A0=A0 /usr/src/xen-unstable.hg/tools/ioemu-remote/hw/pass-throu= gh.c` if [ $? =3D=3D 0 ] ; then =A0kill=A0=A0 -SIGSTOP=A0 $PID_DOWNLOAD =A0exit=A0 1 fi sleep 3 done --- On Sun, 2/22/09, Andrew Lyon wrote: From: Andrew Lyon Subject: Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip To: bderzhavets@yahoo.com Cc: Ian.Jackson@eu.citrix.com, "xen-devel@lists.xensource.com" , "Jeremy Fitzhardinge" Date: Sunday, February 22, 2009, 10:19 AM On Sun, Feb 22, 2009 at 3:10 PM, Boris Derzhavets wrote: >> 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" ? Because the ioemu-remote sources do not exist until the build process downloads them I had to use a very crude method, I started the Xen build process and paused it every few seconds using ctrl+z, if tools/ioemu-remote/hw/pass-through.c exists I applied the patch, if not I resumed the process using "fg ", after a while its easy to spot when the code is downloaded. The patch was posed to the mailing list with subject "[Xen-devel] [PATCH] ioemu: Fix the segmentation fault on assigning device without PM cap.", I copied the patch content into a text file and applied with patch -p1 -i But even with the patch applied qemu-dm crashes and the VM does not start. Andy > > Boris. > > > --- On Sun, 2/22/09, Andrew Lyon wrote: > > From: Andrew Lyon > Subject: Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip > To: Ian.Jackson@eu.citrix.com, "xen-devel@lists.xensource.com" > > Cc: "Jeremy Fitzhardinge" > Date: Sunday, February 22, 2009, 9:20 AM > > On Sat, Feb 21, 2009 at 3:53 PM, Jeremy Fitzhardinge > 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 =3D 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 =3D 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@lists.xensource.com > http://lists.xensource.com/xen-devel > > =0A=0A=0A --0-790121922-1235322791=:11615 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Thank you for explanation, i would try a scri= pt (pseudo code)
Check for pid of download process after start.
Modi= fy script kind of bellow afterwards and start monitor in another
termina= l window

PID_DOWNLOAD =3D XXXX
while [ 1 =3D=3D 1]
do
var= =3D`file   /usr/src/xen-unstable.hg/tools/ioemu-remote/hw/pass-th= rough.c`
if [ $? =3D=3D 0 ] ; then
 kill   -SIGSTOP&nb= sp; $PID_DOWNLOAD
 exit  1
fi
sleep 3
done

---= On Sun, 2/22/09, Andrew Lyon <andrew.lyon@gmail.com> w= rote:
From: Andrew Lyon <andrew.lyon@gmail.c= om>
Subject: Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip
To: bder= zhavets@yahoo.com
Cc: Ian.Jackson@eu.citrix.com, "xen-devel@lists.xensou= rce.com" <xen-devel@lists.xensource.com>, "Jeremy Fitzhardinge" <jeremy@go= op.org>
Date: Sunday, February 22, 2009, 10:19 AM

On Sun,=
 Feb 22, 2009 at 3:10 PM, Boris Derzhavets <bderzhavets@yahoo.com>wrote:
>> 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" ?

Because the ioemu-remote sources do not=
 exist until the build process
downloads them I had to use a very crude =
method, I started the Xen
build process and paused it every few seconds =
using ctrl+z, if
tools/ioemu-remote/hw/pass-through.c exists I applied t=
he patch, if
not I resumed the process using "fg <enter>", after a=
 while its
easy
to spot when the code is downloaded.

The patch=
 was posed to the mailing list with subject "[Xen-devel]
[PATCH] ioemu: =
Fix the segmentation fault on assigning device without
PM cap.",
 I copied the patch content into a text file and applied with
patch -p1 =
-i <patchfile>

But even with the patch applied qemu-dm crashes=
 and the VM does not start.

Andy

>
> Boris.
><=
br>>
> --- On Sun, 2/22/09, Andrew Lyon <andrew.lyon@gmail.com&=
gt; wrote:
>
> From: Andrew Lyon <andrew.lyon@gmail.com><=
br>> Subject: Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip
> To: I=
an.Jackson@eu.citrix.com, "xen-devel@lists.xensource.com"
> <xen-d=
evel@lists.xensource.com>
> Cc: "Jeremy Fitzhardinge" <jeremy@g=
oop.org>
> Date: Sunday, February 22, 2009, 9:20 AM
>
>=
; On Sat, Feb 21, 2009 at 3:53 PM, Jeremy Fitzhardinge
<jeremy@goop.o=
rg>
> 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 managemen=
t:
>>>
>>> [2009-02-21 12:32:33 3486] WARNING (imag=
e:472) domain xptest:
device
>>> model failure: pid 3766: ma=
lfunctioning (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 X=
en 3.3.1 and 3.3.2 both with the backported patches
> from xen-unstab=
le for pv_ops dom0 support, and I've also tried Xen 3.4
> with the fi=
x applied for "pci device without power management",
with
> all 3 =
a existing VM which works under a non pv_ops Xen kernel fails to
> st=
art under pv_ops kernel, I've also tried different disk backends
> (t=
ap: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<=
br>> /var/log/xen/qemu-dm-xptest.log
>
>
> cat /var/lo=
g/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 p=
refix to /root/xp (drv 'aio')
> Watching /local/domain/0/device-model=
/4/logdirty/next-active
> Watching /local/domain/0/device-model/4/com=
mand
> qemu_map_cache_init nr_buckets =3D 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, siz=
e: 0
>
> Andy
>
>
>>
>>   J
&g=
t;>
>>>
>>>  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/de=
vice-model/1/command
>>> qemu_map_cache_init nr_buckets =3D 100=
00 size 3145728
>>> shared page at pfn 1fffe
>>> bu=
ffered io page at pfn 1fffc
>>> Time offset set 0
>>&g=
t; Register xen platform.
>>> Done register platform.
>&g=
t;> medium change watch on `hdc' (index: 1):
>>> I/O request=
 not ready: 0, ptr: 0, port: 0, data: 0, count: 0,
size: 0
>>&g=
t; I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0,
size: 0=

>>>
>>> Which logfiles do I need to post to invest=
igate this problem?
>>>
>>> Andy
>>>>>
>>
>
> _____________________________________=
__________
> Xen-devel mailing list
>
 Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel=

>
>

=0A=0A --0-790121922-1235322791=:11615-- --===============0846398391== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0846398391==--