Hi all,
Anyone else running SABnzbd in a virtual machine under KVM?
I'm having an odd issue where everything works great, but network performance leaves a bit to be desired. For instance, running on the host, I can max out speeds constantly at 5MB/s. However, in the guest, with the same settings, things jump around from .5MB/s to 2.8MB/s. What is odd is that it's only with usenet. Transfering a single large file to the guest goes very quickly.
I'm already using virtio for the NIC, but does anyone else have suggestions on where to even look?
Thanks.
SABnzbd Network Issues in KVM
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: SABnzbd Network Issues in KVM
As it is with most things, you figure something out right after you ask the question. If anyone else runs into this problem, make sure your temporary download folder is inside the guest OS, not mounted from the host through NFS or SMB. That was my issue.
Re: SABnzbd Network Issues in KVM
For virtual Windows is certainly true, because par2 requires a drive letter and not a UNC path.RonnieG wrote:make sure your temporary download folder is inside the guest OS, not mounted from the host through NFS or SMB
For other platforms it's simply advisable.
Other than that, I do most of my testing on virtual machines running under VMWare Fusion.
Re: SABnzbd Network Issues in KVM
This was actually occurring with a CentOS 6.4 guest, using QED filesystem in KVM with virtio.shypike wrote:For virtual Windows is certainly true, because par2 requires a drive letter and not a UNC path.
For other platforms it's simply advisable.
Other than that, I do most of my testing on virtual machines running under VMWare Fusion.
Thanks,
Ben