search for: disk_ful

This action moves second(backup) GPT header to the end of the disk. It is usable in in-place image expanding, since free space after second GPT header is unusable. To use additional space, we have to move second header. This is what sgdisk -e does. However, sgdisk -e may perform additional actions if the partition table has unexpected params (e.g. if we call sgdisk -e /dev/sda1, it may fix

Please take a look. This feature is necessary for in-place image expanding. On 12/01/2015 06:28 PM, Maxim Perevedentsev wrote: > This action moves second(backup) GPT header to the end of the disk. > It is usable in in-place image expanding, since free space after > second GPT header is unusable. To use additional space, we have > to move second header. This is what sgdisk -e does.

This action moves second(backup) GPT header to the end of the disk. It is usable in in-place image expanding, since free space after second GPT header is unusable. To use additional space, we have to move second header. This is what sgdisk -e does. However, sgdisk -e may perform additional actions if the partition table has unexpected params (e.g. if we call sgdisk -e /dev/sda1, it may fix

Thanks Dominique & Daniel. Looks like i need to upgrade my VMs kernel to make it aware of virtio. Found this information from this link: http://wiki.libvirt.org/page/Virtio#Disk_.28block.29_device_driver I tried without upgrading the Kernel and as soon as i start my VM it got into Kernel Panic. I will try using virtio after upgrading my VMs kernel. Thanks for all the responses and

On 4/14/2015 6:32 PM, Tom Hughes wrote: > On 14/04/15 13:33, Jatin Davey wrote: > >> Thanks Dominique & Daniel. >> >> Looks like i need to upgrade my VMs kernel to make it aware of virtio. >> >> Found this information from this link: >> >> http://wiki.libvirt.org/page/Virtio#Disk_.28block.29_device_driver >> >> I tried without

On 4/14/2015 4:58 PM, Daniel P. Berrange wrote: > On Tue, Apr 14, 2015 at 04:53:52PM +0530, Jatin Davey wrote: >> On 4/14/2015 4:42 PM, Dominique Ramaekers wrote: >>> About Spice: I think it’s good practice to use spice because it improves >>> the performance of the VM in general by improving screen performance. If >>> your VM is constantly displaying output,

When possible, make the disk image format explicit when invoking tools or using add-drive. This avoids warnings from qemu about the unspecified format for the image, and also makes qemu slightly faster (skipping the disk image probing). Tests checking the image probing are not touched. This changes also: - old-style invocations of tools (`$tool $filename`) into new style (`$tool -a $filename`)

On 14/04/15 13:33, Jatin Davey wrote: > Thanks Dominique & Daniel. > > Looks like i need to upgrade my VMs kernel to make it aware of virtio. > > Found this information from this link: > > http://wiki.libvirt.org/page/Virtio#Disk_.28block.29_device_driver > > I tried without upgrading the Kernel and as soon as i start my VM it got > into Kernel Panic. I will try

On 14.04.2015 15:16, Jatin Davey wrote: > On 4/14/2015 6:32 PM, Tom Hughes wrote: >> On 14/04/15 13:33, Jatin Davey wrote: >> >>> Thanks Dominique & Daniel. >>> >>> Looks like i need to upgrade my VMs kernel to make it aware of virtio. >>> >>> Found this information from this link: >>> >>>

Jatin, Using qemu without the virtio scsi and nic drivers is like running vmware with ide disks and e1000 nic instead of LSI disks and vmxnet3 nics, it forces the system to emulate completely different hardware. In linux the virtio drivers are implemented in the kernel, so you either need a new kernel or the virtio kernel modules. I'm not sure which for RHEL5, but I suspect you can get

Hi, small series with small improvements to the tests. Pino Toscano (3): tests: specify the image format when possible tests: remove remaining relative paths to binaries fish: generate test-prep.sh with generator .gitignore | 1 + align/test-virt-alignment-scan.sh | 2 +- cat/Makefile.am | 2 +- cat/test-virt-cat.sh

Hi Jatin, The RedHat documentation on this is extremely helpful. It's so helpful that I use it as a reference on completely different distributions. VMWare does a pretty good job of guiding you and giving you defaults that are sensible. With Libvirt/QEMU/KVM, you need to get an idea of those and enable them yourself. For example, I see that you are using qcow2 files, but if you don't

Changes: tools/blktap: remove unneeded pointer dereferencing in convert_dev_name_to_num tools/blktap: constify string arrays in convert_dev_name_to_num tools/blktap: fix params and physical-device parsing tools/blktap: remove unneeded pointer dereferencing from img2qcow.c tools/blktap: remove unneeded pointer dereferencing from qcow2raw.c tools/blktap2: fix build errors caused by Werror in

This is an attempt to fix the issue that some disks' sysfs attributes are not ready at the time its KOBJ_ADD event is sent. The symptom is during device hotplug, udev may fail to find certain attributes, such as serial or wwn, of the disk. As a result the /dev/disk/by-id entries are not created. The cause is device_add_disk emits the uevent before returning, and the callers have to create

This is an attempt to fix the issue that some disks' sysfs attributes are not ready at the time its KOBJ_ADD event is sent. The symptom is during device hotplug, udev may fail to find certain attributes, such as serial or wwn, of the disk. As a result the /dev/disk/by-id entries are not created. The cause is device_add_disk emits the uevent before returning, and the callers have to create