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/
Home Products Support Community News


Re: [Xen-devel] [PATCH] [Xen-API] Patch for fixing the rtc/timeoffset en

To: Stefan Berger <stefanb@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [Xen-API] Patch for fixing the rtc/timeoffset entry
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 07 May 2007 14:01:59 +0100
Cc: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Delivery-date: Mon, 07 May 2007 05:58:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1178376145.4294.5.camel@xxxxxxxxxxxxxxxxxxxxx>
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: AceQp+WjJF2d3vybEdu5fwAWy6hiGQ==
Thread-topic: [Xen-devel] [PATCH] [Xen-API] Patch for fixing the rtc/timeoffset entry
User-agent: Microsoft-Entourage/
On 5/5/07 15:42, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

> This patch rewrites the rtc/timeoffset entry so the VM's record can be
> retrieved with the Java xmlrpc library. If the entry is 'None' it upsets
> the xmlrpc parser. This fixes it, though maybe there's a better place in
> xend to place similar code.

Can't the second argument to vm_details.get() be changed to "0"? If not,
could you just do 'foo = vm_details.get(...) or "0"'?

 -- Keir

Xen-devel mailing list