Re: [libvirt] [PATCHv2 0/3] Xen: Fix handling

2012-02-14 Thread Philipp Hahn
Hello Eric, On Monday 13 February 2012 18:43:21 Eric Blake wrote: > > 2. Instead of implementing a second variant of offset='variable' it would > > be enough to just add an attribute reset='true' (or > > this_is_not_from_a_buggy_libvirt_and_I_really_need_the_reset='true') to > > dumpxml, when a dr

Re: [libvirt] [PATCHv2 0/3] Xen: Fix handling

2012-02-13 Thread Eric Blake
On 02/13/2012 03:36 AM, Philipp Hahn wrote: > Hello Eric, > > On Monday 13 February 2012 08:51:41 Philipp Hahn wrote: >> On Thursday 09 February 2012 23:01:38 Eric Blake wrote: > ... >>> But a better idea is to represent the XML in a way where the default >>> conversion makes sense, but where a us

Re: [libvirt] [PATCHv2 0/3] Xen: Fix handling

2012-02-13 Thread Philipp Hahn
Hello Eric, On Monday 13 February 2012 08:51:41 Philipp Hahn wrote: > On Thursday 09 February 2012 23:01:38 Eric Blake wrote: ... > > But a better idea is to represent the XML in a way where the default > > conversion makes sense, but where a user can explicitly change the XML > > to get what they

Re: [libvirt] [PATCHv2 0/3] Xen: Fix handling

2012-02-12 Thread Philipp Hahn
Hello Eric, On Thursday 09 February 2012 23:01:38 Eric Blake wrote: > > Questions: > > 1. Handling of legacy XML domain configurations > >I'm reluctant to define LIBVIRT_XEND_CLOCK_STRICT, since this would > > probably break many existing XML configuration files, since they would be > > rejec

Re: [libvirt] [PATCHv2 0/3] Xen: Fix handling

2012-02-09 Thread Eric Blake
On 02/09/2012 03:01 PM, Eric Blake wrote: > We absolutely cannot reject existing older xml files; but must load them > with the semantics that make sense. > > But a better idea is to represent the XML in a way where the default > conversion makes sense, but where a user can explicitly change the

Re: [libvirt] [PATCHv2 0/3] Xen: Fix handling

2012-02-09 Thread Eric Blake
On 02/09/2012 04:36 AM, Philipp Hahn wrote: > Before version 3.1 xen only implemented clock/@offset='utc' and 'localtime'. > With the introduction of managed domains in 3.1 xend keeps track of the > rtc_timeoffset, even over reboots. This translates to libvirts > clock/@offset='variable' variant.

[libvirt] [PATCHv2 0/3] Xen: Fix handling

2012-02-09 Thread Philipp Hahn
Before version 3.1 xen only implemented clock/@offset='utc' and 'localtime'. With the introduction of managed domains in 3.1 xend keeps track of the rtc_timeoffset, even over reboots. This translates to libvirts clock/@offset='variable' variant. Be advised that only HV domains have a RTC. In addi