librelist archives

home // archives //

« back to archive

libvirt shared folder support

libvirt shared folder support

From:
yeswanth swami
Date:
2011-06-10 @ 22:47 
Hi,
Looks like libvirt doesnt have a proper support for shared folders. I guess
we will have to go for mounting the virtual hard disk on the slave. Static
VDI image can be mounted easily (
http://serverfault.com/questions/210684/how-do-you-mount-a-vdi-image-on-linux)
, for dynamic VDI image are very difficult(unless converted to other format)
. We will have to look at other formats if we want dynamic harddisks .

-- 
Cheers,
Yeswanth

Re: [pyti] libvirt shared folder support

From:
Pierre-Yves David
Date:
2011-06-10 @ 22:52 
On 11 juin 2011, at 00:47, yeswanth swami wrote:

> Hi,
> Looks like libvirt doesnt have a proper support for shared folders. I 
guess we will have to go for mounting the virtual hard disk on the slave. 
Static VDI image can be mounted easily 
(http://serverfault.com/questions/210684/how-do-you-mount-a-vdi-image-on-linux)
, for dynamic VDI image are very difficult(unless converted to other 
format) . We will have to look at other formats if we want dynamic 
harddisks .

What do you exactly mean by dynamic hard disks ?

-- 
Pierre-Yves

Re: [pyti] libvirt shared folder support

From:
yeswanth swami
Date:
2011-06-11 @ 06:42 
HI,
Here dynamic hard disks mean harddisks which will have minimum storage
initially which will be expanded as and when Guest OS claims space (upto the
size specified) .

On Sat, Jun 11, 2011 at 4:22 AM, Pierre-Yves David <
pierre-yves.david@ens-lyon.org> wrote:

>
> On 11 juin 2011, at 00:47, yeswanth swami wrote:
>
> > Hi,
> > Looks like libvirt doesnt have a proper support for shared folders. I
> guess we will have to go for mounting the virtual hard disk on the slave.
> Static VDI image can be mounted easily (
> http://serverfault.com/questions/210684/how-do-you-mount-a-vdi-image-on-linux)
> , for dynamic VDI image are very difficult(unless converted to other format)
> . We will have to look at other formats if we want dynamic harddisks .
>
> What do you exactly mean by dynamic hard disks ?
>
> --
> Pierre-Yves
>



-- 
Cheers,
Yeswanth

Re: [pyti] libvirt shared folder support

From:
Alexis Métaireau
Date:
2011-06-11 @ 08:55 
On 06/11/2011 12:47 AM, yeswanth swami wrote:
> Looks like libvirt doesnt have a proper support for shared folders.

A patch have been recently provided by the libvirt team to add shared 
folder support for he virtualbox hypervisor [0]. I'm not too fanatic 
about using recently created patches, but depending on their release 
cycle it can be something to consider. Otherwise, using a disk image (as 
you said) or the virtualbox-manage command line could be another 
acceptable idea which will work now and will not depend on libvirt calendar.

On a general note, I found an interesting support matrix for libvirt 
features and hypervisors [1]. As the libvirt documentation is kinda 
poor, this seem to be a good resource to keep in mind to check that the 
features we want are implemented.

What is the problem with static VDI images ? We can reasonably think 
that we will have to deal with a quite small amount of data, as it will 
only be text files and other small dumps. 1GB disk seem more than 
needed, so we can probably go for something like a 200MB capacity disk.

This capacity can be defined by the python script and forged 
automatically before running the VM instance, also using libvirt, using 
this xml syntax [2]

[0] https://www.redhat.com/archives/libvir-list/2011-June/msg00315.html
[1] http://libvirt.org/hvsupport.html
[2] http://libvirt.org/formatstorage.html

I guess
> we will have to go for mounting the virtual hard disk on the slave. Static
> VDI image can be mounted easily (
> http://serverfault.com/questions/210684/how-do-you-mount-a-vdi-image-on-linux)
> , for dynamic VDI image are very difficult(unless converted to other format)
> . We will have to look at other formats if we want dynamic harddisks .
>


-- 
Alexis

Re: [pyti] libvirt shared folder support

From:
yeswanth swami
Date:
2011-06-11 @ 09:35 
2011/6/11 Alexis Métaireau <alexis@notmyidea.org>

> On 06/11/2011 12:47 AM, yeswanth swami wrote:
> > Looks like libvirt doesnt have a proper support for shared folders.
>
> A patch have been recently provided by the libvirt team to add shared
> folder support for he virtualbox hypervisor [0]. I'm not too fanatic
> about using recently created patches, but depending on their release
> cycle it can be something to consider. Otherwise, using a disk image (as
> you said) or the virtualbox-manage command line could be another
> acceptable idea which will work now and will not depend on libvirt
> calendar.
>
> On a general note, I found an interesting support matrix for libvirt
> features and hypervisors [1]. As the libvirt documentation is kinda
> poor, this seem to be a good resource to keep in mind to check that the
> features we want are implemented.
>
>
Saw the mailing list before posting. My opinion, it is too early to comment
on it(as the first patch for shared folder was released a few days back).


> What is the problem with static VDI images ? We can reasonably think
> that we will have to deal with a quite small amount of data, as it will
> only be text files and other small dumps. 1GB disk seem more than
> needed, so we can probably go for something like a 200MB capacity disk.
>
> This capacity can be defined by the python script and forged
> automatically before running the VM instance, also using libvirt, using
> this xml syntax [2]
>
> Agree with a static disk . I just mentioned it to inform you.


> [0] https://www.redhat.com/archives/libvir-list/2011-June/msg00315.html
> [1] http://libvirt.org/hvsupport.html
> [2] http://libvirt.org/formatstorage.html
>
> I guess
> > we will have to go for mounting the virtual hard disk on the slave.
> Static
> > VDI image can be mounted easily (
> >
> http://serverfault.com/questions/210684/how-do-you-mount-a-vdi-image-on-linux
> )
> > , for dynamic VDI image are very difficult(unless converted to other
> format)
> > . We will have to look at other formats if we want dynamic harddisks .
> >
>
>
> --
> Alexis
>



-- 
Cheers,
Yeswanth

Re: [pyti] libvirt shared folder support

From:
Alexis Métaireau
Date:
2011-06-11 @ 14:05 
Hey back,

On 06/11/2011 11:35 AM, yeswanth swami wrote:
> Saw the mailing list before posting. My opinion, it is too early to comment
> on it(as the first patch for shared folder was released a few days back).
Don't be afraid to put your sources here like I did so we are clear 
about what is inferred and what is coming from viable sources :-) (you 
said "Looks like libvirt doesnt have a proper support for shared 
folders" whereas regarding their ML, it's clear that there is no such 
support for now).

> Agree with a static disk. I just mentioned it to inform you.
Ok, again, please try to be explicit in your messages, "I guess
we will have to go for mounting the virtual hard disk on the slave." is 
appealing for opinions on that and clearly let us think that you're 
unclear about this choice. If you are sure about this, then say that 
you'll start working on static disks.

Nothing to take too seriously, but communication can be hard, especially 
when we are not making clear statements, so please keep this in mind 
when writing mails.

-- 
Alexis

Re: [pyti] libvirt shared folder support

From:
yeswanth swami
Date:
2011-06-11 @ 15:32 
Thanks for correcting me. I will try to be more explicit from next time :)

2011/6/11 Alexis Métaireau <alexis@notmyidea.org>

> Hey back,
>
> On 06/11/2011 11:35 AM, yeswanth swami wrote:
> > Saw the mailing list before posting. My opinion, it is too early to
> comment
> > on it(as the first patch for shared folder was released a few days back).
> Don't be afraid to put your sources here like I did so we are clear
> about what is inferred and what is coming from viable sources :-) (you
> said "Looks like libvirt doesnt have a proper support for shared
> folders" whereas regarding their ML, it's clear that there is no such
> support for now).
>
> > Agree with a static disk. I just mentioned it to inform you.
> Ok, again, please try to be explicit in your messages, "I guess
> we will have to go for mounting the virtual hard disk on the slave." is
> appealing for opinions on that and clearly let us think that you're
> unclear about this choice. If you are sure about this, then say that
> you'll start working on static disks.
>
> Nothing to take too seriously, but communication can be hard, especially
> when we are not making clear statements, so please keep this in mind
> when writing mails.
>
> --
> Alexis
>



-- 
Cheers,
Yeswanth

Archives based on code by Armin Ronacher //