* [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
@ 2013-04-30 8:07 Maxim Loparev
2013-04-30 10:04 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
` (23 more replies)
0 siblings, 24 replies; 30+ messages in thread
From: Maxim Loparev @ 2013-04-30 8:07 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i resuming
my host machine, because qemu process starts to take CPU cycles and OS
inside VM is very slow and sluggish. However it's still controllable and
could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
New
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
@ 2013-04-30 10:04 ` Maxim Loparev
2013-04-30 12:54 ` [Qemu-devel] [Bug 1174654] [NEW] " Serge Hallyn
` (22 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Maxim Loparev @ 2013-04-30 10:04 UTC (permalink / raw)
To: qemu-devel
core i3-2120 with kvm accel used on host.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
New
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
2013-04-30 10:04 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
@ 2013-04-30 12:54 ` Serge Hallyn
2013-04-30 13:32 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
` (21 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Serge Hallyn @ 2013-04-30 12:54 UTC (permalink / raw)
To: qemu-devel
Thanks for reporting this bug. I won't be able to test this for another
week or two (waiting on a license). Would it be possible for you to
test with the latest upstream git?
sudo apt-get install git
git clone git://git.qemu.org/qemu.git
cd qemu
./configure x86_64-softmmu
make
cd x86_64-softmmu
sudo mv /usr/bin/qemu-system-x86 /usr/bin/qemu-system-x86.orig
sudo cp x86_64-softmmu /usr/bin/
Then re-test your guest.
If that's not possible then please let us know.
importance: high
status: incomplete
** Changed in: qemu
Importance: Undecided => High
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Incomplete
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
2013-04-30 10:04 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
2013-04-30 12:54 ` [Qemu-devel] [Bug 1174654] [NEW] " Serge Hallyn
@ 2013-04-30 13:32 ` Maxim Loparev
2013-04-30 13:52 ` Serge Hallyn
2013-04-30 13:42 ` Maxim Loparev
` (20 subsequent siblings)
23 siblings, 1 reply; 30+ messages in thread
From: Maxim Loparev @ 2013-04-30 13:32 UTC (permalink / raw)
To: qemu-devel
at least on the clone of
git remote -v
origin http://repo.or.cz/r/qemu.git (fetch)
origin http://repo.or.cz/r/qemu.git (push)
i got
./configure x86_64-softmmu
ERROR: unknown option x86_64-softmmu
I can't clone the repo over git protocol as i'm behind the proxy.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Incomplete
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (2 preceding siblings ...)
2013-04-30 13:32 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
@ 2013-04-30 13:42 ` Maxim Loparev
2013-04-30 14:20 ` Maxim Loparev
` (19 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Maxim Loparev @ 2013-04-30 13:42 UTC (permalink / raw)
To: qemu-devel
Ok, found the corrent link for the main repo
http://git.qemu.org/git/qemu.git, but ./configure still doesn't
recognize this option.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Incomplete
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 13:32 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
@ 2013-04-30 13:52 ` Serge Hallyn
0 siblings, 0 replies; 30+ messages in thread
From: Serge Hallyn @ 2013-04-30 13:52 UTC (permalink / raw)
To: qemu-devel
Quoting Maxim Loparev (laplandersan@gmail.com):
> at least on the clone of
> git remote -v
> origin http://repo.or.cz/r/qemu.git (fetch)
> origin http://repo.or.cz/r/qemu.git (push)
> i got
> ./configure x86_64-softmmu
> ERROR: unknown option x86_64-softmmu
Sorry! That was supposed to read
./configure --target-list="x86_64-softmmu"
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Incomplete
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (3 preceding siblings ...)
2013-04-30 13:42 ` Maxim Loparev
@ 2013-04-30 14:20 ` Maxim Loparev
2013-04-30 14:41 ` Serge Hallyn
` (18 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Maxim Loparev @ 2013-04-30 14:20 UTC (permalink / raw)
To: qemu-devel
Same issue after resume with this -softmmu VM.
At start it also has the new message
qemu-system-x86_64: pci_add_option_rom: failed to find romfile "efi-e1000.rom"
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Incomplete
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (4 preceding siblings ...)
2013-04-30 14:20 ` Maxim Loparev
@ 2013-04-30 14:41 ` Serge Hallyn
2013-04-30 14:50 ` Serge Hallyn
` (17 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Serge Hallyn @ 2013-04-30 14:41 UTC (permalink / raw)
To: qemu-devel
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Confirmed
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (5 preceding siblings ...)
2013-04-30 14:41 ` Serge Hallyn
@ 2013-04-30 14:50 ` Serge Hallyn
2013-05-08 9:11 ` Maxim Loparev
` (16 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Serge Hallyn @ 2013-04-30 14:50 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Changed in: qemu
Status: Incomplete => Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Tags added: windows windows-xp
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Confirmed
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (6 preceding siblings ...)
2013-04-30 14:50 ` Serge Hallyn
@ 2013-05-08 9:11 ` Maxim Loparev
2013-05-08 15:25 ` Serge Hallyn
2013-05-08 19:01 ` John Basila
` (15 subsequent siblings)
23 siblings, 1 reply; 30+ messages in thread
From: Maxim Loparev @ 2013-05-08 9:11 UTC (permalink / raw)
To: qemu-devel
The issue mostly gone after cold reboot via suspend to disk. I managed to reproduce it only once after reboot and it grubs CPU for only minute or two while i checking it and than returned to normal CPU usage. I've checked both distribution and the trunk version.
So suspend this bug until someone can stably reproduce it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Confirmed
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-05-08 9:11 ` Maxim Loparev
@ 2013-05-08 15:25 ` Serge Hallyn
0 siblings, 0 replies; 30+ messages in thread
From: Serge Hallyn @ 2013-05-08 15:25 UTC (permalink / raw)
To: qemu-devel
Quoting Maxim Loparev (laplandersan@gmail.com):
> The issue mostly gone after cold reboot via suspend to disk. I managed to reproduce it only once after reboot and it grubs CPU for only minute or two while i checking it and than returned to normal CPU usage. I've checked both distribution and the trunk version.
> So suspend this bug until someone can stably reproduce it.
Thanks, I'll mark it invalid (meaning "can't reproduce it to get more
information") for now, please do re-open if anyone can reproduce.
status: invalid
** Changed in: qemu (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (7 preceding siblings ...)
2013-05-08 9:11 ` Maxim Loparev
@ 2013-05-08 19:01 ` John Basila
2013-07-31 13:34 ` Richard Jones
` (14 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: John Basila @ 2013-05-08 19:01 UTC (permalink / raw)
To: qemu-devel
I don't know if this will help, but I had a similar problem.
When creating a snapshot image of an XP machine, all works just fine
when loading it. As time passes on the host the loadvm start to become
very slow.
To reproduce:
1. Create a snapshot image (savevm)
2. leave QEMU
3. move the *HOST* clock one month in the future
4. Start QEMU with -loadvm
It turns out that the "-rtc clock=vm" made this disappear. When using
the default caused the problem.
John
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stucked on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (8 preceding siblings ...)
2013-05-08 19:01 ` John Basila
@ 2013-07-31 13:34 ` Richard Jones
2013-10-12 9:06 ` tobias
` (13 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Richard Jones @ 2013-07-31 13:34 UTC (permalink / raw)
To: qemu-devel
** Description changed:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i resuming
my host machine, because qemu process starts to take CPU cycles and OS
inside VM is very slow and sluggish. However it's still controllable and
could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
- stucked on some single process.
+ stuck on some single process.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (9 preceding siblings ...)
2013-07-31 13:34 ` Richard Jones
@ 2013-10-12 9:06 ` tobias
2013-10-13 13:14 ` Paolo Bonzini
` (12 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: tobias @ 2013-10-12 9:06 UTC (permalink / raw)
To: qemu-devel
Hi,
I am also encountering the bug of high cpu usage for a windows guest after suspend resume of my ubuntu host. Problem was in 13.04 but it's also still there in 13.10.
The windows guest has virtio / spice enabled.
Linux guests do not get the high cpu usage.
Are there any more logs required or is investigation going on upstream ?
I am not sure where to look or curious whether there are other workarounds.
** Attachment added: "win7.xml"
https://bugs.launchpad.net/qemu/+bug/1174654/+attachment/3875634/+files/win7.xml
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (10 preceding siblings ...)
2013-10-12 9:06 ` tobias
@ 2013-10-13 13:14 ` Paolo Bonzini
2013-10-17 20:29 ` tobias
` (11 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Paolo Bonzini @ 2013-10-13 13:14 UTC (permalink / raw)
To: qemu-devel
Please try "-global mc146818rtc.lost_tick_policy=slew".
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (11 preceding siblings ...)
2013-10-13 13:14 ` Paolo Bonzini
@ 2013-10-17 20:29 ` tobias
2013-10-18 2:33 ` mike
2013-10-18 7:41 ` tobias
` (10 subsequent siblings)
23 siblings, 1 reply; 30+ messages in thread
From: tobias @ 2013-10-17 20:29 UTC (permalink / raw)
To: qemu-devel
hi,
tried your option but it does not help. (cpu usage is still high)
below my command line syntax:
qemu-system-x86_64 -global mc146818rtc.lost_tick_policy=slew -machine accel=kvm:tcg -name win7 -S -machine pc-i440fx-1.4,accel=kvm,usb=off -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 813f5806-64ec-3319-452a-5e1834e753c9 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x8 -drive file=/data/vmware/win7.img,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -device usb-tablet,id=input0 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -vga std
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-10-17 20:29 ` tobias
@ 2013-10-18 2:33 ` mike
2013-10-18 7:12 ` tobias appelo
0 siblings, 1 reply; 30+ messages in thread
From: mike @ 2013-10-18 2:33 UTC (permalink / raw)
To: Bug 1174654; +Cc: tobias, qemu-devel
On 10/18/2013 04:29 AM, tobias wrote:
> hi,
>
> tried your option but it does not help. (cpu usage is still high)
> below my command line syntax:
> qemu-system-x86_64 -global mc146818rtc.lost_tick_policy=slew -machine accel=kvm:tcg -name win7 -S -machine pc-i440fx-1.4,accel=kvm,usb=off -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 813f5806-64ec-3319-452a-5e1834e753c9 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x8 -drive file=/data/vmware/win7.img,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -device usb-tablet,id=input0 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -vga std
Hi, have you enable the kernel CPU idle driver? especially the guest
kernel.
Thanks
Mike
>
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-10-18 2:33 ` mike
@ 2013-10-18 7:12 ` tobias appelo
2013-10-18 7:26 ` mike
0 siblings, 1 reply; 30+ messages in thread
From: tobias appelo @ 2013-10-18 7:12 UTC (permalink / raw)
To: mike, Bug 1174654; +Cc: qemu-devel
Hello Mike,
Thanks a lot for getting back on this.
Is the "cpu idle driver" a command line option I need to specify for
qemu (the -cpu option ?)
I could not find a reference to "idle" in the man page.
regards,
Tobias.
On 18-10-13 04:33, mike wrote:
> On 10/18/2013 04:29 AM, tobias wrote:
>> hi,
>>
>> tried your option but it does not help. (cpu usage is still high)
>> below my command line syntax:
>> qemu-system-x86_64 -global mc146818rtc.lost_tick_policy=slew -machine
>> accel=kvm:tcg -name win7 -S -machine pc-i440fx-1.4,accel=kvm,usb=off
>> -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
>> 813f5806-64ec-3319-452a-5e1834e753c9 -no-user-config -nodefaults
>> -chardev
>> socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7.monitor,server,nowait
>> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
>> -no-shutdown -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7
>> -device
>> ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5
>> -device
>> ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1
>> -device
>> ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2
>> -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x8 -drive
>> file=/data/vmware/win7.img,if=none,id=drive-virtio-disk0,format=qcow2
>> -device
>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
>> -device usb-tablet,id=input0 -device
>> intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
>> hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
>> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -vga std
> Hi, have you enable the kernel CPU idle driver? especially the guest
> kernel.
>
> Thanks
> Mike
>>
>
>
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-10-18 7:12 ` tobias appelo
@ 2013-10-18 7:26 ` mike
0 siblings, 0 replies; 30+ messages in thread
From: mike @ 2013-10-18 7:26 UTC (permalink / raw)
To: Bug 1174654; +Cc: tobias, qemu-devel
On 10/18/2013 03:12 PM, tobias wrote:
> Hello Mike,
>
> Thanks a lot for getting back on this.
> Is the "cpu idle driver" a command line option I need to specify for
> qemu (the -cpu option ?)
> I could not find a reference to "idle" in the man page.
You need to check the guest kernel config file.
Thanks
Mike
> regards,
>
> Tobias.
>
> On 18-10-13 04:33, mike wrote:
>> On 10/18/2013 04:29 AM, tobias wrote:
>>> hi,
>>>
>>> tried your option but it does not help. (cpu usage is still high)
>>> below my command line syntax:
>>> qemu-system-x86_64 -global mc146818rtc.lost_tick_policy=slew -machine
>>> accel=kvm:tcg -name win7 -S -machine pc-i440fx-1.4,accel=kvm,usb=off
>>> -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
>>> 813f5806-64ec-3319-452a-5e1834e753c9 -no-user-config -nodefaults
>>> -chardev
>>> socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7.monitor,server,nowait
>>> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
>>> -no-shutdown -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7
>>> -device
>>> ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5
>>> -device
>>> ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1
>>> -device
>>> ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2
>>> -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x8 -drive
>>> file=/data/vmware/win7.img,if=none,id=drive-virtio-disk0,format=qcow2
>>> -device
>>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
>>> -device usb-tablet,id=input0 -device
>>> intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
>>> hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
>>> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -vga std
>> Hi, have you enable the kernel CPU idle driver? especially the guest
>> kernel.
>>
>> Thanks
>> Mike
>>
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (12 preceding siblings ...)
2013-10-17 20:29 ` tobias
@ 2013-10-18 7:41 ` tobias
2013-10-18 8:31 ` tobias
` (9 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: tobias @ 2013-10-18 7:41 UTC (permalink / raw)
To: qemu-devel
Hello MIke,
but this concerns a windows guest. you mean a kernel configuration
within the guest (aka recompile ?) or a boot parameter within the guest ?
regards,
Tobias.
On 18-10-13 09:26, mike wrote:
> On 10/18/2013 03:12 PM, tobias wrote:
>> Hello Mike,
>>
>> Thanks a lot for getting back on this.
>> Is the "cpu idle driver" a command line option I need to specify for
>> qemu (the -cpu option ?)
>> I could not find a reference to "idle" in the man page.
> You need to check the guest kernel config file.
>
> Thanks
> Mike
>> regards,
>>
>> Tobias.
>>
>> On 18-10-13 04:33, mike wrote:
>>> On 10/18/2013 04:29 AM, tobias wrote:
>>>> hi,
>>>>
>>>> tried your option but it does not help. (cpu usage is still high)
>>>> below my command line syntax:
>>>> qemu-system-x86_64 -global mc146818rtc.lost_tick_policy=slew -machine
>>>> accel=kvm:tcg -name win7 -S -machine pc-i440fx-1.4,accel=kvm,usb=off
>>>> -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
>>>> 813f5806-64ec-3319-452a-5e1834e753c9 -no-user-config -nodefaults
>>>> -chardev
>>>> socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7.monitor,server,nowait
>>>>
>>>> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
>>>> -no-shutdown -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7
>>>> -device
>>>> ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5
>>>>
>>>> -device
>>>> ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1
>>>> -device
>>>> ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2
>>>> -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x8 -drive
>>>> file=/data/vmware/win7.img,if=none,id=drive-virtio-disk0,format=qcow2
>>>> -device
>>>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
>>>>
>>>> -device usb-tablet,id=input0 -device
>>>> intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
>>>> hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
>>>> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -vga std
>>> Hi, have you enable the kernel CPU idle driver? especially the guest
>>> kernel.
>>>
>>> Thanks
>>> Mike
>>>
>
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (13 preceding siblings ...)
2013-10-18 7:41 ` tobias
@ 2013-10-18 8:31 ` tobias
2013-10-30 21:54 ` tobias
` (8 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: tobias @ 2013-10-18 8:31 UTC (permalink / raw)
To: qemu-devel
Hi,
ok confusion cleared :-)
actually i only have this issue with windows guests. linux guests do not
show a high cpu usage after suspend resume.
so are there any recommendations you would have to work around it ?
regards,
Tobias.
On 18-10-13 09:42, mike wrote:
> On 10/18/2013 03:41 PM, tobias appelo wrote:
>> Hello MIke,
>>
>> but this concerns a windows guest. you mean a kernel configuration
>> within the guest (aka recompile ?) or a boot parameter within the
>> guest ?
>>
> Oh, sorry, I assume it is linux guest :)
>
> for windows, I have no idea of it :)
>
> Thanks
> Mike
>> regards,
>>
>> Tobias.
>>
>> On 18-10-13 09:26, mike wrote:
>>> On 10/18/2013 03:12 PM, tobias wrote:
>>>> Hello Mike,
>>>>
>>>> Thanks a lot for getting back on this.
>>>> Is the "cpu idle driver" a command line option I need to specify for
>>>> qemu (the -cpu option ?)
>>>> I could not find a reference to "idle" in the man page.
>>> You need to check the guest kernel config file.
>>>
>>> Thanks
>>> Mike
>>>> regards,
>>>>
>>>> Tobias.
>>>>
>>>> On 18-10-13 04:33, mike wrote:
>>>>> On 10/18/2013 04:29 AM, tobias wrote:
>>>>>> hi,
>>>>>>
>>>>>> tried your option but it does not help. (cpu usage is still high)
>>>>>> below my command line syntax:
>>>>>> qemu-system-x86_64 -global mc146818rtc.lost_tick_policy=slew
>>>>>> -machine
>>>>>> accel=kvm:tcg -name win7 -S -machine pc-i440fx-1.4,accel=kvm,usb=off
>>>>>> -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
>>>>>> 813f5806-64ec-3319-452a-5e1834e753c9 -no-user-config -nodefaults
>>>>>> -chardev
>>>>>> socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7.monitor,server,nowait
>>>>>>
>>>>>> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
>>>>>> -no-shutdown -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7
>>>>>> -device
>>>>>> ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5
>>>>>>
>>>>>> -device
>>>>>> ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1
>>>>>> -device
>>>>>> ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2
>>>>>> -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x8
>>>>>> -drive
>>>>>> file=/data/vmware/win7.img,if=none,id=drive-virtio-disk0,format=qcow2
>>>>>>
>>>>>> -device
>>>>>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
>>>>>>
>>>>>> -device usb-tablet,id=input0 -device
>>>>>> intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
>>>>>> hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
>>>>>> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -vga std
>>>>> Hi, have you enable the kernel CPU idle driver? especially the guest
>>>>> kernel.
>>>>>
>>>>> Thanks
>>>>> Mike
>>>>>
>>>
>>
>
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (14 preceding siblings ...)
2013-10-18 8:31 ` tobias
@ 2013-10-30 21:54 ` tobias
2014-02-04 7:15 ` Matt Keith
` (7 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: tobias @ 2013-10-30 21:54 UTC (permalink / raw)
To: qemu-devel
Did some testing: if one pauses the vms that run windows before suspending ubuntu no high cpu usage is there once the host and windows vms are resumed.
for me it's workable then in ubuntu by using a suspend / resume script with power manaager. I put this in /etc/pm/sleep.d (and make it executable) :
#!/bin/bash
PS_VM=/var/run/paused_vms
is_there_virsh () {
if [[ -z `which virsh` ]]
then echo "no actions for suspend or resume required"
exit 0
fi
}
case "$1" in
suspend)
is_there_virsh
echo "" > /var/run/paused_vms
for i in $(virsh list --state-running | grep running | awk {'print $2'})
do echo $i >> /var/run/paused_vms
virsh suspend $i
done
;;
resume)
is_there_virsh
for i in $(cat $PS_VM)
do virsh resume $i
done
# optionally remove the file but this seems not required?
rm $PS_VM
;;
*)
;;
esac
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (15 preceding siblings ...)
2013-10-30 21:54 ` tobias
@ 2014-02-04 7:15 ` Matt Keith
2015-07-20 2:59 ` derek
` (6 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Matt Keith @ 2014-02-04 7:15 UTC (permalink / raw)
To: qemu-devel
Thanks for posting your script Tobias, I'm having the same problem on
Fedora 20 and the script alleviates the symptom.
Matt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in “qemu” package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (16 preceding siblings ...)
2014-02-04 7:15 ` Matt Keith
@ 2015-07-20 2:59 ` derek
2015-12-18 22:10 ` varacanero
` (5 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: derek @ 2015-07-20 2:59 UTC (permalink / raw)
To: qemu-devel
I am running Ubuntu Wily (the 20150717 daily build) can reproduce this
problem, whatever the guest is Linux or Windows, after host got resumed
from suspend, the kvm (qemu-system-x86_64) process becomes a 100% cpu
usage,
user@ubuntu-mate:~$ kvm --version
QEMU emulator version 2.3.0 (Debian 1:2.3+dfsg-5ubuntu2), Copyright (c) 2003-2008 Fabrice Bellard
I wonder can the kvm program be fixed?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in qemu package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (17 preceding siblings ...)
2015-07-20 2:59 ` derek
@ 2015-12-18 22:10 ` varacanero
2016-10-06 21:25 ` Jürgen Veidt
` (4 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: varacanero @ 2015-12-18 22:10 UTC (permalink / raw)
To: qemu-devel
Same for me here, Ubuntu wily.
I'm using vagrant-libvirt, and my hosts also very often run wild with 100% cpu usage after suspend.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in qemu package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (18 preceding siblings ...)
2015-12-18 22:10 ` varacanero
@ 2016-10-06 21:25 ` Jürgen Veidt
2017-01-19 18:17 ` Francois Gouget
` (3 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Jürgen Veidt @ 2016-10-06 21:25 UTC (permalink / raw)
To: qemu-devel
I observed a similar behavior with a different application on a Windows host. The application is using the multimedia timer. In my case it seems that the timer is catching up the ticks missed during suspend to ram after resume. The timer thread performing the callbacks has high-priority on Windows and makes the host machine almost unusable for a certain time depending on the suspend duration.
Maybe it is a similar situation here?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in qemu package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (19 preceding siblings ...)
2016-10-06 21:25 ` Jürgen Veidt
@ 2017-01-19 18:17 ` Francois Gouget
2018-12-08 18:43 ` Mark A. Hershberger
` (2 subsequent siblings)
23 siblings, 0 replies; 30+ messages in thread
From: Francois Gouget @ 2017-01-19 18:17 UTC (permalink / raw)
To: qemu-devel
This sounds sort of like a problem I have with reverting to live snapshots.
What I found out is that this is related to restoring the clock in the guest. You can find out more about it there:
https://bugs.launchpad.net/qemu/+bug/1505041
The takeaway is that a workaround is to set track='guest' on the rtc
timer. For instance:
<clock offset='localtime'>
<timer name='rtc' track='guest'/>
</clock>
If you have track='catchup' QEMU seems to try to send millions of
interrupts so the guest clock will catch up to the current time, which
can take minutes during which the guest is unusable.
It is possible this no longer happens though as I have had this
workaround in place for quite some time but nobody formally said this is
fixed or pointed to a commit fixing this.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in qemu package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (20 preceding siblings ...)
2017-01-19 18:17 ` Francois Gouget
@ 2018-12-08 18:43 ` Mark A. Hershberger
2020-11-10 17:57 ` Thomas Huth
2021-01-10 4:17 ` Launchpad Bug Tracker
23 siblings, 0 replies; 30+ messages in thread
From: Mark A. Hershberger @ 2018-12-08 18:43 UTC (permalink / raw)
To: qemu-devel
I was seeing this problem when my Debian laptop suspended. The CentOS
guest would begin consuming a lot of cpu and only a hard-reset would fix
it.
Changing the rtc line to
<timer name='rtc' track='guest'/>
seems to have fixed it, though I haven't done extensive testing yet.
Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Confirmed
Status in qemu package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (21 preceding siblings ...)
2018-12-08 18:43 ` Mark A. Hershberger
@ 2020-11-10 17:57 ` Thomas Huth
2021-01-10 4:17 ` Launchpad Bug Tracker
23 siblings, 0 replies; 30+ messages in thread
From: Thomas Huth @ 2020-11-10 17:57 UTC (permalink / raw)
To: qemu-devel
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Incomplete
Status in qemu package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
` (22 preceding siblings ...)
2020-11-10 17:57 ` Thomas Huth
@ 2021-01-10 4:17 ` Launchpad Bug Tracker
23 siblings, 0 replies; 30+ messages in thread
From: Launchpad Bug Tracker @ 2021-01-10 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
Status in QEMU:
Expired
Status in qemu package in Ubuntu:
Invalid
Bug description:
I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But
after upgraiding to 13.04 i have to restart the VM each time i
resuming my host machine, because qemu process starts to take CPU
cycles and OS inside VM is very slow and sluggish. However it's still
controllable and could be shutdown by itself.
According to the taskmgr any active process takes 99% CPU. It's not
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
^ permalink raw reply [flat|nested] 30+ messages in thread
end of thread, other threads:[~2021-01-10 4:36 UTC | newest]
Thread overview: 30+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
2013-04-30 10:04 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
2013-04-30 12:54 ` [Qemu-devel] [Bug 1174654] [NEW] " Serge Hallyn
2013-04-30 13:32 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
2013-04-30 13:52 ` Serge Hallyn
2013-04-30 13:42 ` Maxim Loparev
2013-04-30 14:20 ` Maxim Loparev
2013-04-30 14:41 ` Serge Hallyn
2013-04-30 14:50 ` Serge Hallyn
2013-05-08 9:11 ` Maxim Loparev
2013-05-08 15:25 ` Serge Hallyn
2013-05-08 19:01 ` John Basila
2013-07-31 13:34 ` Richard Jones
2013-10-12 9:06 ` tobias
2013-10-13 13:14 ` Paolo Bonzini
2013-10-17 20:29 ` tobias
2013-10-18 2:33 ` mike
2013-10-18 7:12 ` tobias appelo
2013-10-18 7:26 ` mike
2013-10-18 7:41 ` tobias
2013-10-18 8:31 ` tobias
2013-10-30 21:54 ` tobias
2014-02-04 7:15 ` Matt Keith
2015-07-20 2:59 ` derek
2015-12-18 22:10 ` varacanero
2016-10-06 21:25 ` Jürgen Veidt
2017-01-19 18:17 ` Francois Gouget
2018-12-08 18:43 ` Mark A. Hershberger
2020-11-10 17:57 ` Thomas Huth
2021-01-10 4:17 ` Launchpad Bug Tracker
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.