Yeah looks like any nfs writing is just rubbish performance wise, on my Gentoo Linux VM its runs really slow from power on. It's been over a week and I've seen no further slowdowns.

Update 11/17: I ended up configuring a second interface on the system, then bringing up a vnic on that interface to use with the VM. I'll toss that out to the forum to see if there are any ideas as to a solution. I have the option of a second physical NIC, but am not able to route between the host's interface and the guest's.

Rebooting the guest every few days is not optimal, but I can live with it. After about a week, I started seeing the same slow downs of write speed on the VM. Update 11/6: Looks like this was a temporary fix. I've implemented it and it resolved the problem I was having between my NFS write-intensive XP VM client running on my OpenIndiana 151a host serving the NFS. Nmiller wrote:Thanks for posting up this solution, carbs. Oct 2011, 09:45 Primary OS: Linux other VBox Version: PUEL Guest OSses: Gentoo Linux I haven't done extensive testing but so far so good. I then started up the virtual machine and my NFS was flying along at 700Mb/s and the VM was also working well, although the first few minutes after a reboot tend to be very slow, then it picks up. These configuration changes survive a reboot so there is nothing more to do to keep it working long term. Note: The MAC address doesn't have leading zero'sĪt this point I noted down the MAC address for vnic1 (padding it with zeros where required, then ran the command below to modify the VM and bridge it to vnic1.Ĭode: Select all Expand view Collapse view VBoxManage modifyvm server -nic1 bridged -bridgeadapter1 vnic1 -macaddress1 0208207af742 So on my machine the one NIC is bge0 and the VM is called server, so these are the commands I used:Ĭode: Select all Expand view Collapse view dladm create-vnic -l bge0 vnic1Ĭode: Select all Expand view Collapse view LINK OVER SPEED MACADDRESS MACADDRTYPE VID There are some limitations though, you need to use one VNIC per virtual machine and the MAC address of the VNIC must be used as the MAC address on the virtual machine. I used Crossbow to create a virtual NIC, then bridge the VM to that. , I was unable to use this solution as my server has a single NIC (its a HP Microserver). I was having issues with VirtualBox 4.1.4 on OpenIndiana, when ever a VM with Bridged networking was running NFS performance (using ZFS NFS sharing) was terrible (7Mb/s as apposed to around 700Mb/s when no VM was running).īut using Crossbow I was able to workaround the problem and have everything working well, so I though I would post my findings in the hope it helps others, another solution is the bridge VM's to a dedicated NIC as I found on this site.

Mac nfs slow