From: Avi Kivity <avi@redhat.com>
To: Duck <duck@roaming.ath.cx>
Cc: kvm@vger.kernel.org
Subject: Re: KVM and 32-bit hosts -- still supposed to work?
Date: Wed, 01 Jul 2009 12:05:20 +0300 [thread overview]
Message-ID: <4A4B26D0.8030904@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0907011532150.28213@mag.ta.eth>
On 07/01/2009 08:57 AM, Duck wrote:
> I'm on 32-bit Linux, kernel 2.6.27.7-smp. When I moved from kvm-83 to
> kvm-87 plus kvm-kmod-devel-87, my Linux host VMs ran fine. But my XP0
> host simply ran too slowly to be useable at all, and my Windows 7 host
> wouldn't boot -- just crashed and restarted early in the boot process.
Are you sure kvm was loaded? "too slowly" often means qemu is emulating.
Check 'info kvm' in the monitor.
> Seeing the module version "-devel-87" I tried kvm-87 with the old
> kvm-83 kernel module (I have no idea whether this is supposed to work)
> and my XP image worked better, but a task such as opening Device
> Manager (to see if any hardware has changed) took several _minutes_
> (it should take a second or so)) and still didn't work correctly.
>
> Kvm-87 with the -83 kernel module also persuaded Windows 7 to boot, to
> report "new devices installed', and thereafter to work with kvm-87
> plus kvm-kmod-devel-87. (Don't you love Windows's driver inflexibility
> :-)
>
> So I presume that this is all down to virtual hardware changes since -83.
>
> Before I rebuild my tired old XP0 image, however, and adopt kvm-87 for
> evermore, I just want to know if it's _supposed_ to work on 32-bit
> (Avi's post about the broken 32-bit compile of -87 due to no 32-bit
> test build system seemed to imply that 32-bit hosts are considered
> passe).
>
> Or should I stick with the older kvm until I upgrade my OS to 64-bit?
kvm is supported on 32-bit hosts. Unfortunately since moving to
kvm-autotest I no longer test on 32-bit, I'll try to improve the
situation there.
If someone has spare cycles and can run kvm-autotest on their hardware,
that would improve kvm quality measurably.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-01 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 5:57 KVM and 32-bit hosts -- still supposed to work? Duck
2009-07-01 9:05 ` Avi Kivity [this message]
2009-07-01 11:38 ` Alexander Graf
2009-07-01 15:17 ` Avi Kivity
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=4A4B26D0.8030904@redhat.com \
--to=avi@redhat.com \
--cc=duck@roaming.ath.cx \
--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 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.