Skip to contentSkip to conversation

VNC with KVM-84 doesn't work

DISCUSSION Robert Wimmer 3 participants 6 messages Feb 23, 2009 – Feb 24, 2009 KVM

lore
Share & tools
lore
#0 lore raw

Hi!

I'm using kernel 2.6.28-r2 (Gentoo) and kvm-84 (Intel Xeon CPU X7350, x86_64, host and guest OS and kernel are the same)

I've normally bound the VNC port to 127.0.0.1:4444 (or 4445, ... if more KVMs are running). But now "netstat -tlpn" doesn't show any KVM bound to localhost. KVM-83 and all other versions before haven't had this problem. I'm always starting the KVMs like this (snippet of the start script):

$KVM -m $MEMORY \
-smp $CPU \
-curses \
-daemonize \
-k de \
-vnc "$VNC" \
-monitor "$MONITOR" \
-localtime \
-pidfile /var/run/kvm-$KVMNAME.pid \
-drive file=/data/kvm/kvmimages/$KVMNAME.qcow2,if=virtio,boot=on \
-net nic,vlan=104,model=virtio,macaddr=$MACADDR_B \
-net tap,vlan=104,ifname=tap.b.$KVMNAME,script=no \
-net nic,vlan=96,model=virtio,macaddr=$MACADDR_F \
-net tap,vlan=96,ifname=tap.f.$KVMNAME,script=no

$VNC is 127.0.0.1:1 for example. KVM images running fine but no VNC port to connect. Connecting with telnet to the kvm and entering "info vnc" tells me "VNC server disabled". But I haven't disabled it.

Additionally after starting a KVM with this script I don't see the cursor of my bash anymore. The screen get's cleared, the prompt appears again and I've to type "exit" on the shell blindly and reconnect to the host to get my cursor back.

Thanks for any hints!
Robert

#1 lore raw
Quoted 23 lines · Robert Wimmer

Hi!

I'm using kernel 2.6.28-r2 (Gentoo) and kvm-84 (Intel Xeon CPU X7350, x86_64, host and guest OS and kernel are the same)

I've normally bound the VNC port to 127.0.0.1:4444 (or 4445, ... if more KVMs are running). But now "netstat -tlpn" doesn't show any KVM bound to localhost. KVM-83 and all other versions before haven't had this problem. I'm always starting the KVMs like this (snippet of the start script):

$KVM -m $MEMORY \

(quoted diff) +0 -9
-smp $CPU \
-curses \
-daemonize \
-k de \
-vnc "$VNC" \
-monitor "$MONITOR" \
-localtime \
-pidfile /var/run/kvm-$KVMNAME.pid \
-drive

file=/data/kvm/kvmimages/$KVMNAME.qcow2,if=virtio,boot=on \

Review

Quoted 4 lines
(quoted diff) +0 -4
-net nic,vlan=104,model=virtio,macaddr=$MACADDR_B \
-net tap,vlan=104,ifname=tap.b.$KVMNAME,script=no \
-net nic,vlan=96,model=virtio,macaddr=$MACADDR_F \
-net tap,vlan=96,ifname=tap.f.$KVMNAME,script=no

You cannot combine -curses and -vnc.

Regards,

Anthony Liguori

#2 lore raw
Quoted 31 lines · Anthony Liguori
Quoted 23 lines · Robert Wimmer

Hi!

I'm using kernel 2.6.28-r2 (Gentoo) and kvm-84 (Intel Xeon CPU X7350, x86_64, host and guest OS and kernel are the same)

I've normally bound the VNC port to 127.0.0.1:4444 (or 4445, ... if more KVMs are running). But now "netstat -tlpn" doesn't show any KVM bound to localhost. KVM-83 and all other versions before haven't had this problem. I'm always starting the KVMs like this (snippet of the start script):

$KVM -m $MEMORY \

(quoted diff) +0 -9
-smp $CPU \
-curses \
-daemonize \
-k de \
-vnc "$VNC" \
-monitor "$MONITOR" \
-localtime \
-pidfile /var/run/kvm-$KVMNAME.pid \
-drive

file=/data/kvm/kvmimages/$KVMNAME.qcow2,if=virtio,boot=on \

Review

Quoted 4 lines
(quoted diff) +0 -4
-net nic,vlan=104,model=virtio,macaddr=$MACADDR_B \
-net tap,vlan=104,ifname=tap.b.$KVMNAME,script=no \
-net nic,vlan=96,model=virtio,macaddr=$MACADDR_F \
-net tap,vlan=96,ifname=tap.f.$KVMNAME,script=no

You cannot combine -curses and -vnc.

Quoted 4 lines

Regards,

Anthony Liguori

Thanks! That helped. But it's strange this I'm using this since kvm-78 (at least).

Regards,
Robert

#3 lore raw
In reply to Anthony Liguori
Quoted 1 line · Anthony Liguori

You cannot combine -curses and -vnc.

Simple dummy questions:
Why cannot we combine visualization options?
In other words, what prevent forks of back-end video message processing in order to have multiple views of the same virtual machines at the same time?

And the corollary is:
Why cannot we switch on/off available visualizations (ncurses, vnc, sdl) at runtime (for instance: using the monitor)?
I mainly use VM as services: they are started with vnc display without any viewer attached, this configuration allows local and remote accesses to the VM display. But this configuration is static. Sometimes, I would like to enable the SDL viewer without restarting the whole VM.

Regards,

- Florent

#4 lore raw
Quoted 10 lines · Florent
Quoted 1 line · Anthony Liguori

You cannot combine -curses and -vnc.

Simple dummy questions:
Why cannot we combine visualization options?
In other words, what prevent forks of back-end video message processing in order to have multiple views of the same virtual machines at the same time?

And the corollary is:
Why cannot we switch on/off available visualizations (ncurses, vnc, sdl) at runtime (for instance: using the monitor)?
I mainly use VM as services: they are started with vnc display without any viewer attached, this configuration allows local and remote accesses to the VM display. But this configuration is static. Sometimes, I would like to enable the SDL viewer without restarting the whole VM.

There is an effort to make the video subsystem in QEMU more dynamic to support the sort of features you're talking about it. We're slowly getting there. It's just a matter of developer effort being a finite resource.

Regards,

Anthony Liguori

Quoted 8 lines

Regards,

- Florent

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#5 lore raw
Quoted 1 line · Anthony Liguori

There is an effort to make the video subsystem in QEMU more dynamic to support the sort of features you're talking about it. We're slowly getting there. It's just a matter of developer effort being a finite resource.

You're right, speaking as the manager of two open-source projects, the problem is the same everywhere :) Although I'm not a C++ guru, I'll see what I can do with qemu.

Regards,

- Florent