On Sun, 2008-11-23 at 10:49 +0200, Avi Kivity wrote: > Kasper Sandberg wrote: > > Hello. > > > > I just noticed that my dmesg had been flooded with backtraces, appearing > > to be of KVM origin. I realize that my kernel is tainted, and slightly > > outdated, however, i just wanted to drop the log here in case it might > > be useful, but feel free to completely ignore it :) > > > > i am not subscribed to the kvm list, so please cc me in case you need > > further info.. > > > > my entire dmesg was flooded with backtraces looking practically > > identical to this one, so i will only paste a few of them, however, > > should you want more(though from a quick look they appear identical), i > > can put online the complete log > > > > What guest are you running?
Yeah sorry, i was gonna include that in the mail, i apparently forgot. I have been running debian, both 32 and 64bit inside it, .18, .24 and .26 kernels, and ubuntu 8.10 .27 kernels, ATLEAST 32bit, i do not remember if i have run 64bit ubuntu 8.10 I can however give some information that _MIGHT_ (i have no clue myself) be relevant on one of the debian guests i had xrandr crash the X server while trying to change resolution, i did this a few times. Using -vga std. also, on the ubuntu 32bit guest, i ran qemu with debian stable, where X crashed during start inside the qemu on the ubuntu guest. This happened only once. im quite certain my ram and that is fine, no errors when doing memory testing etc. but as said, the kernel is tainted, i dont know if that affects the results or not, i just wanted to inform in case this can help someone. That being said, the box has NOT been rebooted since, and i can confirm that kvm works excellently, i have spawned several VMs and used a tad, since i wrote the mail. > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
