mirror of
https://github.com/virt-manager/virt-manager.git
synced 2024-12-22 13:34:07 +03:00
227d6982ae
Some related bits were discussed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * macvtap is kinda problematic in general because it doesn't provide out of the box host<->guest communication, and it requires a special XML option just to get working ipv6. Users that know they want it usually know this distinction, but if someone chooses it without understanding the implications it can cause confusion. This puts it hovering the intermediate/advanced user line which makes me want to not advertise it as prominently as we currently do, with an explicit list of host interfaces """ Part of this is that the only source_mode that will work in a useful way for the vast majority of users is mode=bridge. Any of the other modes either require special hardware, permissions, or other configuration. Default to bridge mode. The XML editor is there for anyone that knows they need something different Signed-off-by: Cole Robinson <crobinso@redhat.com> |
||
|---|---|---|
| .. | ||
| about.ui | ||
| addhardware.ui | ||
| addstorage.ui | ||
| asyncjob.ui | ||
| clone.ui | ||
| connectauth.ui | ||
| createconn.ui | ||
| createnet.ui | ||
| createpool.ui | ||
| createvm.ui | ||
| createvol.ui | ||
| delete.ui | ||
| details.ui | ||
| fsdetails.ui | ||
| gfxdetails.ui | ||
| host.ui | ||
| hostnets.ui | ||
| hoststorage.ui | ||
| manager.ui | ||
| migrate.ui | ||
| netlist.ui | ||
| oslist.ui | ||
| preferences.ui | ||
| snapshots.ui | ||
| snapshotsnew.ui | ||
| storagebrowse.ui | ||
| vmwindow.ui | ||
| vsockdetails.ui | ||
| xmleditor.ui | ||