[ kvm-Bugs-2143498 ] FreeBSD fails to reboot

SourceForge.net
2008-10-09T07:26:37Z

Bugs item #2143498, was opened at 2008-10-03 05:38
Message generated for change (Comment added) made by rtg20
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2143498&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Matt Lehner (mlehner)
Assigned to: Nobody/Anonymous (nobody)
Summary: FreeBSD fails to reboot

Initial Comment:
Xeon E5430, ubuntu 8.04 x86_64, currently kvm-62. Reports of same issue in kvm76:

https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/239107

Host kernel: 2.6.24-19
Guest: FreeBSD 6.2, i386 and amd64

Problem: FreeBSD will start normally as a guest OS. When a "reboot" is issued to the guest, it will not come back up without destroying the guest, and then starting it again.

Screenshots from a reboot:
http://lehner.pair.com/screenshot1.png
Note that the drive is listed.

http://lehner.pair.com/screenshot2.png

In the second screenshot, the drive should be listed right after the Timecounters lines.

If the guest is destroyed at that point, and restarted it will come up fine. This can be reproduced 100% of the time. Happens both when using a file or a partition for the guest OS.

----------------------------------------------------------------------

Comment By: Roman Yepishev (rtg20)
Date: 2008-10-09 10:26

Message:
KVM-76: When passed --no-kvm option - the reboot is happening without any
problems, so this has something to do with kernel kvm module as well.

----------------------------------------------------------------------

Comment By: Roman Yepishev (rtg20)
Date: 2008-10-07 23:35

Message:
Reproducible for kvm-74,kvm-75,kvm-76 with FreeBSD 6.2, 6.3 and 7.0.

This is KVM-specific bug. QEMU 0.9.1 does not suffer from it.

----------------------------------------------------------------------

You can respond by visiting: