I would suggest at minimum including virtio_blk.ko in the initrd that's
downloadable in the directory, so people can skip running half the
installer to have it be present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To reproduce (use a machine with fast CPU...), on xenial as your host:
qemu-system-arm built from source:
rmerrill@ubuntu-1404:~/qemu$ git remote get-url origin
git://git.qemu-project.org/qemu.git
rmerrill@ubuntu-1404:~/qemu$ git rev-parse --abbrev-ref HEAD
stable-2.9
Public bug reported:
Using the netboot vmlinuz and initrd found here: http://ports.ubuntu.com
/ubuntu-ports/dists/bionic-updates/main/installer-armhf/current/images
/generic-lpae/netboot/
Running in a QEMU "virt" machine, the install goes fine but the result
can't boot because virtio_blk is not
Setting to confirmed because the existence of the anomalous behavior is
uncontroversial (it is already documented in another package's bug).
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
This is essentially the same issue as 1818049 but I am bringing it to
the kernel team's attention as it breaks more than just virtualbox: The
signature for get_user_pages was changed from -142 to -143, which breaks
some out-of-tree or DKMS module builds.
In particular, it
Parallels tools are failing to build for me with similar errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818049
Title:
virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error:
Sorry to necro this bug but can someone clarify that as of now, a fresh
16.04 install with the defaults+LVM will *not* fill the /boot partition?
It was still happening for me as recently as a month or two ago I think.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
