similar to: Basic shared storage + KVM

Hi, I have more than 20 VM in production with a shared storage and 6 blades as HV. Things begin to look confusing within virt-manager since there is no way to display only the powered-up nodes (the migrated and switched off machines appear on every hv entry). I wonder if there is something different and more appealing than virt-manager to manage such an infrastructure. My requirement are: be

Hi, I am trying to benchmark disk I/O performance on VM running with "-snapshot" option enabled. In order to do that I specify cache=none in the -drive parameter (yes I am running qemu-kvm at command line0. The problem is that if I use this option kvm seems to ignore the cache=none directive and I get weird output from iozone (I/O values are better than on the real machine,

I have a degraded raid array (originally raid-10, now only two drives) that contains an LVM volume. I can see in the appended text that the Xen domains are there but I don't see how to mount them. No doubt this is just ignorance on my part but I wonder if anyone would care to direct me? I want to be able to retrieve dom-0 and one of the dom-Us to do data recovery, the others are of

Hi All, My CentOS 5.1 server is using iSCSI attached disks connecting to a dual controller storage array. I have also configured multipathd to manage the multiple paths. Everything works well, and on boot the dev nodes are automatically created in /dev/mapper. On these devices, I have created logical volumes using lvm2. My problem is that lvm does not recognize these iscsi/multipath volumes on

Hi, looking at the qemu-kvm man page, it is possible to enable snapshot for a given drive. This is what we need because we would like to start a domain with two drives, one on a file with snapshot=on and an other drive on LVM with snapshot=off. Unfortunately it seems that if you use libvirt the same option is not available when you define the domain with a XML file. I mean, I didn't find

I renamed my volume with vgrename however I didn't complete the other steps. Mainly update fstab and intiramfs. Once I booted, I was dropped on the Dracut shell. From here I can see the newly rename VG and I can lvm lvscan as well as activate it, lvm vgchange -ay. However I can't figure out what to do next, I'm assuming I need to regenerate the initramfs and then boot to change

Hi I've recently rebuilt my home server using centos 7, and transplanted over the main storage disks It's a 3 disk raid5, with an lvm storage group (vg03) on there Activating and mounting works fine: # vgscan ? Reading volume groups from cache. ? Found volume group "vg03" using metadata type lvm2 # vgchange -ay ? 1 logical volume(s) in volume group "vg03" now

Hi, I have an iscsistorage which I attached to a new centos 6.3 server. I added logic volumes as usual, the block devices (sdb & sdc) showed up in dmesg; I can mount and access the stored files. Now we did an firmware software update to that storage (while unmounted/detached from the fileserver) and after reboot of the storage and reatache the iscsi nodes I do get new devices. (sdd &

When the daemon starts up it creates a fresh (empty) LVM configuration and starts up lvmetad (which depends on the LVM configuration). However this appears to cause problems: Some types of PV seem to require lvmetad and don't work without it (https://bugzilla.redhat.com/show_bug.cgi?id=1581810). If we don't start lvmetad earlier, the device nodes are not created. Therefore move the

Hi, I'm trying to resize a 15GB LVM root partition on a fedora20 server with a fedora20 guest and I'm having a problem. Is this supported on fedora20? I recall having a similar problem (maybe even exact same problem) all the way back in fedora16 or fedora17, but hoped/thought it would be fixed by now? # virt-df -h test1-011015.img Filesystem Size Used

Dracut includes what was being patched in Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 47 --------------------------------------------- 1 files changed, 0 insertions(+), 47 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index d13dad2..28d1572 100755 --- a/scripts/ovirt-config-boot +++ b/scripts/ovirt-config-boot @@

Hi, I am trying to recover data from my old system which had LVM. The disk had two partitions - /dev/sda1 (boot, Linux) and /dev/sda2 (Linux LVM). I had taken a backup of both partitions using dd. Now I am booting of CentOS live cd for system restore. I recreated partitions like previous system using fdisk and then used dd to dump all the data onto it. I would like to mount sda2 as LVM, but I

I have an 8-core SuperMicro Xeon server with CentOS 6.3. The OS is installed on a 120 GB SSD connected by SATA, the machine also contains an Areca SAS controller with 24 drives connected. The motherboard is a SuperMicro X9DA7. When I installed the OS, I used the default options, which creates an LVM volume group to contain / and /home, and keeps /boot and /boot/efi outside the volume group.

I converted a system disk from a virtualbox VM and added to the config on a qemu VM. All seems well until I try to mount it. The virtual machine shows data for the disk image using commands like: pvs lvs lvdisplay xena-1 but there is no /dev/xena-1/root to be mounted. I also cannot seem to figure out whether the lvm related modules are available for the virtual machine kernel. Has anyone

Hi, >> > # virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home >> > prop-1.img prop-expand.img >> > command line: virt-resize -d --expand /dev/sda1 --LV-expand >> > /dev/mapper/prop-home prop-1.img prop-expand.img >> > Examining prop-1.img ... >> > libguestfs: trace: add_drive "prop-1.img" "readonly:true"

Hi, I have an fc18 system and trying to resize an LVM partition with an ext4 filesystem and receiving the following message from virt-resize: # virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home prop-1.img prop-expand.img command line: virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home prop-1.img prop-expand.img Examining prop-1.img ... libguestfs: trace:

Hi, I have an fc18 system and trying to resize an LVM partition with an ext4 filesystem and receiving the following message from virt-resize: # virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home prop-1.img prop-expand.img command line: virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home prop-1.img prop-expand.img Examining prop-1.img ... libguestfs: trace:

On 07/21/2013 07:01 PM, Alex wrote: > Hi, > > I have an fc18 system and trying to resize an LVM partition with an > ext4 filesystem and receiving the following message from virt-resize: virt-resize is part of libguestfs, which is layered on top of libvirt. As such, I'm redirecting this mail to the libguestfs mailing list. > > # virt-resize -d --expand /dev/sda1

Dear James, Thank you for being quick to help. Yes, I could see all of them: # vgs # lvs # pvs Regards, Khem On Sat, February 28, 2015 7:37 am, James A. Peltier wrote: > > > ----- Original Message ----- > | Dear All, > | > | I am in desperate need for LVM data rescue for my server. > | I have an VG call vg_hosting consisting of 4 PVs each contained in a > | separate

Hi, >> >> > # virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home >> >> > prop-1.img prop-expand.img >> >> > command line: virt-resize -d --expand /dev/sda1 --LV-expand >> >> > /dev/mapper/prop-home prop-1.img prop-expand.img >> >> > Examining prop-1.img ... >> >> > libguestfs: trace: