search for: add_drivers

The device name is only used by guestfish (when using the -N option to prepare drives). We constructed the device name very naively, basically ‘sprintf ("/dev/sd%c", next_drive)’. This stores the device index instead, and only constructs the device name in guestfish. Also the device name is constructed properly using guestfs_int_drive_name so it can cope with #drives > 26. ---

When parsing the URI, drop the leading '/' from the path also when the protocol is 'nbd': in this case, the path represents the export name, which does not need the '/' coming from the URI format. Improve the coverage for nbd in test-add-uri.sh, adding a couple of tests, and adjusting the result of an existing one. --- fish/test-add-uri.sh | 8 +++++++- fish/uri.c

> > > By default, when saving a URI using xmlSaveUri it escapes everything in > the URI. QEMU doesn't want anything escaped, so now I unescape > everything after the URI is generated. Unfortunately there's no flag to > change the default behavior. > > I'm not sure that's the actual issue here, but I'm somehow included to > think this is another

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:

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:

On Tue, Sep 27, 2016 at 11:20:07AM +0200, Pino Toscano wrote: > When parsing the URI, drop the leading '/' from the path also when the > protocol is 'nbd': in this case, the path represents the export name, > which does not need the '/' coming from the URI format. > > Improve the coverage for nbd in test-add-uri.sh, adding a couple of > tests, and

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

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

(apologies if you see this twice, forgot the CC the first time) In data venerdì 26 giugno 2015 18:50:16, Gabriel Hartmann ha scritto: > > > > > By default, when saving a URI using xmlSaveUri it escapes everything in > > the URI. QEMU doesn't want anything escaped, so now I unescape > > everything after the URI is generated. Unfortunately there's no flag to

Dear Team I show below my problem when try to apply setfacl to share directory in domain controller My Problem is: I have one Samba AD [4.1] it work fine. I create common share folder in domain controller when try to apply ACL permission it show the following message [root at sambadc ~]# setfacl -m "u:RISHI\Administrator:rwx" /ADD_Drive/Samplesetfacl: Option -m: Invalid argument near

Also fix two tests which assumed that you could add a non-existent socket. --- fish/test-add-uri.sh | 16 ++++++++++++---- lib/drives.c | 14 +++++++++++++- tests/disks/test-qemu-drive.sh | 19 ++++++++++++++----- 3 files changed, 39 insertions(+), 10 deletions(-) diff --git a/fish/test-add-uri.sh b/fish/test-add-uri.sh index 756df997b..cb4d40199 100755 ---

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

These two patches are for discussion of the proposed API only (in fact, it doesn't compile). virtio-scsi allows you to name drives (using the qemu serial=... option or libvirt <serial/>). Let's allow users to specify a serial when adding a drive, and then map that to a well-known name in the libguestfs API (/dev/disk/guests/SERIAL[PARTNUM]). Note that I chose not to change

Seeing `g.add_drive_opt :readonly => 1` allows one to imply that ensuring writable access to drive should happen via `g.add_drive_opt :readonly => 0`. However, the passed option value gets passed down to C according to Ruby Boolean semantics, that is, any value apart from `false` and `nil` will be true (see RTEST in Ruby C API). So its more idiomatic and provides a better hint if we use

With VMWare (server), you can pre-allocate your image in several vmdk files. But I have not bee able to mount that in guestfs. On file (e.g. guest.vmdk) is a text file pointing to all the other files (e.g. guest-f001.vmdk, guest-f002.vmdk,...). I tried the following scenarios without success: 1- just adding the base vmdk: add_drive guest.vmdk 2- adding all the files: add_drive guest-f001.vmdk

So far the failure of some test would have not reported a non-zero return value by run-tests.php. Since now all the PHP tests pass, we can ask for failures to be fatal, by exporting REPORT_EXIT_STATUS=1 for run-tests.php. --- php/run-php-tests.sh | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/php/run-php-tests.sh b/php/run-php-tests.sh index 6f9ae10..e498987 100755 ---

On Friday, 28 April 2017 11:08:21 CEST Richard W.M. Jones wrote: > The device name is only used by guestfish (when using the -N option to > prepare drives). We constructed the device name very naively, > basically ‘sprintf ("/dev/sd%c", next_drive)’. > > This stores the device index instead, and only constructs the device > name in guestfish. Also the device name is