[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] !!!!help!Problem with qcow2 image during a PVM's setting up




I have seen that there is a file called block-qcow2.c in blktap/drives  and I just would like to use it.So I have to use the type of para-virtualized machines.Do you mean xcp could help me create a pvm whose image file is based on some backing  file and whose image file format is qcow2?




At 2012-12-29 10:52:59,"Andrew Wells" <agwells0714@xxxxxxxxx> wrote:
That part I cannot help with to much, google converting said images. Also are you starting with fresh images? Xcp can import other vm types.

On Friday, December 28, 2012, hxkhust wrote:

First of all ,thank you very mouch .Then I have never used the XCP.Is its source code similar to xen?qemu-img ,qemu-img-xen ,qcow2-create these three tools ,which one should I choose? 




At 2012-12-29 03:05:17,"Andrew Wells" <agwells0714@xxxxxxxxx> wrote:

Use Xcp and qemu image converter

On Dec 28, 2012 10:13 AM, "hxkhust" <hxkhust@xxxxxxx> wrote:
The following was what  I did.
1) dd if=/dev/zero of =centos_raw.img bs=1024 count=8000000
2) install the os centos 5.5 x64 in the image file centos_raw.img and the correspongding config file is :
kernel = "/home/pvm/vmlinuz-2.6.18-194.el5xen"
ramdisk = "/home/pvm/initrd-2.6.18-194.el5xen.img"
memory = 768
#maxmem = 768
name = "centos_raw_pv"
vcpus = 1
vif = ['mac=00:24:7C:3C:CE:EF,bridge=eth0']
disk = ['tap:aio:/home/pvm/centos_raw.img,xvda,w']
root = "/dev/xvda1 ro"

3) qemu-img-xen create -b centos_raw.img -f qcow2 centos_raw_qcow2_1.img 5G
4) xm create centos_raw_qcow2_1.cfg and the centos_raw_qcow2_1.cfg is just like this:
kernel = "/home/pvm/vmlinuz-2.6.18-194.el5xen"
ramdisk = "/home/pvm/initrd-2.6.18-194.el5xen.img"
memory = 768
name = "centos_raw_qcow2_1_pv"
vcpus = 1
vif = ['mac=00:24:7C:3C:C1:EF,bridge=eth0']
disk = ['tap:qcow2:/home/pvm/centos_raw_qcow2_1.img,xvda,w']
root = "/dev/xvda1 ro"

 
however I'm failed.the error message after the above command is entered is :
Using config file "./centos_raw_qcow2_1.cfg".
Error: Device 51712 (tap) could not be connected.Setting up the backend failed. See the log files in /var/log/xen/ for details.
 
So I have tried another way.
after I install centos in centos_raw.img, I did the following:
qemu-img-xen convert -O qcow2 centos_raw.img centos_qcow2.img
here this image file centos_qcow2.img can be running normally with the config file :
kernel = "/home/pvm/vmlinuz-2.6.18-194.el5xen"
ramdisk = "/home/pvm/initrd-2.6.18-194.el5xen.img"
memory = 768
name = "centos_raw_pv"
vcpus = 1
vif = ['mac=00:24:7C:3C:CE:EF,bridge=eth0']
disk = ['tap:qcow2:/home/pvm/centos_qcow2.img,xvda,w']
root = "/dev/xvda1 ro"

 
Then I input the command below:
qemu-img-xen create -b centos_qcow2.img -f qcow2 centos_qcow2_qcow2.img 5G
and I edit  the config file centos_qcow2_qcow2.cfg:
kernel = "/home/pvm/vmlinuz-2.6.18-194.el5xen"
ramdisk = "/home/pvm/initrd-2.6.18-194.el5xen.img"
memory = 768
name = "centos_qcow2_qcow2_pv"
vcpus = 1
vif = ['mac=00:24:7C:3C:CE:1F,bridge=eth0']
boot="c"
disk = ['tap:qcow2:/home/pvm/centos_qcow2_qcow2.img,sda,w']
root = "/dev/sda1 ro"

 
and implement the command:
xm create centos_qcow2_qcow2.cfg
 
but what was posted were:
Using config file "./centos_qcow2_qcow2.cfg".
Error: Device 2048 (tap) could not be connected.Setting up the backend failed. See the log files in /var/log/xen/ for details.
 
I need to run a para-virtualized machine whose image file is qcow2 format and is based on another  image file.What can i do with this?I need your help.
In fact,I have no way to go through.My boss just now tell me that if I could not overcome this problem ,the only thing I could do is to die.HELP!
ANY suggestion would be fine!





_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users




_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.