<br><br><div class="gmail_quote">2013/2/1 harryxiyou <span dir="ltr"><<a href="mailto:harryxiyou@gmail.com" target="_blank">harryxiyou@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Fri, Feb 1, 2013 at 6:14 PM, Gao Yongwei <<a href="mailto:itxx00@gmail.com">itxx00@gmail.com</a>> wrote:<br>
[...]<br>
<div><div class="h5">>> We can get "Boot VMs from sheepdog volumes in Libvirt" way<br>
>> from <a href="https://github.com/collie/sheepdog/wiki/Libvirt" target="_blank">https://github.com/collie/sheepdog/wiki/Libvirt</a> like following.<br>
>><br>
>> a, prepare a file containing an XML domain description<br>
>><br>
>> $ cat > sheepdog.xml<br>
>> <domain type='qemu'><br>
>> <name>testvm</name><br>
>> <memory>1048576</memory><br>
>> <os><br>
>> <type arch='x86_64'>hvm</type><br>
>> </os><br>
>> <devices><br>
>> <disk type='network'><br>
>> <source protocol="sheepdog" name="testvdi"/><br>
>> <target dev='hda' bus='ide'/><br>
>> </disk><br>
>> <graphics type='vnc' port='-1' autoport='yes'/><br>
>> </devices><br>
>> </domain><br>
>><br>
>> b, boot from testvdi with virsh<br>
>><br>
>> $ virsh create sheepdog.xml<br>
>><br>
>> c, connect to a VNC console of the running VM<br>
>><br>
>> $ vncviewer localhost<br>
>><br>
>> I have some following questions about up three steps.<br>
>><br>
>> 1, Before a or b(up boot step) step, should we have to install our OS<br>
>> into 'testvdi'?<br>
><br>
> As I know, you should install an OS in the disk,or cannot boot from a 'NULL'<br>
> disk.you know what i mean.<br>
><br>
<br>
</div></div>You just said with a common sense, which has no *real* help for me. *Please*<br>
see the step a then explain how to install os into testvdi. I think boot from<br>
VMs from Sheepdog volumes, which has to install OS into Sheepdog volumes.<br>
How should we install OS into Sheepdog volumes?</blockquote><div>soga,you may not understand my english,^^,if you can speak Chinese I think I can help you more comfortable.</div><div>I will try my best to share my experience.</div>
<div>to get a bootable disk with os installed, you could try this command:</div><div>wget <a href="http://wiki.qemu.org/download/linux-0.2.img.bz2">http://wiki.qemu.org/download/linux-0.2.img.bz2</a></div><div>bunzip2 linux-0.2.img.bz2</div>
<div>kvm-img convert -t directsync linux-0.2.img sheepdog:test </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
>><br>
>> That is to say, we have to install OS from os.iso file into 'testvdi',<br>
>> which should use<br>
>> 'qemu-system-x86_64' command to install OS, right?<br>
><br>
> To install an OS, you could use 'virt-install' ,or use the virt-manager GUI<br>
> tool.<br>
><br>
<br>
</div>Are you sure about your words? I think Step a boots VM from testvdi, which<br>
is a Sheepdog volume. You could use 'virt-install' to install a OS into Sheepdog<br>
volumes, like testvdi?<br>
<br>
BTW: Does 'virt-install' belong to Libvirt library source code? After i compile<br>
libvirt source code, i cannot find 'virt-install'.</blockquote><div>virt-install does not belong to libvirt,but if you use RHEL or CentOS you could install this tool from yum:</div><div>yum provides */virt-install</div>
<div>or you can get the source from <a href="http://virt-manager.org">virt-manager.org</a> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
>> 3, This is the storage online management in Libvirt, right?<br>
><br>
> later version of libvirt support managing sheepdog storage,use may have a<br>
> search at <a href="http://libvirt.org" target="_blank">libvirt.org</a>.<br>
><br>
<br>
</div>Have you ever booted a VM from Sheepdog volume? What steps did you<br>
do to finish this job?</blockquote><div>to boot a vm from sheep vol you can use command like:</div><div>kvm -hda sheepdog:test -hdb sheepdog:data</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">
>><br>
>> 4, This test just test the codes Morita take a patch named "add<br>
>> network disk support"<br>
>> for Libvirt, which is located here:<br>
>><br>
>> <a href="http://libvirt.org/git/?p=libvirt.git;a=commit;h=036ad5052b43fe9f0d197e89fd16715950408e1d" target="_blank">http://libvirt.org/git/?p=libvirt.git;a=commit;h=036ad5052b43fe9f0d197e89fd16715950408e1d</a><br>
>> and also test Sheepdog driver for QEMU, right?<br>
><br>
> I think just test libvirt environment..<br>
<br>
</div>You may not understand my question.<br>
<div class="im"><br>
<br>
>> 5, If i installed a 32bits OS to testvdi, should i modify<br>
>> <os><br>
>> <type arch='x86_64'>hvm</type><br>
>> </os><br>
>> to be<br>
>> <os><br>
>> <type arch='x86'>hvm</type><br>
>> </os><br>
>> , right?<br>
><br>
> If arch='x86_64', then this configuration support both x86 and x64.<br>
<br>
</div>What is *x64*? I am not clear about your words.<br>
<div class="im"><br>
>><br>
>> 6, The step c (up boot step), which is<br>
>> $ vncviewer localhost<br>
>> Actually, i am not clear about this 'localhost'. Why should we link<br>
>> localhost but other ip addresses?<br>
><br>
> As localhost allways singed to 127.0.0.1 ,or you can use 127.0.0.1 instead<br>
> of a name like 'locallhost'.<br>
><br>
<br>
</div>I just ask why we should link localhost. *NOT* what is localhost. You may not<br>
understand my question.<br>
<br>
Thanks for your suggestions.</blockquote><div>because VM's default vnc configuration in libvirt xml just binding the vnc port to 127.0.0.1,you can change the default ip address of vnc using virsh:</div><div>virsh edit testvm </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888"><br>
--<br>
Thanks<br>
Harry Wei<br></font></span></blockquote><div><br></div><div> </div></div><br>