Is it a good idea to use qcow2 format to have a backup image for whole disk with partition table?
I'm not sure that an image with partition table will be able to mount normally and in the same time it will be impossible to run the image in virtual machine because of mess with fstab/mtab / virtual hdd's UUID-s.
I need to clean up some HDD but I will need some of it's content later.
First of all sorry if my question would be not relevant, I'm quite beginner. In short:
I have 2 physical machines -> first(Windows Server 2007, Apache 2.2) on the second machine esxi installed to host virtual machines . I have been converted my physical machine(1) on esxi(2) and in the next step I would like to deploy a load balancer between the physical and virtual machine.
I have a virtual machine running CentOS 5 on a Windows server 2008 R2 with the Hyper-V role installed. The virtual machine has two harddrives installed that points to physical disks on an iSCSI target (see image below for details)
I've had this question long ago and still I've been unable to find a correct answer to it.
I know it's possible to run several virtual machines. Let's say that I'm running Windows Server 2008 R2 with two virtual machines running Ubuntu and Centos.
How do IT manages to make the three operating systems (one physical, two virtuals) available to be accesed over the internet.
I have come to figure out that qemu-img will only create sparse qcow2 images. I even tried creating a raw file then converting but as soon as I convert it also converts to a sparse file. I don't get why during the original install using virt-install doesn't do this.
I am trying to add a disk image to a windows 2008 server guest.