Hi all,
When i compiled libvirt like following
1. git clone git://libvirt.org/libvirt.git；cd libvirt
2. git reset --hard v1.0.1
3. wget
http://cloudxy.googlecode.com/svn/branches/hlfs/person/harry/hlfs/patches/hlfs_driver_for_libvirt_network_disk.patch
4. wget
On Wed, Feb 27, 2013 at 11:04 AM, Eric Blake ebl...@redhat.com wrote:
[...]
You trimmed too much of your make line to tell us what was happening.
It might also help to run 'make V=1' to get the full command line being
attempted. I have to wonder if you have an unexpanded '$JAVA_HOME'
injected
On Thu, Feb 28, 2013 at 12:47 AM, Eric Blake ebl...@redhat.com wrote:
[...]
What a waste of resources - that forks a shell to do an echo every time
that you use ${JVM_DIR}. Much simpler to write as:
JVM_DIR=${JAVA_HOME}
I am not familiar with automake so i just use shell to finish this job.
On Tue, Mar 5, 2013 at 11:15 PM, Guannan Ren g...@redhat.com wrote:
Hi Guannan,
I met this problem yesterday too, but now, it is fixed.
you can try again.
We have to reset libvirt git tree to libvirt v1.0.1 so that our patches work
well. Therefore, could you please tell us the
On Wed, Mar 6, 2013 at 11:35 PM, Guannan Ren g...@redhat.com wrote:
[...]
I am not quite sure it was fixed by a patch.
It probably caused by gnulib git server problem(I guess)
I just tried just now, it worked well.
Ok, thanks very much ;-)
--
Thanks
Harry Wei
--
libvir-list
On Fri, Feb 8, 2013 at 4:07 PM, Michal Privoznik mpriv...@redhat.com wrote:
On 07.02.2013 16:19, Stefan Hajnoczi wrote:
I have created the Google Summer of Code 2013 wiki page where you can
add project ideas:
http://wiki.qemu.org/Google_Summer_of_Code_2013
Please add project ideas you are
Hi all,
I copy portions of libvirt/src/storage/storage_backend_sheepdog.c
[...]
125 ret = virCommandRun(cmd, NULL);
126 if (ret == 0)
127 ret = virStorageBackendSheepdogParseNodeInfo(pool-def, output);
[...]
I found virCommandRun may return '-1', which hinds something error
On Thu, Apr 11, 2013 at 9:38 PM, Michal Privoznik mpriv...@redhat.com wrote:
[...]
Maybe you've pasted wrong code snippet, but the one you've pasted is
correct. If virCommandRun() fails and returns -1; we return that value
to the caller. And if the command doesn't fail, we call
From: Harry Wei harryxi...@gmail.com
virCommandNewArgList may return NULL so we need not
do following stuffs and just return '-1'.
Signed-off-by: Harry Wei harryxi...@gmail.com
CC: Osier Yang jy...@redhat.com
CC: Michal Privoznik mpriv...@redhat.com
---
src/storage/storage_backend_sheepdog.c |
On Thu, Apr 11, 2013 at 10:26 PM, Eric Blake ebl...@redhat.com wrote:
Hi Eric,
[...]
Not necessary. virCommand is DESIGNED for streamlined usage, so that it
is much easier to read how the command is constructed without being
distracted by error checking in the caller every step of the way.
On Thu, Apr 11, 2013 at 11:03 PM, Eric Blake ebl...@redhat.com wrote:
[...]
No need. You are talking about the error path, the one that only hits
on the RARE case of OOM. If we are OOM, we are already hosed - what
does it matter if we take a few extra calls to a few more virCommand*()
On Thu, Apr 11, 2013 at 10:59 PM, Daniel P. Berrange
berra...@redhat.com wrote:
[...]
The question of efficiency is irrelevant in this context. We are
explicitly choosing to prioritize reliability and readability of
the code here.
ACK.
--
Thanks
Harry Wei
--
libvir-list mailing list
Hi all,
I am not very clear about the usage of ‘virsh vol-wipe vol_name’. I think
if 'virsh vol-wipe vol_name' can just wipe all the datas in this volume and
it is similar as we format a volume which the datas would be wiped, right?
After this wipe, we can use this volume like a new one.
On Fri, Apr 12, 2013 at 10:22 AM, harryxiyou harryxi...@gmail.com wrote:
Hi all,
I am not very clear about the usage of ‘virsh vol-wipe vol_name’. I think
if 'virsh vol-wipe vol_name' can just wipe all the datas in this volume and
it is similar as we format a volume which the datas would
On Fri, Apr 12, 2013 at 10:22 AM, harryxiyou harryxi...@gmail.com wrote:
Hi all,
I am not very clear about the usage of ‘virsh vol-wipe vol_name’. I think
if 'virsh vol-wipe vol_name' can just wipe all the datas in this volume and
it is similar as we format a volume which the datas would
On Fri, Apr 12, 2013 at 1:07 PM, Osier Yang jy...@redhat.com wrote:
[...]
Not sure if you planned to request separate projects for these, but I don't
think it's deserved for separate projects. They can be just one project,
as the work need to do for them is similar.
Sure, they are a whole
On Fri, Apr 12, 2013 at 12:42 PM, Osier Yang jy...@redhat.com wrote:
Hi Osier,
On Fri, Apr 12, 2013 at 10:22 AM, harryxiyou harryxi...@gmail.com wrote:
Hi all,
I am not very clear about the usage of ‘virsh vol-wipe vol_name’. I think
if 'virsh vol-wipe vol_name' can just wipe all
On Fri, Apr 12, 2013 at 12:39 PM, Osier Yang jy...@redhat.com wrote:
[...]
The command is there, and the docs is there too. So you already had the
guide, why not to try it?
Thanks, i will.
Could anyone please give me some suggestions? Thanks in advance.
However, if users just want to
On Fri, Apr 12, 2013 at 2:34 PM, Michal Privoznik mpriv...@redhat.com wrote:
Hi Michal,
I am not sure we want *rename virsh commands. Not only for storage, but
in general. And even if we do want these, they don't require a new API.
They can be implemented with simple vir*GetXML();
On Fri, Apr 12, 2013 at 2:34 PM, Michal Privoznik mpriv...@redhat.com wrote:
Hi Michal,
I am not sure we want *rename virsh commands. Not only for storage, but
in general. And even if we do want these, they don't require a new API.
They can be implemented with simple vir*GetXML();
Hi Osier,
From the actual bug messages like fowllowing
Actual results:
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/createvol.py, line 191,
in _async_vol_create
poolobj = self.vol.install(meter=meter)
File
On Fri, Apr 12, 2013 at 5:20 PM, Osier Yang jy...@redhat.com wrote:
On 12/04/13 16:02, harryxiyou wrote:
Hi Osier,
From the actual bug messages like fowllowing
Actual results:
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/createvol.py, line 191
On Fri, Apr 12, 2013 at 11:29 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
[...]
Michal said earlier that virsh vol-move seemed too small a task.
Do you think that these 4 tasks together merit a 12-week project?
Yes, these 4 tasks should be a whole project which may merit
almost a 12-week
On Fri, Apr 12, 2013 at 11:47 PM, harryxiyou harryxi...@gmail.com wrote:
On Fri, Apr 12, 2013 at 11:29 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
[...]
Michal said earlier that virsh vol-move seemed too small a task.
Do you think that these 4 tasks together merit a 12-week project?
Yes
On Fri, Apr 12, 2013 at 11:47 PM, harryxiyou harryxi...@gmail.com wrote:
On Fri, Apr 12, 2013 at 11:29 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
[...]
Michal said earlier that virsh vol-move seemed too small a task.
Do you think that these 4 tasks together merit a 12-week project?
Yes
On Fri, Apr 12, 2013 at 11:57 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
[...]
Right, I'm trying to check with danpb, mprivozn, eblake, and osier
whether these tasks are worthy of a 12-week project.
There needs to be agreement here before we can add this as a project
idea to the GSoC wiki
On Sat, Apr 13, 2013 at 1:35 PM, Osier Yang jy...@redhat.com wrote:
On 13/04/13 00:05, harryxiyou wrote:
On Fri, Apr 12, 2013 at 11:57 PM, Stefan Hajnoczi stefa...@gmail.com
wrote:
[...]
Right, I'm trying to check with danpb, mprivozn, eblake, and osier
whether these tasks are worthy
On Fri, Apr 12, 2013 at 11:29 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Apr 12, 2013 at 10:58 AM, Daniel P. Berrange
berra...@redhat.com wrote:
On Fri, Apr 12, 2013 at 08:34:18AM +0200, Michal Privoznik wrote:
On 10.04.2013 15:13, harryxiyou wrote:
Hi all,
I've also got
On Mon, Apr 15, 2013 at 5:13 PM, Daniel P. Berrange berra...@redhat.com wrote:
[...]
I'm not hugely comfortable with the idea of capability support being
done by a student. IMHO to do a good job on that design-wise requires
someone with a very good understanding of libvirt architecture
On Mon, Apr 15, 2013 at 9:43 PM, harryxiyou harryxi...@gmail.com wrote:
On Mon, Apr 15, 2013 at 5:13 PM, Daniel P. Berrange berra...@redhat.com
wrote:
[...]
I'm not hugely comfortable with the idea of capability support being
done by a student. IMHO to do a good job on that design-wise
On Mon, Apr 15, 2013 at 11:00 PM, Osier Yang jy...@redhat.com wrote:
On 15/04/13 22:41, harryxiyou wrote:
On Mon, Apr 15, 2013 at 9:43 PM, harryxiyou harryxi...@gmail.com wrote:
On Mon, Apr 15, 2013 at 5:13 PM, Daniel P. Berrange berra...@redhat.com
wrote:
[...]
I'm not hugely comfortable
On Mon, Apr 15, 2013 at 10:56 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
[...]
A project must be a 12-week effort. Are you saying you'd like to
focus on just capability support for 12 weeks?
Yup, after i read the comments from Danpb and Osier, i find Renaming all
APIs is more comfortable
On Mon, Apr 15, 2013 at 10:55 PM, Daniel P. Berrange
berra...@redhat.com wrote:
[...]
Enthusiasm of the students to learn libvirt isn't the only consideration.
The project mentors have to put non-trivial effort into GSoC and want to
have some level of confidence that the project will result in
On Tue, Apr 16, 2013 at 12:22 AM, Eric Blake ebl...@redhat.com wrote:
[...]
This indeed feels like a reasonable project, where there is enough work
to do to fill up 12 weeks of good effort while still having something
measurable to commit, and where the design is known enough in advance
that
On Mon, Apr 15, 2013 at 11:28 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
[...]
I asked because it seems like a very mechanical and relatively short
thing to work on.
If you still think the scope is good, then please add the project idea
to the GSoC wiki using this template:
On Tue, Apr 16, 2013 at 12:22 AM, Eric Blake ebl...@redhat.com wrote:
On 04/15/2013 09:16 AM, harryxiyou wrote:
I could be if you want, but the question is which project you are focusing
on? This one or the renaming APIs? And as far as I got from the wiki page,
we generally don't want
On Tue, Apr 16, 2013 at 10:39 PM, harryxiyou harryxi...@gmail.com wrote:
On Tue, Apr 16, 2013 at 12:22 AM, Eric Blake ebl...@redhat.com wrote:
On 04/15/2013 09:16 AM, harryxiyou wrote:
I could be if you want, but the question is which project you are focusing
on? This one or the renaming APIs
From: Harry Wei harryxi...@gmail.com
Vol-rename is a convenience function, requiring when
one wanna rename a volume name.
Signed-off-by: Harry Wei harryxi...@gmail.com
---
tools/virsh-volume.c | 103 ++
1 file changed, 103 insertions(+)
diff
On Thu, Apr 18, 2013 at 5:27 PM, Osier Yang jy...@redhat.com wrote:
On 18/04/13 16:29, harryxi...@gmail.com wrote:
From: Harry Wei harryxi...@gmail.com
Vol-rename is a convenience function, requiring when
one wanna rename a volume name.
NACK. It should use the upcoming rename APIs for the
On Thu, Apr 18, 2013 at 5:30 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Thu, Apr 18, 2013 at 04:29:45PM +0800, harryxi...@gmail.com wrote:
From: Harry Wei harryxi...@gmail.com
Vol-rename is a convenience function, requiring when
one wanna rename a volume name.
Signed-off-by: Harry
On Thu, Apr 18, 2013 at 11:03 PM, Eric Blake ebl...@redhat.com wrote:
[...]
Exactly - we need to add a new libvirt API that can support renames at
the backend driver level, with instant effect (a directory pool
forwarding to rename(2), other pools using pool-specific renaming commands).
It
On Fri, Apr 19, 2013 at 1:42 PM, Osier Yang jy...@redhat.com wrote:
[...]
There is no new things in the wiki.
Sorry, i have not put my new design plan for 'Rename volume name'.
Before writing the code, I'd suggest going through the HACKING
and the document for how to implement a new API for
From: Harry Wei harryxi...@gmail.com
After i read libvirt/HACKING file, i find we should
Omit braces with a single-line body. So this patch
fix this coding style problem for Sheepdog storage
backend driver.
Signed-off-by: Harry Wei harryxi...@gmail.com
---
src/storage/storage_backend_sheepdog.c
On Mon, Apr 22, 2013 at 9:13 PM, Osier Yang jy...@redhat.com wrote:
On 22/04/13 20:33, harryxi...@gmail.com wrote:
From: Harry Wei harryxi...@gmail.com
After i read libvirt/HACKING file, i find we should
s/i/I/,
Actually, i wonder what 's/i/l/' means?
Omit braces with a single-line
On Mon, Apr 22, 2013 at 10:33 PM, Eric Blake ebl...@redhat.com wrote:
[...]
It's capital 'I', not lower case 'l'. That's shorthand using sed syntax
for an in-place replacement you should perform on your text. It means
you should have written:
After I read libvirt/HACKING file, I find we
Hi all,
I wanna add a new block storage driver by Libvirt/Qemu way for Openstack, which
is as same as Sheepdog driver for Openstack. So i think the theories
are like this.
1, In the Openstack Nova branch, Openstck driver call libvirt client
and send parameters
to libvirt client.(From this point,
On Sat, Jan 19, 2013 at 10:04 PM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
At Sat, 19 Jan 2013 16:47:37 +0800,
[...]
If you do the above work, I think you can use your file system with
OpenStack.
Thanks for your review ;-)
But I suggest doing them step by step. If your file system
Hi all,
I read the source code of Openstack Nova branch source codes but i
can not find the standard libvirt library packages, which i think
Nova uses libvirt
interfaces they are from standard libvirt library to attach Sheepdog(or others)
volumes to QEMU. If i add a new block storage driver for
On Mon, Jan 21, 2013 at 8:14 PM, Daniel P. Berrange berra...@redhat.com wrote:
[...]
The nova driver for talking to libvirt is in nova/virt/libvirt/
Yup, i think so. Therefore, i also think nova driver in nova/virt/libvirt
has some relationships with libvirt code itself, right? Nova driver
send
On Tue, Jan 22, 2013 at 12:20 AM, Daniel P. Berrange
berra...@redhat.com wrote:
[...]
Nova simply uses the standard libvirt python module, which is a thin
python wrapper around the libvirt.so C library.
I think so, but i wonder if the standard libvirt python module is
On Tue, Jan 22, 2013 at 1:10 AM, Daniel P. Berrange berra...@redhat.com wrote:
[...]
That isn't the libvirt python module. That is Nova's libvirt integration
driver code.
That is to say, libvirt.so is from standard libvirt code itself and libvirt
python module is from libvirt.so.
On Tue, Jan 22, 2013 at 9:21 AM, longeek mengql112...@gmail.com wrote:
Hi friends,
Hi Meng,
the python interface of libvirt maybe help you, because openstack uses it in
nova/virt/libvirt/
If openstack use it direactly, how to call these interface effectively? I think
Nova should place
On Sat, Jan 19, 2013 at 10:04 PM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
[...]
If you do the above work, I think you can use your file system with
OpenStack.
But I suggest doing them step by step. If your file system is not
supported in QEMU, I think libvirt won't support it. If
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
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On Fri, Jan 25, 2013 at 9:37 PM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
[...]
Libvirt documentation contains an example XML format for Sheepdog.
http://libvirt.org/formatdomain.html#elementsDisks
Thanks, let me have a try ;-)
You're CCing too many lists which is not appropriate
Hi Morita,
I just wanna test if sheepdog works well in libvirt. I am not sure if
i can only use
libvirt environment to finish this test? Or maybe i should also set up
QEMU/Sheepdog/Openstack environment, right? I have done following jobs.
1, git clone git://libvirt.org/libvirt.git
2, cd libvirt
On Sun, Jan 27, 2013 at 5:52 PM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
[...]
I wrote a minimum guide to use sheepdog volumes from virsh. Hope it
would help you:
https://github.com/collie/sheepdog/wiki/Libvirt
Hmmm..., let me have a try, thanks for your jobs.
libvirt-list is a
On Sun, Jan 27, 2013 at 6:24 PM, harryxiyou harryxi...@gmail.com wrote:
On Sun, Jan 27, 2013 at 5:52 PM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
[...]
I wrote a minimum guide to use sheepdog volumes from virsh. Hope it
would help you:
https://github.com/collie/sheepdog/wiki/Libvirt
Hi Daniel and other developers,
We have programed a HLFS(HDFS based Log-Structured FileSystem)
driver for QEMU, which you can see it here.
http://cloudxy.googlecode.com/svn/trunk/hlfs/patches/hlfs_driver_for_qemu_1.3.0.patch
And i have tested in QEMU environment, which works well for us.
Now, we
On Sun, Jan 27, 2013 at 11:14 PM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
At Sun, 27 Jan 2013 20:46:15 +0800,
harryxiyou wrote:
On Sun, Jan 27, 2013 at 6:24 PM, harryxiyou harryxi...@gmail.com wrote:
On Sun, Jan 27, 2013 at 5:52 PM, MORITA Kazutaka
morita.kazut...@gmail.com wrote
On Mon, Jan 28, 2013 at 12:43 AM, harryxiyou harryxi...@gmail.com wrote:
[...]
I also have two questions.
1, Before create Sheepdog volume by virsh command, i must build Sheepdog
and libvirt environment, right?
2, There are all the commit logs of Sheepdog, which can be found here.
http
On Mon, Jan 28, 2013 at 12:55 AM, harryxiyou harryxi...@gmail.com wrote:
On Mon, Jan 28, 2013 at 12:43 AM, harryxiyou harryxi...@gmail.com wrote:
[...]
I also have two questions.
1, Before create Sheepdog volume by virsh command, i must build Sheepdog
and libvirt environment, right?
2
Hi Morita and other developers,
I have done following jobs.
1, git clone git://libvirt.org/libvirt.git
2, cd libvirt
3, git reset --hard 036ad50
4, ./autogen.sh
5, make
NOTE: step 3 calls back to Morita's patch for Libvirt version, which is here
On Mon, Jan 28, 2013 at 11:04 AM, harryxiyou harryxi...@gmail.com wrote:
Hi Morita and other developers,
I have done following jobs.
1, git clone git://libvirt.org/libvirt.git
2, cd libvirt
3, git reset --hard 036ad50
4, ./autogen.sh
5, make
NOTE: step 3 calls back to Morita's patch
On Mon, Jan 28, 2013 at 11:28 AM, Osier Yang jy...@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
On Mon, Jan 28, 2013 at 9:32 PM, MORITA Kazutaka
morita.kazut...@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
On Mon, Jan 28, 2013 at 9:32 PM, MORITA Kazutaka
morita.kazut...@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
On Mon, Jan 28, 2013 at 9:36 PM, Daniel P. Berrange berra...@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
On Mon, Jan 28, 2013 at 10:44 PM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
[...]
I'm not familiar with HLFS at all. Sheepdog examples I explained to
you in another mail may help you, but I cannot give you any other
suggestions about HLFS.
Thanks for your reminder, i have found this
On Mon, Jan 28, 2013 at 11:06 PM, harryxiyou harryxi...@gmail.com wrote:
On Mon, Jan 28, 2013 at 10:44 PM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
[...]
I'm not familiar with HLFS at all. Sheepdog examples I explained to
you in another mail may help you, but I cannot give you any
On Mon, Jan 28, 2013 at 11:23 PM, harryxiyou harryxi...@gmail.com wrote:
On Mon, Jan 28, 2013 at 11:06 PM, harryxiyou harryxi...@gmail.com wrote:
On Mon, Jan 28, 2013 at 10:44 PM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
[...]
I'm not familiar with HLFS at all. Sheepdog examples I
On Tue, Jan 29, 2013 at 12:05 AM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
At Mon, 28 Jan 2013 23:43:04 +0800,
harryxiyou wrote:
Following test is Libvirt v0.8.6, which you just add Sheepdog volume
patch to Libvirt.
The version doesn't support Sheepdog storage pool and volume
On Tue, Jan 29, 2013 at 8:18 AM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
[...]
I've looked at the upstream tree, but it certainly contains sheepdog
codes.
http://libvirt.org/git/?p=libvirt.git;a=tree;f=src/storage
Sorry, my libvirt git tree was not the latest one, which may not
On Tue, Jan 29, 2013 at 12:05 AM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
At Mon, 28 Jan 2013 23:43:04 +0800,
harryxiyou wrote:
Following test is Libvirt v0.8.6, which you just add Sheepdog volume
patch to Libvirt.
The version doesn't support Sheepdog storage pool and volume
On Tue, Jan 29, 2013 at 8:55 PM, harryxiyou harryxi...@gmail.com wrote:
On Tue, Jan 29, 2013 at 12:05 AM, MORITA Kazutaka
morita.kazut...@gmail.com wrote:
At Mon, 28 Jan 2013 23:43:04 +0800,
harryxiyou wrote:
Following test is Libvirt v0.8.6, which you just add Sheepdog volume
patch
Hi Sebastian, Morita and other developers,
I have studied Sheepdog pool/volume storage driver for libvirt and i have
following questions. Please give me some suggestions. Thanks in advance ;-)
1, In libvirt/src/storage/storage_backend_sheepdog.c, i just find we realized
create/delete/resize
On Wed, Jan 30, 2013 at 2:49 AM, Eric Blake ebl...@redhat.com wrote:
On 01/29/2013 10:42 AM, harryxiyou wrote:
Hi Sebastian, Morita and other developers,
Answering what I can...
Eric, thanks for your answers, you are awesome ;-)
And i have some questions about your answers like following.
3
On Thu, Jan 31, 2013 at 2:52 AM, Eric Blake ebl...@redhat.com wrote:
[...]
Pastebin links expire, making it harder to follow the conversation when
revisiting the list archives in the future. It is okay to paste the
actual error into the message rather than making people chase through a
link.
On Thu, Jan 31, 2013 at 4:19 PM, Claudio Bley cb...@av-test.de wrote:
[...]
AFAIK, the DTD files are not required, they are just used to validate
the generated HTML files.
Apparently, xsltproc is broken since there's a mismatch with its
libraries. Why is xsltproc installed in /usr but the
On Thu, Jan 31, 2013 at 3:05 AM, Eric Blake ebl...@redhat.com wrote:
[...]
There's two aspects to storage management in libvirt.
Eric, very thanks for your perfectly answers ;-)
[...]
But without at least one online user (qemu), it
doesn't make sense to worry about offline management in
Hi all,
Morita added network disk support for Libvirt, which supported
nbd, rbd, sheepdog, and other protocols. Now, i wanna test
network disk support for sheepdog solely. I have following questions.
Could anyone please give me some suggestions? Thanks in advance.
1, Before this test, whether
On Thu, Jan 31, 2013 at 2:52 AM, Eric Blake ebl...@redhat.com wrote:
[...]
[...]
/usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information
available (required by /usr/lib/libxslt.so.1)
/usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information
available (required
On Fri, Feb 1, 2013 at 1:18 AM, Eric Blake ebl...@redhat.com wrote:
[...]
Libvirt exists to manage existing hypervisor capabilities. It makes no
sense for libvirt to be able to create storage volumes for a new
protocol if there are no hypervisors that are also able to support that
storage
Hi all,
We can get Boot VMs from sheepdog volumes in Libvirt way
from https://github.com/collie/sheepdog/wiki/Libvirt like following.
a, prepare a file containing an XML domain description
$ cat sheepdog.xml
domain type='qemu'
nametestvm/name
memory1048576/memory
On Fri, Feb 1, 2013 at 12:06 PM, MORITA Kazutaka
morita.kazut...@lab.ntt.co.jp wrote:
[...]
1. prepare a file containing an XML domain description
$ cat sheepdog.xml
domain type='qemu'
nametestvm/name
memory1048576/memory
os
type arch='x86_64'hvm/type
/os
Hi all,
I wanna boot VMs from sheepdog volumes so i do according to
https://github.com/collie/sheepdog/wiki/Libvirt
However, some errors happened to me like following.
$ ./virsh create os.xml
error：create domain from os.xml failure
error：(domain_definition):14: Premature end of data in tag
On Fri, Feb 1, 2013 at 6:14 PM, Gao Yongwei itx...@gmail.com wrote:
[...]
We can get Boot VMs from sheepdog volumes in Libvirt way
from https://github.com/collie/sheepdog/wiki/Libvirt like following.
a, prepare a file containing an XML domain description
$ cat sheepdog.xml
On Sat, Feb 2, 2013 at 12:49 AM, Eric Blake ebl...@redhat.com wrote:
On 02/01/2013 04:08 AM, harryxiyou wrote:
Hi all,
I wanna boot VMs from sheepdog volumes so i do according to
https://github.com/collie/sheepdog/wiki/Libvirt
However, some errors happened to me like following.
$ ./virsh
On Sat, Feb 2, 2013 at 1:33 AM, Gao Yongwei itx...@gmail.com wrote:
[...]
soga,you may not understand my english,^^,if you can speak Chinese I think I
can help you more comfortable.
I will try my best to share my experience.
to get a bootable disk with os installed, you could try this command:
Hi all,
After i clone libvirt git repo, how i could get this libvirt version exactly?
$ git clone git://libvirt.org/libvirt.git
$ git branch -a
* master
remotes/origin/HEAD - origin/master
remotes/origin/master
remotes/origin/v0.10.2-maint
remotes/origin/v0.9.11-maint
Hi all,
I see our libvirt snapshot XML form like following, which this
XML is to create a disk snapshot of just vda on a qemu domain
with two disks.
domainsnapshot
descriptionSnapshot of OS install and updates/description
disks
disk name='/path/to/old'
source file='/path/to/new'/
On Sat, Feb 2, 2013 at 9:49 PM, Matthias Bolte
matthias.bo...@googlemail.com wrote:
[...]
You can look at the AC_INIT line in configure.ac
AC_INIT([libvirt], [1.0.2], [libvir-list@redhat.com], [],
[http://libvirt.org])
the second argument is the latest released version.
This is just the
Hi all,
I wanna test start a snapshot of Sheepdog volume in Libvirt. However, i
cannot find a test description from
https://github.com/collie/sheepdog/wiki/Libvirt.
From http://libvirt.org/formatsnapshot.html, i can find some snapshot
operations
in Libvirt, which may be different from Sheepdog
Hi all,
I test libvirt boots QEMU VM from Sheepdog snapshot image by specify
snapshot id like following.
1, $ collie vdi list
NameIdSizeUsed SharedCreation time VDI id Copies Tag
Alice1 10 GB 1.3 GB 0.0 MB 2013-02-01 18:59 15d167
2
s testvdi 1 20
On Tue, Feb 5, 2013 at 4:49 AM, Eric Blake ebl...@redhat.com wrote:
[...]
For an offline guest, libvirt does not yet drive 'collie' to create any
sheepdog snapshots; I don't know if 'qemu-img' has that capability
either. In other words, you are treading on frontier territory, where
you may
On Tue, Feb 5, 2013 at 4:31 AM, Eric Blake ebl...@redhat.com wrote:
[...]
I'm not that familiar with sheepdog, but I'll give it a shot:
id 1 is a static point in time. But you booted your guest, which means
you have made modifications since that point in time. Those
modifications have to be
Hi all,
In libvirt/src/storage/storage_backend_sheepdog.c file, func
virStorageBackendSheepdogCreateVol calls func
virStorageBackendSheepdogRefreshVol to refresh Sheepdog volume infos.
But we do not check func virStorageBackendSheepdogRefreshVol's return
value. Following patch can fix this bug.
On Wed, Feb 6, 2013 at 11:19 PM, Eric Blake ebl...@redhat.com wrote:
[...]
Thanks for attempting a patch. However, the commit message is
unconventionally formatted; did you use 'git send-email' to send your
patch, as suggested in HACKING? We would have to amend the message to
get rid of the
---
src/storage/storage_backend_sheepdog.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/src/storage/storage_backend_sheepdog.c
b/src/storage/storage_backend_sheepdog.c
index cd18f33..2cbfe01 100644
--- a/src/storage/storage_backend_sheepdog.c
+++
Signed-off-by: Harry Wei harryxi...@gmail.com
---
src/storage/storage_backend_sheepdog.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/src/storage/storage_backend_sheepdog.c
b/src/storage/storage_backend_sheepdog.c
index cd18f33..2cbfe01 100644
---
1 - 100 of 118 matches
Mail list logo
