This is still a problem on Oneiric.
** Also affects: linux (Ubuntu Natty)
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu Natty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oneiric)
Importance: Undecided
Status: Confirmed
I'm affected by this bug too.
I recently upgraded my laptop from a Dell Latitude D380 running Lucid
64-bit to a Dell Latitude E6520 running Natty 64. I moved all my VMs
from the old machine to the new. All the VMs had been working fine for
a long time on the old system.
The first VM i booted
Serge Hallyn wrote in #15:
So far, having two vm's (built by vmbuilder) doing apt-getinstall
ubuntu-desktop,
what I got was apt-cacher-ng on the host disappearing (!).
In my experience, apt-cacher-ng is a flaky crock that crashes all the
time. I'd guess it's not related to this bug.
--
You
I think Jamie Strandboge is on to something in comment #18 (even though
Kees Cook reports something contradictory in #28).
I have a very similar wifi chipset, and if i disable wifi the problem
appears to be gone. At least my VM successfully compiled a whole
kernel, which it's never done with
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER
model name : Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz
--
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/694029
Title:
[natty] kvm guests become unstable after a while
--
I have no wireless on my system, and I just saw this in a VM I started.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
@Kees,
what sort of system do you have?
I was actually wanting to ask Jamie to do something like
10 or 20 parallel jobs doing wget, tar xvf, and
diff -nrup linux-2.6.37.tar.gz, wgetting from a local
mirror and looking for differences or segfaults.
--
You received this bug notification because
FYI, I double checked maverick kernel on wireless and it is solid. The
latest natty kernel (2.6.38-4.31 using wireless) still shows the bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
** Changed in: linux (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
--
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/694029
Title:
[natty] kvm guests become
Looking through the changelog for the wireless driver (assuming this is
drivers/net/wireless/iwlwifi/iwl-agn and friends) didn't seem helpful.
At this point I'm afraid the most likely path to figuring this out would
be to take the upstream kernel, reproduce it on there, and then bisect
from 2.6.35
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Invalid
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
I tried to reproduce this on a similar platform as Jamie, but could not,
at least in my initial testing.
I'm running two Natty desktop live ISOs:
kvm -m 1024 -smp 4 -cdrom
/home/kirkland/.cache/testdrive/iso/ubuntu_natty-desktop-amd64.iso -drive
So after clearing some space and running the identical test I did in
comment #19 I had no errors after 64 runs. So without ecryptfs and with
wired networking it seems ok. I am going to run the same test but with
wireless instead of wired and see what happens.
** Attachment removed: kern.oops
Ok, after one run with ext3, plenty of room, no ecryptfs and using
wireless, I have the instability. I do not have any kernel messages
related to this, and ifconfig shows no errors.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
So at this point possible culprits seem to include: ext3, aufs, and the
kvm_intel module (and your hard drive)?
Do you have space in which to try on an xfs filesystem?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
I still don't think it is the hard drive because a) it is a pretty new
intel SSD drive (less than one year), b) I am not getting any other
errors outside of kvm (fscks are clean, not file corruption, nothing in
kern.log) and c) rebooting into the maverick kernel does not exhibit
this problem.
Hi Serge,
Yes I am still having this problem. I have not tried to reproduce on
another machine because I don't have a natty installation that can do
kvm anywhere else. I have not yet tried outside of ecryptfs, but will
try to do that today. I can say this though: I am using the
Ok, I tried this without ecryptfs on an ext3 partition and still got the
errors by running a modified script to use only 2 maverick VMs, one
amd64 and one i386. Interestingly, this time I got a kernel oops on the
host (which I never had before) after 17 runs (I had many guest errors
all along the
And here is an updated dmesg with the 2.6.38-1.28-generic kernel that
oopsed.
** Attachment added: 2.6.38-1.28-generic.dmesg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/694029/+attachment/1826452/+files/2.6.38-1.28-generic.dmesg
--
You received this bug notification because you are
Hi Jamie,
are you still having this problem? Have you been able to reproduce on
any other machine, and/or without ecryptfs backing store?
I have yet to reproduce it, but will attempt to reproduce in an entirely
new environment this afternoon if you are still having this problem.
--
You
I might also mention that in my testing in comment #12, one was a i386
guest and one amd64.
--
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/694029
Title:
[natty] kvm guests become
So far, having two vm's (built by vmbuilder) doing apt-getinstall
ubuntu-desktop, what I got was apt-cacher-ng on the host disappearing
(!).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
Installing 0.12.5+noroms-0ubuntu7, I rebooted and ran my script for 37
runs (~14 hours) and received no Segmentation faults or other weird dpkg
errors. This is with the natty kernel.
While I find it odd that 0.12.5 with the natty kernel is ok, 0.13 with
the natty kernel is not, and either with
Marking qemu-kvm task as Confirmed since it is repeatable.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
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/694029
Well, I just had a segmentation fault and other weird behavior in a
maverick guest with a host with 0.12.5+noroms-0ubuntu7 and the natty
kernel. Seems the combination of 0.13 and the natty kernel is the worst,
and that the maverick kernel is still ok.
--
You received this bug notification
Meh, strike that last comment. I had tracebacks due to bug #621195 in my
last dmesg so the kernel might have been in a weird state when the guest
got the segfault.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
Ok, no aufs kernel tracebacks (ie bug #621195) and the guests are flaky.
What is triggering it is a maverick dist-upgrade in one guest, and an
'apt-get install ubuntu-desktop' in another maverick guest, that only
has ubuntu-minimal installed. I will try disabling ksm.
--
You received this bug
Disabling ksm by adjusting /etc/default/qemu-kvm to have KSM_ENABLED=0
did not help.
--
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/694029
Title:
[natty] kvm guests become
Based on the comments so far, marking Incomplete, as per the Ubuntu
Server triage process. Thanks.
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member
I thought I tested this with 0.12.5, but will try again. This bug (so
far) only happens on my primary system, and testing it sometimes
requires significant time. I will try against 0.12.5 later today.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Tags added: regression-release
** Tags removed: regression-update
--
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/694029
Title:
[natty] kvm guests become unstable after a while
I wonder whether it could be related to
http://www.spinics.net/lists/kvm/msg47235.html
--
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/694029
Title:
[natty] kvm guests become
More info. Tried this again this morning and it happened on the first
run of the script, with the chill mat on and the temperature reasonable.
I don't think it is temperature related.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Thanks for posting this bug, Jamie. Given your two hunches, could you
try to reproduce with ksm disabled, and also with non-virtio disks?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
** Also affects: kvm (Ubuntu)
Importance: Undecided
Status: New
** Package changed: kvm (Ubuntu) = qemu-kvm (Ubuntu)
--
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/694029
Added qemu-kvm task as this is only with kvm quests.
** Description changed:
After upgrading to natty's kernel I noticed that my VMs would sometimes
become highly unstable, with random guest applications segfaulting and
crashing in weird ways. This seems to be more pronounced when running
37 matches
Mail list logo
