[vbox-dev] [PATCH] VDE native support for VirtualBox v0.1

[James Lucas]

In terms of adding it to VBoxManage, I'm guess that modifyvm --nic<1-N> needs to
be modified and the switch --vdenet<1-N> needs to be added.

VBoxManage modifyvm         <uuid|name>
                            [--nic<1-N>
none|null|nat|bridged|intnet|hostonly|vde]
                            [--vdenet<1-N> <network>|default]

correct?

Does VBoxManage controlvm --nic<1-N> also need to be modified? Not sure how the
network name would be set when changing the network while powered on.

I'm happy to have a go at this over the weekend, the API is there, just needs to
be exposed in VBoxManage.

- James

P.S. This list really needs to have reply-to set to vbox-dev at virtualbox.org
instead of the sender. Nearly posted to Klaus directly.

Quoting Klaus Espenlaub <Klaus.Espenlaub at Sun.COM>:

> Hi Alexey,
> 
> Alexey Eremenko wrote:
> > Actually I would like to see it in GUI...
> > Having one more entry does not make the GUI _that_ heavy. This is
> > because the new VDE entry is not intrusive to the casual user
> > workflow.
> 
> I disagree. Having entries which 98% of the user base will never use and 
> probably even more will never understand is bad UI design. If we'd 
> squeeze everything into the GUI "just because it's not _that_ heavy" 
> we'd end up being as unusable as the qemu GUI wrappers.
> 
> We have lots of other features which are VBoxManage only (e.g. the 
> medium modes), as they'd just make the GUI harder to understand for the 
> vast majority of our users. Having everything in the GUI mainly 
> increases the possibilities of misconfiguring something by our average 
> user, which (somewhat to my surprise) has quite limited understanding of 
> how a PC works or how networks are configured properly.
> 
> > If you want to make network choices more clear, you can can change
> > text "Attached to: NAT" to "Attached to: NAT (default)".
> 
> Indicating that something is default doesn't really help the user 
> understand what it does.
> 
> > As for the GUI in general, the new storage design is a bit too complex
> > (compared to what we had in 3.0.x), so this is the place to start
> > cleaning up the GUI, plus make GUI accessible.
> 
> Repeating the criticism doesn't help us in any way. It doesn't give us 
> any more manpower.
> 
> > See:
> > Feature-request: New Storage GUI: VM/Storage Settings, Wish #5811
> > Feature-request: New Storage GUI: The CD-ROM menu in VM, Wish #5813
> 
> Klaus
> 
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> http://vbox.innotek.de/mailman/listinfo/vbox-dev
> 


--
UTS CRICOS Provider Code:  00099F
DISCLAIMER: This email message and any accompanying attachments may contain
confidential information.  If you are not the intended recipient, do not
read, use, disseminate, distribute or copy this message or attachments.  If
you have received this message in error, please notify the sender
immediately and delete this message. Any views expressed in this message
are those of the individual sender, except where the sender expressly, and
with authority, states them to be the views the University of Technology,
Sydney. Before opening any attachments, please check them for viruses and
defects.