On Tue, Jan 26, 2016 at 10:12 AM, David Sommerseth <sl+us...@lists.topphemmelig.net> wrote: > On 26/01/16 08:13, Yasha Karant wrote: >> >> As neither VMware player nor VirtualBox seem capable of providing a MS >> Win guest with any form of Internet access to an 802.11 connection from >> the host (in both cases, the claim from a MS Win 7 Pro guest is that >> there is no networking hardware, despite being shown by the guest as >> existing), it is possible that the "native" (ships with) vm >> functionality of EL 7 may address this issue. > > So you want the guest to have full control over the wireless network > adapter? That is possible, but only through a hypervisor ... and these > days, unless the adapter supports PCI SR-IOV [1], you need to disable > the interface (unload all drivers, unconfigure it) and allow your guest > to access the PCI interface directly (so called PCI passthrough). > > With PCI SR-IOV support (this requires hardware support), you can > actually split a physical PCI device also supporting SR-IOV into > multiple "virtual functions" (VF) which results in more PCI devices > appearing on your bare-metal host and you can then grant a VM access to > this VF based PCI device. For network cards, that also includes a > separate MAC address per VF. > > [1] <http://blog.scottlowe.org/2009/12/02/what-is-sr-iov/> > > But the downside, from your perspective, all this requires a hypervisor.
IIRC, Yasha's issue with 802.11 is that he cannot bridge a wifi NIC (I pointed out in Oct/Nov that it's because the kernel prevents it).
