From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Duck <duck@roaming.ath.cx>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM and 32-bit hosts -- still supposed to work?
Date: Wed, 01 Jul 2009 18:17:26 +0300 [thread overview]
Message-ID: <4A4B7E06.5010309@redhat.com> (raw)
In-Reply-To: <B83D08EC-5936-432A-86F7-27B7F0937428@suse.de>
On 07/01/2009 02:38 PM, Alexander Graf wrote:
>> 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.
>
> Can't you just run the tests in a 32 bit VM? :)
I'm afraid. I don't know what I'm more afraid of: that it won't work,
or that it will work.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-07-01 15:15 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
2009-07-01 11:38 ` Alexander Graf
2009-07-01 15:17 ` Avi Kivity [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=4A4B7E06.5010309@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox