kvm guests become unstable after a while

Bug #694029 reported by Jamie Strandboge
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
GROS-PRUGNY
Natty
Invalid
Undecided
Unassigned
Oneiric
Fix Released
Undecided
Unassigned
qemu-kvm (Ubuntu)
Invalid
Medium
Unassigned
Natty
Invalid
Undecided
Unassigned
Oneiric
Invalid
Medium
Unassigned

Bug Description

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 more than one VM at a time. This does not seem to be a hardware issue-- the host is a 6 month old laptop and I ran memtest86 for 12 hours with 18 successful completions and no errors. There is no host instability or messages in dmesg that I could see that would indicate a host problem. Downgrading to the maverick kernel fixes this problem. I have a script that will launch 10 VMs and run some commands:

#!/bin/sh
count=0
while /bin/true ; do
    count=$(( $count + 1 ))
    echo "RUN $count"
    vm-stop -f -p sec
    sleep 3
    vm-start -s -v -p sec
    sleep 15
    vm-cmd -c -r -p sec apt-get update
    vm-cmd -c -r -p sec apt-get -y --force-yes dist-upgrade

    vm-cmd -c -r -p sec apt-get -y --force-yes install chromium-browser
    vm-cmd -c -r -p sec apt-get -y --force-yes remove --purge chromium-browser*

    vm-cmd -c -r -p sec apt-get -y --force-yes install chromium-browser
    vm-cmd -c -r -p sec apt-get -y --force-yes remove --purge chromium-browser*

    vm-cmd -c -r -p sec apt-get -y --force-yes install chromium-browser
    vm-cmd -c -r -p sec apt-get -y --force-yes remove --purge chromium-browser*

    vm-cmd -c -r -p sec apt-get -y --force-yes install chromium-browser
    vm-cmd -c -r -p sec apt-get -y --force-yes remove --purge chromium-browser*

    vm-cmd -c -r -p sec apt-get -y --force-yes install chromium-browser
    vm-cmd -c -r -p sec apt-get -y --force-yes remove --purge chromium-browser*
done

'vm-start' starts 10 VMs via libvirt with snapshotted qcow2 disks, and vm-stop kills them off, discarding the snapshot. 'vm-cmd' will ssh into each machine and run the command for each machine in sequence. The VMs themselves are all pristine and are resnapshotted on each loop iteration. The point of this explanation is to illustrate that while the VMs all start in the same state, they fail differently or sometimes not at all. I am able to reproduce guest instability within 4-5 iterations of this script on a natty kernel. With the maverick kernel it ran for 18 times with no errors (around 8 hours).

For example, with the above, I saw a maverick/i386 guest fail once with:
dpkg: parse error, in file '/var/lib/dpkg/status' near line 5914 package 'libtelepathy-glib0':
 'Depends' field, reference to 'libglib2.0-0': error in version: version string is empty

Another time the maverick/i386 failed with:
Processing triggers for man-db ...
dpkg: error processing man-db (--unpack):
 subprocess installed post-installation script killed by signal (Segmentation fault)
Errors were encountered while processing:
 man-db

A lucid/i386 guest failed another time with:
Processing triggers for python-gmenu ...
Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...
Segmentation fault
dpkg: error processing python-gmenu (--purge):
 subprocess installed post-installation script returned error exit status 139
Processing triggers for man-db ...
Errors were encountered while processing:
 python-gmenu

There are many other failures....

On my laptop I have an i7 with two cores and 4 hyperthreads per core (this is the default configuration for this machine from the factory and the configuration used to report this bug). I am able to 'disable' hyperthreads in the BIOS, and if I do, I end up with 2 cores and 2 threads per core. In this configuration, I noticed that I don't have to run as many VMs to see the problem. I've seen it with as little as 2 VMs at a time. I mention this as it seems that the issue is exacerbated when the ratio of VMs to CPUs is 1:1 or higher.

I can say for certain that the rc6 and rc7 kernel in natty exhibit the problem, and maverick's does not. I can also say that the natty kernel runs considerably hotter than the maverick kernel, with average temperatures being 10-15C higher underload according to /proc/acpi/ibm/thermal (I had to buy a 'chill mat' (a laptop mat with 2 fans) after upgrading to natty). My gut feeling is that it has to do with KSM or virtio, but I don't know that for sure. This may by chipset specific as a colleague was unable to reproduce this on the rc6 kernel (but also did not run my script-- only did the chromium-browser updates over and over again). I thought it could be the high temperatures causing problems, but then why wasn't the host having problems? I thought it could be the host ram, but memtest86 was ok and running the script for 8 hours on maverick fills the ram and swap and there were still no problems in the guests and no problems on the host. Based on the above it seems clear to me that something in the natty kernel is causing the problem.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.37-11-generic 2.6.37-11.25
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7
Uname: Linux 2.6.37-11-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jamie 2360 F.... pulseaudio
 /dev/snd/pcmC0D0p: jamie 2360 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2520000 irq 43'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:14f15069,17aa2156,00100302 HDA:80862804,17aa21b5,00100000'
   Controls : 16
   Simple ctrls : 7
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6QHT28WW-1.09'
   Mixer name : 'ThinkPad EC 6QHT28WW-1.09'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [off]
