View previous topic :: View next topic |
Author |
Message |
Hossie Tux's lil' helper
Joined: 08 Dec 2005 Posts: 116
|
Posted: Sat Jan 03, 2015 12:14 pm Post subject: libguestfs: Ebuild not working at all? |
|
|
Hi,
I'm trying to get libguestfs to work as I'm running a KVM hypervisor.
I'm curious if somebody had luck getting this to work, as I'm not.
After reconfiguring my kernel as the ebuild suggested and adding support for virtio (linux guest stuff on a hypervisor, is that really necessary?!) it always complained about the missing supermin:
libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH
In an strace you see that the program is looking for initramfs.x86_64.img and vmlinuz.x86_64, but the ebuild libguestfs-appliance just puts the files as "kernel" and "initrd" there.
After creating two symlinks the error from above vanishes, it successfully boots the temp machine, and then just hangs, waiting for $SOMETHING:
[pid 14182] read(12, "supermin: waiting another 262144"..., 8192) = 76
Anybody had any luck with this? |
|
Back to top |
|
|
rwmjones n00b
Joined: 05 Jan 2015 Posts: 2
|
Posted: Mon Jan 05, 2015 1:21 am Post subject: |
|
|
Bottom line is you need to run "libguestfs-test-tool". If you decide to post the output here then please post the complete output and do not edit it.
Symptoms look like you are missing a virtio driver in your kernel, but hard to tell w/o seeing the output above.
If you want to use different host & appliance kernels then see the guestfs FAQ. |
|
Back to top |
|
|
Hossie Tux's lil' helper
Joined: 08 Dec 2005 Posts: 116
|
Posted: Mon Jan 05, 2015 10:48 am Post subject: |
|
|
Here you go: http://pastebin.com/Gv1gRMrs
It seems strange, as it seems the kernel is waiting for sdb to appear, where no sdb is configured?
Code: |
<disk type='file' device='disk'>
<driver name='qemu' type='raw' cache='unsafe'/>
<source file='/tmp/libguestfsH4L6LT/scratch.1'/>
<backingStore/>
<target dev='sda' bus='scsi'/>
<alias name='scsi0-0-0-0'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
|
<cmdline> even specifies root=/dev/sdb? |
|
Back to top |
|
|
rwmjones n00b
Joined: 05 Jan 2015 Posts: 2
|
Posted: Mon Jan 19, 2015 8:52 am Post subject: |
|
|
Yes, something very wrong is going on there. However I am not able to reproduce the problem here.
I downloaded the fixed appliance from http://libguestfs.org/download/binaries/appliance/appliance-1.28.1.tar.xz , and unpacked it in /tmp (ie. creating the directory /tmp/appliance).
Then I set:
Code: | export LIBGUESTFS_PATH=/tmp/appliance |
I was able to run libguestfs-test-tool successfully with both the direct and libvirt backends. I did not observe the bug that you are seeing. |
|
Back to top |
|
|
Hossie Tux's lil' helper
Joined: 08 Dec 2005 Posts: 116
|
Posted: Mon Jan 19, 2015 4:39 pm Post subject: |
|
|
This is _very_ strange.
When downloading the appliance like you did and specifying it with LIBGUESTFS_PATH it works! So there seems something wrong with app-emulation/libguestfs-appliance...
I'll have a look if I can figure out what's different. |
|
Back to top |
|
|
Hossie Tux's lil' helper
Joined: 08 Dec 2005 Posts: 116
|
Posted: Mon Jan 19, 2015 6:32 pm Post subject: |
|
|
For some VERY, VERY strange reason the problem's gone when copying the README.fixed into /usr/share/guestfs/appliance (that's the only difference between the tar and the ebuild's directory, even the md5sums match) |
|
Back to top |
|
|
Hossie Tux's lil' helper
Joined: 08 Dec 2005 Posts: 116
|
|
Back to top |
|
|
|