* VNC with KVM-84 doesn't work
@ 2009-02-23 8:58 Robert Wimmer
2009-02-23 15:13 ` Anthony Liguori
0 siblings, 1 reply; 6+ messages in thread
From: Robert Wimmer @ 2009-02-23 8:58 UTC (permalink / raw)
To: kvm
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: VNC with KVM-84 doesn't work
2009-02-23 8:58 VNC with KVM-84 doesn't work Robert Wimmer
@ 2009-02-23 15:13 ` Anthony Liguori
2009-02-23 20:49 ` Robert Wimmer
2009-02-23 21:26 ` Florent
0 siblings, 2 replies; 6+ messages in thread
From: Anthony Liguori @ 2009-02-23 15:13 UTC (permalink / raw)
To: Robert Wimmer; +Cc: kvm
Robert Wimmer wrote:
> 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
>
You cannot combine -curses and -vnc.
Regards,
Anthony Liguori
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: VNC with KVM-84 doesn't work
2009-02-23 15:13 ` Anthony Liguori
@ 2009-02-23 20:49 ` Robert Wimmer
2009-02-23 21:26 ` Florent
1 sibling, 0 replies; 6+ messages in thread
From: Robert Wimmer @ 2009-02-23 20:49 UTC (permalink / raw)
To: Anthony Liguori; +Cc: kvm
Anthony Liguori wrote:
> Robert Wimmer wrote:
>> 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
>>
>
> You cannot combine -curses and -vnc.
>
> Regards,
>
> Anthony Liguori
>
Thanks! That helped. But it's strange this I'm using this since kvm-78
(at least).
Regards,
Robert
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: VNC with KVM-84 doesn't work
2009-02-23 15:13 ` Anthony Liguori
2009-02-23 20:49 ` Robert Wimmer
@ 2009-02-23 21:26 ` Florent
2009-02-24 1:09 ` Anthony Liguori
1 sibling, 1 reply; 6+ messages in thread
From: Florent @ 2009-02-23 21:26 UTC (permalink / raw)
To: kvm
Anthony Liguori a écrit :
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: VNC with KVM-84 doesn't work
2009-02-23 21:26 ` Florent
@ 2009-02-24 1:09 ` Anthony Liguori
2009-02-24 6:24 ` Florent
0 siblings, 1 reply; 6+ messages in thread
From: Anthony Liguori @ 2009-02-24 1:09 UTC (permalink / raw)
To: Florent; +Cc: kvm
Florent wrote:
> Anthony Liguori a écrit :
>> 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
> Regards,
>
> - Florent
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: VNC with KVM-84 doesn't work
2009-02-24 1:09 ` Anthony Liguori
@ 2009-02-24 6:24 ` Florent
0 siblings, 0 replies; 6+ messages in thread
From: Florent @ 2009-02-24 6:24 UTC (permalink / raw)
To: kvm
Anthony Liguori a écrit :
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-02-24 6:28 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-23 8:58 VNC with KVM-84 doesn't work Robert Wimmer
2009-02-23 15:13 ` Anthony Liguori
2009-02-23 20:49 ` Robert Wimmer
2009-02-23 21:26 ` Florent
2009-02-24 1:09 ` Anthony Liguori
2009-02-24 6:24 ` Florent
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox