From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Cc: turnkey-discuss@lists.turnkeylinux.org,
Liraz Siri <liraz@turnkeylinux.org>
Subject: Re: [Qemu-devel] Merging improvements from VirtualBox OSE into qemu?
Date: Thu, 25 Dec 2008 09:11:40 +0200 [thread overview]
Message-ID: <4953322C.2060002@redhat.com> (raw)
In-Reply-To: <20081224231849.GA1238@shareable.org>
Jamie Lokier wrote:
> Paul Brook wrote:
>
>> Any hardware that supports KVM is already 64-bit, and you're almost
>> entirely targetting obsolete hardware.
>>
>
> 32-bit hardware is still in use. My laptop is just over 2 years old,
> and there were *no* 64-bit Intel laptop CPUs available when I bought
> it (or I would have bought one).
>
> I use 32-bit KVM very often on my laptop, for OS compatibility
> testing, Windows development, BSD development, old Linux development
> and binary software packaging.
>
> (I also use QEMU, with and without KQEMU, to run older guest OSes that
> KVM does not work for.)
>
> To say 32-bit KVM-capable hardware is obsolete implies all _relevant_
> laptop users buy new ones every less than 2 years, which sounds
> ridiculous to me.
>
>
Well, your laptop won't run 64-bit guests at native speeds. The
VirtualBox hack requires 64-bit capable hardware, more than likely. It
just allows you to run a 32-bit host OS.
If you do have 64-bit capable hardware, then nothing prevents you from
running a 64-bit host OS (still capable of running 32-bit apps) or a
64-bit kernel and 32-bit userspace. The VirtualBox trick is mostly
relevant to Windows, where 32-bit is still much more popular than 64-bit.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-12-25 7:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 12:48 [Qemu-devel] Merging improvements from VirtualBox OSE into qemu? Liraz Siri
2008-12-24 13:17 ` Samuel Thibault
2008-12-24 13:26 ` Alexey Eremenko
2008-12-24 13:31 ` Alexey Eremenko
2008-12-24 13:36 ` Paul Brook
2008-12-24 14:33 ` Liraz Siri
2008-12-24 14:51 ` Jernej Simončič
2008-12-24 15:02 ` Paul Brook
2008-12-24 15:29 ` Liraz Siri
2008-12-24 15:40 ` Anthony Liguori
2008-12-24 20:52 ` Liraz Siri
2008-12-25 4:37 ` C.W. Betts
2008-12-25 4:37 ` C.W. Betts
2008-12-25 7:06 ` Avi Kivity
2008-12-25 7:07 ` Avi Kivity
2008-12-25 7:08 ` Avi Kivity
2008-12-25 14:51 ` Liraz Siri
2008-12-25 16:14 ` Avi Kivity
2008-12-24 23:18 ` Jamie Lokier
2008-12-25 7:11 ` Avi Kivity [this message]
2008-12-24 15:23 ` Anthony Liguori
2008-12-24 20:21 ` Liraz Siri
2008-12-24 20:55 ` Liraz Siri
2009-01-05 21:12 ` Frank Mehnert
2009-01-05 22:03 ` Stefan Weil
2009-01-05 23:58 ` Anthony Liguori
2009-01-06 7:41 ` Frank Mehnert
2009-01-06 15:46 ` Blue Swirl
2009-01-06 17:33 ` Anthony Liguori
2009-01-06 20:40 ` Frank Mehnert
2009-01-06 22:17 ` Jamie Lokier
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=4953322C.2060002@redhat.com \
--to=avi@redhat.com \
--cc=liraz@turnkeylinux.org \
--cc=qemu-devel@nongnu.org \
--cc=turnkey-discuss@lists.turnkeylinux.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.