From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Neo Jia <neojia-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: What should I do for kvm development first?
Date: Mon, 19 Nov 2007 07:49:57 +0200 [thread overview]
Message-ID: <47412405.3090102@qumranet.com> (raw)
In-Reply-To: <47409A38.50700-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Neo Jia wrote:
>>>>
>>>>> Another question is about the architecture, I found it seems that the
>>>>> 32-bit platform is much more stable than 64-bit. Should I switch my
>>>>> system to 64-bit for later work?
>>>>>
>>>>>
>>>>>
>>>> Where do you get this impression? I do almost all of my development on
>>>> 64-bit, and I don't recall an issue that was 64-bit host specific.
>>>>
>>>>
>>> Sorry about that ...
>>>
>>> because I always saw "host 64-bit" in the bug report although maybe
>>> they are not 64-bit host specific problem.
>>>
>>>
>> Yes. Most testing (and production use) is done on 64-bit hosts, since
>> virtualization is memory-intensive. Also, you can test more types of
>> guests this way. Almost all virtualization-capable processors are
>> also 64-bit capable.
>>
> So, does that mean I need to install a 64-bit host to make the reproduce
> easier?
>
A 32-bit host is fine, if you don't run 64-bit guests.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-11-19 5:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 5:46 What should I do for kvm development first? Neo Jia
[not found] ` <5d649bdb0711162146x32d4b74bicbf58c0f851b9ede-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-17 15:29 ` Dan Kenigsberg
[not found] ` <20071117152930.GA4968-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
2007-11-17 15:47 ` Izik Eidus
[not found] ` <473F0CFC.4000908-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-18 7:02 ` Neo Jia
[not found] ` <5d649bdb0711172302y4e3e8292r7ac10c89f0479b13-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-18 8:09 ` Izik Eidus
2007-11-18 10:47 ` Avi Kivity
[not found] ` <4740182E.1070208-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-18 11:00 ` Neo Jia
[not found] ` <5d649bdb0711180300p1720e15co5383337a9b5181b1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-18 11:04 ` Avi Kivity
[not found] ` <47401C4F.20508-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-18 11:15 ` Neo Jia
[not found] ` <5d649bdb0711180315u4a22c1c2kfe8f2a450aae38e0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-18 11:21 ` Avi Kivity
[not found] ` <4740202D.4070502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-18 20:02 ` Neo Jia
[not found] ` <47409A38.50700-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-11-19 5:49 ` Avi Kivity [this message]
2007-11-18 10:45 ` Avi Kivity
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=47412405.3090102@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=neojia-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.