All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Neo Jia <neojia@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: 32-bit qemu + 64-bit kvm be a problem?
Date: Wed, 02 Jun 2010 10:52:30 +0400	[thread overview]
Message-ID: <4C05FFAE.4070209@msgid.tls.msk.ru> (raw)
In-Reply-To: <AANLkTimwbs8IGxYM2Q1_9JCPdzC0aVwBQ_xFX9IZky42@mail.gmail.com>

02.06.2010 09:44, Neo Jia wrote:
> On Wed, Mar 10, 2010 at 2:12 PM, Michael Tokarev<mjt@tls.msk.ru>  wrote:
[]
>> I use 32bit kvm on 64bit kernel since the day one.  Nothing of interest
>> since that, everything just works.

> I just came back to this thread because I am seeing that I can't run
> VISTA 64-bit inside 64/32 mode, which will crash with bugcheck 0x5D.
> Is this a known issue?

I haven't seen it myself, but I never tried vista.  Win7 64bit installs
and works just fine.  STOP 0x0000005D, according to M$, means "there is
a processor present that is not supported".  I'd say try to experiment
with different -cpu options.  Also see if it works in native 64bit mode.

>> Recently (this week) I come across a situation when something does not
>> work in 64/32 mode.  Namely it is linux aio (see the other thread in
>> kvm@ a few days back) - but this is not due to kvm but due to other
>> kernel subsystem (in this case aio) which lacks proper compat handlers
>> in place.
>
> Could you tell me more about the AIO issue? Will this will slow down
> the guest if it does a lot I/O? Will setting up coalescing help?

You can search it yourself.  In a nutshell it's an optimisation in kvm
since version 0.12  to let raw devices be used a bit more efficient.

/mjt

      reply	other threads:[~2010-06-02  6:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  9:59 32-bit qemu + 64-bit kvm be a problem? Neo Jia
2010-03-10 10:07 ` Avi Kivity
2010-03-10 21:12 ` Michael Tokarev
2010-06-02  5:44   ` Neo Jia
2010-06-02  6:52     ` Michael Tokarev [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=4C05FFAE.4070209@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=kvm@vger.kernel.org \
    --cc=neojia@gmail.com \
    /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.