Public bug reported:
Hi,
I can no longer boot my Windows 7 guest after this commit (update
seabios to latest master)
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=01afdadc92e71e29700e64f3a5f42c1c543e3cf9
When I tried to boot Windows, it BSOD and said "The BIOS in this system
is not fully ACPI
I have tried both 32-bit and 64-bit Windows 7, both have the same issue.
But I can also boot into the Window 7 setup. I have tried to use the
repair option but it cannot repair it. I then recreated the partion and
do a fresh installation and it then boots fine. So this issue only
affects the guest
I am now trying to reinstall a new instance without the BIOS update,
then update the BIOS after that to see if I can reproduce the issue.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1042084
Title:
I cannot reproduce the issue with newly created image, so looks like
this is not a qemu bug, but just a problem of my corrupted image. Sorry
for the noise, please close the issue and I will report another one if I
find other things.
--
You received this bug notification because you are a member o
v/linux/x86_64/lowlevellock.S:103
- #1 0x7748c714 in __GI___pthread_mutex_lock (mutex=0x56518340
) at ../nptl/pthread_mutex_lock.c:80
- #2 0x55d8ae7b in qemu_mutex_lock_impl (mutex=0x56518340
,
- file=0x55e7a298 "/home/vic/Projects/tc-qemu/exec.c",
mutex_lock.c:80
#2 0x55d8ae7b in qemu_mutex_lock_impl (mutex=0x56518340
,
file=0x55e7a298 "/home/vic/Projects/tc-qemu/exec.c", line=3197) at
util/qemu-thread-posix.c:66
#3 0x00005584cf66 in qemu_mutex_lock_iothread_impl (file=0x55e7a298
"/home/vic/Pro
03
#1 0x7748c714 in __GI___pthread_mutex_lock (mutex=0x56518340
) at ../nptl/pthread_mutex_lock.c:80
#2 0x55d8ae7b in qemu_mutex_lock_impl (mutex=0x56518340
,
file=0x55e7a298 "/home/vic/Projects/tc-qemu/exec.c", line=3197) at
util/qemu-thread-p
Fix committed in slirp/src/socket.c
** 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/1817865
Title:
sorecvfrom freezes guest
Status in QEMU:
Sometimes sorecvfrom() is called from slirp.c because revents == G_IO_IN,
but there is 0 bytes available and recvfrom could be blocking indefinitely.
This is likely due to 0-length udp payload. This also adds an error
checking for ioctlsocket.
Signed-off-by: Vic Lee
---
slirp/socket.c | 10
Sometimes sorecvfrom() is called from slirp.c because revents == G_IO_IN,
but there is 0 bytes available and recvfrom could be blocking indefinitely.
This is likely due to 0-length udp payload. This also adds an error
checking for ioctlsocket.
Signed-off-by: Vic Lee
---
slirp/socket.c | 10
10 matches
Mail list logo