Date: Thu Dec 23 23:22:11 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=58280e6e-d161-43ea-8593-a89fb7b6851a
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
MachineType: LENOVO 5129CTO
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-11-generic root=UUID=82571cfb-fdda-4d2f-b708-f8924aa0fe21 ro vt.handoff=7 quiet splash
RelatedPackageVersions: linux-firmware 1.44
SourcePackage: linux
dmi.bios.date: 04/20/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET44WW (1.14 )
dmi.board.name: 5129CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6QET44WW(1.14):bd04/20/2010:svnLENOVO:pn5129CTO:pvrThinkPadX201s:rvnLENOVO:rn5129CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 5129CTO
dmi.product.version: ThinkPad X201s
dmi.sys.vendor: LENOVO

Revision history for this message
Jamie Strandboge (jdstrand) wrote :
affects: kvm (Ubuntu) → qemu-kvm (Ubuntu)
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Added qemu-kvm task as this is only with kvm quests.

description: updated
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for posting this bug, Jamie. Given your two hunches, could you try to reproduce with ksm disabled, and also with non-virtio disks?

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

I wonder whether it could be related to http://www.spinics.net/lists/kvm/msg47235.html

Revision history for this message
Dave Walker (davewalker) wrote :

Based on the comments so far, marking Incomplete, as per the Ubuntu Server triage process. Thanks.

Changed in qemu-kvm (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

tags: added: regression-release
removed: regression-update
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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 the maverick kernel seems ok, at this point it seems that it is indeed an issue with qemu-kvm.

Changed in qemu-kvm (Ubuntu):
status: Incomplete → New
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Marking qemu-kvm task as Confirmed since it is repeatable.

Changed in qemu-kvm (Ubuntu):
status: New → Confirmed
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Disabling ksm by adjusting /etc/default/qemu-kvm to have KSM_ENABLED=0 did not help.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I disabled virtio disks in the two guests and tested them using the same procedure in comment #12 with no luck. The ksm and virtio testing was done with the 0.12.5+noroms-0ubuntu7 qemu-kvm.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

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 (!).

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I might also mention that in my testing in comment #12, one was a i386 guest and one amd64.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

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.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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 2.6.38-1.28-generic kernel and am still seeing it. Also, I hadn't seen it for a while but have been connected via wired ethernet. I then was connected to wireless and saw it. That might be a fluke, but I am starting to think I see it more often when using wireless (weird).

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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 way).

Attached is that kernel oops.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

And here is an updated dmesg with the 2.6.38-1.28-generic kernel that oopsed.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

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?

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

aufs should be ruled out based on the kernel team's evaluation in bug #621195, which in summary states that on natty, the aufs 'issue' was purely cosmetic.

As for xfs, unfortunately, no, but this prompted to look at how much space I have, and I think the OOPS yesterday may have to do with the fact that I could have hit 95% of my disk space on that test run (which would explain why that is the first time I saw a host error). I've freed up some space and I am retesting now and will report back.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

Changed in qemu-kvm (Ubuntu):
status: Confirmed → Invalid
Changed in linux (Ubuntu):
assignee: nobody → Serge Hallyn (serge-hallyn)
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

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 file=/home/kirkland/.cache/testdrive/img/testdrive-disk-suoUtC.img,if=virtio,cache=writeback,index=0,boot=on -usb -usbdevice tablet -net nic,model=virtio -net user -soundhw es1370 -vga cirrus

The backing disk is on an ext4 filesystem (a symlink busts it out of my encrypted home).

I'm on an x201 with an i7 processor, and Centrino Ultimate-N 6300 wireless. Kernel is:
Linux x201 2.6.38-3-generic #30-Ubuntu SMP Thu Feb 10 00:33:26 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Changed in linux (Ubuntu):
assignee: Serge Hallyn (serge-hallyn) → nobody
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

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 to git head to find the offensive commit.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

Revision history for this message
Kees Cook (kees) wrote :

I have no wireless on my system, and I just saw this in a VM I started.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

@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.

Revision history for this message
Kees Cook (kees) wrote :

model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote :

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 is a 64-bit Lucid machine. When I try compiling the linux kernel on it (2.6.38.something, from git), it fails every time with an error like this:

  gcc -Wp,-MD,drivers/firewire/.sbp2.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/4.4.3/include -I/home/seb/uvc/uvcvideo/arch/x86/include -Iinclude -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=1024 -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -pg -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(sbp2)" -D"KBUILD_MODNAME=KBUILD_STR(firewire_sbp2)" -c -o drivers/firewire/.tmp_sbp2.o drivers/firewire/sbp2.c
In file included from include/linux/mm.h:250,
                 from include/linux/pagemap.h:7,
                 from include/linux/blkdev.h:12,
                 from drivers/firewire/sbp2.c:31:
include/linux/page-flags.h: In function ‘PageOwnerPriv1’:
include/linux/page-flags.h:225: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
make[2]: *** [drivers/firewire/sbp2.o] Error 1
make[1]: *** [drivers/firewire] Error 2
make: *** [drivers] Error 2

If I run make again, it compiles that file fine and segfaults on some other file.

The host machine is totally stable, no problems at all. The host machine has plenty of disk free on / and /home (where the VMs live). / and /home are both ext4, though I think that's irrelevant.

Please let me know if you want me to run any experiments...

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote :

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.

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote :

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 wifi on.

I'll attach my system information from apport.

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : apport information

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 PID ACCESS COMMAND
 /dev/snd/controlC0: seb 1579 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xe2e60000 irq 47'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:111d76e7,10280494,00100102 HDA:80862805,80860101,00100000'
   Controls : 27
   Simple ctrls : 13
DistroRelease: Ubuntu 11.04
HibernationDevice: RESUME=UUID=4dce84f4-fd2f-4dd4-b0be-46a9f45b1083
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Dell Inc. Latitude E6520
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=c0882da2-2906-45ee-946f-28fac848f4ef ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.52
Tags: natty running-unity
Uname: Linux 2.6.38-8-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
dmi.bios.date: 04/13/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0NVF5K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd04/13/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

tags: added: apport-collected
Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : AcpiTables.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : AlsaDevices.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : AplayDevices.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : BootDmesg.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : Card0.Codecs.codec.3.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : IwConfig.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : Lspci.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : Lsusb.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : PciMultimedia.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : ProcCpuinfo_.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : ProcModules.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : RfKill.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : UdevDb.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : UdevLog.txt

apport information

Revision history for this message
Sebastian Kuzminsky (seb-highlab) wrote : WifiSyslog.txt

apport information

Revision history for this message
Jamie Strandboge (jdstrand) wrote : Re: [natty] kvm guests become unstable after a while

This is still a problem on Oneiric.

Changed in qemu-kvm (Ubuntu Natty):
status: New → Invalid
Changed in linux (Ubuntu Natty):
status: New → Confirmed
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Removing '[natty]' from description as this affects oneiric too, and the bug is targeted to both natty and oneiric already.

summary: - [natty] kvm guests become unstable after a while
+ kvm guests become unstable after a while
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Hi Jamie,

Do you think the priority of this should be raised?

Has this been reproduced on anything that is not a thinkpad x201 or
similar?

I've been meaning to reproduce this on the qa rig, but firewall
prevented me from bzr fetching the vm-tools suite. A script
relying only on kvm itself should certainly be able to reproduce
this, but i've not gotten around to writing that.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I am happy to report that for the last several weeks this bug seems to be fixed. It appears to coincide with either linux-firmware 1.60 (possibly 1.59, since I went from 1.58 straight to 1.60) or linux 3.0.0-9.13 (or 3.0.0-9.12). I did updates around 2011-08-23 and found this bug is no longer a problem. I have done a lot of testing including the test case in the description along with a lot of VM use and updates in general. Marking Oneiric as 'Fix Released', but will re-open if this comes up again.

Changed in linux (Ubuntu Oneiric):
status: Confirmed → Fix Released
Revision history for this message
GROS-PRUGNY (bouliky) wrote :

Welcome to Testdrive!

  1. Ubuntu Desktop (precise-i386)
     +-cache--> [2012-01-01 09:27:07] precise-desktop-i386.iso
  2. Ubuntu Alternate (precise-i386)
  3. Ubuntu DVD (precise-i386)
  4. Ubuntu Server (precise-i386)
  5. Other (prompt for ISO URL)

Select an image to testdrive [1]: 1
INFO: Syncing the specified ISO...
      rsync://cdimage.ubuntu.com/cdimage/daily-live/current/precise-desktop-i386.iso

receiving incremental file list
precise-desktop-i386.iso
   741650432 100% 1.20MB/s 0:09:50 (xfer#1, to-check=0/1)

sent 190693 bytes received 146158997 bytes 242501.56 bytes/sec
total size is 741650432 speedup is 5.07
INFO: Validating Virtualization Method....
INFO: VirtualBox 4.1 detected.
INFO: Setting up Virtual Machine...
INFO: Creating disk image...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Disk image created. UUID: 1f3c3666-5df9-4ec1-8fe4-64c3f1202ab1
INFO: Creating the Virtual Machine...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Virtual machine 'testdrive' is created and registered.
UUID: 0c68d3f0-e2e2-44e3-84a7-9e86db51c0eb
Settings file: '/root/VirtualBox VMs/testdrive/testdrive.vbox'
INFO: Launching Virtual Machine...
Running the Virtual Machine...
 VBoxManage startvm testdrive
INFO: You may wish to clean up the cache directory...
      /root/.cache/testdrive/iso and /root/.cache/testdrive/img

Changed in linux (Ubuntu):
assignee: nobody → GROS-PRUGNY (bouliky)
dino99 (9d9)
Changed in linux (Ubuntu Natty):
status: Confirmed → Invalid
To post a comment you must log in.