Public bug reported:
$ vagrant up tactyle
...
==> tactyle: Creating shared folders metadata...
==> tactyle: Starting domain.
==> tactyle: Waiting for domain to get an IP address...
And it stalls there.
Using Virtual Machine Manager GUI I was able to monitor what the
vagrant-libvirt VM was doing and found it had dropped to the initramfs
shell.
Using 'blkid' and also checking /sys/block/ and /dev/block/ revealed
there were no storage devices (only loop device nodes).
Looking at the device config revealed the "Controller SCSI" was using
the type "Hypervisor default" instead of "VirtIO SCSI". Changing that
manually via Virtual Machine Manager and forcing a reboot solved the
issue.
Currently vagrant-libvirt does not provide a way to set the device type.
It seems that the QEMU default may have changed relatively recently to
cause this.
** Affects: vagrant-libvirt
Importance: Unknown
Status: Unknown
** Affects: vagrant-libvirt (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/vagrant-libvirt/vagrant-libvirt/issues #633
https://github.com/vagrant-libvirt/vagrant-libvirt/issues/633
** Also affects: vagrant-libvirt via
https://github.com/vagrant-libvirt/vagrant-libvirt/issues/633
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784241
Title:
18.04: VM stalls at initramfs due to not finding the rootfs block
device
To manage notifications about this bug go to:
https://bugs.launchpad.net/vagrant-libvirt/+bug/1784241/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
