virtio-9p error
Hi,
Every time I try to rsync something to my 9p fs mounted I get the following message on guest kernel:
8<--------------------
[ 45.866789] 9pnet_virtio virtio2: requests:id 0 is not a head!
8<--------------------
I'm "sending" the FS with the following argument via qemu-kvm (commit head 422476cc422 of August 12):
-virtfs local,path=/home/outras/montecristo,mount_tag=home,security_model=passthrough
And I'm mounting on the guest with:
mount -t 9p -o trans=virtio home /home
My guest is running kernel 2.6.34.
After I start the rsync (a second later) i get the message i showed above and the the virtio fs crashes and i have to reboot the virtual machine.
Another 'interesting' thing is that the filesystem wont show in 'df'. But appears correct in /proc/mounts
8<--------------------
montecristo-nova:/home# mount|tail -1 home on /home type 9p (rw,sync,dirsync,relatime,trans=virtio) 8<--------------------
Here is a little of my rsync output:
8<--------------------
montecristo-nova:/home# cd nobackup/ montecristo-nova:/home/nobackup# rsync -aHx --progress xadrezlivre:/ xadrezlivre/ receiving incremental file list rsync: symlink "/home/nobackup/xadrezlivre/cdrom" -> "media/cdrom" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/initrd.img" -> "boot/initrd.img-2.6.26-1-486" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/initrd.img.old" -> "boot/initrd.img-2.6.18-6-486" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/vmlinuz" -> "boot/vmlinuz-2.6.26-1-486" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/vmlinuz.old" -> "boot/vmlinuz-2.6.18-6-486" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/bin/nc" -> "/etc/alternatives/nc" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/bin/netcat" -> "/etc/alternatives/netcat" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/bin/pidof" -> "../sbin/killall5" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/bin/rnano" -> "nano" failed: No such file or directory (2) 8<--------------------
If anyone knows what it is or what else should I send to understand better the problem, please tell me
Thanks in advance
Signature · 3 lines
Bruno Ribas - [email protected] http://www.inf.ufpr.br/ribas C3SL: http://www.c3sl.ufpr.br
Quoted 9 lines · Bruno Cesar Ribas
Hi,
Every time I try to rsync something to my 9p fs mounted I get the following message on guest kernel:
8<--------------------
[ 45.866789] 9pnet_virtio virtio2: requests:id 0 is not a head!8<--------------------
Quoted 8 lines
I'm "sending" the FS with the following argument via qemu-kvm (commit head
422476cc422of August 12):
-virtfs local,path=/home/outras/montecristo,mount_tag=home,security_model=passthroughAnd I'm mounting on the guest with:
mount -t 9p -o trans=virtio home /homeMy guest is running kernel 2.6.34.
I tested with the latest kernel, 2.6.35-rc6+ ..
rsync -avz guest:/pmnt/rsync_dir/ /tmp/rsync_dir/ rsync /pmnt/rsync_dir/ /tmp/rsync_dir/
rsync -aHx --progress host:/tmp/rsync_dir/ /pmnt/rsync_dir/
This quick test is with QEMU patches that are on mailing lists but not merged into mainline.
Being said that, I don't think they really affect this.
Quoted 6 lines
After I start the rsync (a second later) i get the message i showed above and the the virtio fs crashes and i have to reboot the virtual machine.
Another 'interesting' thing is that the filesystem wont show in 'df'. But appears correct in
/proc/mounts
This works only on 9P2000.L protocol. (Need "-o version=9p2000.L" option on the mount)
But please note that, all the 9P2000.L protocol patches are not yet merged into QEMU.
Thanks,
JV
Quoted 38 lines
8<--------------------
montecristo-nova:/home# mount|tail -1 home on /home type 9p (rw,sync,dirsync,relatime,trans=virtio) 8<--------------------Here is a little of my rsync output:
8<--------------------
montecristo-nova:/home# cd nobackup/ montecristo-nova:/home/nobackup# rsync -aHx --progress xadrezlivre:/ xadrezlivre/ receiving incremental file list rsync: symlink "/home/nobackup/xadrezlivre/cdrom" -> "media/cdrom" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/initrd.img" -> "boot/initrd.img-2.6.26-1-486" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/initrd.img.old" -> "boot/initrd.img-2.6.18-6-486" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/vmlinuz" -> "boot/vmlinuz-2.6.26-1-486" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/vmlinuz.old" -> "boot/vmlinuz-2.6.18-6-486" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/bin/nc" -> "/etc/alternatives/nc" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/bin/netcat" -> "/etc/alternatives/netcat" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/bin/pidof" -> "../sbin/killall5" failed: No such file or directory (2) rsync: symlink "/home/nobackup/xadrezlivre/bin/rnano" -> "nano" failed: No such file or directory (2) 8<--------------------If anyone knows what it is or what else should I send to understand better the problem, please tell me
Thanks in advance
Quoted 7 lines · Venkateswararao Jujjuri (JV)
Quoted 2 lines · Bruno Cesar Ribas
Hi,
[snip]
This quick test is with QEMU patches that are on mailing lists but not merged into mainline.
Being said that, I don't think they really affect this.
is there any work to bring these patches to mainline?
There's no imprevement on virtio-9p in qemu since my first email.
Quoted 2 lines
Quoted 1 line
[snip]
Signature · 3 lines
Bruno Ribas - [email protected] http://www.inf.ufpr.br/ribas C3SL: http://www.c3sl.ufpr.br
Quoted 4 lines · Bruno Cesar Ribas
Quoted 3 lines · Venkateswararao Jujjuri (JV)
Quoted 2 lines · Bruno Cesar Ribas
Hi,
Quoted 8 lines
Quoted 4 lines
[snip]
This quick test is with QEMU patches that are on mailing lists but not merged into mainline.
Being said that, I don't think they really affect this.is there any work to bring these patches to mainline?
There's no imprevement on virtio-9p in qemu since my first email.
I sent a new revision on Thursday. I am expecting that they will go in anytime.
Last time I talked to Anthony, he is planning on taking these patches soon.
Thanks,
JV
Quoted 3 lines
Quoted 2 lines
Quoted 2 lines
[snip]
Quoted 10 lines · Venkateswararao Jujjuri (JV)
Quoted 9 lines · Bruno Cesar Ribas
Quoted 7 lines · Venkateswararao Jujjuri (JV)
Quoted 2 lines · Bruno Cesar Ribas
Hi,
[snip]
This quick test is with QEMU patches that are on mailing lists but not merged into mainline.
Being said that, I don't think they really affect this.
Quoted 7 lines
Quoted 3 lines
is there any work to bring these patches to mainline?
There's no imprevement on virtio-9p in qemu since my first email.
I sent a new revision on Thursday. I am expecting that they will go in anytime.
Last time I talked to Anthony, he is planning on taking these patches soon.
Hello, now the patches are on the mainline tree. Please try them out.
Thanks,
JV
Quoted 13 lines
Thanks,
JVQuoted 3 lines
Quoted 2 lines
Quoted 2 lines
[snip]
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html