Jim,
Both changing the nic (to rtl8139) and rebooting the host solved the issue for me. My VM's have now survived over 12 hours of intense activity without a glitch. To be clear: soly changing the nic without rebooting the host worked; after rebooting the host the default nic works again. Kind regards, Joris 2007/10/20, Joris <[EMAIL PROTECTED]>: > 2007/10/20, Jim Paris <[EMAIL PROTECTED]>: > > > > I'm in the same boat -- upgraded from kvm-36 to kvm-46 and I'm seeing > > identical network problems. > > Great I'm not the only one. Does it help to ifdown && ifup in your case? > > > No difference with -no-kvm-irqchip and with "taskset -c 1". I haven't > > had a chance to debug it much further yet, although trying a different > > network card might be my next step. I was also (reluctantly) going to > > try rebooting the host in case unloading the kvm-36 modules left > > something in a bad state. > > I have a host reboot scheduled for this weekend, I'll report on it. > A different nic is a good idea, I'll try that as well. > > > > An especially strange thing is that, before the network dies, sshing > > I haven't really observed that, but I'll keep an eye out. > > > Kind regards, > Joris > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
