From: Avi Kivity <avi@redhat.com>
To: Kenni Lund <kenni@kelu.dk>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: HAL type for Win2003 Server on recent KVM versions?
Date: Thu, 18 Nov 2010 12:52:35 +0200 [thread overview]
Message-ID: <4CE50573.80601@redhat.com> (raw)
In-Reply-To: <AANLkTikrpePk8cCQA=Ypmk2NJQWwjZ-i1s-wD3S1=a=x@mail.gmail.com>
On 11/18/2010 12:58 AM, Kenni Lund wrote:
> Hi
>
> I'm about to move a couple of virtual machines from a Fedora 11 system
> to a new server with a more recent operating system and newer version
> of KVM, etc.
>
> One of the guests is a Windows Server 2003 Standard SP2, which is
> currently running with the "ACPI Multiprocessor PC" HAL.
>
> Considering moving to RHEL, I've been reading the virtualization
> documentation for RHEL 6.0, which says that I need to set HAL to
> "Standard PC" when installing a new Win2003 guest.
>
> Since my current guest has been running perfectly fine for a long time
> with its current HAL, I was wondering if the system will become
> unstable, unbootable or what the disadvantage will be, if I move the
> guest to for example RHEL 6.0, without reinstalling or upgrading the
> guest to select another HAL mode?
>
> On the other hand, it seems like I can "upgrade" from the current
> "ACPI Multiprocessor PC" into "Standard PC", but I'm not sure if I'll
> gain anything by trying this.
>
I suggest using the default HAL, whatever it is. That's what everyone
else is using so you get the best tested configuration.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-11-18 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 22:58 HAL type for Win2003 Server on recent KVM versions? Kenni Lund
2010-11-18 10:52 ` Avi Kivity [this message]
2010-11-18 14:05 ` Kenni Lund
2010-11-18 14:46 ` Cole Robinson
2010-11-18 20:41 ` Kenni Lund
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=4CE50573.80601@redhat.com \
--to=avi@redhat.com \
--cc=kenni@kelu.dk \
--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