similar to: Re: a small problem about *Disk* type pool

On 07/21/2014 10:01 PM, shyu wrote: > > # rpm -q libvirt qemu-kvm-rhev > libvirt-1.1.1-29.el7.x86_64 > qemu-kvm-rhev-1.5.3-60.el7ev_0.2.x86_64 These are downstream builds. Can you reproduce your situation with upstream libvirt 1.2.6 and qemu 2.1-rc2? It may be that you are hitting behavior that was introduced by downstream backports. > 1. Check source file > # qemu-img

This adds the ability to select 2 different disks for root and HostVG. ovirt_init kernel arg still works as intended but does not support multiple arguments, this will be added in next --- scripts/ovirt-config-storage | 150 ++++++++++++++++++++++++++---------------- 1 files changed, 94 insertions(+), 56 deletions(-) diff --git a/scripts/ovirt-config-storage b/scripts/ovirt-config-storage index

Hi messmer, seems that anaconda supports partitioned RAID devices. Disk selection see one mdraid device and permits to create partition on it. Il 13/03/2016 01:04, Gordon Messmer ha scritto: > On 03/12/2016 08:22 AM, Alessandro Baggi wrote: >> From several how-to concerning raid1 installation, I must put each >> partition on a different md devices. > > Not necessarily. You

root at five-72 ~ # dd if=/dev/zero of=/dev/sdb bs=1M count=1000 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB) copied, 8.67101 s, 121 MB/s root at five-72 ~ # parted /dev/sdb GNU Parted 2.1 Using /dev/sdb Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) mklabel gpt (parted) print Model: ATA ST3000DM001-1CH1 (scsi) -->

