Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1092132

Bug#989462: Info received (About bumping Vagrant box disk image to 1TB)

Show all headers | View raw

On 2/3/22 22:58, Hans-Christoph Steiner wrote:
>  > - you add to your pull request a change of the virtualized disk
>  > controller from virtio-blk to virtio-scsi and to the default libvirt
>  > vagrantfile the "unmap" option so that deletion of blocks in the guest
>  > are propagated om host storage
> 
> I looked into this a bit more.  These feature weren't added to 
> vagrant-libvirt until 0.4.0, so no stable Debian package of 
> vagrant-libvirt could support this yet.  Debian/testing has 0.7.0, and a 
> backport to stable would be possible.  I guess a lot of people just use 
> `vagrant plugin install ...`. It might be possible to make it work with 
> older vagrant-libvirt versions by using a hack like this:
> 
> https://github.com/vagrant-libvirt/vagrant-libvirt/pull/692#issuecomment-922329049 
> 
> 
> 
> There is a little more info here:
> https://github.com/vagrant-libvirt/vagrant-libvirt/issues/999#issuecomment-487728207 
> 
> 
> 
> ```
> ENV['VAGRANT_EXPERIMENTAL'] = 'typed_triggers'
> 
> require 'open3'
> 
> Vagrant.configure('2') do |config|
>    ...
>    config.vm.provider :libvirt do |lv, config|
>      lv.storage :file, :size => '3G', :device => 'sda', :bus => 'scsi', 
> :discard => 'unmap', :cache => 'unsafe'
>      config.trigger.before 
> :'VagrantPlugins::ProviderLibvirt::Action::StartDomain', type: :action 
> do |trigger|
>        trigger.ruby do |env, machine|
>          stdout, stderr, status = Open3.capture3(
>            'virt-xml', machine.id,
>            '--edit', 'type=scsi',
>            '--controller', 'model=virtio-scsi')
>          if status.exitstatus != 0
>            raise "failed to run virt-xml to modify the controller model. 
> status=#{status.exitstatus} stdout=#{stdout} stderr=#{stderr}"
>          end
>        end
>      end
>      ...
>    end
> end
> ```

Hi Hans-Christoph

I had a look at this and it looks like although we can now set via the 
`disk_driver` options to use `discard` when a SCSI controller is 
choosed, it is still not possible to set the SCSI controller `model` to 
virtio-scsci via a vagrant-libvirt option. Without a virtio-scsi SCSI 
controller I/O will be 10 times slower.

We could actually force the controller model and the discard option 
manually in the Vagrantfile shipped by the box using the hack/workaround 
you pasted above. But the :action trigger used there is an experimental 
feature, requiring VAGRANT_EXPERIMENTAL="typed_triggers" to be set.
So this is too much of an over stretch here at the momment.

When time allows, I will now try to use a box with virtio-fs and see how 
it works against NFS as this seem to be way the way forward (maybe use 
virtio-fs instead of NFS too by default for libvirt too)

Emmanuel




-- 
You know an upstream is nice when they even accept m68k patches.
   - John Paul Adrian Glaubitz, Debian OpenJDK maintainer

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#989462: About bumping Vagrant box disk image to 1TB Emmanuel Kasper <manu@debian.org> - 2022-01-20 19:30 +0100
  Bug#989462: About bumping Vagrant box disk image to 1TB Hans-Christoph Steiner <hans@eds.org> - 2022-01-21 12:20 +0100
    Bug#989462: Info received (About bumping Vagrant box disk image to 1TB) Hans-Christoph Steiner <hans@eds.org> - 2022-02-03 23:10 +0100
      Bug#989462: Info received (About bumping Vagrant box disk image to 1TB) Emmanuel Kasper <manu@debian.org> - 2022-02-05 14:10 +0100

csiph-web