From: Alistair John Strachan <alistair@devzero.co.uk>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc1, KVM-AMD problem
Date: Sun, 29 Jul 2007 15:10:31 +0100 [thread overview]
Message-ID: <200707291510.31731.alistair@devzero.co.uk> (raw)
In-Reply-To: <46AC9A8D.8060003@qumranet.com>
On Sunday 29 July 2007 14:47:57 you wrote:
> Alistair John Strachan wrote:
> > On Sunday 29 July 2007 12:34:28 you wrote:
> > [snip]
> >
> >>> Doesn't help, I still get the same crashes. I tried 2.6.22 again and
> >>> it's rock solid by comparison.
> >>
> >> Do you mean, kvm-33 on top of 2.6.22, or the kvm modules from 2.6.22?
> >> Please describe your configuration *exactly*.
> >
> > I'm using the kvm-33 *userspace* package (based on Debian's kvm-28
> > packaging) and 2.6.23-rc1's KVM modules. I patched 2.6.23-rc1 with the
> > patch you provided in your last email. So I'm not using -git HEAD.
> >
> > Maybe there's been additional necessary fixes to -git requiring me to
> > update to HEAD? That wasn't clear from your last email.
>
> No, that patch is the only potential fix post -rc1. There are a few
> other fixes there, but they are intended to avoid guest crashes, not
> host crashes.
>
> What guest are you running? Maybe I can reproduce it here.
Right now, Windows XP. I'm pretty sure Linux (well, Debian Etch) works fine. I
could only get Windows to install with -no-acpi, but I run it with the
following (if this is at all useful):
kvm -no-acpi -m 256 -hda $IMAGE -net nic -net tap,script=/etc/kvm/kvm-ifup
Basically, the installer seems to work fine, but Windows seemed to have
problems after installing post-SP2 updates. Maybe that's why not everybody is
seeing it yet.
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
WARNING: multiple messages have this Message-ID (diff)
From: Alistair John Strachan <alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 2.6.23-rc1, KVM-AMD problem
Date: Sun, 29 Jul 2007 15:10:31 +0100 [thread overview]
Message-ID: <200707291510.31731.alistair@devzero.co.uk> (raw)
In-Reply-To: <46AC9A8D.8060003-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Sunday 29 July 2007 14:47:57 you wrote:
> Alistair John Strachan wrote:
> > On Sunday 29 July 2007 12:34:28 you wrote:
> > [snip]
> >
> >>> Doesn't help, I still get the same crashes. I tried 2.6.22 again and
> >>> it's rock solid by comparison.
> >>
> >> Do you mean, kvm-33 on top of 2.6.22, or the kvm modules from 2.6.22?
> >> Please describe your configuration *exactly*.
> >
> > I'm using the kvm-33 *userspace* package (based on Debian's kvm-28
> > packaging) and 2.6.23-rc1's KVM modules. I patched 2.6.23-rc1 with the
> > patch you provided in your last email. So I'm not using -git HEAD.
> >
> > Maybe there's been additional necessary fixes to -git requiring me to
> > update to HEAD? That wasn't clear from your last email.
>
> No, that patch is the only potential fix post -rc1. There are a few
> other fixes there, but they are intended to avoid guest crashes, not
> host crashes.
>
> What guest are you running? Maybe I can reproduce it here.
Right now, Windows XP. I'm pretty sure Linux (well, Debian Etch) works fine. I
could only get Windows to install with -no-acpi, but I run it with the
following (if this is at all useful):
kvm -no-acpi -m 256 -hda $IMAGE -net nic -net tap,script=/etc/kvm/kvm-ifup
Basically, the installer seems to work fine, but Windows seemed to have
problems after installing post-SP2 updates. Maybe that's why not everybody is
seeing it yet.
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-07-29 14:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 17:55 2.6.23-rc1, KVM-AMD problem Alistair John Strachan
2007-07-28 17:55 ` Alistair John Strachan
2007-07-29 8:16 ` Avi Kivity
2007-07-29 8:16 ` Avi Kivity
2007-07-29 11:29 ` Alistair John Strachan
2007-07-29 11:29 ` Alistair John Strachan
2007-07-29 11:34 ` Avi Kivity
2007-07-29 11:34 ` Avi Kivity
2007-07-29 13:44 ` Alistair John Strachan
2007-07-29 13:44 ` Alistair John Strachan
2007-07-29 13:47 ` Avi Kivity
2007-07-29 13:47 ` Avi Kivity
2007-07-29 14:10 ` Alistair John Strachan [this message]
2007-07-29 14:10 ` Alistair John Strachan
2007-07-30 13:00 ` Avi Kivity
2007-07-30 13:00 ` Avi Kivity
2007-07-30 17:00 ` Alistair John Strachan
2007-07-30 17:00 ` Alistair John Strachan
2007-07-30 17:05 ` Avi Kivity
2007-07-30 17:05 ` Avi Kivity
2007-08-04 13:17 ` Prakash Punnoor
2007-08-04 13:17 ` Prakash Punnoor
2007-08-04 14:24 ` Alistair John Strachan
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=200707291510.31731.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@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 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.