6:22 a.m.
Hi all,
I wanna test if a storage driver (like Sheepdog) works well in Libvirt
separately. How
should i finish this job. Could anyone give me some suggestions?
--
Thanks
Harry Wei
9:28 p.m.
On 2013年01月25日 20:22, harryxiyou wrote:
Hi all,
I wanna test if a storage driver (like Sheepdog) works well in Libvirt
separately. How
should i finish this job. Could anyone give me some suggestions?
It's bad that we don't have sheepdog pool documented in [1]
when doing the patches. But the good thing is there are some
documents for it in [2]. If you see the document is not
enough. You can check the RNG schema to figure out the XMLs
the sheepdog pool supports.
$libvirt_source/docs/schemas/storagepool.rng
Or even you may want to have a look at the test files:
% grep -r sheepdog $libvirt_source/tests/storagepool*
Once you have a workable pool XML, you can test it via virsh
To see all the commands for pool and vol:
% virsh help pool
% virsh help volume
Note that sheepdog pool in libvirt only support small parts
of the operations though.
Hope it helps. And please don't hestimate pinging the list if
you find any problems.
[1] http://libvirt.org/formatstorage.html
[2] http://libvirt.org/storage.html
Osier
3:42 a.m.
On Mon, Jan 28, 2013 at 11:28 AM, Osier Yang <jyang(a)redhat.com> wrote:
[...]
It's bad that we don't have sheepdog pool documented in [1]
when doing the patches. But the good thing is there are some
documents for it in [2]. If you see the document is not
enough. You can check the RNG schema to figure out the XMLs
the sheepdog pool supports.
$libvirt_source/docs/schemas/storagepool.rng
Or even you may want to have a look at the test files:
% grep -r sheepdog $libvirt_source/tests/storagepool*
Once you have a workable pool XML, you can test it via virsh
To see all the commands for pool and vol:
% virsh help pool
% virsh help volume
Note that sheepdog pool in libvirt only support small parts
of the operations though.
Hope it helps. And please don't hestimate pinging the list if
you find any problems.
[1] http://libvirt.org/formatstorage.html
[2] http://libvirt.org/storage.html
Hi Yang,
Thanks for your suggestions ;-)
Currently, i also have following questions.
1, What are the differences between Sheepdog pool and Sheepdog
storage volumes? Actually, what are the differences between
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=036ad5052b43fe9f0d19...
and
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=29bc4fe6460d80c2aca1...
?
2, I wanna test patch
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=036ad5052b43fe9f0d19...
and i have call back my libvirt git tree to the patch's commit version.
Could you please give me some suggestions for testing this patch?
3, Morita said if QEMU does not support Sheepdog then Libvirt will not
support Sheepdog but i am not clear about their communicating details.
Could you please tell me their communicating details?
Thanks in advance ;-)
--
Thanks
Harry Wei
7:32 a.m.
3, Morita said if QEMU does not support Sheepdog then Libvirt will not
support Sheepdog but i am not clear about their communicating details.
Could you please tell me their communicating details?
If QEMU doesn't officially support your file system, we cannot use
your system from VMs without applying your patch - libvirt shouldn't
support such kind of system. This is what I wanted to say, so I
suggested you to start from QEMU. I'm not sure how libvirt
maintainers think about this, though.
Thanks,
Kazutaka
7:36 a.m.
On Mon, Jan 28, 2013 at 10:32:42PM +0900, MORITA Kazutaka wrote:
>
> 3, Morita said if QEMU does not support Sheepdog then Libvirt will not
> support Sheepdog but i am not clear about their communicating details.
> Could you please tell me their communicating details?
If QEMU doesn't officially support your file system, we cannot use
your system from VMs without applying your patch - libvirt shouldn't
support such kind of system. This is what I wanted to say, so I
suggested you to start from QEMU. I'm not sure how libvirt
maintainers think about this, though.
I agree with that. I don't see this being a part of libvirt until
the QEMU community accepts it into the mainline QEMU GIT tree. So
I'd focus on the latter first.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
8:18 a.m.
On Mon, Jan 28, 2013 at 9:36 PM, Daniel P. Berrange <berrange(a)redhat.com> wrote:
[...]
I agree with that. I don't see this being a part of libvirt
until
the QEMU community accepts it into the mainline QEMU GIT tree. So
I'd focus on the latter first.
After HLFS has a good performance, we will submmit patches to QEMU&Libvirt
community. Thanks for your seggestions.
--
Thanks
Harry Wei
8:04 a.m.
On Mon, Jan 28, 2013 at 9:32 PM, MORITA Kazutaka
<morita.kazutaka(a)gmail.com> wrote:
>
> 3, Morita said if QEMU does not support Sheepdog then Libvirt will not
> support Sheepdog but i am not clear about their communicating details.
> Could you please tell me their communicating details?
If QEMU doesn't officially support your file system, we cannot use
your system from VMs without applying your patch - libvirt shouldn't
support such kind of system. This is what I wanted to say, so I
suggested you to start from QEMU. I'm not sure how libvirt
maintainers think about this, though.
Thanks for your suggestions. After HLFS has a good performance, we
will submmit our patches to QEMU&Libvirt community. Morita, i have
sent you a latest email named "How to test HLFS driver for Libvirt",
which you may give me some other suggestions. Thanks in advance ;-)
--
Thanks
Harry Wei
8:10 a.m.
On Mon, Jan 28, 2013 at 9:32 PM, MORITA Kazutaka
<morita.kazutaka(a)gmail.com> wrote:
>
> 3, Morita said if QEMU does not support Sheepdog then Libvirt will not
> support Sheepdog but i am not clear about their communicating details.
> Could you please tell me their communicating details?
If QEMU doesn't officially support your file system, we cannot use
your system from VMs without applying your patch - libvirt shouldn't
support such kind of system. This is what I wanted to say, so I
suggested you to start from QEMU. I'm not sure how libvirt
maintainers think about this, though.
Thanks for your suggestions. After HLFS has a good performance, we
will submmit our patches to QEMU&Libvirt community. Morita, i have
sent you a latest email named "How to test HLFS driver for Libvirt",
which you may give me some suggestions. Thanks in advance ;-)
--
Thanks
Harry Wei
4316
days inactive
4319
days old
7 comments
4 participants
participants (4)
-
Daniel P. Berrange -
harryxiyou -
MORITA Kazutaka -
Osier Yang