Re: Now that I've built gnome-boxes with jhbuild...



On 12/05/2011 12:09 PM, Daniel P. Berrange wrote:
On Mon, Dec 05, 2011 at 12:03:13PM -0200, Lucas Meneghel Rodrigues wrote:
Ok, so after a bit of thinkering I've got a successful build of
gnome boxes. Some things that are worth mentioning:

2) I know virt-manager does ask me for the admin password, so I
would assume you will need some sort of root-like access for gnome
boxes as well. In any case, I'm figuring out how the jhbuild libvirt
version would coexist with my system wide one, even considering
there's the libvirt daemon to care about.

The reason virt-manager asks for admin password is that it is using
the privileged 'qemu:///system' instance. Since gnome-boxes is
intended as a per-user desktop session application, it naturally
uses 'qemu:///session' instead, which is a private per-user instance
of libvirt&  thus not requiring any password.

WRT to having jhbuild co-exist with system libvirt build, the key
is to make sure LD_LIBRARY_PATH points the newly build libvirt
client library. In addition, normally qemu:///session will autospawn
the libvirtd daemon - if you ever run the RPM installed 'virsh'
instead of the jhbuild one, you'll end up with the wrong libvirtd
binary auto-spawned.

I've tried to investigate a bit what is going on, for some reason I can't start qemu:///session by no means, the error is always:

internal error Process exited while reading console log output:

I've tried using jhbuild, that sets LD_LIBRARY_PATH

[lmr@freedom ~]$ set | grep LD_LIBRARY_PATH
LD_LIBRARY_PATH=/home/lmr/gnome/lib64
UNMANGLED_LD_LIBRARY_PATH=

So, digging a little further I managed to get the qemu command line that boxes (through libvirt) was assembling and tried to run it to see what the fuss was all about:

/usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -name Microsoft Windows 7 -uuid ded18667-a76b-8c56-6e1a-86d45641d466 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/home/lmr/.libvirt/qemu/lib/Microsoft Windows 7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -drive file=/home/lmr/.config/gnome-boxes/images/Microsoft Windows 7.qcow2,if=none,id=drive-ide0-0-0,format=qcow2 -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/home/lmr/Virt/isos/windows/en_windows_7_ultimate_x64_dvd_x15-65922.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -drive file=/home/lmr/.cache/gnome-boxes/win7-unattended.img,if=none,id=drive-fdc0-0-0,format=raw -global isa-fdc.driveA=drive-fdc0-0-0 -netdev user,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:11:22:33:44:55,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing -vga std -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4

And the reason of failure:

connect(unix:/home/lmr/.libvirt/qemu/lib/Microsoft): No such file or directory
chardev: opening backend "socket" failed: No such file or directory

Aha, so the domain names have spaces on it:

[lmr@freedom ~]$ virsh list --all
 Id Name                 State
----------------------------------
  - Microsoft Windows 7    shut off


I just recall that in virt-manager I could not create domain names with spaces on it, something that boxes is doing. So, it seems plausible that this is the problem. Makes sense?

Lucas


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]