Can anyone reproduce this error on Hardy, Intrepid, or Jaunty?
The last comment is a year old. I'm going to mark this bug Fix
Released. Please reopen if you're still experiencing this problem.
Thanks,
:-Dustin
** Changed in: kvm (Ubuntu)
Status: Incomplete = Fix Released
--
[gutsy]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Hardy Heron. It would help us greatly if you could
test with it so we can work
The same thing happens on my system. After upgrading from feisty to
gutsy kvm-amd (as shipped with kernel package) crashes the system. I
can't build a working version of kvm-modules on gutsy (it yells kvm:
Unknown symbol set_64bit) while it worked on feisty (even when trying
to build from
It seems that my problem is bios related. Newer kvm releases tell that
svm instructions are disabled by bios and doesn't crash.
I've talked with the mainboard maker support and they say that it's on
purpose due to some possible instabilities when svm is enabled and
that they are working with AMD
OK, this seems to be a bug in -rt flavor of the kernel. The -generic
flavor works OK.
--
[gutsy] System crash on kvm-amd load
https://bugs.launchpad.net/bugs/124941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Have you tried following
https://help.ubuntu.com/community/DebuggingSystemCrash ? Are you sure
that your system actually supports the hardware virtualisation
extensions? egrep '^flags.*(vmx|svm)' /proc/cpuinfo should produce
some output if your system does support a VT extension. What kvm
Yea, I've tried doing all that and I can't get any info. I'm sure the
system supports virtualisation because i've been using previous kvm
releases. Tthis problem started for me with a kernel upgrade in
feisty, then I upgraded to gutsy (tribe 2 was the latest) and same thing
happens.
I've tested
Some BIOS's are capable of disabling SVM. Newer versions of KVM are
able to detect this and present an error message but the version in
neither Feisty nor Gutsy is.
If you enable SVM in the BIOS, KVM will no longer crash. There are some
broken BIOSes too where disabled really means enabled and
I've got the same problem here.
Using a dell optiplex 740 (amd X2 3800 + nvidia GF 6150).
I first thought it was because of the nvidia kernel module but even when it's
not loaded, the kernel freezes hard.
--
[gutsy] System crash on kvm-amd load
https://bugs.launchpad.net/bugs/124941
You
I've tried to set a netconsole, but no message is shown in the remote
system when i load kvm-amd.
Sometimes I can use alt+sysrq+b to reboot the system, but sometimes that
doesn't work either.
I've set the system to start a new kernel through kexec when the system
crashes, but can't find the
I tried to compile the kvm module from kvm-source package and same thing
happens.
** Changed in: kvm (Ubuntu)
Sourcepackagename: None = kvm
--
[gutsy] System crash on kvm-amd load
https://bugs.launchpad.net/bugs/124941
You received this bug notification because you are a member of Ubuntu
Bugs,
11 matches
Mail list logo
