similar to: [PATCH for discussion only] launch: Add add_drive 'serial' option.

This completes the implementation previously posted here: https://www.redhat.com/archives/libguestfs/2012-October/msg00002.html Instead of using 'serial', the option is now called 'label' and these are collectively called disk labels. Also the updated patch adds a test. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming

From: "Richard W.M. Jones" <rjones at redhat.com> You can now add remote NBD drives using: ><fs> add-drive "" format:raw protocol:nbd server:localhost (Note that you also need to add port:NNNN if the server is running on a non-standard port). The corresponding qemu-nbd service can be started by doing: qemu-nbd disk.img -t This commit also adds a test. ---

On Wed, Dec 02, 2015 at 02:10:52PM +0100, Pino Toscano wrote: > Hi, > > one of the bugs we have (#1092583) is about the lack of query string > for http/https URLs: there were patches about that (not merged yet), > whose solution was to add a new optional argument "querystring". > > Another bug that I'm looking at (#1118305) is about setting initiator > IQNs

From: "Richard W.M. Jones" <rjones@redhat.com> NULL means that libvirt gets to guess what connection URI we meant. Currently it guesses qemu:///session for non-root and qemu:///system for root. Except if LIBVIRT_DEFAULT_URI is set in which case this is used even if it's not appropriate. Except if Xen is installed in which case it guesses xen:/// which is not helpful at all.

Allow `launch` call to accept an optional argument, called `blocksize`. Example: $ guestfish --listen -a raw.img $ guestfish --remote -- launch blocksize:4096 The actual qemu command is: [...] -device virtio-scsi-ccw,id=scsi -drive file=raw.img,cache=writeback,id=hd0,if=none -device scsi-hd,drive=hd0,physical_block_size=4096,logical_block_size=4096 [...] Signed-off-by: Tuan Hoang

libguestfs recently added support for virtio-scsi and libvirt, and when these are both available this lets us relatively easily add hotplugging of drives. This email is about how we would present that through the libguestfs API. (a) The current API Currently you have to add drive(s) via guestfs_add_drive* and then call guestfs_launch, ie. your program must look something like this: guestfs_h

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.

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

This patch updates the guestfs_inspect_get_drive_mappings API call to also return drive letters for GPT paritions. Previously this worked only for MBR partitions. This is achieved by matching the GPT partition GUID with the info stored in the blob from HKLM\SYSTEM\MountedDevices\DosDevices keys. For GPT partions this blob contains a "DMIO:ID:" prefix followed by a 16 byte binary GUID.

Hi, one of the bugs we have (#1092583) is about the lack of query string for http/https URLs: there were patches about that (not merged yet), whose solution was to add a new optional argument "querystring". Another bug that I'm looking at (#1118305) is about setting initiator IQNs for iSCSI drives; a good solution IMHO would be add a new initiator-name parameter for this. Thinking

On Thursday 03 December 2015 11:52:14 Richard W.M. Jones wrote: > On Wed, Dec 02, 2015 at 02:10:52PM +0100, Pino Toscano wrote: > > Hi, > > > > one of the bugs we have (#1092583) is about the lack of query string > > for http/https URLs: there were patches about that (not merged yet), > > whose solution was to add a new optional argument "querystring".

On Sat, Feb 08, 2020 at 01:25:28AM +0200, Mykola Ivanets wrote: > From: Nikolay Ivanets <stenavin@gmail.com> > > I faced with situation where libguestfs cannot recognize partitions on a > disk image which was partitioned on a system with "4K native" sector > size support. > > In order to fix the issue we need to allow users to specify desired > physical

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

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

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

Move the list_filesystems API into the daemon, reimplementing it in OCaml. Since this API makes many other API calls, it runs a lot faster in the daemon. --- daemon/Makefile.am | 2 + daemon/ldm.ml | 3 + daemon/ldm.mli | 2 + daemon/listfs.ml | 156 +++++++++++++++++++++++++++++ daemon/listfs.mli | 19 ++++ daemon/lvm.ml | 3 +

Hello Richard, I'm using: >> virt-sysprep 1.25.6 I honestly don't remember if the currently installed version is from the tarball or pulled from the github source... Now that you mention it, I think it could even be the version with my "hack" to fix virt-sysprep... Which version are you building? I see there's a: >>

Previously we used (on arm): -M virt -machine accel=... After this change, we use: -machine virt,accel=... On x86 there is no change. The -M option is an abbreviation for -machine, and we can combine the two options together. (Qemu combines the two options internally, but it's more predictable if we do it ourselves). Upstream qemu has supported the -machine option for over 5 years, and in

On Mon, Nov 25, 2013 at 12:52:21PM -0700, Jon wrote: > Hello, > > I'm having trouble connecting to rbd images. It seems like somewhere the > name is getting chewed up. I wonder if this is related to my previous > troubles [1] [2] with rbd images. > > I'm trying to add an rbd image, but when I launch the guestfs object I get > an error: > > >>