Just to confirm Stephane in #39, all we did was modprobe vhost_net (and
add it to /etc/modules) then stop and start all our VMs. libvirtd
detected vhost_net and added the vhost=on parameter automatically to our
VMs. So far no crashes.
--
You received this bug notification because you are a
Just to confirm Stephane in #39, all we did was modprobe vhost_net (and
add it to /etc/modules) then stop and start all our VMs. libvirtd
detected vhost_net and added the vhost=on parameter automatically to our
VMs. So far no crashes.
--
You received this bug notification because you are a
This bug affects me as well, is it related to the one discussed here
https://bugzilla.kernel.org/show_bug.cgi?id=42829
I will try using the vhost_net driver in the host and vhost=on as a
guest parameter to see if it bypasses the issue.
** Bug watch added: Linux Kernel Bug Tracker #42829
This bug affects me as well, is it related to the one discussed here
https://bugzilla.kernel.org/show_bug.cgi?id=42829
I will try using the vhost_net driver in the host and vhost=on as a
guest parameter to see if it bypasses the issue.
** Bug watch added: Linux Kernel Bug Tracker #42829
The problem still exists in Ubuntu 12.04 beta 2 - kernel
3.2.0-20-generic. The kernel module has been renamed to iwlwifi so use
the following filename and contents:
/etc/modprobe.d/iwlwifi.conf :
options iwlwifi bt_coex_active=N
--
You received this bug notification because you are a member of
Just an update, create a file /etc/modprobe.d/iwlagn.conf with the
following:
options iwlagn bt_coex_active=N
This seems to work for 3.* kernels. The workaround comes from here
https://lkml.org/lkml/2011/12/12/256
--
You received this bug notification because you are a member of Ubuntu
Bugs,
As a temporary workaround natty's 2.6.38 kernel seems to work
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.38.8-natty/
I just started using it so I don't know if there will be other problems
caused by using a kernel compiled for natty. Another option might be to
recompile 2.6.38 from
Update for MSI Wind U100. The problem still happens with a clean install
of 11.04. It only seems to happen when resuming on battery power:
AC before suspend - battery on resume
battery before suspend - battery on resume
and it does not happen when resuming on AC power:
AC before suspend - AC on
Confirmed on MSI Wind U100 with all updates as of 2010-10-22. If I don't
turn on the wireless the computer suspends and resumes fine. I tried
removing the r8187se module before suspend and adding it back after
resume but the computer freezes when trying to reconnect to the wireless
network.
