similar to: Resize errors with virt-resize/vgchange

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

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:

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 ...

On Mon, Jul 22, 2013 at 10:18:21AM -0600, Eric Blake wrote: > 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

On Tue, Jul 23, 2013 at 03:10:07PM -0400, Alex wrote: > 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 ... >

On Tue, Jul 23, 2013 at 07:18:30PM -0400, Alex wrote: > 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 > >>

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:

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"

On Wed, Jul 24, 2013 at 02:57:58PM -0400, Alex wrote: > Yes, here's the layout from the vm: > > # df -h > Filesystem Size Used Avail Use% Mounted on > devtmpfs 7.9G 0 7.9G 0% /dev > tmpfs 7.9G 0 7.9G 0% /dev/shm > tmpfs 7.9G 643M 7.3G 9% /run > tmpfs 7.9G

Hi, >> Yes, here's the layout from the vm: >> >> # df -h >> Filesystem Size Used Avail Use% Mounted on >> devtmpfs 7.9G 0 7.9G 0% /dev >> tmpfs 7.9G 0 7.9G 0% /dev/shm >> tmpfs 7.9G 643M 7.3G 9% /run >> tmpfs 7.9G 0 7.9G 0%

On Wed, Oct 21, 2015 at 03:53:33PM +0200, Pino Toscano wrote: > Use the common open_guestfs to open Guestfs handles, so we get > debugging, tracing, and other common options set. > --- > v2v/convert_windows.ml | 4 +--- > v2v/input_disk.ml | 2 +- > v2v/input_libvirt_other.ml | 2 +- > v2v/input_ova.ml | 2 +- > v2v/output_glance.ml | 2 +- >

We?ve been seeing this a lot lately on generic CentOS 6 rpm installs: rpm -qa | grep libguestfs libguestfs-java-1.16.19-1.el6.x86_64 libguestfs-java-devel-1.16.19-1.el6.x86_64 libguestfs-1.16.19-1.el6.x86_64 libguestfs-tools-1.16.19-1.el6.x86_64 libguestfs-javadoc-1.16.19-1.el6.x86_64 libguestfs-devel-1.16.19-1.el6.x86_64 libguestfs-tools-c-1.16.19-1.el6.x86_64

On Mon, Jan 20, 2014 at 04:39:42PM +0100, Olaf Hering wrote: > > Is "luks-format" supposed to work with guestfish? Like guestfish <<EOF > luks-format /dev/sda4 0 > EOF > > Appearently it lacks an option to give the passphrase programmatically. > Was this option skipped on purpose? The underlying API takes a passphrase parameter, ie:

Use the common open_guestfs to open Guestfs handles, so we get debugging, tracing, and other common options set. --- v2v/convert_windows.ml | 4 +--- v2v/input_disk.ml | 2 +- v2v/input_libvirt_other.ml | 2 +- v2v/input_ova.ml | 2 +- v2v/output_glance.ml | 2 +- v2v/output_null.ml | 2 +- v2v/output_rhev.ml | 2 +- v2v/output_vdsm.ml | 2 +-

Hello, I have an issue with virt-resize on the newest version of proxmox which is running on debian wheezy. when I run the virt-resize on a windows 2008 qemu image I got an error. Here is the last part of the debug message: Copying /dev/sda1 ... libguestfs: trace: copy_device_to_device "/dev/sda1" "/dev/sdb1" "size:32210026496" 100%

More evidence this is a real bug affecting users. I still have no idea why this bug happens. Rich. ----- Forwarded message from bugzilla at redhat.com ----- Date: Tue, 05 Mar 2013 20:29:23 +0000 Subject: [Bug 916990] inspect_os: mount_ro: /dev/sda on / (options: 'ro'): mount: /dev/sda is already mounted or /sysroot busy Product: Virtualization Tools

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

On 11.01.2015 02:57, Alex Regan wrote: > 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? > > #

I have a report for 1.20.4 about this error. There is no /etc/lvm/lvm.conf in the guest, which is handled as fatal error. Creating an emtpy file with that name is a workaround for the time being. $ virt-resize --expand /dev/sda2 in.img out.img Examining in.img ... Fatal error: exception Guestfs.Error("lvm_set_filter: open: /tmp/lvmiUFSBa/lvm/lvm.conf: No such file or directory") Maybe