On Tue, Mar 21, 2017 at 3:59 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Tue, 2017-03-21 at 20:48 +0000, Richard W.M. Jones wrote:
On Tue, Mar 21, 2017 at 12:58:06PM -0700, Adam Williamson wrote:
On Tue, 2017-03-21 at 19:40 +0000, Richard W.M. Jones wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1430297
This has been going on for a few weeks with no attention. It prevents anyone from running libguestfs on Fedora 26.
It's (IMHO) pretty serious for anyone using virtualization: "kernel doesn't boot on qemu" should be a blocker for a Fedora release.
Can anyone see what's going on?
The earlier case looks like https://bugzilla.redhat.com/show_bug.cgi?id=1430043 , which was fixed in rc2. I'm not sure about the latter case, though Thorsten Leemhuis reported intermittent crash / hang during boot with rc2 as:
https://bugzilla.kernel.org/show_bug.cgi?id=194911
Since rc2 I've seen occasional failures which are probably the same as the ones Thorsten was seeing, but usually it works OK. I run 26-on-26 VMs via virt-manager quite a lot, they certainly don't fail every time.
Does libguestfs-test-tool work for you in F26?
Hum, interesting results:
If I run it as a regular user, it works. If I run it as root as usual, it gives me a libvirt error, some permission issue. If I run it as root with LIBGUESTFS_BACKEND=direct , it hits the same kernel trace you hit.
Off the top of my head, I'd guess that the failing cases are using vhost on the host. I've never used vhost in my life, so I have no clue about it.
--Andy