Finally marking as invalid since the BIOS upgrade fixed the problem.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/13679
Not any crash since I updated the BIOS to version 502 and after
installing linux-crashdump. It's been 11 days since the last crash so
maybe the BIOS update was the fix. I'll wait some more days and will
remove linux-crashdump just to see if this could have some impact.
--
You received this bug no
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chris J Arges (arges)
--
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/1367932
Title:
qemu VM crashes the host
Status in “linu
On 09/12/2014 07:33 AM, Christopher M. Penalver wrote:
> ** Tags added: bios-outdated-0502
I'm not sure about this flag since the outdated BIOS version was 305 and
the 502 one is the latest.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags added: bios-outdated-0502
** Tags added: saucy
--
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/1367932
Title:
qemu VM crashes the host
Status in “linux” package in Ubuntu:
Inc
Hi Chris,
On 09/11/2014 01:16 PM, Chris J Arges wrote:
> How often does this occur?
It depends: can be once a week or 3 days in a row. It almost always
happened at night (during backup jobs).
> Have you been able to reproduce this issue without pinning your VMs to cpus?
> Can you still reproduce
@sdeziel:
Hi,
How often does this occur?
Have you been able to reproduce this issue without pinning your VMs to cpus?
Can you still reproduce the issue after disabling seccomp filtering?
Another approach would be to get a full system crash using the following:
https://wiki.ubuntu.com/Kernel/Cras
On 09/10/2014 06:03 PM, Joseph Salisbury wrote:
> id this issue occur in a previous version of Ubuntu, or is this a new
> issue?
The problem also happened when the host was running Saucy and the
OpenBSD guest was at version 5.4.
Looking at the trace more closely, I noticed
"__secure_computing+0x7
id this issue occur in a previous version of Ubuntu, or is this a new
issue?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.17 kernel[0].
If this bug is fixed in the mainline kernel, please add the
** Attachment added: "bck guest (Trusty 64bit)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1367932/+attachment/4200960/+files/bck.xml
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Attaching the libvirt definition of the 2 guests
** Attachment added: "fw guest (OpenBSD 5.5 64bit)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1367932/+attachment/4200959/+files/fw.xml
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
11 matches
Mail list logo
