<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Verdana">Perusing the changeset this was not as trivial
</font>as it may have sounded. <br>
Personally I think Klaus deserves a *BIG* thank you for taking the
time to integrate this as well and as fast as he has.<br>
Not to mention that he was not obligated to do so.<br>
<br>
Take the rest of the day off! :-)<br>
<br>
<br>
<br>
<br>
<br>
On 05/25/2011 03:49 AM, Klaus Espenlaub wrote:
<blockquote cite="mid:4DDCC2A9.3050206@oracle.com" type="cite">On
25.05.2011 09:50, Alexey Eromenko wrote:
<br>
<blockquote type="cite">
<blockquote type="cite"> VBoxManage.exe modifyvm "Windows XP
immu 01" --nicproperty2 sport="10001"
<br>
VBoxManage.exe modifyvm "Windows XP immu 01" --nicproperty2
dest="127.0.0.1"
<br>
VBoxManage.exe modifyvm "Windows XP immu 01" --nicproperty2
dport="10002"
<br>
(three separate properties!)
<br>
</blockquote>
<br>
This also works: (quotes around dport)
<br>
--nicproperty2 "dport=10002"
<br>
</blockquote>
<br>
quotes are not needed if there are no spaces or other funny
characters...
<br>
<br>
<blockquote type="cite">Thanks.
<br>
Now after trying this I don't see what has changed, besides
moving the
<br>
UDP driver to a deeper level.
<br>
(network-->udp became network-->generic-->udp)
<br>
</blockquote>
<br>
Nothing has changed regarding the driver stacking. Just made
things mor modular/generic, and having one property containing
several properties was so weird that I split them up.
<br>
<br>
<blockquote type="cite">Anyway the current way has several
problems:
<br>
1. Incorrect parameters result in inability to start VM
(VBoxManage
<br>
needs to filter incorrect parameters somehow)
<br>
If I type in driver incorrectly or parameter incorrectly, I
should get
<br>
some error from "VBoxManage", if possible.
<br>
</blockquote>
<br>
This wasn't included in the contribution, and with the generic
network attachment driver approach it's right now not possible to
do any custom checks before the VM is started. For the VirtualBox
API everything is just strings with no particular meaning. Only
the driver knows what the properties mean and can do sanity
checking.
<br>
<br>
Even checking the availability of driver is not helpful, as this
would prevent loading/saving configs which refer to drivers which
are not (yet) installed, which I find worse than detecting a typo
only at VM start.
<br>
<br>
<blockquote type="cite">2. Inability to see vm info:
<br>
VBoxManage showvminfo must show me sport, dest, dport
<br>
</blockquote>
<br>
You're right... trying to find some time, but I can't promise that
I can squeeze it in this or next week.
<br>
<br>
<blockquote type="cite">3. GUI, the same. I expect to see
something like:
<br>
Generic, UDPTunnel="sport=10001;dest=127.0.0.1;dport=10002"
<br>
-or-
<br>
Generic, VDE="/tmp/vdeswitch"
<br>
<br>
Currently it is impossible to debug virtual topologies.
<br>
</blockquote>
<br>
Same as 2.
<br>
<br>
Klaus
<br>
<br>
_______________________________________________
<br>
vbox-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://vbox.innotek.de/mailman/listinfo/vbox-dev">http://vbox.innotek.de/mailman/listinfo/vbox-dev</a>
<br>
<br>
</blockquote>
</body>
</html>