Yeah works now for me as well.
--
Cannot load kvm and subsequent "oops"
https://launchpad.net/bugs/92159
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Works on my machine as well.
$ uname -a
Linux mk 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux
$ cat /var/lib/acpi-support/*-*
68YVD Ver. F.0F
Hewlett-Packard
HP Compaq nw8440 (RH415EA#ABB)
F.0F
--
Cannot load kvm and subsequent "oops"
https://launchpad.net/bugs/92159
--
The linux-2.6.20-11 kernel release fixes the kvm problems.
** Changed in: kvm (Ubuntu)
Status: Confirmed => Fix Released
--
Cannot load kvm and subsequent "oops"
https://launchpad.net/bugs/92159
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
Added uname -a log, as requested in
https://wiki.ubuntu.com/DebuggingKernelProblems
** Attachment added: "uname-a"
http://librarian.launchpad.net/6823973/uname-a.log
** Changed in: kvm (Ubuntu)
Status: Unconfirmed => Confirmed
--
Cannot load kvm and subsequent "oops"
https://launchpad
Added lspci -vvnn log as requested in
https://wiki.ubuntu.com/DebuggingKernelProblems
** Attachment added: "lspci-vvn"
http://librarian.launchpad.net/6823971/lspci-vvnn.log
--
Cannot load kvm and subsequent "oops"
https://launchpad.net/bugs/92159
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Attached the Oops dmesg trace so we can cleanup the bug description.
** Attachment added: "dmesg-oops"
http://librarian.launchpad.net/6823929/dmesg-oops.txt
** Description changed:
Binary package hint: kvm
Hi,
This on Core 2 Duo E6600, Asrock 775-VSTA, nvidia-glx and Atheros.
Li
Also attached a cpuinfo for information.
** Attachment added: "cpuinfo"
http://librarian.launchpad.net/6823723/cpuinfo.txt
--
Cannot load kvm and subsequent "oops"
https://launchpad.net/bugs/92159
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
I can confirm this. modprobe kvm fails, kvm-intel fails, and a
subsequent oops is bound to happen (and did).
Attaching dmesg of the failed symbols
** Attachment added: "dmesg"
http://librarian.launchpad.net/6823721/dmesg.txt
--
Cannot load kvm and subsequent "oops"
https://launchpad.net/bugs
Confirmed here. See bug 92291 regarding failure of kvm-intel to load.
Then, I start to get a kernel "oops" with almost anything I run in a
virutal terminal.
[EMAIL PROTECTED]:~$ mv
Segmentation fault
[EMAIL PROTECTED]:~$
Message from [EMAIL PROTECTED] at Wed Mar 14 11:01:28 2007 ...
localhost ke
