On Tue, 2011-09-20 at 16:55 -0300, Marcelo Tosatti wrote:
and the wall clock stays behind my host wall clock by the amount of
time it took to resume.
This is expected, similar to savevm/loadvm.
That seems like pretty undesirable behavior to me. It's too bad that it
does that with
On Wed, Sep 21, 2011 at 07:11:08AM -0700, Dave Hansen wrote:
On Tue, 2011-09-20 at 16:55 -0300, Marcelo Tosatti wrote:
and the wall clock stays behind my host wall clock by the amount of
time it took to resume.
This is expected, similar to savevm/loadvm.
That seems like pretty
On Tue, Sep 20, 2011 at 09:03:51PM +0100, Jamie Lokier wrote:
Marcelo Tosatti wrote:
In case the VM stops for whatever reason, the host system is not
supposed to adjust time related hardware state to compensate, in an
attempt to present apparent continuous time.
If you save a VM and
On Tue, 2011-09-20 at 16:55 -0300, Marcelo Tosatti wrote:
and the wall clock stays behind my host wall clock by the amount of
time it took to resume.
This is expected, similar to savevm/loadvm.
That seems like pretty undesirable behavior to me. It's too bad that it
does that with
On Wed, Sep 21, 2011 at 07:11:08AM -0700, Dave Hansen wrote:
On Tue, 2011-09-20 at 16:55 -0300, Marcelo Tosatti wrote:
and the wall clock stays behind my host wall clock by the amount of
time it took to resume.
This is expected, similar to savevm/loadvm.
That seems like pretty
On Thu, 15 Sep 2011, Marcelo Tosatti wrote:
On Tue, Sep 13, 2011 at 04:49:55PM -0400, Eric B Munson wrote:
On Fri, 09 Sep 2011, Marcelo Tosatti wrote:
On Thu, Sep 01, 2011 at 02:27:49PM -0600, emun...@mgebm.net wrote:
On Thu, 01 Sep 2011 14:24:12 -0500, Anthony Liguori wrote:
On
On Tue, Sep 20, 2011 at 03:00:54PM -0400, Eric B Munson wrote:
On Thu, 15 Sep 2011, Marcelo Tosatti wrote:
On Tue, Sep 13, 2011 at 04:49:55PM -0400, Eric B Munson wrote:
On Fri, 09 Sep 2011, Marcelo Tosatti wrote:
On Thu, Sep 01, 2011 at 02:27:49PM -0600, emun...@mgebm.net wrote:
Marcelo Tosatti wrote:
In case the VM stops for whatever reason, the host system is not
supposed to adjust time related hardware state to compensate, in an
attempt to present apparent continuous time.
If you save a VM and then restore it later, it is the guest
responsability to adjust its
On Thu, 15 Sep 2011, Marcelo Tosatti wrote:
On Tue, Sep 13, 2011 at 04:49:55PM -0400, Eric B Munson wrote:
On Fri, 09 Sep 2011, Marcelo Tosatti wrote:
On Thu, Sep 01, 2011 at 02:27:49PM -0600, emun...@mgebm.net wrote:
On Thu, 01 Sep 2011 14:24:12 -0500, Anthony Liguori wrote:
On
Marcelo Tosatti wrote:
In case the VM stops for whatever reason, the host system is not
supposed to adjust time related hardware state to compensate, in an
attempt to present apparent continuous time.
If you save a VM and then restore it later, it is the guest
responsability to adjust its
On Tue, Sep 13, 2011 at 04:49:55PM -0400, Eric B Munson wrote:
On Fri, 09 Sep 2011, Marcelo Tosatti wrote:
On Thu, Sep 01, 2011 at 02:27:49PM -0600, emun...@mgebm.net wrote:
On Thu, 01 Sep 2011 14:24:12 -0500, Anthony Liguori wrote:
On 08/30/2011 07:26 AM, Marcelo Tosatti wrote:
On
On Fri, 09 Sep 2011, Marcelo Tosatti wrote:
On Thu, Sep 01, 2011 at 02:27:49PM -0600, emun...@mgebm.net wrote:
On Thu, 01 Sep 2011 14:24:12 -0500, Anthony Liguori wrote:
On 08/30/2011 07:26 AM, Marcelo Tosatti wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
On Fri, 09 Sep 2011, Marcelo Tosatti wrote:
On Thu, Sep 01, 2011 at 02:27:49PM -0600, emun...@mgebm.net wrote:
On Thu, 01 Sep 2011 14:24:12 -0500, Anthony Liguori wrote:
On 08/30/2011 07:26 AM, Marcelo Tosatti wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
On Thu, Sep 01, 2011 at 02:27:49PM -0600, emun...@mgebm.net wrote:
On Thu, 01 Sep 2011 14:24:12 -0500, Anthony Liguori wrote:
On 08/30/2011 07:26 AM, Marcelo Tosatti wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will
On Thu, Sep 01, 2011 at 02:27:49PM -0600, emun...@mgebm.net wrote:
On Thu, 01 Sep 2011 14:24:12 -0500, Anthony Liguori wrote:
On 08/30/2011 07:26 AM, Marcelo Tosatti wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will
On 08/30/2011 07:26 AM, Marcelo Tosatti wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a soft lockup
message when it resumes. This set provides the ability for qemu to comminucate
to the guest that it has
On Thu, 01 Sep 2011 14:24:12 -0500, Anthony Liguori wrote:
On 08/30/2011 07:26 AM, Marcelo Tosatti wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a
soft lockup
message when it resumes. This set provides the
On 08/30/2011 07:26 AM, Marcelo Tosatti wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a soft lockup
message when it resumes. This set provides the ability for qemu to comminucate
to the guest that it has
On Thu, 01 Sep 2011 14:24:12 -0500, Anthony Liguori wrote:
On 08/30/2011 07:26 AM, Marcelo Tosatti wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a
soft lockup
message when it resumes. This set provides the
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a soft lockup
message when it resumes. This set provides the ability for qemu to
comminucate
to the guest that it has been stopped. When the guest hits the watchdog
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 07:35]:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a soft
lockup
message when it resumes. This set provides the ability for qemu to
comminucate
to the
On Tue, Aug 30, 2011 at 09:12:17AM -0500, Ryan Harper wrote:
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 07:35]:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a soft
lockup
message when it resumes.
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 09:40]:
On Tue, Aug 30, 2011 at 09:12:17AM -0500, Ryan Harper wrote:
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 07:35]:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that
On Tue, Aug 30, 2011 at 06:26, Marcelo Tosatti mtosa...@redhat.com wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a soft lockup
message when it resumes. This set provides the ability for qemu to
On Tue, Aug 30, 2011 at 10:37:13AM -0600, Eric B Munson wrote:
On Tue, Aug 30, 2011 at 06:26, Marcelo Tosatti mtosa...@redhat.com wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a soft
lockup
message
On Tue, Aug 30, 2011 at 09:43:19AM -0500, Ryan Harper wrote:
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 09:40]:
On Tue, Aug 30, 2011 at 09:12:17AM -0500, Ryan Harper wrote:
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 07:35]:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B
On Tue, 30 Aug 2011 15:36:13 -0300, Marcelo Tosatti wrote:
On Tue, Aug 30, 2011 at 10:37:13AM -0600, Eric B Munson wrote:
On Tue, Aug 30, 2011 at 06:26, Marcelo Tosatti mtosa...@redhat.com
wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 07:35]:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a soft
lockup
message when it resumes. This set provides the ability for qemu to
comminucate
to the
On Tue, Aug 30, 2011 at 09:12:17AM -0500, Ryan Harper wrote:
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 07:35]:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a soft
lockup
message when it resumes.
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 09:40]:
On Tue, Aug 30, 2011 at 09:12:17AM -0500, Ryan Harper wrote:
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 07:35]:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that
On Tue, Aug 30, 2011 at 06:26, Marcelo Tosatti mtosa...@redhat.com wrote:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B Munson wrote:
Currently, when qemu stops a guest kernel that guest will issue a soft lockup
message when it resumes. This set provides the ability for qemu to
On Tue, Aug 30, 2011 at 09:43:19AM -0500, Ryan Harper wrote:
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 09:40]:
On Tue, Aug 30, 2011 at 09:12:17AM -0500, Ryan Harper wrote:
* Marcelo Tosatti mtosa...@redhat.com [2011-08-30 07:35]:
On Mon, Aug 29, 2011 at 05:27:11PM -0600, Eric B
Currently, when qemu stops a guest kernel that guest will issue a soft lockup
message when it resumes. This set provides the ability for qemu to comminucate
to the guest that it has been stopped. When the guest hits the watchdog on
resume it will check if it was suspended before issuing the
33 matches
Mail list logo
