From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: HAL type for Win2003 Server on recent KVM versions? Date: Thu, 18 Nov 2010 12:52:35 +0200 Message-ID: <4CE50573.80601@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm To: Kenni Lund Return-path: Received: from mx1.redhat.com ([209.132.183.28]:61255 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750917Ab0KRKwm (ORCPT ); Thu, 18 Nov 2010 05:52:42 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 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