On Sun, 18 Aug 2013 09:09:51 -0700 Matthew Hall <mh...@mhcomputing.net> wrote:
> You got it backwards. I am 99% sure they mean the VM needs to be set into the > non default ICH9 mode. Probably because the other older chipset doesn't have > VT-D on it. > -- > Sent from my mobile device. You are right, but unfortunately it did not really help either. I switched the guest to ICH9, then I could pci-attach the two questionable network cards. The guest booted and everything looked fine, but did not work. The cards produced no interrupts at all. So I downed the guest and detached the devices - only to find out that the original driver (igb) didn't want them back... :-( (yes, I know how to bind via /sys) I had to reboot the host to get the networks back and during the shutdown vbox completely crashed and hung the box. After coldboot everything is back to normal now - without pciattached networks of course. I cannot recommend that to joe-average-user ... -- Regards, Stephan ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe