search for: disk_typ

Just spent a little time poking around w/ p2v and am attaching the following pseudo-code for consideration. Note the patches aren't commit ready yet, just looking for thoughts - The first is a fix to get client image building process working on F17. It seems the version of ksflatten there didn't expand the nested %includes which was causing errors (also --interpreter image-minimizer

...t in case the main disk is faulty # $1 is either /dev/hdb or /dev/sdb grub_setup_scsi() { grub << EOF find /boot/grub/stage1 device (hd0) /dev/sdb root (hd0,0) setup (hd0) EOF } grub_setup_ide() { grub << EOF find /boot/grub/stage1 device (hd0) /dev/hdb root (hd0,0) setup (hd0) EOF } DISK_TYPE=`fdisk -l /dev/hda | grep "/dev/hda"` if [ "$DISK_TYPE" = "" ] then echo "Assuming SCSI drives" sfdisk -d /dev/sda > /etc/silentm/raidinfo.partitions.sda sfdisk -d /dev/sdb > /etc/silentm/raidinfo.partitions.sdb grub_...

Following discussion, and a bit of slip to allow better contributions from those who''ve been away for the Chinese New Year, the plan for 4.1 now looks like this. We intend to go into code freeze at the end of the week, after which patches even for bugfixes will be much harder to get into the tree. We are here: | Feature code freeze | | Bugfixes are allowed provided they are

...r name: cluster1.jigamartyrs.local Master node: node1.jigamartyrs.local Architecture (this node): 64bit (x86_64) Default hypervisor: xen-pvm Enabled hypervisors: xen-hvm, xen-pvm Hypervisor parameters: - xen-hvm: nic_type: rtl8139 cdrom_image_path: vnc_bind_address: 0.0.0.0 boot_order: dc pae: True disk_type: ioemu acpi: True - xen-pvm: root_path: /dev/sda1 kernel_path: /boot/initrd-2.6-xenU initrd_path: /boot/initrd-2.6-xenU kernel_args: ro Cluster parameters: - candidate pool size: 10 - master netdev: eth0 - default bridge: eth0 - lvm volume group: xenvg - file storage path: /srv/ganeti/file-storage...

When importing from VMware via the libvirt driver, the libvirt driver can add an empty source bridge name: <interface type='bridge'> <mac address='00:01:02:03:04:05:06'/> <source bridge=''/> </interface> Replicate what we do on the -i ova path, and map these to "eth0", "eth1" etc. This also includes a bunch

It turns out that RHEL 5 Xen conversions don't work if the source disk is located on a block device. See patch 1/4 for the gory details. This patch series proposes a new tool called virt-v2v-copy-to-local which essentially is a way to make new virt-v2v work like the old virt-v2v, ie. copy first, convert after. Of course this is very slow and would only be used as a last resort, but I

This patch series copies the core of the tapdisk process from blktap2, with updates coming from blktap2.5. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

This patch series introduces the shared ring used by the front-end to pass request descriptors to tapdisk, as well as responses from tapdisk to the front-end. Requests from this ring end up in tapdisk''s standard request queue. When the tapback daemon detects that the front-end tries to connect to the back-end, it spawns a tapdisk and tells it to connect to the shared ring. The shared

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

This patch series aims to move the logical block size checking to the block code. This was inspired by missing check for valid logical block size in virtio-blk which causes the kernel to crash in a weird way later on when it is invalid. I added blk_is_valid_logical_block_size which returns true iff the block size is one of supported sizes. I added this check to virtio-blk, and also converted

This patch series aims to move the logical block size checking to the block code. This was inspired by missing check for valid logical block size in virtio-blk which causes the kernel to crash in a weird way later on when it is invalid. I added blk_is_valid_logical_block_size which returns true iff the block size is one of supported sizes. I added this check to virtio-blk, and also converted

Hi, here is the next version of changes to enable Linux to run as an SEV-ES guest. The code was rebased to v5.7-rc3 and got a fair number of changes since the last version. What is SEV-ES ============== SEV-ES is an acronym for 'Secure Encrypted Virtualization - Encrypted State' and means a hardware feature of AMD processors which hides the register state of VCPUs to the hypervisor by

Hi, here is the next version of changes to enable Linux to run as an SEV-ES guest. The code was rebased to v5.7-rc3 and got a fair number of changes since the last version. What is SEV-ES ============== SEV-ES is an acronym for 'Secure Encrypted Virtualization - Encrypted State' and means a hardware feature of AMD processors which hides the register state of VCPUs to the hypervisor by