All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "G.R." <firemeteor@users.sourceforge.net>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: dom0pvh issue with XEN 4.8.0
Date: Tue, 7 Feb 2017 13:02:33 +0000	[thread overview]
Message-ID: <20170207130233.rppfjxnra544zreh@dhcp-3-221.uk.xensource.com> (raw)
In-Reply-To: <CAKhsbWbotxAOvGtQPrHHdrrSGSa6nOmJdXcxgOamgt6H9woveQ@mail.gmail.com>

On Mon, Feb 06, 2017 at 06:25:57PM +0800, G.R. wrote:
> On Mon, Feb 6, 2017 at 5:33 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > Hi,
> >
> > On Sun, Feb 05, 2017 at 04:05:32PM +0800, G.R. wrote:
> >> Hi all,
> >> dom0pvh=1 is not working well for me with XEN 4.8.0 + linux kernel 4.9.2.
> >>
> >> The system boots with no obvious issue.
> >> But many user mode application are suffering from segfault, which
> >> makes the dom0 not useable: The segfault always come from libc-2.24.so
> >> while it works just fine in PV dom0.
> >> I have no idea why, but those segfault would kill my ssh connection
> >> while sshd is not showing up in the victim list.
> >>
> >> Some examples:
> >> Feb  5 14:25:28 gaia kernel: [  123.446346] getty[3044]: segfault at 0
> >> ip 00007f5e769e6c60 sp 00007ffc57bc0a98 error 6 in
> >> libc-2.24.so[7f5e769b7000+195000]
> >> Feb  5 14:29:04 gaia kernel: [  339.671742] grep[4195]: segfault at 0
> >> ip 00007f5d3b95ac60 sp 00007ffcc1620bb8 error 6 in
> >> libc-2.24.so[7f5d3b92b000+195000]
> >> Feb  5 14:29:23 gaia kernel: [  358.495888] tail[4203]: segfault at 0
> >> ip 00007f751314bc60 sp 00007fffe5ce5e48 error 6 in
> >> libc-2.24.so[7f751311c000+195000]
> >> Feb  5 14:35:06 gaia kernel: [  701.314247] bash[4323]: segfault at 0
> >> ip 00007f3fef30ec60 sp 00007ffd48cc2058 error 6 in
> >> libc-2.24.so[7f3fef2df000+195000]
> >> Feb  5 14:48:43 gaia kernel: [ 1518.809924] ls[4910]: segfault at 0 ip
> >> 00007f29e9bc1c60 sp 00007ffd712752b8 error 6 in
> >> libc-2.24.so[7f29e9b92000+195000]
> >>
> >> Any suggestion on how to get this fixed?
> >> I don't think I can do live debug since the userspace is quite unstable.
> >> On the other hand, dmesg from both dom0 && XEN looks just fine.
> >>
> >> PS: I'm using a custom compiled dom0 kernel. Is there any specific
> >> kernel config is required to get dom0pvh=1 work?
> >>
> >
> > I think the plan is to replace/rewrite the PVH (dom0) support with PVHv2,
> > see Roger's recent series here on xen-devel mailinglist..
> >
> 
> Thanks for all your input.
> Just had another check on the feature sheet, really didn't notice that
> PVH is still an 'preview' feature.
> Had the wrong impression since the feature had been announced for 2~3
> years anyway.
> Will avoid this for the moment.

Hello,

Yes, it's best to avoid it for the time being, but I'm still concerned by this.
The classic PVH mode is used by FreeBSD, and I have never received any reports
of SEGFAULTs in user-space applications, so it looks like an issue on the Linux
kernel and not Xen itself.

Roger.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2017-02-07 13:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05  8:05 dom0pvh issue with XEN 4.8.0 G.R.
2017-02-05  8:21 ` Steven Haigh
2017-02-06  9:33 ` Pasi Kärkkäinen
2017-02-06 10:25   ` G.R.
2017-02-07 13:02     ` Roger Pau Monné [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170207130233.rppfjxnra544zreh@dhcp-3-221.uk.xensource.com \
    --to=roger.pau@citrix.com \
    --cc=firemeteor@users.sourceforge.net \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.