** 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
** 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
Public bug reported:
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:50:19 UTC 2010 x86_64 GNU/Linux
kvm version is:
kvm-88-5908-gdd67374
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
Updated to v2.6.36.6 with https://patchwork.kernel.org/patch/127401/ and
it still has the problem. It increases the memory usage not as fast, but
it still quite a lot.
I also tried to mount it using -oversion=9p2000.L
/sys/kernel/debug/kmemleak says on unmount:
unreferenced object 0xf791a870 (s
** Description changed:
I 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:50:19 UTC 2010 x86_64 GNU/Linux
kvm version is:
kv
Fixed for me by http://article.gmane.org/gmane.linux.utilities.util-
linux-ng/3500/raw and
http://article.gmane.org/gmane.linux.kernel/1041020/raw
** Changed in: qemu
Status: New => In Progress
--
VirtFS: Cannot mount 9p during boot
https://bugs.launchpad.net/bugs/648128
You received this
Fixed by the mentioned documentation
** Changed in: qemu
Status: New => Invalid
--
VirtFS mapped symlinks resolved wrong
https://bugs.launchpad.net/bugs/646427
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Inva
Public bug reported:
I 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:50:19 UTC 2010 x86_64 GNU/Linux
kvm version is:
kvm-88-5908-gdd67374
So it is a problem that pwd inside the root shell is / and thus it finds
/host and informs the kernel that it should mount /host using 9p to /mnt
(which is of course bogus). I am quite unsure how to work around that
problem without a stupid hack in rc.local instead of /etc/fstab
So there is still
Next steps were to use the old envs:
$ for i in USER MAIL OLDPWD HOME HUSHLOGIN PS1 LOGNAME TERM PATH SHELL PWD; do
unset $i; done
$ export CONSOLE=/dev/console
$ export HOME=/
$ export runlevel=2
$ export INIT_VERSION=sysvinit-2.88
$ export COLUMNS=80
$ export TERM=linux
$ export PATH=/sbin:/usr
Important information: There exists a folder /host in the guest
filesystem
--
VirtFS: Cannot mount 9p during boot
https://bugs.launchpad.net/bugs/648128
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: New
Bug descriptio
Public bug reported:
I 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:50:19 UTC 2010 x86_64 GNU/Linux
kvm version is:
kvm-88-5908-gdd67374
** Description changed:
I tried to map a folder with qemu-kvm qemu-kvm-0.13.0-rc1-3-gc9c2179
(this is v0.13.0-rc1-16667-gc9c2179). I mounted it first in passthrough
mode and saw all symlinks as expected. Then I used mapped and noticed
that the target of a symlink changed to the actual data
But mapped is also really confusing. Everything inside the vm:
$ id
uid=0(root) gid=0(root) groups=0(root)
$ touch newfile
$ -rw-r--r-- 1 root 1000 0 Sep 24 20:39 newfile
So the gid is not set correctly. On thhe host:
% xattr newfile
user.virtfs.uid
user.virtfs.mode
I started it using:
% /usr/l
Host OS is Debian sid/experimental amd64 with 2.6.32-5-amd64
(2.6.32-23). qemu-kvm version can be found above. As said before the
symlink were created outside the vm and then tried to access inside the
vm.
So I have to use passthrough in host/client shared folders... which
means I have to run kvm
And maybe you should use lsetxattr and lgetxattr instead of the symlink
resolving versions setxattr and getxattr
--
VirtFS mapped symlinks resolved wrong
https://bugs.launchpad.net/bugs/646427
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QE
Why not using simple symlinks on the host with xattr like on normal
files instead of those hacks which either don't work on client or don't
work on the host?
--
VirtFS mapped symlinks resolved wrong
https://bugs.launchpad.net/bugs/646427
You received this bug notification because you are a member
Public bug reported:
I tried to map a folder with qemu-kvm qemu-kvm-0.13.0-rc1-3-gc9c2179
(this is v0.13.0-rc1-16667-gc9c2179). I mounted it first in passthrough
mode and saw all symlinks as expected. Then I used mapped and noticed
that the target of a symlink changed to the actual data inside the
21 matches
Mail list logo
