| 2012-06-27 15:10:17 |
Chris J Arges |
bug |
|
|
added bug |
| 2012-06-27 15:10:41 |
Chris J Arges |
affects |
ubuntu |
linux (Ubuntu) |
|
| 2012-06-27 15:12:23 |
Chris J Arges |
attachment added |
|
0002-KVM-VMX-do-not-overwrite-uptodate-vcpu-arch.cr3-on-K.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1018440/+attachment/3205689/+files/0002-KVM-VMX-do-not-overwrite-uptodate-vcpu-arch.cr3-on-K.patch |
|
| 2012-06-27 15:13:43 |
Chris J Arges |
attachment removed |
0002-KVM-VMX-do-not-overwrite-uptodate-vcpu-arch.cr3-on-K.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1018440/+attachment/3205689/+files/0002-KVM-VMX-do-not-overwrite-uptodate-vcpu-arch.cr3-on-K.patch |
|
|
| 2012-06-27 15:14:02 |
Chris J Arges |
attachment added |
|
0002-KVM-VMX-do-not-overwrite-uptodate-vcpu-arch.cr3-on-K.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1018440/+attachment/3205690/+files/0002-KVM-VMX-do-not-overwrite-uptodate-vcpu-arch.cr3-on-K.patch |
|
| 2012-06-27 15:46:23 |
Chris J Arges |
description |
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 |
SRU Justification:
Impact: KVM domain restore reboots the domain instead, the reported uptime is incorrect.
Fix: Upstream patch : 5233dd51ece1615d54ab96c4cbe9ac3cc595e955 fixes the issue.
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 |
|
| 2012-06-27 16:18:13 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2012-06-27 16:18:13 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Joseph Salisbury |
| 2012-06-27 16:20:54 |
Chris J Arges |
nominated for series |
|
Ubuntu Natty |
|
| 2012-06-27 16:20:54 |
Chris J Arges |
bug task added |
|
linux (Ubuntu Natty) |
|
| 2012-06-27 16:21:01 |
Chris J Arges |
linux (Ubuntu Natty): status |
New |
In Progress |
|
| 2012-06-27 16:21:32 |
Chris J Arges |
linux (Ubuntu): status |
In Progress |
Fix Released |
|
| 2012-06-27 16:21:34 |
Chris J Arges |
linux (Ubuntu Natty): importance |
Undecided |
High |
|
| 2012-06-27 16:21:36 |
Chris J Arges |
linux (Ubuntu): importance |
High |
Undecided |
|
| 2012-06-27 16:21:38 |
Chris J Arges |
linux (Ubuntu): assignee |
Chris J Arges (christopherarges) |
|
|
| 2012-06-27 16:21:41 |
Chris J Arges |
linux (Ubuntu Natty): assignee |
|
Chris J Arges (christopherarges) |
|
| 2012-06-27 16:22:01 |
Chris J Arges |
description |
SRU Justification:
Impact: KVM domain restore reboots the domain instead, the reported uptime is incorrect.
Fix: Upstream patch : 5233dd51ece1615d54ab96c4cbe9ac3cc595e955 fixes the issue.
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 |
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 |
|
| 2012-06-27 19:03:36 |
Tim Gardner |
linux (Ubuntu Natty): status |
In Progress |
Fix Committed |
|
| 2012-07-09 10:11:45 |
Luis Henriques |
tags |
patch |
patch verification-needed-natty |
|
| 2012-07-13 14:59:36 |
Chris J Arges |
tags |
patch verification-needed-natty |
patch verification-done-natty |
|
| 2012-07-16 23:12:09 |
Launchpad Janitor |
linux (Ubuntu Natty): status |
Fix Committed |
Fix Released |
|
