© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Tested against Kernel 4.18 from mainline builds:
http://
For the latter SRU I summarized the testing procedure:
Note: This can but does not have to be tested in nested virtualization (Since we need to change the kernel it is probably the preferred way to do it in nested, so this is what I describe)
1. Get a KVM guest with the Release to test (Cosmic as an example) and give it a size to be able to host a nested guest
$ sudo apt install uvtool-libvirt
$ uvt-simplestrea
$ uvt-kvm create --cpu 8 --memory 4096 --password ubuntu c-nested-kvm-4.18 arch=amd64 release=cosmic label=daily
$ uvt-kvm ssh c-nested-kvm-4.18
2. In the guest set up another guest
$ uvt-kvm ssh c-nested-kvm-4.18
$ uvt-simplestrea
$ uvt-kvm create --password ubuntu c-nested-guest arch=amd64 release=cosmic label=daily
$ sudo apt install uvtool-libvirt
3. The above will work, now get a kernel >=4.18 e.g. the mainline kernels at
https:/
$ wget (link of the day)
$ sudo dpkg -i *.deb
4. reboot into the 4.18 kernel
$ sudo reboot
5. Start the guest again
$ virsh start c-nested-guest
Without fix this will fail like:
error: Failed to start domain c-nested-guest
error: internal error: child reported: Kernel does not provide mount namespace: Permission denied
And an associated Dmesg/Apparmor entry:
[ 519.529760] audit: type=1400 audit(153536482
6. In the guest update from PPA/Proposed that you want to test to bring in the libvirt package with the updated rules (Example with the PPA).
$ sudo add-apt-repository ppa:ci-
$ sudo apt upgrade
7. Start the guest again and it will now work
$ virsh start c-nested-guest