All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Natalia Portillo <claunia@claunia.com>
Cc: Bug 596106 <596106@bugs.launchpad.net>,
	Andrew Cathrow <acathrow@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 596106] Re: kvm to emulate 64 bit cpu on 32 bit host
Date: Sun, 20 Jun 2010 14:46:03 +0100	[thread overview]
Message-ID: <20100620134603.GC15818@shareable.org> (raw)
In-Reply-To: <82AFD1E1-29B1-4DDF-B1F3-3B3EB98C13BB@claunia.com>

Natalia Portillo wrote:
>    You got the point wrong, I'm talking running WITH 64 bit hardware in a
>    32 bit guest.
>    This is done in Mac OS X Leopard (kernel is only 32 bit) and Mac OS X
>    Snow Leopard (using 32 bit kernel not 64 bit one) by VMWare, Parallels
>    and VirtualBox, as well as on Windows 32 bit using VMWare (dunno about
>    VBox and Parallels, VirtualPC is unable to run 64 bit guests at all
>    even on 64 bit hosts), just provided of course, the hardware is 64
>    bit.

Ah yes, Mac OS X too.

Apart from breaking userspace, the other reason people stick with
32-bit host kernels on both Windows and Macs is the 64-bit device
drivers often don't work properly, or aren't available at all.  They
continue to improve, but still aren't as mature and dependable as
32-bit drivers.

This is also true of Linux 64-bit kernels - both bugs and unavailable
third party drivers/firmware.  (But less so than the other OSes.)
So even with Linux people cannot assume dropping in a 64-bit host
kernel is always free of kernel/driver issues.

Marking this feature request "won't fix" is just a statement that KVM
developers aren't inclined to support this feature.

But there's nothing to stop an interested contributor having a go.
I'm sure if it works and the code is clean enough it will be accepted.

>    VirtualPC is unable to run 64 bit guests at all even on 64 bit
>    hosts

Are you sure?  Microsoft provides numerous downloadable 64-bit guest
Windows images, and VirtualPC is Microsoft's; they must be running on
something.

-- Jamie

  reply	other threads:[~2010-06-20 13:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3425203.2261276981549347.JavaMail.acathrow@aic-desktop.cathrow.org>
2010-06-19 21:12 ` [Qemu-devel] [Bug 596106] Re: kvm to emulate 64 bit cpu on 32 bit host Andrew Cathrow
2010-06-19 23:21   ` Natalia Portillo
2010-06-20 13:46     ` Jamie Lokier [this message]
2010-06-20 14:08       ` Natalia Portillo
2010-06-18 22:15 [Qemu-devel] [Bug 596106] [NEW] " dennyhalim.com
2010-06-18 22:53 ` [Qemu-devel] [Bug 596106] " Iggy
2010-06-20 13:21   ` Avi Kivity
2010-06-18 23:18 ` Anthony Liguori
2010-06-19 13:01 ` Natalia Portillo
2010-06-20 10:01   ` [Qemu-devel] " Paolo Bonzini
2010-06-20 13:31     ` 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=20100620134603.GC15818@shareable.org \
    --to=jamie@shareable.org \
    --cc=596106@bugs.launchpad.net \
    --cc=acathrow@redhat.com \
    --cc=claunia@claunia.com \
    --cc=qemu-devel@nongnu.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.