From: "Richard W.M. Jones" <rjones@redhat.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: qemu-dm segfault installing FreeBSD 32 bit FV on a heavily loaded machine
Date: Mon, 14 May 2007 16:19:08 +0100 [thread overview]
Message-ID: <46487DEC.7080101@redhat.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --]
I'm seeing a segfault in qemu-dm when installing FreeBSD 6.2 32 bit
fullvirt on a 64 bit 4-core AMD machine. The segfault only occurs (or
at least is much more common) when the machine is heavily loaded. In
this case, doing 'make -j 4' kernel compile in the background. There
are no other domUs running.
The symptom is that while FreeBSD is downloading and installing
packages, qemu-dm segfaults with dmesg output like this:
qemu-dm[10011]: segfault at 0000000000000000 rip 0000000000000000 rsp
0000000041400c18 error 14
Xen 3.1 from xen-3.1-testing.hg which I cloned this afternoon.
Fedora 7 with all latest updates applied; in particular the
2.6.20-2925.8.fc7xen kernel.
I started a Fedora BZ entry for this here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=240009
It seems similar, but not the same as this:
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=542, but note
that I've only got one FV domain running (indeed only one domU running
at all).
Rich.
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3237 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2007-05-14 15:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46487DEC.7080101@redhat.com \
--to=rjones@redhat.com \
--cc=xen-devel@lists.xensource.com \
/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.