Hi List, yesterday i tried to install CentOS6 on Server bei Hetzner.de I noticed that Anaconda Installer is not possible to handle the 3TB Disks in Server when u try to Partition them. U can do only 3 normal partitions or u can do only 3 raid partitions, the SOLUTION is: Before U install Centos6 on the new naked server: a) Start Server in Rescue mode b) parted /dev/sda c) mklabel gpt (

Hi Eric, On 07/22/2014 08:52 PM, Eric Blake wrote: > On 07/21/2014 10:01 PM, shyu wrote: > >> # rpm -q libvirt qemu-kvm-rhev >> libvirt-1.1.1-29.el7.x86_64 >> qemu-kvm-rhev-1.5.3-60.el7ev_0.2.x86_64 > These are downstream builds. Can you reproduce your situation with > upstream libvirt 1.2.6 and qemu 2.1-rc2? It may be that you are hitting > behavior that was

--- scripts/ovirt-config-boot | 13 +++++- scripts/ovirt-config-storage | 111 ++++++++++++++++++++++++------------------ 2 files changed, 75 insertions(+), 49 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index d545878..8cc127b 100755 --- a/scripts/ovirt-config-boot +++ b/scripts/ovirt-config-boot @@ -29,6 +29,12 @@ ovirt_boot_setup() { local disk2

--- scripts/ovirt-config-boot | 13 +++++++- scripts/ovirt-config-storage | 73 +++++++++++++++++++++++++---------------- 2 files changed, 56 insertions(+), 30 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index d545878..8cc127b 100755 --- a/scripts/ovirt-config-boot +++ b/scripts/ovirt-config-boot @@ -29,6 +29,12 @@ ovirt_boot_setup() { local disk2

Quote everywhere that we reference wwid in o-c-storage, o-c-boot and ovirt-functions. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 6 +- scripts/ovirt-config-storage | 178 +++++++++++++++++++++--------------------- scripts/ovirt-functions | 38 +++++----- 3 files changed, 111 insertions(+), 111 deletions(-) diff --git

hi to the list, Hello everyone, I am new in the world of pxe booting and i try to use AOE to boot my linux debian lenny machines. I install the linux like this: parted -s /dev/etherd/e10.1 mklabel gpt parted -s /dev/etherd/e10.1 mklabel gpt parted -s /dev/etherd/e10.1 mkpart primary ext3 17408B 314590207B parted -s /dev/etherd/e10.1 mkpart primary ext3 314590208B 3535815679B parted -s

Used in conjunction with livecd-iso-to-iscsi. Creates a local boot partition with vmlinuz/initrd and grub configuration. Disk Partitioning > enable iscsi target > configure storage > local install and reboot --- scripts/ovirt-config-boot | 131 +++++++++++++++++++-------------- scripts/ovirt-config-storage | 164 +++++++++++++++++++++++++----------------- tools/livecd-iso-to-iscsi

On 03/12/2016 08:22 AM, Alessandro Baggi wrote: > From several how-to concerning raid1 installation, I must put each > partition on a different md devices. Not necessarily. You could put LVM on top of the RAID device, and create logical volumes. > I've asked times ago if it's more correct create the md device, > partitioning it and create fs on each partition created on

Hi There, There is a case I met about the destination file's disk size after do blockcopy Details as below: Env: # rpm -q libvirt qemu-kvm-rhev libvirt-1.1.1-29.el7.x86_64 qemu-kvm-rhev-1.5.3-60.el7ev_0.2.x86_64 1. Check source file # qemu-img info /var/lib/libvirt/images/rhel6.img image: /var/lib/libvirt/images/rhel6.img file format: qcow2 virtual size: 5.0G (5368709120 bytes) disk

Hi all, Does anyone have a working example of creation of a logical storage pool and volume? I'm hitting a wall getting logical volumes to work on RHEL 6 beta. There's a single drive I'm trying to setup (sdc) as a libvirt managed logical storage pool, but all volume creation on it fails. Here's what I'm finding so far: Prior to any storage pool work, only the host

- dracut does not currently support booting a dmsquash file system on an iscsiroot - can not be configured in standalone mode since networking is not up, although works fine if ovirt-config-setup is run once booted. Signed-off-by: Joey Boggs <jboggs at redhat.com> --- recipe/common-pkgs.ks | 1 + scripts/ovirt-config-boot | 67 ++++++++++++++++----

This patch introduces the concept of an "Advanced Storage Configuration", specifically for automated installs (although it could be hooked into manual install), while preserving the original style of specifying LVs. It accomplishes the following: * Add an optional AppVG * Offer new optional LVs - Data2,Swap2 - as part of the new AppVG * Allows the specification of multiple disks, per VG

We just got in a few server-class drives. They're Seagate Constellations, 3TB. I went to partition and format, and did a mklabel gpt in parted. Ooops. It claims Sector size (logical/physical): 512B/512B After data sheet that doesn't tell me, and a long wait*, I spoke to a Seagate tech, who agreed that it *is* 4k physical. This is CentOS 6.2 Anyone know any way to correct this, or if

Ken Smith wrote: > > Hi All, Slightly OT as this is on a Centos 6 system > Not at all OT. We started using parted when we started using 3TB drives a few years ago, since fdisk can't handle > 2TB. > I'm getting the fdisk message "partition does not start on a physical > sector boundary" on a 4096 sector disk. I understand why this has > happened. > > I

the closest i have gotten to a consistent way to test a MS-DOS filesystem setup is: dd if=/dev/zero of=binary.img bs=1M count=500 i="$(losetup -f --show binary.img )" parted binary.img mklabel msdos -s -m dd if=/usr/lib/syslinux/mbr.bin of="${i}" parted binary.img mkpart primary -a optimal -s -m 0% 100% parted binary.img set 1 boot on mkfs.ext4 $(kpartx -savu "${i}"

From: Mike Kercher <mike at CamaroSS.net> > I'm about to deploy a new server for hosting sites and email for a > number of small individuals using a CentOS 4 box. I've been looking > for a recommended installation guide for RHEL4/CentOS4 giving > recommended disk partitioning I have personal recommendations I follow. One thing I really try to do is make 2-3