All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Wimmer <r.wimmer@tomorrow-focus.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm@vger.kernel.org
Subject: Re: VNC with KVM-84 doesn't work
Date: Mon, 23 Feb 2009 21:49:08 +0100	[thread overview]
Message-ID: <49A30BC4.1070503@tomorrow-focus.de> (raw)
In-Reply-To: <49A2BD31.9090702@codemonkey.ws>

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


  reply	other threads:[~2009-02-23 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2009-02-23 21:26   ` Florent
2009-02-24  1:09     ` Anthony Liguori
2009-02-24  6:24       ` Florent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49A30BC4.1070503@tomorrow-focus.de \
    --to=r.wimmer@tomorrow-focus.de \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.