Hello,
jstanek pinged me today with some weird errors :) so I got tempted to ask:
Is anyone else experiencing some Vagrant-related issues?
Most probable cause:
- there was a Change, in which `qemu://session` (user session) is used by
default. That means root privilleges are not required
On Sun, 2019-03-31 at 10:04 +0200, Dridi Boukelmoune wrote:
> Hello,
>
> If like me you use Vagrant with VirtualBox, you may see an update to
> version 6 from RPM Fusion free for f29. The problem you may face
> later
> is that f29's version of Vagrant doesn't support VirtualBox 6.
>
> This was
Hello,
If like me you use Vagrant with VirtualBox, you may see an update to
version 6 from RPM Fusion free for f29. The problem you may face later
is that f29's version of Vagrant doesn't support VirtualBox 6.
This was enough to solve it for me:
dnf upgrade vagrant --releasever 30
Assuming
On Thu, Nov 28, 2013 at 09:47:34PM -0700, Nathanael Noblet wrote:
[root@mba Vagrant]# vagrant up --provider=kvm
Bringing machine 'default' up with 'kvm' provider...
[default] Importing base box 'f19'...
qemu-img:
/root/.vagrant.d/tmp/storage-pool/box-disk1-1385699731.img: error
while
Sorry for the cross + top post however I figured perhaps -devel folks
may have some ideas as to what is going on belowl
On 10/17/2013 06:36 AM, Alex Drahon wrote:
On 16/10/13 23:54, Nathanael D. Noblet wrote:
On 10/15/2013 01:06 PM, Alex Drahon wrote:
Hope some of you can test it.
After
