KVM domain restore reboots the domain instead

Bug #1018440 reported by Chris J Arges
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Natty
Fix Released
High
Chris J Arges

Bug Description

SRU Justification:

Impact: KVM domain restore reboots the domain instead, the reported uptime is incorrect.
Fix: Upstream patch : 5233dd51ece1615d54ab96c4cbe9ac3cc595e955 fixes the issue. This patch is present in Oneiric onwards.
Testcase:
  1 Start a VM
  2 let it accumulate some uptime; maybe start a background job
  3 save or managedsave the VM and verify that it becomes "shut off"
  4 restore or start the saved VM.
  5 check uptime of VM and state of background job, if started.

The uptime of the restored VM should represent the time it was up before being saved. It shows
as being 0 since the VM gets rebooted

--

1. Description of the problem:

KVM domain restore reboots the domain instead

2. Ubuntu release, software version, Release Number and Architecture of the selected components.
Ubuntu 11.04 Natty x86_64 running latest server kernel

3. How reproducible is the problem?
Start a VM and let it accumulate time. save the VM then restore it. Uptime should be accumulated time;
it is 0 as it is rebooted.

4. Steps to reproduce
4.1 Start a VM
4.2 let it accumulate some uptime; maybe start a background job
4.3 save or managedsave the VM and verify that it becomes "shut off"
4.4 restore or start the saved VM.
4.5 check uptime of VM and state of background job, if started.

The uptime of the restored VM should represent the time it was up before being saved. It shows
as being 0 since the VM gets rebooted

5. Known Workaround:
N/A

Revision history for this message
Chris J Arges (arges) wrote :
affects: ubuntu → linux (Ubuntu)
Chris J Arges (arges)
description: updated
tags: added: patch
Chris J Arges (arges)
Changed in linux (Ubuntu Natty):
status: New → In Progress
Changed in linux (Ubuntu):
status: In Progress → Fix Released
Changed in linux (Ubuntu Natty):
importance: Undecided → High
Changed in linux (Ubuntu):
importance: High → Undecided
assignee: Chris J Arges (christopherarges) → nobody
Changed in linux (Ubuntu Natty):
assignee: nobody → Chris J Arges (christopherarges)
description: updated
Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Natty):
status: In Progress → Fix Committed
Revision history for this message
Luis Henriques (henrix) wrote :

This bug is awaiting verification that the kernel for natty in -proposed solves the problem (2.6.38-15.64). Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-natty' to 'verification-done-natty'.

If verification is not done by one week from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-natty
Revision history for this message
Luis Henriques (henrix) wrote :

Chris, any chances of taking a look at this bug? We need to have this bug verified with the current -proposed kernel. Thanks.

Revision history for this message
Chris J Arges (arges) wrote :

This has been verified in Natty.

tags: added: verification-done-natty
removed: verification-needed-natty
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 2.6.38-15.64

---------------
linux (2.6.38-15.64) natty-proposed; urgency=low

  [ Andy Whitcroft ]

  * fix ABI directory naming

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1019992

linux (2.6.38-15.63) natty-proposed; urgency=low

  [ Andy Whitcroft ]

  * No change upload to fix .ddeb generation in the PPA.

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1019992

linux (2.6.38-15.62) natty-proposed; urgency=low

  [Luis Henriques]

  * Release Tracking Bug
    - LP: #1019992

  [ Upstream Kernel Changes ]

  * tun: reserves space for network in skb
    - LP: #905219
  * KVM: VMX: do not overwrite uptodate vcpu->arch.cr3 on KVM_SET_SREGS
    - LP: #1018440
 -- Andy Whitcroft <email address hidden> Fri, 06 Jul 2012 15:49:42 +0100

Changed in linux (Ubuntu Natty):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.