Personal computing discussed
MarkG509 wrote:However, there are two things I'm not completely happy about with VirtualBox: it does not virtualize the AES-NI x86 instructions, and I cannot assign physical devices to virtual machines.
bthylafh wrote:To expand this question a bit, how about Hyper-V? I'm starting to play with it a bit at work. First impressions are that it's pretty decent as long as you don't use a Linux distro with a GUI as a guest, because the connection window doesn't know what to do with X: it seems to assume that RDP is present.
just brew it! wrote:Thanks! How did I miss that?!?!? I've been wanting to set up a FreeNAS box, and will definitely try setting it up with raw disk access!Because there *is* a way to assign raw block devices or partitions to a VM via VBoxManage commands.
MarkG509 wrote:I was also referring to things like graphics adapters (e.g., run games in a Windows guest with full performance (or at least enough to run Flight Simulator), but now I see in section 9.6 of the manual this may also work on Linux hosts with proper kernel configuration and an extension pack.
Saribro wrote:I've used VirtualBox here at work to maintain our Linux SDK (for our IR cameras). Basic functionality and camera connection was no problem, but image capture, processing and display was damn near impossible: 2-5 frames every 30 seconds for a camera that should be throwing out up to 100fps (depending on settings). This is odd, because everything else seems to work fine. So for proper testing I have some distributions installed natively where I had to reboot to.
Savyg wrote:I've only used VBox, and have had enough problems with it I don't plan to ever use it again. heh.
just brew it! wrote:Did you have the Extension Pack (for USB 2.0 support) installed? Otherwise, the camera connection was probably running at USB 1.1 speeds.
bthylafh wrote:To expand this question a bit, how about Hyper-V? I'm starting to play with it a bit at work. First impressions are that it's pretty decent as long as you don't use a Linux distro with a GUI as a guest, because the connection window doesn't know what to do with X: it seems to assume that RDP is present.
Savyg wrote:Hyper-V seems to mess with NVidia drivers a bit from what I was reading and experienced.
It wasn't catastrophic, but it was plenty odd.
Ryu Connor wrote:bthylafh wrote:To expand this question a bit, how about Hyper-V? I'm starting to play with it a bit at work. First impressions are that it's pretty decent as long as you don't use a Linux distro with a GUI as a guest, because the connection window doesn't know what to do with X: it seems to assume that RDP is present.
Eh? Using Mint 17 KDE in Hyper-V with no issues.
bthylafh wrote:It may also help to use the virtio paravirtualized network adapter instead of the default emulated Intel NIC.
bthylafh wrote:but for VMware you have to either hammer the key to get into the BIOS setup or just edit the .vmx file.
bthylafh wrote:It may also help to use the virtio paravirtualized network adapter instead of the default emulated Intel NIC.
just brew it! wrote:Wait... what? Why didn't I notice that before?
Forge wrote:bthylafh wrote:but for VMware you have to either hammer the key to get into the BIOS setup or just edit the .vmx file.
That actually got fixed quite a while back. Now you power off VM, right click, Power->Power on to bios and poof. No key hammering.
bthylafh wrote:You need at least a 2.6.25 kernel to use the virtio NIC. I suppose we'll need to wait a bit longer before they make that default for Linux guests, alas.