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

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

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] [Xen-API] Patch for fixing the rtc/timeoffset entry
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Sat, 05 May 2007 10:42:25 -0400
Cc: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Delivery-date: Sat, 05 May 2007 07:00:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
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.

Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>


Attachment: rtc_platform_fix.diff
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>