Il giorno dom, 23/10/2011 alle 16.13 +0200, Matthias Bolte ha scritto: I tried the patch with VirtualBox 4.1.4, and it seems to work. The only difference with QEMU is that VMs are displayed in a VirtualBox window instead of the native virt-manager window. I never tried previous version of VirtualBox so I don't know if this is expected. Cheers -- Stefano Facchini <stefano.facchini(a)gmail.com&gt;

Il giorno lun, 24/10/2011 alle 09.04 +0800, Osier Yang ha scritto: Sure, I created a connection to vbox+unix:///session which lets me see my virtualbox VMs in virt-manager. But if a open a VM, virt-manager runs VirtualBox to show the display (differently from QEMU guests, for example). Then I tried to launch the machine with: $ VirtualHeadless --startvm "GuestMachine" -vnc -vncport 5900 and then tried to connect to it with $ virt-manager -c vnc+tcp://localhost:5900 but I got this: packet 1380336156 bytes received from server too large, want 262144 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 1146, in _open_thread self.vmm = self._try_open() File "/usr/share/virt-manager/virtManager/connection.py", line 1130, in _try_open flags) File "/usr/lib/python2.7/site-packages/libvirt.py", line 102, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: packet 1380336156 bytes received from server too large, want 262144 Why I can't connect via VNC? Other clients seems to be able to do that (Vinagre for example). Cheers -- Stefano Facchini <stefano.facchini(a)gmail.com&gt;