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-devel

Re: [Xen-devel] xen.git branch reorg

To: William Pitcock <nenolod@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen.git branch reorg
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Tue, 28 Apr 2009 08:51:49 -0700 (PDT)
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 28 Apr 2009 08:53:06 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1240933910; bh=7oWh8KDnS0fPdWckNjiMKYYbqYXjMqIolIovnDwHfg0=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=4X7OIakFSCSQeIw2k9pwJjh4KDSfnlEtfcCXqmRtFukjbaIm8l2yTQOvSo5sUGuaps1PaLfVRt4Oh4JaX00uba2HFhSnMuO1cDnJWzvBX0ZpnyUj4h7sZuAOyXgiEZfFB17d1vC7t1iXBi+nNV1I9CMCQ7jieLfgtm3qaaYCyVU=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=PDHbwQPjLnp7GYxv769Oub+st8K3ojpw9Pgq5prCrh5WWajjZWiu5tiOxMEA2IzBm93J38SWUzEeBXE/5DKhraWKspW1hMQH2rit/776bxUM842m+QbmnxBtkgvh388LBezyGtgMtTEsurovCNUD2ZSD3Q/GjIlyknMm8TbMKgw=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1240932793.10269.99.camel@petrie>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I've got a similar results

Boris

-- On Mon, 2/23/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

    From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
    Subject: Re: [Xen-devel] HVM pvops failures
    To: "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx>
    Cc: "Andrew Lyon" <andrew.lyon@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Ian Campbell" <Ian.Campbell@xxxxxxxxxx>
    Date: Monday, February 23, 2009, 7:12 PM

    Ian Jackson wrote:
    > Andrew Lyon writes ("Re: [Xen-devel] HVM guest question (was Re:
    [PATCH] ioemu: Cleanup the code of PCI passthrough.)"):
    >  
    >> On Mon, Feb 23, 2009 at 2:53 PM, Ian
     Jackson
    <Ian.Jackson@xxxxxxxxxxxxx> wrote:
    >>    
    >>> 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:
    >>    
    >
    > Ah.  This is rather odd.  Normally I would hope that xend would report
    > an exit status.  (I haven't tried pvops with qemu.)
    >
    >  
    Hm, I'm getting:
    [2009-02-23 15:26:18 4380] WARNING (image:482) domain win7: device model
    failure: pid 5409: died due to signal 7; see /var/log/xen/qemu-dm-win7.log

    Hm, signal 7 - SIGBUS.  I wonder if

    Using stub domains doesn't work either.

    > I would suggest running qemu-dm under strace.  This can be done easily
    > enough with a simple wrapper script, something like:
    >   #!/bin/sh
    >   set -e
    >   exec strace -vvs500 -f -o /root/qemu-dm.strace \
    >   
     /usr/lib/xen/bin/qemu-dm "$@"
    > and then give the name of the script as device_model in your config file.
    >  
    I see:

    ...
    5079  ioctl(10, EVIOCGKEYCODE, 0x7fffdfd52b70) = 0
    5079  clock_gettime(CLOCK_MONOTONIC, {1324, 539747423}) = 0
    5079  clock_gettime(CLOCK_MONOTONIC, {1324, 539837298}) = 0
    5079  select(14, [3 6 10 11 13], [], [], {0, 10000}) = 1 (in [10], left {0,
    9995})
    5079  read(10, "\36\0\0\0"..., 4)       = 4
    5079  write(10, "\36\0\0\0"..., 4)      = 4
    5079  ioctl(10, EVIOCGKEYCODE, 0x7fffdfd52b70) = 0
    5079  clock_gettime(CLOCK_MONOTONIC, {1324, 540495964}) = 0
    5079  clock_gettime(CLOCK_MONOTONIC, {1324, 540591278}) = 0
    5079  select(14, [3 6 10 11 13], [], [], {0, 10000}) = 1 (in [10], left {0,
    9995})
    5079  read(10, "\36\0\0\0"..., 4)       = 4
    5079  write(10, "\36\0\0\0"..., 4)      = 4
    5079  mmap(NULL, 1048576, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0) =
    0x7f1ad5f2b000
    5079
     ioctl(4, SNDCTL_DSP_STEREO, 0x7fffdfd52230) = 0
    5079  --- SIGBUS (Bus error) @ 0 (0) ---
    5157  +++ killed by SIGBUS +++


    This mmap and ioctl is from /proc/xen/privcmd.

        J

--- On Tue, 4/28/09, William Pitcock <nenolod@xxxxxxxxxxxxxxxx> wrote:
From: William Pitcock <nenolod@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen.git branch reorg
To: bderzhavets@xxxxxxxxx
Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Tuesday, April 28, 2009, 11:33 AM

Hmm.

I'll try to debug it if I have time over the weekend. It shouldn't be
very hard to do.

Do you have any specifics on what is failing?

William

On Tue, 2009-04-28 at 08:01 -0700, Boris Derzhavets wrote:
> I am talking about usual HVM DomUs.
> >the only difference is the running qemu-dm process or stub
> > domain.
>
> That's failing with current 2.6.30-rc3-tip under Xen 3.4-rc3-pre
> at least through my experience.
> Should be well known issue for Jeremy.
>
> Boris.
>
>
>
> --- On Tue, 4/28/09, William Pitcock <nenolod@xxxxxxxxxxxxxxxx>
wrote:
> From: William Pitcock <nenolod@xxxxxxxxxxxxxxxx>
> Subject: Re: [Xen-devel] xen.git branch reorg
> To: bderzhavets@xxxxxxxxx
> Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>,
"Xen-devel"
> <xen-devel@xxxxxxxxxxxxxxxxxxx>
> Date: Tuesday, April 28, 2009, 10:51 AM
>
> I think you are talking about HVM PV drivers. HVM itself is no
different
> than
> booting a paravirtualized guest as far as the dom0 kernel is
> concerned... the only difference is the running qemu-dm process or
stub
> domain.
>
> William
>
> On Tue, 2009-04-28 at 02:14 -0700, Boris Derzhavets wrote:
> > >I could pull a spare server out of the production
> > >grid for testing HVM under 2.6.30 if needed.
> >
> > As far as to my knowledge Xen 3.4-rc3-pre Dom0 &
(2.6.30-rc3-tip)
> > support only PV DomUs. HVM is still unsolved problem.
> > If i am wrong about that, please advise.
> >
> > Boris.
> >
> >
> > --- On Tue, 4/28/09, William Pitcock
<nenolod@xxxxxxxxxxxxxxxx>
> wrote:
> > From: William Pitcock
<nenolod@xxxxxxxxxxxxxxxx>
> > Subject: Re: [Xen-devel] xen.git branch reorg
> > To: "Jeremy Fitzhardinge"
<jeremy@xxxxxxxx>
> > Cc: "Xen-devel"
<xen-devel@xxxxxxxxxxxxxxxxxxx>
> > Date:
> Tuesday, April 28, 2009, 3:13 AM
> >
> > On Mon, 2009-04-27 at 16:48 -0700, Jeremy
Fitzhardinge wrote:
> > > William Pitcock
> > wrote:
> > > > Yeah, it's working here now. Thanks for
that.
> > > >
> > > > We intend to start testing the 3.4 release
candidate
> with 2.6.30
> > > > paravirt-ops dom0 in our test environment
this weekend.
> > > >
> > >
> > > OK, that'll be interesting. What's your
test
> environment?
> >
> > Paravirtualization-only nocona-based (early EM64T)
Xeon hardware,
> with
> > nodes comprising of dual 2.8ghz CPUs with 8GB of
memory, on Debian
> > testing.
> >
> > Production is presently at 3.2 with XenLinux 2.6.18
patches
> rebased
> > against 2.6.26. Production machines
> are dual opteron 2216 machines
> with
> > 8GB-16GB of RAM, with both HVM and Paravirtualized
domains.
> >
> > The test and production grids use the same storage
backend, which
> is
> > presently provided through exporting LVM volumes with
AoE and
> > cluster-lvm.
> >
> > I could pull a spare server out of the production
grid for testing
> HVM
> > under 2.6.30 if
> > needed.
> >
> > William
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >
>
>


Attachment: qemu-dm.strace.gz
Description: GNU Zip compressed data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>