From: Michael Tokarev <mjt@tls.msk.ru>
To: Juan Quintela <quintela@redhat.com>
Cc: Peter Lieven <pl@dlh.net>, Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Qemu-KVM Livate Migration 0.12.2 -> 0.12.3/4 broken?
Date: Mon, 17 May 2010 13:11:30 +0400 [thread overview]
Message-ID: <4BF10842.7060702@msgid.tls.msk.ru> (raw)
In-Reply-To: <m3r5laaoc5.fsf@trasno.mitica>
17.05.2010 13:07, Juan Quintela wrote:
> Michael Tokarev<mjt@tls.msk.ru> wrote:
[]
>> http://www.mail-archive.com/kvm@vger.kernel.org/msg34051.html
>> I wonder why it is not noticed before -- it's broken since 0.12...
>
> People has become rich and everybody has a 64 bit hardware :-)
Actually I don't think there's a CPU that's 32bits and has
necessary VT instructions. At least not the ones to care
about - maybe there were some models but they'e not common
and are gone long time ago.
But apparently there are quite some people who use 32bit
OS on 64bit-capable hardware, for one reason or another.
I'm doing it due to historical reasons, but at least I'm
running 64bit kernel... ;)
> Will take a look at the end of the week.
Thank you!
/mjt
next prev parent reply other threads:[~2010-05-17 9:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 10:59 [Qemu-devel] Qemu-KVM Livate Migration 0.12.2 -> 0.12.3/4 broken? Peter Lieven
2010-05-11 23:11 ` [Qemu-devel] " Juan Quintela
2010-05-12 13:42 ` Peter Lieven
2010-05-16 12:02 ` Avi Kivity
2010-05-16 14:42 ` Juan Quintela
2010-05-16 14:47 ` Avi Kivity
2010-05-16 20:04 ` Juan Quintela
2010-05-17 7:00 ` Avi Kivity
2010-05-17 8:23 ` Michael Tokarev
2010-05-17 9:07 ` Juan Quintela
2010-05-17 9:11 ` Michael Tokarev [this message]
2010-05-17 9:38 ` Alexander Graf
2010-05-16 18:03 ` Jan Kiszka
2010-05-16 20:06 ` Juan Quintela
2010-05-17 10:35 ` Jan Kiszka
2010-06-08 9:54 ` Peter Lieven
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=4BF10842.7060702@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).