From: Steven Haigh <netwiz@crc.id.au>
To: xen-devel@lists.xen.org
Subject: Re: dom0pvh issue with XEN 4.8.0
Date: Sun, 05 Feb 2017 19:21:31 +1100 [thread overview]
Message-ID: <4052094.MzQkSSh4kS@dhcp-10-1-1-170.lan.crc.id.au> (raw)
In-Reply-To: <CAKhsbWYUfF8YbjO87=NX7gZmZTVz34oP2BNBuhJDkL6uuZCNGg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1937 bytes --]
On Sunday, 5 February 2017 4:05:32 PM AEDT 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've been down this path before - and the only thing that gave me stability
back was to disable the pvh options. I had everything from disk corruption to
what you mention with apps while trying this option.
--
Steven Haigh
Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-05 8:21 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 [this message]
2017-02-06 9:33 ` Pasi Kärkkäinen
2017-02-06 10:25 ` G.R.
2017-02-07 13:02 ` Roger Pau Monné
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=4052094.MzQkSSh4kS@dhcp-10-1-1-170.lan.crc.id.au \
--to=netwiz@crc.id.au \
--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.