On Wed, Sep 22, 2010 at 06:04:48PM +0100, Daniel P. Berrange wrote:
>
> Rebased version of my original patch, changing to use 'passthrough'
> security model by default. Support for other models can be added
> in a follow up patch
>
> Make use of the existing element to support plan9fs
> filesyst
On Wed, Sep 22, 2010 at 06:04:48PM +0100, Daniel P. Berrange wrote:
>
> Rebased version of my original patch, changing to use 'passthrough'
> security model by default. Support for other models can be added
> in a follow up patch
>
> Make use of the existing element to support plan9fs
> filesyst
Rebased version of my original patch, changing to use 'passthrough'
security model by default. Support for other models can be added
in a follow up patch
Make use of the existing element to support plan9fs
filesystem passthrough in the QEMU driver
NB, the target is not
On Wed, Jul 21, 2010 at 8:27 PM, Daniel P. Berrange wrote:
> Make use of the existing element to support plan9fs
> filesystem passthrough in the QEMU driver
>
>
>
>
>
>
> NB, the target is not actually a directory, it is merely a arbitrary
> string tag that is exported to the
Make use of the existing element to support plan9fs
filesystem passthrough in the QEMU driver
NB, the target is not actually a directory, it is merely a arbitrary
string tag that is exported to the guest as a hint for where to mount
it.
---
src/qemu/qemu_conf.c
On 06/07/2010 03:32 AM, Daniel P. Berrange wrote:
> Make use of the existing element to support plan9fs
> filesystem passthrough in the QEMU driver
>
>
>
>
>
>
> NB, the target is not actually a directory, it is merely a arbitrary
> string tag that is exported to the gues
Make use of the existing element to support plan9fs
filesystem passthrough in the QEMU driver
NB, the target is not actually a directory, it is merely a arbitrary
string tag that is exported to the guest as a hint for where to mount
it.
---
src/qemu/qemu_conf.c
