I'm having a weird problem getting a ubuntu VM working.  I am using the .iso that Tom posted about in the Beta 3 release thread (and I've tried upgrading it to 13.10 as well with no change.  The VM starts fine until, then the machine just stops responding for a few seconds, then continues, and this repeats over and over at random intervals.  When this happens, if I open a SSH session, it may take 45 seconds to ask for the password after entering the user, or a similar amount of time for a command such as ls.  I initially noticed this with Plex running, but even when I stop the Plex service it still happens (although not as frequently). 

 

I've looked at both top on the VM and XL Top, and it doesn't appear that it's processor related.  I also tried bumping the RAM up to 8 GB to see if that made a difference from the original 4, and that didn't seem to change anything, so I'm not sure what else to check or try at this point (free and free -l show about 3 GB free).  I've checked the syslog, and there is nothing in it at the times when the machine stops responding (or when it starts responding again).  I have been able to run the ArchVM image, including Plex on the server without issue, so I don't think it's a hardware limitation.

 

I'm listing my config file, and I can attach a syslog if anyone things that would help.

 

bootloader = "pygrub"

memory = 4096

vcpus = 6

 

name = "ubuntu.13-04.xfce.x86-64.20130424"

vif = [ 'mac=00:16:3e:01:01:02,bridge=br0' ]

disk = ['file:/mnt/cache/domains/ubuntu/ubuntu.13-04.xfce.x86-64.20130424.img,xvda,w']

root = "/dev/xvda"

extra = "fastboot"

vfb = ['type=vnc,vnclisten=0.0.0.0,vncunused=1']

I found the issue for this.  After trying multiple VM's, and getting similar behavior, I happened to open the console for the ArchVM that I was testing.  When I did this, I saw some of the "skb rides the rocket" error messages that seem to be related to packet loss.  I decided that since I was using a bonded NIC in unraid, I would try disabling one of the NICs to see if this solved the problem.  After rebooting to disable the NIC, the problem is solved.