similar to: Fwd: is there a way to set discard=unmap when using guestmount? (#52)

On Thu, Oct 22, 2020 at 10:57:05 +0800, Han Han wrote: > Hello, > I find "discard":"unmap" is defaultly enabled in qemu cmdline(libvirt > v6.6, qemu v5.1): > XML: > <disk type="file" device="disk"> > <driver name="qemu" type="qcow2"/> > <source

Hello, I find "discard":"unmap" is defaultly enabled in qemu cmdline(libvirt v6.6, qemu v5.1): XML: <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/var/lib/libvirt/images/new.qcow2" index="2"/> <backingStore/> <target

On Fri, Jun 01, 2018 at 07:54:32AM -0500, Ian Pilcher wrote: > On 06/01/2018 05:19 AM, Daniel P. Berrangé wrote: > > On Thu, May 31, 2018 at 02:34:15PM -0500, Ian Pilcher wrote: > > > Is it possible to make discard='unmap' the default for virtio-scsi > > > disks? (Related, is it possible to make virtio-scsi the default disk > > > type, rather than

Is it possible to make discard='unmap' the default for virtio-scsi disks? (Related, is it possible to make virtio-scsi the default disk type, rather than virtio-blk?) Thanks! -- ======================================================================== Ian Pilcher arequipeno@gmail.com -------- "I grew up before Mark Zuckerberg invented

On Thu, May 31, 2018 at 02:34:15PM -0500, Ian Pilcher wrote: > Is it possible to make discard='unmap' the default for virtio-scsi > disks? (Related, is it possible to make virtio-scsi the default disk > type, rather than virtio-blk?) This is really a question for whatever management tool you're using with libvirt, since it is essentially defining an opinionated usage policy.

On 06/01/2018 05:19 AM, Daniel P. Berrangé wrote: > On Thu, May 31, 2018 at 02:34:15PM -0500, Ian Pilcher wrote: >> Is it possible to make discard='unmap' the default for virtio-scsi >> disks? (Related, is it possible to make virtio-scsi the default disk >> type, rather than virtio-blk?) > > This is really a question for whatever management tool you're

2017-07-31 18:57 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > On Mon, Jul 31, 2017 at 06:52:28PM +0800, lampahome wrote: > > if I mount through guestfs library in python or guestfish, the same > > condition happenes? > > > > I mean the insane number of layers and the performance > > No. The layers are only present because guestmount uses FUSE. >

Hello all, I am having an issue with guestmount in respect to live instances and I was hoping someone might have an idea where I've gone wrong. The following output is from my shell session, if there's any more information needed please let me know and I'll happily provide it. [root at longitude ~]# virt-filesystems -d F16-rawhide/dev/sda2 /dev/sda3 [root at longitude ~]#

On Fri, Feb 26, 2016 at 06:56:07PM -0800, Vadaseri Vadaseri wrote: > lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description: Ubuntu 14.04.3 LTS > Release: 14.04 > Codename: trusty > > guestmount --ro -a agent-disk1.vmdk -i /mnt/vmdk --> Works fine > > guestmount --rw -a agent-disk1.vmdk -i /mnt/vmdk > libguestfs: error:

Currently guestfish has mount-vfs, and the libguestfs API has guestfs_mount_vfs(), but guestmount doesn't allow the user to specify a filesystem. This patch extends the --mount argument, so you can force an ext2 partition to mount as ext4: guestmount -a mydisk.img -m /dev/vda:/:defaults:ext4 mountpoint You could also use it to choose between ntfs and ntfs-3g, or between hfsplus and the

On Thu, Feb 06, 2014 at 02:53:05AM +0000, Patrick Schleizer wrote: > Hi, > > Apparently, > > guestmount -o allow_other -a "/path/to/raw_file" -m /dev/sda1 > "/path/to/mountfolder" > > is much slower than > > kpartx -av "/path/to/raw_file" > mount /dev/mapper/loop0p1 /path/to/mountfolder > > (Doing lots of

On Mon, Jul 31, 2017 at 06:52:28PM +0800, lampahome wrote: > if I mount through guestfs library in python or guestfish, the same > condition happenes? > > I mean the insane number of layers and the performance No. The layers are only present because guestmount uses FUSE. libguestfs itself performs very well if you are careful to use it in the correct way. The architecture of

[A question about whether it is possible to use guestmount on a guest which does not have /etc/fstab. I've no reproduced this because I'm CC-ing my reply to a public mailing list] It's definitely possible. I would suggest first using $ virt-filesystems -a disk.img --all --long -h to get an idea of what's inside your disk image, then you use a command such as: $ guestmount

On Fri, Jun 01, 2018 at 08:37:30AM -0500, Ian Pilcher wrote: > On 06/01/2018 08:14 AM, Daniel P. Berrangé wrote: > > Yes, it inherits some defaults to libvirt and/or QEMU. If those are not > > suitable for some reason, then virt-manager needs to override it. The > > decision about whether to enable discard or not is a policy decision > > that doesn't have a single

On Sun, May 12, 2019 at 04:11:08PM -0700, Jun Aruga wrote: > I am using libguestfs tool on Fedora 30. > > libguestfs version: 1.40.2 > libguestfs-tools-c RPM package version: libguestfs-tools-c-1.40.2-4.fc30.x86_64 > > > I have a question about `virt-tar-out`. > > ``` > $ rpm -qf /usr/bin/virt-tar-out > libguestfs-tools-c-1.40.2-4.fc30.x86_64 > ``` >

Thanks for your response Rich. Please see the output of --trace --verbose below. Regarding your suggestion to convert the vmdk to some other format, I do not want to do it. A security consultant said by modifying certain files in our VM and restarting the VM, one can gain access to encrypted data in our VM. I want to reproduce it. I am able to mount the VM but not able to modify files since it can

On 06/01/2018 08:14 AM, Daniel P. Berrangé wrote: > Yes, it inherits some defaults to libvirt and/or QEMU. If those are not > suitable for some reason, then virt-manager needs to override it. The > decision about whether to enable discard or not is a policy decision > that doesn't have a single perfect answer. So changing it in libvirt > might make it better for you, but worse

On Tue, Jan 10, 2017 at 05:06:13PM +0100, Jelle de Jong wrote: > Hello everybody, > > I am using libguestfs-tools version 1.28.1 in a bunch of bash > scripts to make back-ups of the files on a visualisation platform. > > I been trying to get read access to ntfs volumes with data > deduplication working. Do you have more information about data deduplication? It's the

When possible, make the disk image format explicit when invoking tools or using add-drive. This avoids warnings from qemu about the unspecified format for the image, and also makes qemu slightly faster (skipping the disk image probing). Tests checking the image probing are not touched. This changes also: - old-style invocations of tools (`$tool $filename`) into new style (`$tool -a $filename`)

Existing virtio-blk protocol doesn't have DISCARD/WRITE ZEROES commands support, this will impact the performance when using SSD backend over file systems. Commit 88c85538 "virtio-blk: add discard and write zeroes features to specification"(see https://github.com/oasis-tcs/virtio-spec) extended existing virtio-blk protocol, adding extra DISCARD and WRITE ZEROES commands support.