Thanks for checking! Looks like upstream commit
2b96b6676e5a4b464cdfc9d816d8828a4a5d3c0d
fixes this. So this should be fixed on 0.6.1 in testing.
I can confirm - I backported libvirt 0.6.1-1 from squeeze to lenny.
The VNC console immediately works with virt-manager 0.6.0-6 after
passing
reassign 519809 libvirt0
found 519809 0.4.6-10
thanks
On Tue, Mar 17, 2009 at 07:47:03PM +0100, Andreas Unterkircher wrote:
>> Good to know! Does "virsh vncdisplay" list the right port? If
>> not we have to look for the problem in libvirt, not virt-manager.
>
> You seem to be right - vncdisplay f
Good to know! Does "virsh vncdisplay" list the right port? If
not we have to look for the problem in libvirt, not virt-manager.
You seem to be right - vncdisplay for a machine with an automatically
allocated port simply returns nothing (here the first app-vmtest-02).
While the other two's whi
On Sun, Mar 15, 2009 at 08:58:37PM +0100, Andreas Unterkircher wrote:
>> Please attach the domains xml.
>> -- Guido
>
> Sure, XML dump is below. When I start this guest, VNC is indeed
> listening on port 5900 and I can connect to it per hand.
Good to know! Does "virsh vncdisplay" list the right
Please attach the domains xml.
-- Guido
Sure, XML dump is below. When I start this guest, VNC is indeed
listening on port 5900 and I can connect to it per hand.
xenhost:~# netstat -avpn | grep qemu-dm
tcp0 0 127.0.0.1:5900 0.0.0.0:*
LISTEN 2146/qemu-dm
unix 3
severity 519809 normal
thanks
On Sun, Mar 15, 2009 at 01:26:47PM +0100, Andreas Unterkircher wrote:
> When I create a new guest via Virtual Machine Manager, the initial display is
> set to VNC with the VNC port automatically allocated. When I now power up the
> guest and switch to the console tab,
6 matches
Mail list logo
