From: Thomas Beinicke <thomas.beinicke@fsd-web.de>
To: KVM mailing list <kvm@vger.kernel.org>
Subject: Re: 0.12.x: message "Option 'ipv4': Use 'on' or 'off'"
Date: Wed, 10 Feb 2010 10:04:10 +0100 [thread overview]
Message-ID: <201002101004.10307.thomas.beinicke@fsd-web.de> (raw)
In-Reply-To: <519a8b111002100030x25237ebucd88d7f00cd59730@mail.gmail.com>
On Wednesday 10 February 2010 09:30:57 xming wrote:
> hi,
Hi,
> I am hitting this bug as well, using qemu-kvm-0.12.2 with the following
> command
>
> /usr/bin/kvm -name pfsense,process=pfsense -m 256 -vnc
> 192.168.0.254:13 -smp 1 -hda /dev/volume01/G-pfsense -vga std
> Option 'ipv4': Use 'on' or 'off'
> Failed to parse "yes" for "dummy.ipv4"
> inet_listen_opts: bind(ipv4,192.168.0.254,5913): Address already in use
> inet_listen_opts: FAILED
It looks like the same VNC port (5913 in your case) is already in use by
another VM or service.
Does 'netstat -lnp' list any program using that port?
For me the first two messages disappeard when I left out the IP in the vnc
defintion. So instead of -vnc 192.168.0.254:13 I just used -vnc :13 . Of
course that makes only sense if you just have a single IP on that machine and
there is no need to bind it to a specific one.
Cheers,
Thomas
>
> I check the source in the tarball and git master, this patch is not in
> them. Is there any reason that this is not merged?
>
> cheers
>
>
> PS. this mail was only sent to Marcelo the first time, sorry for that.
> --
> 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
next prev parent reply other threads:[~2010-02-10 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 10:53 0.12.x: message "Option 'ipv4': Use 'on' or 'off'" Thomas Mueller
2010-01-04 8:18 ` Thomas Beinicke
2010-01-06 8:29 ` Marcelo Tosatti
2010-02-10 8:30 ` xming
2010-02-10 9:04 ` Thomas Beinicke [this message]
2010-02-12 15:11 ` xming
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=201002101004.10307.thomas.beinicke@fsd-web.de \
--to=thomas.beinicke@fsd-web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox