** Changed in: qemu
Status: New = 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/1278977
Title:
qemu-system-sparc64 crash when initializing disk
Status in QEMU:
Fix Released
HI Waldemar,
Glad that you now have something that works for you.
I've tried to reproduce your virtio hang this morning with multiple 100%
CPU and find / -name 'foo' processes running but I can't seem to get
virtio to hang on my system here.
Since this is the second report I've had of this
Hi Mark,
I tried the cmd646 driver again and it works fine now. I can even extract the
perl code without problems.
No deadlock, even with a high load of the host system.
When switching back to virtio using following command:
qemu-system-sparc64 -M sun4u -nographic -net nic,model=virtio -net
Hi Waldemar,
An update on this bug: it seems there is a problem with QEMU's block AIO
code which seems to be easily triggerable with virtio. I think it's be
identified within recent discussions on the mailing list, but I don't
believe a patch has been committed to resolve the issue.
Note that as
Hi,
here is the kernel and image:
http://www.openadk.org/sparc64/
Inside the system do:
rw
tar xvf perl-5.18.1.tar.gz
The kernel contains full debug info. Be sure that your system has a high
load.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
We don't implement the sparc64 iommu, and the kernel expects to be able
to use it.
The kernel sets up an iommu translation table, but qemu does not adjust its
internal mappings,
and thus the first time the kernel touches the PCI bus we get an oops.
If you build a kernel with virtio built in,
Hi Artyom,
okay, with 1.7.0 on Maverick I get:
(qemu) info block
virtio0: qemu-sparc64.img (raw)
ide0-hd0: qemu-sparc64.img (raw)
ide1-cd0: [not inserted]
Removable device: not locked, tray closed
floppy0: [not inserted]
Removable device: not locked, tray closed
sd0: [not inserted]
Hi Waldemar,
It can be a Linux kernel bug or a QEMU bug. To get the further info,
try -serial telnet::,server,wait
and use the telnet as a serial console. When the guest hangs use the
telnet menu to send break, and then type 'T'.
This would produce the same result as magic SysRq+T: the kernel
Hi Artyom,
unfortunately there is no output, when the system gets the deadlock:
perl-5.18.1/pod/perlvms.pod
perl-5.18.1/pod/rofftoc
telnet send brk
When the system is running, I get
ENTER
and can then push the t key to get the running threads/tasks.
Any other idea?
best regards
Waldemar
--
Hi Mark,
I have done some more testing on this and giving up. It is very fuzzy. Seems to
work on MacOSX and Linux hosts with Qemu 1.7 and
Qemu 2.0rc0 when the load of the system is under 2-3. If it is higher sometimes
the deadlock occur.
So I think we can close the bug and hope nobody is
Hi Waldemar,
can you try launching QEMU with -monitor telnet::4442,server,nowait
(or any other port), and check if the monitor is available when the
suspected deadlock occurs? If connecting works, try info block and
blockstats, this may give some further clues, whether the hang happens
in host or
Hi Waldemar,
Apologies for the delay in the reply! A few more questions for you:
- Do you still see the same issue with qemu git master? (soon to be 2.0)
- Can you use gdb or similar to get a backtrace from one of the deadlocked
processes?
- Does the extraction always freeze at the same place,
Hi Mark,
the strace is from qemu-system-sparc64 host process. Inside the running system
(Linux 3.13.3, glib 2.19, busybox) I get:
[pid 273] umask(0)= 022
[pid 273] umask(022) = 0
[pid 273] mkdir(perl-5.18.1/, 0777) = -1 EEXIST (File exists)
[pid 273]
Hi Waldemar,
I can't say that I've seen anything like that here, although I don't
tend to push my images too much. It does sound like some kind of
deadlock though.
Are these the straces from the qemu-system-sparc64 host process or the
qemu-system-sparc64 guest process? If it's the former, can
Hi,
my linux system boots up fine in the emulator, but when I try to extract perl
source code it just hangs after a while:
..
perl-5.18.1/cpan/Pod-Simple/t/basic.t
perl-5.18.1/cpan/Pod-Simple/t/begin.t
perl-5.18.1/cpan/Pod-Simple/t/cbacks.t
perl-5.18.1/cpan/Pod-Simple/t/chunking.t
no further
Hi Mark,
thanks for the tip. It works fine with virtio drivers. Is there any
specific reason, why Qemu sparc64 virtualization have to use the cmd646
driver? For example mips emulator is using PIIX3/4 IDE driver.
thanks so far,
Waldemar
--
You received this bug notification because you are a
Hi Waldemar,
The bug you are seeing is related to the Linux cmd646 driver which
happens to cause an illegal access in the kernel under qemu-system-
sparc64. It is most likely due to the lack of IOMMU emulation, however I
haven't had a chance to dig into it in much detail yet.
The good news is
17 matches
Mail list logo
