QEMU loadvm causes guest OS freeze

Bug #1242963 reported by NanothylL
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
QEMU
Expired
Undecided
Unassigned

Bug Description

HOST: ubuntu 13.10 x64
GUEST: winxp sp 3 x86

AFFECT QEMU(tested): v1.5.2, v1.5.3, v1.6.0, v1.6.1

I compile QEMU by myself with "./configure --target-list=i386-softmmu && make && make install".
After installing a winxp sp3 into the qemu-system-i386 with command line:
> qemu-system-i386 -m 512 -hda xp.img -net user -net nic,model=rtl8139 -rtc base=localtime,clock=vm

I use monitor to create a live snapshot:
> stop
> savevm xxx
> cont

And then I load this snapshot (I also try it in commad line: -loadvm xxx):
> loadvm xxx
> cont

After that, the windows system is freeze (don't accept any keyboard or mouse input, although I knew vcpu is still working).

If I compile with -enable-kvm and launch qemu-system-i386 with -enable-kvm, it looks like everything works well.
I think it is a bug for qemu system.

BTW: freeze is not appearing 100%, but in my test, 95% cases would cause system freeze.

NanothylL (nanothyll)
Changed in qemu:
status: New → Incomplete
NanothylL (nanothyll)
Changed in qemu:
status: Incomplete → New
Revision history for this message
NanothylL (nanothyll) wrote :

Hi guys,

This bug has reported in a very long time. I have tested v1.7.0, v1.7.1 and even v2.0.0rc1, v2.0.0rc2.
The bug is still there. This is very easy to reproduce. I dunno why it is not fixed until today.

I think living-snapshot is a very important feature for Qemu. Somebody can take a look at this issue.
Or at least, give me some tips to let me know how to fix this?

Thanks!

Revision history for this message
NanothylL (nanothyll) wrote :

I found something, hope this could be useful.

(qemu) info cpus
* CPU #0: pc=0x000000008054b7f1 thread_id=20447
(qemu) savevm x
(qemu) loadvm x
(qemu) info cpus
* CPU #0: pc=0x00000000806f69ba (halted) thread_id=20447

Revision history for this message
Mark (ms-h) wrote :

Pinging this as I'm running into the same issue, Win7 seems to be fine as a guest, just getting this with XP (SP3).

I'm 99% certain that 1.5.0 was still fine. I looked at the commits between that and 1.5.2 but did not really see anything obvious that could cause it.

Revision history for this message
None (none123456-deactivatedaccount) wrote :

I have the same bug, is there any news concerning a fix?

Revision history for this message
Thomas Huth (th-huth) wrote :

Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?

Changed in qemu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for QEMU because there has been no activity for 60 days.]

Changed in qemu:
status: Incomplete → Expired
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.