I installed the 2.6.32-32 kernel in https://launchpad.net/~serge-
hallyn/+archive/kernel and I see the same kvm guest crashes on my AMD
Opteron host (the system in bug 799166) that I observed with the stock
2.6.32-32 kernel.
wmldev@1p19l3j:~/standard_tests/test1$ aptitude show
linux-image-2.6.32-
Serge - I will try it in the next couple of days and report back.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/790789
Title:
KVM Guest freezing following Ubuntu update
To manage
>From bug 799166:
Current prerelease kernel 2.6.32-33 doesn't fix this issue for me.
This issue is restricted to AMD processors.
Falling back to 2.6.32-31 is an alternative work-around.
For me, modifying the Linux command line in our guests is an undesirable
workaround and I will be using 2.6.3
Ok, running the guest with clock=acpi_pm added to the Linux command
line, whilst the host is running the 2.6.32-32 kernel has given me
stable behaviour for 20 minutes with constant CPU usage, so it very much
looks like this is a duplicate of bug 790789.
--
You received this bug notification becau
** Summary changed:
- KVM virtual machines crash with host on linux-image-2.6.32-32-server on AMD
processor
+ KVM guests freeze on an AMD-based host since it was upgraded to kernel
2.6.32-32
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscrib
A better title for this would be "KVM guests freeze on AMD-based host
since upgrade to kernel 2.6.32-32"
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/799166
Title:
KVM virtual ma
Did the 2.6.32-33 kernel provided by Serge solve the issue?
I see this report is for an AMD machine; it might possibly be related to
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/799166 although
in that case there was no "kvm-clocksource has been installed" message
in the logs prior to a
I've just noticed that although I refer to 2.6.32-32-server in my bug
report, the Dell T105 for which I submitted the bug was running
2.6.32-32-generic. I have observed the same behaviour for
2.6.32-32-server on our other Dell T105 and confirmed that in each case,
the crashes occur for 2.6.32-32 an
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/799166
Title:
KVM virtual machines crash with host on linux-image-2.6.32-32-server
on AMD processor
To manage notifications about t
Public bug reported:
Binary package hint: qemu-kvm
Since the 31st May I've been seeing random crashes in the virtual
machines that we run on an AMD processor based system in our office. We
run Ubuntu 10.04 on this server, which is a Dell T105 and I keep it
patched with all the updates. The virtua
I made use of Mika's patch on a 10.04 system and found it solved my
problem.
I had been confused and thought that there was something wrong with
my/the apparmor config for libvirt, because there were a few apparmor
audit messages in the log, but in fact, it was this issue with the
bridge interface
11 matches
Mail list logo
