Ovirt devel - Jun 2008 - [PATCH] Changed so ACPI is removed from both the wui appliance and the Managed Nodes

It looks like in some cases the KVM clock skew issue goes away (or it is at
least less problematic) if ACPI is removed from the guests.  So this is a
temporary fix until KVM gets fixed upstream.

Signed-off-by: Perry Myers <pmyers at redhat.com>
---
 wui-appliance/create-wui-appliance.sh |    5 +----
 1 files changed, 1 insertions(+), 4 deletions(-)

diff --git a/wui-appliance/create-wui-appliance.sh
b/wui-appliance/create-wui-appliance.sh
index 7fefba5..a9a210c 100755
--- a/wui-appliance/create-wui-appliance.sh
+++ b/wui-appliance/create-wui-appliance.sh
@@ -104,9 +104,6 @@ cat <<EOF
     <type>hvm</type>
     <boot dev='network'/>
   </os>
-  <features>
-    <acpi/>
-  </features>
   <clock offset='utc'/>
   <on_poweroff>destroy</on_poweroff>
   <on_reboot>restart</on_reboot>
@@ -190,4 +187,4 @@ virsh undefine $NAME > /dev/null 2>&1
 virt-install -n $NAME -r $RAM -f "$IMGDIR/$IMGNAME" -s $IMGSIZE --vnc
\
     --accelerate -v --os-type=linux --arch=$ARCH \
     -w network:default -w network:$BRIDGENAME \
-    $location_arg $cdrom_arg $extra_flag "$extra_arg"
+    $location_arg $cdrom_arg $extra_flag "$extra_arg" --noacpi
-- 
1.5.5.1

Perry Myers wrote:
> It looks like in some cases the KVM clock skew issue goes away (or it is at
> least less problematic) if ACPI is removed from the guests.  So this is a
> temporary fix until KVM gets fixed upstream.
Well, I'm a little hesitant because this may cause our fake nodes not to
boot,
and will almost certainly cause them to be UP only.  That being said, if we
can't control them at all, it's not much good.

ACK, assuming our fake managed nodes still boot with this change.

Chris Lalancette