Hi Chris,
I can confirm that VMs with latest kernel have no issues. Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic for AMD smp trusty guests
To
@lei-zhang-s
This fix needs to be applied to the VM's kernel. So ensure those images are
updated as well.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic
Has this bug been fixed in 3.13.0-44.73?
I recently upgraded some of our precise compute nodes(Dell C6145 AMD
Opteron(tm) Processor 6376) to trusty, with the latest kernel 3.13.0-45-generic
#74-Ubuntu, but still seeing this kernel panic in vm's console log.
Using libvirt_cpu_mode=host-model
This bug was fixed in the package linux - 3.16.0-29.39
---
linux (3.16.0-29.39) utopic; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1402822
[ AceLan Kao ]
* SAUCE: Add use_native_backlight quirk for HP ProBook 6570b
- LP: #1359010
[ Andy
This bug was fixed in the package linux - 3.13.0-44.73
---
linux (3.13.0-44.73) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1402872
[ AceLan Kao ]
* SAUCE: Add use_native_backlight quirk for HP ProBook 6570b
- LP: #1359010
[ Andy
I've verified with a Utopic guest running 3.16.0-29.39.
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
During the weekend I was able to reproduce the issue using a Trusty VM with
kernel 3.13.0-43.72
kernel 3.13.0-44.73 fixes the issue.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
I can confirm that the issue looks fixed using 3.13.0-44.73~precise1
from precise-proposed.
I made more than ten reboots with the new kernel installed on VMs and
all were successful. Then I switched back to the previous
3.13.0-43.72~precise1 and VMs boot failed at the first trial. Again back
to
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic for AMD smp trusty guests
To manage notifications
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic for AMD smp trusty guests
To manage notifications
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic for AMD smp trusty guests
To manage notifications about
I have this issue running an Ubuntu 12.04.5 guest (running kernel
3.13.0-43-generic) on a KVM Hypervisor with the same configuration
(Ubuntu 12.04.5, 3.13.0-43, CPU 4x AMD Opteron(TM) Processor 6274, Dell
R915).
I'm unable to boot the guest the 80% of the trials. The error is
reproducible even
@daniele-vigano:
The fix has not yet been released, but I believe it will be in 3.13.0-44.
Thanks for the report,
--chris
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm
** Changed in: linux (Ubuntu Utopic)
Status: In Progress = Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this patch fixes the issue:
https://lkml.org/lkml/2014/9/22/211
Looking at the stacktrace:
[4.690909] divide error: [#1] SMP
[4.690909] Modules linked in: dm_crypt kvm_amd kvm serio_raw isofs
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw
** Description changed:
+ [Impact]
+ When using KVM on an AMD host with a kernel that has CONFIG_DEBUG_RODATA
enabled, a guest with: multiple vCPUs, and exposing features to the guest such
as tsc_adjust can cause a divide error on kvm_unlock_kick when booting the VM.
+
+ [Test Case]
+ 1)
** Changed in: linux (Ubuntu)
Assignee: Chris J Arges (arges) = (unassigned)
** Description changed:
[Impact]
- When using KVM on an AMD host with a kernel that has CONFIG_DEBUG_RODATA
enabled, a guest with: multiple vCPUs, and exposing features to the guest such
as tsc_adjust can cause
@dhruvahuja
Thanks, but I can reproduce this issue, so no need to collect any more
information.
Testing once I get a fix will be appreciated. : )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Marking vivid task Fix Released as I believe this is fixed in 3.18
series kernels (and Vivid will be there soon...)
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I am happy to run apport-collect if anybody still needs it. FYI, my
Hypervisor is Centos 7 KVM. Guest is Ubuntu trusty . At which Kernel
version and with how many CPUs would you like to have that command run?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
** No longer affects: qemu (Ubuntu)
** No longer affects: qemu (Ubuntu Trusty)
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
** No longer affects: qemu (Ubuntu)
** No longer affects: qemu (Ubuntu Trusty)
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
I'm able to reproduce this and currently it looks like its fixed in
3.18-rc1. The main things that need to be enabled are 'cpu mode=host-
passthrough' and 1 CPU. If 'cpu mode=host-model' is enabled and 1
CPU things work fine.
The differences in cpu features were:
npt nrip_save tsc_adjust
I've
Not keen on providing apport info as this is a production system with
multiple tenants and we have no agreement with Canonical. The info here
and verification from others indicates this is a simple bug to reproduce
and not specific to our systems.
--
You received this bug notification because
Here's an example of an affected qemu command, as already pointed out
the relevant parts are the -cpu host and -smp n where n1.
qemu-system-x86_64 -enable-kvm -name instance-000173d4 -S -machine
pc-1.0,accel=kvm,usb=off -cpu host -m 16384 -realtime mlock=off -smp
4,sockets=4,cores=1,threads=1
** Tags added: amd
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic for AMD smp trusty guests
To manage notifications about this bug go to:
I'm able to reproduce this and currently it looks like its fixed in
3.18-rc1. The main things that need to be enabled are 'cpu mode=host-
passthrough' and 1 CPU. If 'cpu mode=host-model' is enabled and 1
CPU things work fine.
The differences in cpu features were:
npt nrip_save tsc_adjust
I've
Not keen on providing apport info as this is a production system with
multiple tenants and we have no agreement with Canonical. The info here
and verification from others indicates this is a simple bug to reproduce
and not specific to our systems.
--
You received this bug notification because
Here's an example of an affected qemu command, as already pointed out
the relevant parts are the -cpu host and -smp n where n1.
qemu-system-x86_64 -enable-kvm -name instance-000173d4 -S -machine
pc-1.0,accel=kvm,usb=off -cpu host -m 16384 -realtime mlock=off -smp
4,sockets=4,cores=1,threads=1
** Tags added: amd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic for AMD smp trusty guests
To manage notifications about this bug go to:
Marked as affecting the kernel given tha last few commits - thank you
for the information.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: qemu (Ubuntu)
Status: New = In Progress
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Hi, could you provide the exact command used to launch qemu to produce this
error? If using libvirt, you can find this in /var/log/libvirt/qemu/name.log
if using virsh for example.
Thanks,
--chris
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Marked as affecting the kernel given tha last few commits - thank you
for the information.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: qemu (Ubuntu)
Status: New = In Progress
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Hi, could you provide the exact command used to launch qemu to produce this
error? If using libvirt, you can find this in /var/log/libvirt/qemu/name.log
if using virsh for example.
Thanks,
--chris
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic for AMD smp trusty guests
To manage notifications about this bug go to:
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic for AMD smp trusty guests
To manage notifications about this bug go to:
I have more-or-less the same underlying hardware and tested with [1].
Same results. Keen to help in any possible way.
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.11-trusty
/linux-
image-3.13.11-0313-generic_3.13.11-0313.20141336_amd64.deb
--
You received this bug
Update. Upon testing the 'daily' build as had been suggested, I found
that [1] appears to work for me in a stably. I'll update this thread if
I find it crashing in the near future.
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/linux-
I have more-or-less the same underlying hardware and tested with [1].
Same results. Keen to help in any possible way.
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.11-trusty
/linux-
image-3.13.11-0313-generic_3.13.11-0313.20141336_amd64.deb
--
You received this bug
Update. Upon testing the 'daily' build as had been suggested, I found
that [1] appears to work for me in a stably. I'll update this thread if
I find it crashing in the near future.
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/linux-
** Summary changed:
- qemu-kvm guest panic for smp trusty guests
+ qemu-kvm guest panic for AMD smp trusty guests
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
Thanks for reporting this bug.
Would it be possible for you to test with the daily upstream kernel
builds, to rule out any temporary kernel regressions? Instructions for
that are here: https://wiki.ubuntu.com/Kernel/MainlineBuilds
I'll also build an uptodate daily qemu build so we can test
** Summary changed:
- qemu-kvm guest panic for smp trusty guests
+ qemu-kvm guest panic for AMD smp trusty guests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic
Thanks for reporting this bug.
Would it be possible for you to test with the daily upstream kernel
builds, to rule out any temporary kernel regressions? Instructions for
that are here: https://wiki.ubuntu.com/Kernel/MainlineBuilds
I'll also build an uptodate daily qemu build so we can test
48 matches
Mail list logo
