Virtual instruments and effects run at the very least in their own thread within the host process, and some run as their own process and use a form of IPC to communicate with the host. Sure, the single virtual instrument won't parallelize, but a typical project has dozens of effects/instruments, and a bunch of threads that pretty much just read data from one buffer and write data to another buffer without any inter-dependencies is pretty trivial for the kernel to schedule across as many cores as available.
So, rather than useless MAC filtering, how about doing what's sane and secure: run WPA2-Enterprise and require users to use 802.1x to get on your wireless network. You're either authing user/pass against a RADIUS server (which can hit corporate AD or LDAP) or authing the client cert against an internal CA revocation list, or both. Someone leaves? Invalidate their cert and disable their account. Problem solved.
Take a look at Ubersmith. It's designed for quite a few use cases and is pretty much a complete CRM for ISPs/Telcos/Colo facilities/etc with integration into just about everything.
Yeah, some of the players that have stuck around seem to think that the way people do things in comp are the only way to do things, and have completely lost sight of the fact that it's a game that's meant to be fun first and foremost.
Probably because you haven't used it and the person who modded you has. Diablo 3 at 1920x1200, maxed out, getting 60 FPS in a VM is certainly working 'very well'.
Where have you been for the past 3 or 4 years? 3D acceleration works very well in VMWare Workstation/Fusion and Parallels Desktop.
In my admittedly anecdotal experience Diablo 3 runs better in a Parallels Win 7 VM on my MBP than it does natively in OSX. Of course, that's a rare exception because of how poorly optimized D3 is on OSX. Typically with other games I see about 80-85% of the native (dual boot Win7, specifically) framerate when running in Parallels.
Of course, if you're using something like VirtualBox or QEMU, yeah, expect total crap performance. However, VMWare and Parallels devote a lot of time to 3D acceleration and it's very usable in their products.
Hila hila plant is what they call it over in Hawaii. It folds up into itself on contact, and it has thorns. It's classified as an invasive weed, and it lays low to the ground. Those suckers hurt when you step on them, as due to their structure the thorns actually get thrust upwards when the plant folds. Species is called mimosa pudica. Couldn't tell you if the story's true, but the plant certainly is there and isn't native to the area.
Nope, no astroturf here, just a happy network admin.
Juniper is seriously that awesome. They put a ton of thought into their stuff, and it makes my life that much easier.
Too bad I can't mod "+1 Fuck Yes." Juniper rocks.
It's amazing how content you are with ignorance. I'll just go ahead and add you to my "Never met a smart Australian in my life" list and leave it at that.
Ok. Let me lay this out for you, since you're apparently a dunce who can't use google.
How live migration works:
1. Snapshot system memory, live, while the system is running.
2. Transmit snapshot to shared storage.
3. After transmit, load snapshot into RAM on second host.
4. Suspend VM.
5. Send deltas of RAM, to bring second host up to date.
6. Resume VM.
7. Gratuitously ARP out so the switches know where the machine is.
The guest is never shut down. It is never aware it has even been suspended. As far as it, and clients are aware, it just experienced additional network latency for about 1/10th of a second between 4 and 6. During that time, its entire state was transferred to different physical hardware. Now, in many cases, this requires identical, or similar CPUs, but that's trivial.
It's not that complex, and if you were willing to do a bit of research, you'd avoid making yourself look like a total dunce.