public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* 0.12.x: message "Option 'ipv4': Use 'on' or 'off'"
@ 2010-01-02 10:53 Thomas Mueller
  2010-01-04  8:18 ` Thomas Beinicke
  0 siblings, 1 reply; 6+ messages in thread
From: Thomas Mueller @ 2010-01-02 10:53 UTC (permalink / raw)
  To: kvm

hi

since 0.12.x i get the following messages starting a vm: 

Option 'ipv4': Use 'on' or 'off'
Failed to parse "yes" for "dummy.ipv4"


command is:


kvm -usbdevice tablet -drive file=~/virt/xp/drive1.qcow2,cache=writeback -
drive file=~/virt/xp/drive2.qcow2,cache=writeback -net nic -net 
user,hostfwd=tcp:127.0.0.1:3389-:3389 -k de-ch -m 1024 -smp 2 -vnc 
127.0.0.1:20 -monitor unix:/var/run/kvm-winxp.socket,server,nowait -
daemonize -localtime

what is option ipv4?

- Thomas


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 0.12.x: message "Option 'ipv4': Use 'on' or 'off'"
  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
  0 siblings, 1 reply; 6+ messages in thread
From: Thomas Beinicke @ 2010-01-04  8:18 UTC (permalink / raw)
  To: kvm@vger.kernel.org

I get the same message since the update, is it -chardev option related?


On Saturday 02 January 2010 11:53:42 Thomas Mueller wrote:
> hi
> 
> since 0.12.x i get the following messages starting a vm:
> 
> Option 'ipv4': Use 'on' or 'off'
> Failed to parse "yes" for "dummy.ipv4"
> 
> 
> command is:
> 
> 
> kvm -usbdevice tablet -drive file=~/virt/xp/drive1.qcow2,cache=writeback -
> drive file=~/virt/xp/drive2.qcow2,cache=writeback -net nic -net
> user,hostfwd=tcp:127.0.0.1:3389-:3389 -k de-ch -m 1024 -smp 2 -vnc
> 127.0.0.1:20 -monitor unix:/var/run/kvm-winxp.socket,server,nowait -
> daemonize -localtime
> 
> what is option ipv4?
> 
> - Thomas
> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 0.12.x: message "Option 'ipv4': Use 'on' or 'off'"
  2010-01-04  8:18 ` Thomas Beinicke
@ 2010-01-06  8:29   ` Marcelo Tosatti
  2010-02-10  8:30     ` xming
  0 siblings, 1 reply; 6+ messages in thread
From: Marcelo Tosatti @ 2010-01-06  8:29 UTC (permalink / raw)
  To: Thomas Beinicke, Mark McLoughlin; +Cc: kvm@vger.kernel.org

On Mon, Jan 04, 2010 at 09:18:01AM +0100, Thomas Beinicke wrote:
> I get the same message since the update, is it -chardev option related?
> 
> 
> On Saturday 02 January 2010 11:53:42 Thomas Mueller wrote:
> > hi
> > 
> > since 0.12.x i get the following messages starting a vm:
> > 
> > Option 'ipv4': Use 'on' or 'off'
> > Failed to parse "yes" for "dummy.ipv4"
> > 
> > 
> > command is:
> > 
> > 
> > kvm -usbdevice tablet -drive file=~/virt/xp/drive1.qcow2,cache=writeback -
> > drive file=~/virt/xp/drive2.qcow2,cache=writeback -net nic -net
> > user,hostfwd=tcp:127.0.0.1:3389-:3389 -k de-ch -m 1024 -smp 2 -vnc
> > 127.0.0.1:20 -monitor unix:/var/run/kvm-winxp.socket,server,nowait -
> > daemonize -localtime
> > 
> > what is option ipv4?

This patch should fix it:

Fix inet_parse typo

qemu_opt_set wants on/off, not yes/no.

diff --git a/qemu-sockets.c b/qemu-sockets.c
index 8850516..a88b2a7 100644
--- a/qemu-sockets.c
+++ b/qemu-sockets.c
@@ -424,7 +424,7 @@ static int inet_parse(QemuOpts *opts, const char *str)
                     __FUNCTION__, str);
             return -1;
         }
-        qemu_opt_set(opts, "ipv6", "yes");
+        qemu_opt_set(opts, "ipv6", "on");
     } else if (qemu_isdigit(str[0])) {
         /* IPv4 addr */
         if (2 != sscanf(str,"%64[0-9.]:%32[^,]%n",addr,port,&pos)) {
@@ -432,7 +432,7 @@ static int inet_parse(QemuOpts *opts, const char *str)
                     __FUNCTION__, str);
             return -1;
         }
-        qemu_opt_set(opts, "ipv4", "yes");
+        qemu_opt_set(opts, "ipv4", "on");
     } else {
         /* hostname */
         if (2 != sscanf(str,"%64[^:]:%32[^,]%n",addr,port,&pos)) {
@@ -450,9 +450,9 @@ static int inet_parse(QemuOpts *opts, const char *str)
     if (h)
         qemu_opt_set(opts, "to", h+4);
     if (strstr(optstr, ",ipv4"))
-        qemu_opt_set(opts, "ipv4", "yes");
+        qemu_opt_set(opts, "ipv4", "on");
     if (strstr(optstr, ",ipv6"))
-        qemu_opt_set(opts, "ipv6", "yes");
+        qemu_opt_set(opts, "ipv6", "on");
     return 0;
 }
 

^ permalink raw reply related	[flat|nested] 6+ messages in thread

* Re: 0.12.x: message "Option 'ipv4': Use 'on' or 'off'"
  2010-01-06  8:29   ` Marcelo Tosatti
@ 2010-02-10  8:30     ` xming
  2010-02-10  9:04       ` Thomas Beinicke
  0 siblings, 1 reply; 6+ messages in thread
From: xming @ 2010-02-10  8:30 UTC (permalink / raw)
  To: kvm@vger.kernel.org

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


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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 0.12.x: message "Option 'ipv4': Use 'on' or 'off'"
  2010-02-10  8:30     ` xming
@ 2010-02-10  9:04       ` Thomas Beinicke
  2010-02-12 15:11         ` xming
  0 siblings, 1 reply; 6+ messages in thread
From: Thomas Beinicke @ 2010-02-10  9:04 UTC (permalink / raw)
  To: KVM mailing list

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 0.12.x: message "Option 'ipv4': Use 'on' or 'off'"
  2010-02-10  9:04       ` Thomas Beinicke
@ 2010-02-12 15:11         ` xming
  0 siblings, 0 replies; 6+ messages in thread
From: xming @ 2010-02-12 15:11 UTC (permalink / raw)
  To: Thomas Beinicke; +Cc: KVM mailing list

On Wed, Feb 10, 2010 at 10:04 AM, Thomas Beinicke
<thomas.beinicke@fsd-web.de> wrote:
> 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.

That port is not in use, I checked with netstat, you can also see that
before bind
failed there are 2 other error messages.

Anyway it's applied now
http://lists.gnu.org/archive/html/qemu-devel/2010-02/msg00731.html
but that's qemu not qemu-kvm, or will the next version of kvm-qemu be rebased on
qemu?

cheers

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2010-02-12 15:11 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2010-02-12 15:11         ` xming

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox