From: Kasper Sandberg <lkml@metanurb.dk>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm kernel backtrace 2.6.27.3 using kvm 78 userspace
Date: Sun, 23 Nov 2008 17:16:15 +0100 [thread overview]
Message-ID: <1227456976.19624.115.camel@localhost> (raw)
In-Reply-To: <4929684A.7030704@redhat.com>
On Sun, 2008-11-23 at 16:27 +0200, Avi Kivity wrote:
> Kasper Sandberg wrote:
> >> What guest are you running?
> >>
> >
> > Yeah sorry, i was gonna include that in the mail, i apparently forgot.
> >
> > I have been running debian, both 32 and 64bit inside it, .18, .24
> > and .26 kernels, and ubuntu 8.10 .27 kernels, ATLEAST 32bit, i do not
> > remember if i have run 64bit ubuntu 8.10
> >
> > I can however give some information that _MIGHT_ (i have no clue myself)
> > be relevant
> >
> > on one of the debian guests i had xrandr crash the X server while trying
> > to change resolution, i did this a few times. Using -vga std.
> >
> > also, on the ubuntu 32bit guest, i ran qemu with debian stable, where X
> > crashed during start inside the qemu on the ubuntu guest. This happened
> > only once.
> >
> > im quite certain my ram and that is fine, no errors when doing memory
> > testing etc.
> >
> >
> > but as said, the kernel is tainted, i dont know if that affects the
> > results or not, i just wanted to inform in case this can help someone.
> > That being said, the box has NOT been rebooted since, and i can confirm
> > that kvm works excellently, i have spawned several VMs and used a tad,
> > since i wrote the mail
>
> Well, if you can find a recipe that reliably reproduces the problems, we
> want to hear of it.
Within the coming week i will try to find the time to update to latest
kernel/kvm, and then do all the things i remember doing in the VMs, to
try and reproduce
>
prev parent reply other threads:[~2008-11-23 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 20:49 kvm kernel backtrace 2.6.27.3 using kvm 78 userspace Kasper Sandberg
2008-11-23 8:49 ` Avi Kivity
2008-11-23 14:23 ` Kasper Sandberg
2008-11-23 14:27 ` Avi Kivity
2008-11-23 16:16 ` Kasper Sandberg [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=1227456976.19624.115.camel@localhost \
--to=lkml@metanurb.dk \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox