WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] 3.1.3 (and ??) timer_mode fix in xend for virt-i

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] 3.1.3 (and ??) timer_mode fix in xend for virt-install
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 18 Jan 2008 22:09:15 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 18 Jan 2008 14:11:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080118215927.GE25808@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchaHsMrAddAT8YSEdyX+wAWy6hiGQ==
Thread-topic: [Xen-devel] [PATCH] 3.1.3 (and ??) timer_mode fix in xend for virt-install
User-agent: Microsoft-Entourage/11.3.6.070618
On 18/1/08 21:59, "Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:

> I've not seen any problems on Xen 3.2 release with creating domains, but have
> not had any time to test the 3.1-testing tree since the 3.1.2 release came out
> so can't confirm that yet. I'll try and reproduce it - what error were you
> getting
> when trying to create a VM ?  libvirt doesn't specify any timer_mode parameter
> when creating VMs, so it should use whatever XenD's default is for that.

In Dan's patch, I don't know about the change to XendConfig.py, but the
change from ['platform'].get('timer_mode') to ['timer_mode'] doesn't look
very likely. All other HVM config parameters handed down from xm create end
up in the 'platform' dict.

Is the change to XendConfig.py to specify a default for timer_mode actually
ending up putting that default value in the wrong place: in the vmconfig as
a first-class entry in its own right, rather than as a sub-key of
'platform'?

If the problem is lack of a default value for timer_mode in some cases, I'd
rather fix XendDomainInfo.py to handle non-existent timer_mode key.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel