qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH -V2 00/22] virtio-9p: paravirtual file system pa


From: Luiz Capitulino
Subject: Re: [Qemu-devel] [PATCH -V2 00/22] virtio-9p: paravirtual file system passthrough
Date: Wed, 24 Mar 2010 12:04:26 -0300

On Wed, 24 Mar 2010 09:28:36 +0530
"Aneesh Kumar K. V" <address@hidden> wrote:

> On Tue, 23 Mar 2010 20:17:33 -0300, Luiz Capitulino <address@hidden> wrote:
> > On Tue, 16 Mar 2010 14:44:58 +0530
> > "Aneesh Kumar K.V" <address@hidden> wrote:
> > 
> > > Hi,
> > > 
> > > 
> > > This patch series adds a paravirtual file system passthrough mechanism to 
> > > QEMU
> > > based on the 9P protocol. With the current implementation, all I/O is 
> > > implemented
> > > in the VCPU thread.  We've modified the protocol handlers so that we can 
> > > support
> > > dispatch I/O in a thread pool. The actual thread pool implementation will 
> > > be posted later
> > > 
> > > This patch set should work with any recent Linux kernel as virtio-9p has 
> > > been
> > > supported for a few kernel releases now. Export dir is specified using 
> > > the below
> > > Qemu option.
> > > 
> > > -device virtio-9p-pci,share_path=/mnt/,mount_tag=v_mnt
> > > 
> > > mount_tag is used to identify the mount point in the kernel. This will be 
> > > available in Linux
> > > kernel via /sys/devices/virtio-pci/virtio1/mount_tag file.
> > 
> >  I tried this very '-device' line and I can see that the guest has loaded
> > the virtio modules, but there isn't anything in the virtio0 directory other
> > than standard sysfs files.
> > 
> >  Is there a way to debug this?
> > 
> 
> which version of the kernel ? 

2.6.31.5

> The latest linus tree have all the needed
> changes. You should have  /sys/bus/virtio/drivers/9pnet_virtio/ if you
> have CONFIG_NET_9P_VIRTIO enabled.

 I have it, but still no mount_tag. I'll try with a more recent
kernel but this will take more time.

> You can then find mount tag at virtio<n>/mount_tag 
> 
> 
> >  Something possibly related is that, I had to rewind the tree by some 
> > commits
> > because this series doesn't apply against current HEAD.
> 
> 
> 
> The patches are against 0aef4261ac0ec9089ade0e3a92f986cb4ba7317e of the
> master branch 
> 
> 
> -aneesh





reply via email to

[Prev in Thread] Current Thread [Next in Thread]