** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1127369
Title:
i386 emulation unreliable since commit
b76f0d8c2e3eac94bc7fd90a510cb7
My tests are now working again. The point in time when they started
working is consistent with this having been fixed by commit
38ebb396c955ceb2ef7e246248ceb7f8bfe1b774, "target-i386: ROR r8/r16 imm
instruction fix". Many thanks to everyone involved in fixing it.
--
You received this bug notifi
Now that bug 1154328 has been fixed, the NetBSD OS test suite
successfully starts, but it still does not work as expected; actually
things have gone from bad to worse. Every test run since the 1154328
fix has either timed out after running only a fraction of the tests, or
has ended in a guest ker
Anthony,
On Sun, Mar 31, 2013 at 07:24:20PM -, Andreas Gustafsson wrote:
> Thank you. Now if someone could also fix bug 1154328 , my automated
> tests might run again...
This bug is indeed quite problematic and is caused by one of your
patches:
commit a29753f8aa79a34a324afebe340182a51a5ae
Thanks - fix committed to Fedora. Hopefully this will squash the rare
and random segfaults in the libguestfs test suite.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1127369
Title:
i386 emulatio
Thank you. Now if someone could also fix bug 1154328 , my automated
tests might run again...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1127369
Title:
i386 emulation unreliable since commit
b
Oops sorry. The correct commit hash is
52ae646d4a3ebdcdcc973492c6a56f2c49b6578f
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1127369
Title:
i386 emulation unreliable since commit
b76f0d8c2e3eac9
Thanks for the detailed test case and fix. However unfortunately I cannot see
d6e839e718 in the current qemu git. Is it possible the commit hash changed
because of a rebase when it was committed?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscrib
This has been fixed in commit d6e839e718c2540b880ac9d2d7a49fb7ade02cfb
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1127369
Title:
i386 emu
