GNOME Bugzilla – Bug 738444
Use virtio-scsi rather than virtio-blk
Last modified: 2018-01-11 10:11:49 UTC
Description of problem: gnome-boxes by default uses virtio-blk disks backed by qcow2 files stored in home directories. It would be nice to use virtio-scsi disks by default with "<driver ... discard='unmap'/>" option tuned on for guests that support virtio-scsi (IIRC RHEL >= 6.4, RHEL 7, Windows >= 7 with virtio drivers). That way, valuable space in user's home can be conserved: ## backing file usage on host $ du -sm .local/share/gnome-boxes/images/rhel7.0 8820 .local/share/gnome-boxes/images/rhel7.0 ## run fstrim in the guest: [root@rhel7 ~]# fstrim -v / /: 2.4 GiB (2528993280 bytes) trimmed ## backing file usage after guest's fstrim [djasa@cihla ~]$ du -sm .local/share/gnome-boxes/images/rhel7.0 6768 .local/share/gnome-boxes/images/rhel7.0 Note that Windows 7 by default issue discards without user intervention, in RHEL (and IIRC Fedora as well), you either have to set up a cron job for fstrim or add "discards" to mount options Version-Release number of selected component (if applicable): gnome-boxes-3.8.3-9.el7.x86_64 How reproducible: always Steps to Reproduce: 1. install a guest that supports virtio-scsi 2. inspect domain xml for the VM 3. Actual results: virtio-blk is used Expected results: virtio-scsi with discard='unmap' is configured Additional info:
Hmm.. I didn't know of virtio-scsi. Thanks for filing this. I should look into it.
Would this be a duplication of bug#685032?
(In reply to comment #2) > Would this be a duplication of bug#685032? I think #685032 is more generic, it discusses different approaches for image compressions. This bug is specifical about TRIM/unmap
(In reply to comment #3) > (In reply to comment #2) > > Would this be a duplication of bug#685032? > > I think #685032 is more generic, it discusses different approaches for image > compressions. This bug is specifical about TRIM/unmap Yeah, thats what I was thinking but if we act on this bug, do we really need more generic solutions?
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > Would this be a duplication of bug#685032? > > > > I think #685032 is more generic, it discusses different approaches for image > > compressions. This bug is specifical about TRIM/unmap > > Yeah, thats what I was thinking but if we act on this bug, do we really need > more generic solutions? Being more specific, makes it much more likely for me (or anyone) to act on it. :) You can see how long bug#685032 has been open w/o any patches.
(In reply to comment #5) > Being more specific, makes it much more likely for me (or anyone) to act on it. > :) You can see how long bug#685032 has been open w/o any patches. I agree with you, I wouldn't mind if you close it as dup.
*** Bug 685032 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/35.