OK, thanks for your response! So let's assume it's the same bug as
643430, i.e. it should be fixed nowadays.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.l
Hi Thomas, thanks for the triage. I'm a few years past working on this
project directly so if it's not affecting anyone else I'd probably just
close this bug.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net
Sounds like this could have been a duplicate bug of
https://bugs.launchpad.net/qemu/+bug/643430 ? If so, it should have been
fixed in late 2011. Could you check with the latest version of QEMU /
Seabios if the problem still persists?
** Changed in: qemu
Status: New => Incomplete
--
You re
qemu 0.12 and newer reboot of FreeBSD (m0n0wall.vmdk http://m0n0.ch/wall/ )
fails.
The Server (IBM xSeries 206), on which i found this "problem", has no kvm
support...
finally i decided not to use the IBM server [it is awfully slow when booting,
although ubuntu server is really fast available
This patch to SeaBIOS seems to fix it, but I still think there's a bug
in kvm if it behaves differently with or without the "-no-kvm" flag.
** Tags added: bios kvm reset
** Patch added: "qemu-reset.patch"
https://bugs.launchpad.net/qemu/+bug/732155/+attachment/1906859/+files/qemu-reset.patch
A bit of bisection on SeaBIOS shows that commit
244caf86f11f5f65d166d91704f64cb673167abc was the first to exhibit this
behaviour. Arguably a SeaBIOS bug, but I don't know enough about the
reset process to judge.
--
You received this bug notification because you are a member of qemu-
devel-ml, wh
