0.12.x: message "Option 'ipv4': Use 'on' or 'off'"
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
I get the same message since the update, is it -chardev option related?
Quoted 21 lines · 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
Quoted 22 lines · Thomas Beinicke
I get the same message since the update, is it -chardev option related?
Quoted 18 lines · 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.
qemu-sockets.c +4 -4
@@ -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 ; }
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 useinet_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.
Quoted 1 line · On Wednesday 10 February 2010 09:30:57 xming wrote:
hi,
Hi,
Quoted 9 lines
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 useinet_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
Quoted 12 lines
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 15 lines · Thomas Beinicke
Quoted 1 line · On Wednesday 10 February 2010 09:30:57 xming wrote:
hi,
Hi,
Quoted 9 lines
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 useinet_listen_opts: FAILED
Quoted 8 lines
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