[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: Stefan Berger <stefanb@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AceQp+WjJF2d3vybEdu5fwAWy6hiGQ==
  • Thread-topic: [Xen-devel] [PATCH] [Xen-API] Patch for fixing the rtc/timeoffset entry

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.