Issue with new ARGS option

B

bitbud

New Member
Dec 2, 2008
25
0
1
Dietmar,
Grateful for the new "args" option in the conf files. However, there is a "no whitespace" problem with it. Several of the most useful arguments to pass require white spaces, and quotes. I am trying to pass a single argument of:

-incoming "exec:dd if=fedstate.img"

This is what it looks like from the KVM command line. It is a single argument 'incoming' with a single parameter. That parameter must be in quotes as above. I tried several formats (without the leading hyphen) to get it to take, but it didnt work. I assume the whitespace is the issue, and possible the quotes as well.

Anything you can do to adjust the args option to allow for this properly?

Thanks
 
bitbud said:
Dietmar,
Grateful for the new "args" option in the conf files. However, there is a "no whitespace" problem with it.
Click to expand...

I documented that behaviour in the manual page.

bitbud said:
Several of the most useful arguments to pass require white spaces, and quotes.
Click to expand...

really - which ones?

bitbud said:
I am trying to pass a single argument of:

-incoming "exec:dd if=fedstate.img"
Click to expand...

Why dont you use:

Code: 
qm start VMID --incoming fedstate.img

bitbud said:
Anything you can do to adjust the args option to allow for this properly?
Click to expand...

We need a better parser, i know.

- Dietmar
 
Still testing

Thanks for the quick turn-around. I download the patch and have been testing since then. I haven't been able to get it to work yet, but I need to test it more. I am trying to pass the full string as above, so I am not sure if there is a problem with the quotes, or a need to escape them somehow. As it may also be an issue with my test system, I need to test it more.

More updates to follow.
 
Last edited:
You must log in or register to reply here.
Top Bottom