Re: [fedora-virt] trying to test qemu-spice on F12
On Wed, Dec 23, 2009 at 11:19:50AM +0100, Gianluca Cecchi wrote:
hello,
I'm testing qemu-spice for some windows guests..
I installed repo files and sw components as I read on
www.linux-kvm.com web site
Now I would like to try this on my host that is a F12 x86_64 where I
already have virt-manager / livirtd set up for other pre-existing vm.
I'm afraid that this might not be the best place for asking, as spice is
still not a part of Fedora.
Better luck at spice-space-devel(a)lists.sourceforge.net
So some sort of questions arise:
1) Can I manually start a VM from command line taking advantage of
libvirtd setup already in place?
For example I have virbr0 as default enabled and I tried something like:
/usr/libexec/qemu-spice -hda disc0.img -m 512 -localtime -qxl 1
-spice port=5930,disable-ticketing -cdrom spice-windows.iso -net nic
-net user,net=192.168.122.0/24,host=192.168.122.1
but it seems the guest takes the default 10.0.2.15 ip and it is not
able to exit to the internet as I would like to see and verify
graphical improvements in my guest....
what would be the manual command to attach to virbr0?
There's nothing simple that I know of, as you have to create a tap device,
connect it to virbr0 on one end and to qemu on the other. But if all you
want is to try out youtube, why don't you try qemu's defaults (this
should give the guest the 10.0.2.15 and let it access the world via
NAT).
I also tried to mimic start line of a vm started from virt-manager
using
"-net nic,vlan=0,name=nic.0 -net tap,fd=24,vlan=0,name=tap.0"
but then I'm not able to connect via spice to the guest....
I suspect it's related to the fact that no one opened file descriptor 24
for your qemu.
2) doing some tests with the client, run with the command:
/usr/bin/spicec -h localhost -p 5930
I saw previous posts telling to hit Ctrl+F12 to exit its window, but
it seems it is not working for me.
Shift F12 should release the keyboard focus, while Shift F11 toggles
fullscreen mode.
tried severale key combinations but the only chance to come back
with
the pointer to the host is to shutdown the VM....
any hint on this?
HTH,
Dan.