Can wirelss (AirPort) be ON but inactive in OS X?

I need to use a wireless connection from my Windows and/or Linux VM's, so I need to have the AirPort adapter turned on , but I don't want OS X to participate on the wireless network.

Putting eth4 (or whatever) into a down state shuts off the adapter.

Has anyone found a way to do this, or do I need to plug in a USB wireless NIC, and even if I do that, how do I keep OS X from finding it and using it?

 

In the USB section of the devices at the bottom of the VM window search for the wireless device and connect it there, it will stop being available for OSX, this is only possible if the Airport is on the USB Bus, if it isn't, it won't appear on that menu and there's no way in Parallels Desktop to assign it to the VM.

 

Thanks for the reply ...
I'm already able to connect my Ubuntu VM to the wireless (via built-in AirPort) but that does NOT stop OS X from also getting an IP address on the wireless network. In other words, I can ping from the Ubuntu machine to OS X using the wireless network. That's what I don't want. I need the wireless to work only in Ubuntu (or Windows) but not OS X.
OS X should use the WIRED connection (only), but Ubuntu (or Win) should use Wireless (only).

 

I understood you the first time, the only way with the current version is if the device is on the USB bus (Bluetooth is), that's the only way to isolate a physical device in Parallels currently.

I'm hoping that this will also be possible for firewire (without the need for VT-d). In the future all devices will have the possibility of being isolated using VT-d in intel processors and Parallels supporting it, currently VT-d is supported in the Parallels Server albeit experimentally, and will possibly be implemented in PDM 4, the thing is, not all Intel CPUs support VT-d even if they support VT-x. If you don't know what the hell am I talking about, please ignore this paragraph and stick just to the first.