Crash indicates that the QEMU is older version. Basically client is sending
something that QEMU doesn't have support on.
We have a bug opened internally to handle this situation gracefully instead of
crashing. I will post the patch soon.
Moving to latest QEMU should resolve this issue...
Thanks,
** Changed in: qemu
Status: New => Invalid
--
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Invalid
Bug description:
use a
Yes, it is a lot better... now only the complete machine crashes when
accessing the 9p.L mounted directory
{{{
virtio-9p.c:3448: submit_pdu: Assertion `!(handler == ((void *)0))' failed.
}}}
--
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received th
Yes, I can't reproduce this anymore with the updated tree.
This can probably be closed.
Thanks!
--
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
We had a bunch of patches went into today's kernel. With those set of
patches, this problem is not reproducible.
--
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscr
Reproducible here with guest kernel 2.6.36 built for i686 and qemu-kvm built
from a fresh git clone taken on 27/10/2010.
Host kernel is 2.6.30.10105.2.23.fc11.i686.PAE
Guest 9p filesystem mounted as both 9p2000.u and 9p2000.L with the same problem.
In the guest syscall 'stat' on a non-existent pa
** Description changed:
- use as client Debian squeeze i386 with a custom kernel:
+ use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux
And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21
The untar without bz2 (second example) also happens when setting PATH to
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
--
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
deve
a good other example is tar:
$ cd /mnt
$ tar xvfj linux-2.6.35.2.tar.bz2
tar (child): bzip2: Cannot exec: Bad address
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
$ tar xvf 2.6.36-rc6.tar
2.6.36-rc6/
tar: 2.6.36-rc6: Can
