dear virt-manger community, moreover, the virtual disk size is dynamically expanded.
just FYI thanks, david su On Sat, Nov 17, 2012 at 11:07 PM, Qiubo Su (David Su) <[email protected]>wrote: > dear virt-manager community, > > the 40GB is the virtual size of the image.vdi image, while the 1.3GB is > the acutal size of the image.vdi image. > > just FYI. > > thanks, > david su > > > On Sat, Nov 17, 2012 at 10:40 PM, Qiubo Su (David Su) > <[email protected]>wrote: > >> dear virt-manager team, >> >> i run "VBoxManage clonehd --format RAW image.vdi image.img" to convert >> the virtualbox .vdi vm instance to raw format, and with virt-manager to >> create new vm with the raw format, it works fine, i.e. can start the new vm >> instance successfully and the networking access is the same as before. >> >> but after run "qemu-img convert -f raw image.img -O qcow2 image.qcow" to >> convert the raw format to qcow2 format, and with virt-manager to create new >> vm with the qcow2 format, it doesn't work, i.e. get "no bootable device" >> error when start the new vm with qcow2 format, no need to say the >> networking access. >> >> the size of the ram format disk is about 40GB, while the size of the >> qcow2 format disk is about 1.3GB (similar as that of the original image.vdi >> size), nearly 30 times smaller than the raw format. >> >> if not convert the raw format to qcow2 format, then the disk size is too >> large, waste of disk space. >> >> there are ubuntu 12.04, opennebula 3.6.0, and kvm, qemu, libvirt etc >> installed. >> >> it is much appreciated if you can help with this. >> >> thanks, >> david su >> >> >> On Thu, Nov 15, 2012 at 10:48 PM, Qiubo Su (David Su) >> <[email protected]>wrote: >> >>> dear virt-manager team, >>> >>> i have some applications (e.g. web hosting system and VOIP telephony >>> system) installed in the virtualbox vm instances (with bridged adapter for >>> networking), but since i set up the opennebula cloud system with kvm >>> hypervisor, i have been trying to migrate these virtualbox vm instances to >>> under kvm hypervisor. i run "qemu-img convert virtualboximage.vdi -O >>> qcow2 kvmimage.qcow" to get vm instance under kvm hypervisor. but when i >>> tried to use virt-manager (corresponding to virtualbox) to import the >>> kvmimage.qcow (as the virtualboximage.vdi in the virtualbox) and configure >>> everything for the kvmimage.qcow vm instance, and then run this vm instance >>> under virt-manager, it is unbootable. the attached file is the screenshot >>> when this vm instance is booting. >>> >>> it is much appreciated if anyone can let me know the correct procedure >>> to convert the virtualbox vm instance to kvm vm instance, to import the >>> disk image to virt-manager, to configure this vm instance in the >>> virt-manager, to make it starts successfully and networking access >>> correctly as well. >>> >>> thanks, >>> david su >>> >> >> >
_______________________________________________ virt-tools-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-tools-list
