boot problems with 3.18: an observation which may be related to the described problem: using kernel 3.18-rc2-vivid (or any other 3.18 kernel published so far!) in lubuntu-14.10 x86 32bit the machine does not come up correctly. In particular, it comes up without WIFI. Moreover, "sudo" does not work, and synaptic cannot be used.
Kernels 3.17 and 3.16 show no problems. On the other hand, If I run 14.10 with kernel 3.17, I can boot a lubuntu-14.10 VM in virtualbox with kernel 3.18 without any problems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1387140 Title: Linux 3.18: VM fails to start because of unactive virtual network Status in “libvirt” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Since Linux 3.18 my VM fails to start. Trying it in virt-manager causes error message: Error during domain starting: Requested operation is not valid: network 'default' is not active Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1360, in startup self._backend.create() File "/usr/lib/python2.7/dist-packages/libvirt.py", line 999, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: Requested operation is not valid: network 'default' is not active Trying to start Virtual Network in connection parameters causes another error: Помилка під час спроби запуску мережі «default»: internal error: Failed to apply firewall rules /sbin/iptables --table filter --insert FORWARD --in-interface virbr0 --jump REJECT: iptables: No chain/target/match by that name. Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/network.py", line 104, in start self._backend.create() File "/usr/lib/python2.7/dist-packages/libvirt.py", line 2820, in create if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self) libvirtError: internal error: Failed to apply firewall rules /sbin/iptables --table filter --insert FORWARD --in-interface virbr0 --jump REJECT: iptables: No chain/target/match by that name. In linux 3.17 all is working good. Kubuntu 14.10 x86_64 Libvirt0: 1.2.9-0~14.10~ppa0 Virt-manager: 1:1.1.0-0~14.10~ppa0 --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-06-08 (143 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Package: linux (not installed) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-031800rc2-generic root=UUID=b76fc0ae-d31c-4b13-8f4e-424542d850c9 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Error: [Errno 2] Немає такого файла або каталогу: '/proc/version_signature' Tags: utopic utopic Uname: Linux 3.18.0-031800rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to utopic on 2014-10-24 (5 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Відмовлено у доступі: u'/etc/libvirt/qemu.conf'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1387140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
