On 11.02.2014 22:45, Eric Blake wrote:
On 02/11/2014 02:37 PM, Marcelo Tosatti wrote:
I think we may need both approaches. I too think that resume with
syncing guest time is so common use case that is deserves to be
exposed as a single operation outside the libvirt.
On the other hand, we
On Wed, Feb 12, 2014 at 02:05:11PM -0700, Eric Blake wrote:
On 02/12/2014 01:45 PM, Marcelo Tosatti wrote:
On Wed, Feb 12, 2014 at 10:22:11AM +, Daniel P. Berrange wrote:
I agree that this should be a completely separate command, not
merely a flag to the Resume API. The reason is that
On 02/13/2014 02:09 AM, Michal Privoznik wrote:
Maybe even both additions would be appropriate (a knob for automatic
libvirt syncing as well as a new API for explicit syncing outside the
events where libvirt would normally do it automatically).
I don't think we should add the on_resume/
On 13.02.2014 14:32, Eric Blake wrote:
On 02/13/2014 02:09 AM, Michal Privoznik wrote:
Maybe even both additions would be appropriate (a knob for automatic
libvirt syncing as well as a new API for explicit syncing outside the
events where libvirt would normally do it automatically).
I don't
On Thu, Feb 13, 2014 at 03:02:38PM +0100, Michal Privoznik wrote:
On 13.02.2014 14:32, Eric Blake wrote:
On 02/13/2014 02:09 AM, Michal Privoznik wrote:
Maybe even both additions would be appropriate (a knob for automatic
libvirt syncing as well as a new API for explicit syncing outside the
On Tue, Feb 11, 2014 at 11:48:58AM +0100, Michal Privoznik wrote:
On 11.02.2014 01:04, Marcelo Tosatti wrote:
On Mon, Feb 10, 2014 at 03:42:45PM -0700, Eric Blake wrote:
On 02/10/2014 03:10 PM, Marcelo Tosatti wrote:
Since QEMU commit kvmclock: clock should count only if vm is running
On Wed, Feb 12, 2014 at 10:22:11AM +, Daniel P. Berrange wrote:
I agree that this should be a completely separate command, not
merely a flag to the Resume API. The reason is that you cannot
do sensible error reporting if you overload this in one API
call. ie consider that resuming the
On Wed, Feb 12, 2014 at 06:45:28PM -0200, Marcelo Tosatti wrote:
On Wed, Feb 12, 2014 at 10:22:11AM +, Daniel P. Berrange wrote:
I agree that this should be a completely separate command, not
merely a flag to the Resume API. The reason is that you cannot
do sensible error reporting if
On 02/12/2014 01:45 PM, Marcelo Tosatti wrote:
On Wed, Feb 12, 2014 at 10:22:11AM +, Daniel P. Berrange wrote:
I agree that this should be a completely separate command, not
merely a flag to the Resume API. The reason is that you cannot
do sensible error reporting if you overload this in
On 02/12/2014 02:05 PM, Eric Blake wrote:
I'll go write a virsh alias and virt-manager patch.
A single virsh command that makes multiple API calls under the hood is
just fine - on partial failure, it can make it quite clear which of the
steps failed. I have no problem with creating a 'virsh
On 11.02.2014 01:04, Marcelo Tosatti wrote:
On Mon, Feb 10, 2014 at 03:42:45PM -0700, Eric Blake wrote:
On 02/10/2014 03:10 PM, Marcelo Tosatti wrote:
Since QEMU commit kvmclock: clock should count only if vm is running
(http://lists.gnu.org/archive/html/qemu-devel/2013-06/msg01225.html),
On Tue, Feb 11, 2014 at 11:48:58AM +0100, Michal Privoznik wrote:
On 11.02.2014 01:04, Marcelo Tosatti wrote:
On Mon, Feb 10, 2014 at 03:42:45PM -0700, Eric Blake wrote:
On 02/10/2014 03:10 PM, Marcelo Tosatti wrote:
Since QEMU commit kvmclock: clock should count only if vm is running
On 02/11/2014 02:37 PM, Marcelo Tosatti wrote:
I think we may need both approaches. I too think that resume with
syncing guest time is so common use case that is deserves to be
exposed as a single operation outside the libvirt.
On the other hand, we certainly want to expose this as a new
On Tue, Feb 11, 2014 at 02:45:28PM -0700, Eric Blake wrote:
On 02/11/2014 02:37 PM, Marcelo Tosatti wrote:
I think we may need both approaches. I too think that resume with
syncing guest time is so common use case that is deserves to be
exposed as a single operation outside the libvirt.
Since QEMU commit kvmclock: clock should count only if vm is running
(http://lists.gnu.org/archive/html/qemu-devel/2013-06/msg01225.html),
guests have their realtime clock stopped during pause.
To correct the situation, invoke guest agent to sync time from
host time.
Signed-off-by: Marcelo
On 02/10/2014 03:10 PM, Marcelo Tosatti wrote:
Since QEMU commit kvmclock: clock should count only if vm is running
(http://lists.gnu.org/archive/html/qemu-devel/2013-06/msg01225.html),
guests have their realtime clock stopped during pause.
To correct the situation, invoke guest agent to
On Mon, Feb 10, 2014 at 03:42:45PM -0700, Eric Blake wrote:
On 02/10/2014 03:10 PM, Marcelo Tosatti wrote:
Since QEMU commit kvmclock: clock should count only if vm is running
(http://lists.gnu.org/archive/html/qemu-devel/2013-06/msg01225.html),
guests have their realtime clock stopped
17 matches
Mail list logo
