From: Mogens Valentin <monz@danbbs.dk>
To: xen-devel@lists.xensource.com
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
Goetz Bock <bock@blacknet.de>,
xen-users@lists.xensource.com
Subject: Re: Re: [Xen-devel] VMX Hardware
Date: Sun, 14 Aug 2005 14:23:27 +0200 [thread overview]
Message-ID: <42FF37BF.6000504@danbbs.dk> (raw)
In-Reply-To: <8813001a9664f4ada850cb1ff23dd564@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 14 Aug 2005, at 11:44, Goetz Bock wrote:
>
>> As the VMX hardware is supposed to be out "soon" I actually wanted to
>> wait for it to hit the shelvs first.
>>
>> Looks like I can not do this. so I've a question for the informed.
>>
>> What hardware should I get now, and still be able to upgrade to VMX when
>> it's available? If possible only by getting a new CPU.
>
>
> Buying a mainboard with LGA775 socket is probably a fairly safe bet, but
> there's no guarantee that future processor generations will run on it
> even if the socket doesn't change. Compatibility might depend on the
> manufacturer creating appropriate BIOS patches, for example.
Looking at Intels latest 'upgrade' path, which shows we'll often have to
buy new HW for new cpu's, I'd go for AMD.
Seems they're into the game of longtime support, so my bet is that
you'll be able to outfit quite a lot of the latest mobos with future
AMD64 cpu's.
This has of late been the case with i.e. their X2 line. Most resent
mobos can handle those with a BIOS upgrade.
I'd be looking at Iwill, Tyan, Gigabye.
I assume by VMX, you're talking about cpu/hardware with HW-support for
virtualisation, i.e. Intels Vanderbilt Technology (VT) and AMD'
Pacifica. If so, it's clear to me that AMD will be leading, because of
it's onchip memory controller, and hence reduced needs for software
support to do the page switching, for which Intel needs quite a lot of
software to emulate.
However, I'm not sufficiently familiar with Xen on this topic (just
getting started). What I've read is that Xen won't benefit from or even
use those HW-enabled mechanisms.
Someone pls. correct me if I'm wrong here - I'd very much like to be
wrong. Would be a pity not to take advantage of such mechanisms, IMHO.
--
Kind regards,
Mogens Valentin
next prev parent reply other threads:[~2005-08-14 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 10:44 VMX Hardware Goetz Bock
2005-08-14 11:09 ` Keir Fraser
2005-08-14 12:23 ` Mogens Valentin [this message]
2005-08-14 13:27 ` [Xen-users] " Keir Fraser
2005-08-14 18:09 ` Re: [Xen-devel] " Anthony Liguori
2005-08-14 18:23 ` [Xen-users] " Keir Fraser
2005-08-16 2:36 ` David
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=42FF37BF.6000504@danbbs.dk \
--to=monz@danbbs.dk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=bock@blacknet.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.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.