On Sun, Jul 28, 2013 at 09:10:16PM -0500, Anthony Liguori wrote: > On Sun, Jul 28, 2013 at 6:55 PM, Rusty Russell <ru...@rustcorp.com.au> wrote: > >> Or something vaguely understandable by a human? > > > > OK. It seems to me that each net device has a host side and a guest > > side, which you can mix and match. So the commandline should reflect > > that explicitly: > > > > qemu -hostdev net,[tap|user|bridge|socket|vde],.... -guestdev > > net,.... > > > > If you have a built-in net device on your emulated board, you've got one > > implied -guestdev net. And similar principles apply to other things > > like consoles and disks. > > See, we have this: > > qemu -netdev tap,... -device virtio-net-pci,... > > > Now, guest and host terms may suck. But please pick one terminology and > > use it *everywhere*. Documentation, code and cmdline. > > But *this* is the problem.
It's not the only problem though. Here's a list off the top of my head. Use of -device lacks documentation almost completely (Marcel's recent patches are a step in the right direction here), many devices also lack any user-readable description, legal parameters to -global are undocumented, -global does not validate parameters, device properties are undocumented, bus address formats are undocumented, for complex devices such as pci express switches, which device can be connected to which is also undocumented. > Our documentation (man page, --help, > qemu-doc.texi) hasn't been touched since the beginning. I get the > feedback, will take a look at it for 1.7. > > Regards, > > Anthony Liguori > > > Thanks, > > Rusty.
