Bug#573071:
Am Dienstag, 11. Mai 2010 schrieb dann frazier: On Tue, May 11, 2010 at 09:52:34AM +0200, Werner Opriel wrote: I haven't been able to reproduce this issue on my systems, for whatever reason. Would you be able to verify that this build fixes it for you? http://people.debian.org/~dannf/bugs/573071/ Sorry, i didn't mentioned that i'm using linux-image-2.6.26-2-686-bigmem (2.6.26-21lenny4) on Debian 5.0.4, 32 bits on a AMD64 Board. The behaviour is nearly the same as described with the 64bit kernel. I would like to verify this build as soon as it is available for me. Thanks a lot. i386 builds are available in the same location now. Installing the linux-image-2.6.26-2-686-bigmem_2.6.26-22lenny1_i386.deb fixed the problem for me. Your fixed kernel let me boot my guests, Debian squeeze (kernel 2.6.30 / 2.6.32) , as well as xubuntu (2.6.31), with no problems. Thank you! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201005121903.25...@dolan
Bug#573071:
On Wed, May 12, 2010 at 07:03:25PM +0200, Werner Opriel wrote: Am Dienstag, 11. Mai 2010 schrieb dann frazier: On Tue, May 11, 2010 at 09:52:34AM +0200, Werner Opriel wrote: I haven't been able to reproduce this issue on my systems, for whatever reason. Would you be able to verify that this build fixes it for you? http://people.debian.org/~dannf/bugs/573071/ Sorry, i didn't mentioned that i'm using linux-image-2.6.26-2-686-bigmem (2.6.26-21lenny4) on Debian 5.0.4, 32 bits on a AMD64 Board. The behaviour is nearly the same as described with the 64bit kernel. I would like to verify this build as soon as it is available for me. Thanks a lot. i386 builds are available in the same location now. Installing the linux-image-2.6.26-2-686-bigmem_2.6.26-22lenny1_i386.deb fixed the problem for me. Your fixed kernel let me boot my guests, Debian squeeze (kernel 2.6.30 / 2.6.32) , as well as xubuntu (2.6.31), with no problems. Thank you! Great - thanks for testing. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100512172728.ga16...@lackof.org
Bug#573071:
I haven't been able to reproduce this issue on my systems, for whatever reason. Would you be able to verify that this build fixes it for you? http://people.debian.org/~dannf/bugs/573071/ -- dann frazier Sorry, i didn't mentioned that i'm using linux-image-2.6.26-2-686-bigmem (2.6.26-21lenny4) on Debian 5.0.4, 32 bits on a AMD64 Board. The behaviour is nearly the same as described with the 64bit kernel. I would like to verify this build as soon as it is available for me. Thanks a lot. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201005110952.34139.w@gmx.de
Bug#573071:
On Tue, May 11, 2010 at 09:52:34AM +0200, Werner Opriel wrote: I haven't been able to reproduce this issue on my systems, for whatever reason. Would you be able to verify that this build fixes it for you? http://people.debian.org/~dannf/bugs/573071/ Sorry, i didn't mentioned that i'm using linux-image-2.6.26-2-686-bigmem (2.6.26-21lenny4) on Debian 5.0.4, 32 bits on a AMD64 Board. The behaviour is nearly the same as described with the 64bit kernel. I would like to verify this build as soon as it is available for me. Thanks a lot. i386 builds are available in the same location now. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100511214445.gd5...@lackof.org
Bug#573071: Bug#57307: Fixed Kernel 2.6.26 for Lenny
On Thu, 2010-04-23 at 02:35:16 +0100, Ben Hutchings wrote: Sorry about this. We now have a candidate fix for this, which should be released soon. Please, can you tell us, when a Kernel e.g. 2.6.26-22lenny4 with the patch/fix included is going to be available? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201005060959.19573.w@gmx.de
Bug#573071: Any idea when the fix is going to available?
Applying this patch and building the kernel fixed the problem for me. Thank you! On 04/22/2010 08:35 PM, Ben Hutchings wrote: On Thu, 2010-04-22 at 19:18 -0500, Kevin Burge wrote: It's been almost two months now since I've been able to boot my Linux vms. I'm really surprised by this - usually with Debian problems are fixed within a couple hours to at most a few days. Sorry about this. We now have a candidate fix for this, which should be released soon. Perhaps you would like to test it? Instructions for rebuilding an official kernel package with extra patches are at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. Ben. Date: Fri, 19 Mar 2010 15:47:39 +0100 Subject: KVM: x86: disable paravirt mmu reporting From: Marcelo Tosattimtosa...@redhat.com commit a68a6a7282373bedba8a2ed751b6384edb983a64 upstream Disable paravirt MMU capability reporting, so that new (or rebooted) guests switch to native operation. Paravirt MMU is a burden to maintain and does not bring significant advantages compared to shadow anymore. Signed-off-by: Marcelo Tosattimtosa...@redhat.com Signed-off-by: Avi Kivitya...@redhat.com Signed-off-by: Stefan Baderstefan.ba...@canonical.com Signed-off-by: Greg Kroah-Hartmangre...@suse.de [bwh: Adjust context for 2.6.26] --- arch/x86/kvm/x86.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -1242,8 +1242,8 @@ int kvm_dev_ioctl_check_extension(long e case KVM_CAP_NR_MEMSLOTS: r = KVM_MEMORY_SLOTS; break; - case KVM_CAP_PV_MMU: - r = !tdp_enabled; + case KVM_CAP_PV_MMU:/* obsolete */ + r = 0; break; default: r = 0; --- END --- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bd17750.3030...@systemware.com
Bug#573071: Any idea when the fix is going to available?
It's been almost two months now since I've been able to boot my Linux vms. I'm really surprised by this - usually with Debian problems are fixed within a couple hours to at most a few days. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bd0e773.1080...@systemware.com
Bug#573071: Any idea when the fix is going to available?
On Thu, 2010-04-22 at 19:18 -0500, Kevin Burge wrote: It's been almost two months now since I've been able to boot my Linux vms. I'm really surprised by this - usually with Debian problems are fixed within a couple hours to at most a few days. Sorry about this. We now have a candidate fix for this, which should be released soon. Perhaps you would like to test it? Instructions for rebuilding an official kernel package with extra patches are at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. Ben. Date: Fri, 19 Mar 2010 15:47:39 +0100 Subject: KVM: x86: disable paravirt mmu reporting From: Marcelo Tosatti mtosa...@redhat.com commit a68a6a7282373bedba8a2ed751b6384edb983a64 upstream Disable paravirt MMU capability reporting, so that new (or rebooted) guests switch to native operation. Paravirt MMU is a burden to maintain and does not bring significant advantages compared to shadow anymore. Signed-off-by: Marcelo Tosatti mtosa...@redhat.com Signed-off-by: Avi Kivity a...@redhat.com Signed-off-by: Stefan Bader stefan.ba...@canonical.com Signed-off-by: Greg Kroah-Hartman gre...@suse.de [bwh: Adjust context for 2.6.26] --- arch/x86/kvm/x86.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -1242,8 +1242,8 @@ int kvm_dev_ioctl_check_extension(long e case KVM_CAP_NR_MEMSLOTS: r = KVM_MEMORY_SLOTS; break; - case KVM_CAP_PV_MMU: - r = !tdp_enabled; + case KVM_CAP_PV_MMU:/* obsolete */ + r = 0; break; default: r = 0; --- END --- -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#573071: Oops: 0003 [#1] SMP - BUG: unable to handle kernel paging request
Similar (buggy) behaviour in stable 686-kernel package: linux-image-2.6.26-2-686-bigmem (2.6.26-21lenny4) Tested on Debian 5.0.4, 32 bits, on AMD64. Any idea on how long could it take a new kernel .deb to be released? Cheers, -r -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ba89494.3040...@rs-labs.com
Bug#573071: linux-image-2.6.32-2-amd64: KVM linux guests oops in kvm_leave_lazy_mmu on boot
tags 573071 + patch thanks The patch posted at http://marc.info/?l=kvmm=126834221504655w=2 should fix this. It's cc'd to stable so we may just pick it up that way. Ben. -- Ben Hutchings If God had intended Man to program, we'd have been born with serial I/O ports. signature.asc Description: This is a digitally signed message part
Bug#573071: linux-image-2.6.32-2-amd64: KVM linux guests oops in kvm_leave_lazy_mmu on boot
Hi, I am also affected by this bug. When the guest is running kernel = 2.6.29 - no problem, = 2.6.30 - instant crash. Rebooting the host back into 2.6.30 makes all guests work normally (with any guest kernel version). Regards, -- .''`. Philipp Huebner debala...@debian.org : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` HP: http://www.debalance.de, Skype: philipp-huebner `- ICQ: 235-524-440, Jabber: der_scha...@jabber.org signature.asc Description: OpenPGP digital signature
Processed: bug 573071 is forwarded to k...@vger.kernel.org
Processing commands for cont...@bugs.debian.org: # See thread at http://thread.gmane.org/gmane.linux.kernel/958334 forwarded 573071 k...@vger.kernel.org Bug #573071 [linux-2.6] linux-image-2.6.32-2-amd64: KVM linux guests oops in kvm_leave_lazy_mmu on boot Set Bug forwarded-to-address to 'k...@vger.kernel.org'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12682750433466.transcr...@bugs.debian.org
Bug#573071: linux-image-2.6.32-2-amd64: KVM linux guests oops in kvm_leave_lazy_mmu on boot
Package: linux-2.6 Version: 2.6.32-8 Severity: normal After installing linux-image-2.6.32-2-amd64 (version 2.6.32-8) on the *host*, some linux *guest* kernels oops in kvm_leave_lazy_mmu on boot. Tested guest kernels that fail are linux-image-2.6.30-2-amd64 (2.6.30-8squeeze1), linux- image-2.6.32-trunk-amd64 (2.6.32-5), linux-image-2.6.32-2-amd64 (2.6.32-8), linux-image-2.6.32-3-amd64 (2.6.32-9). However linux-image-2.6.26-2-amd64 from stable (version 2.6.26-21lenny3) boots ok. After rebooting the host back to linux-image-2.6.32-trunk-amd64 (2.6.32-5) guest kernels boot normally. Ubuntu seems to have similar bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/531823 Kernel logs from guest are attached. KVM version is qemu-kvm 0.11.1+dfsg-1 -- Vadim Solomin Loading Linux 2.6.32-3-amd64 ... Loading initial ramdisk ... [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-3-amd64 (Debian 2.6.32-9) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Wed Feb 24 18:07:42 UTC 2010 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-3-amd64 root=UUID=ba75fa3b-56f7-4d29-a88c-56681927c7e5 ro rootflags=acl console=tty0 console=ttyS0,115200n8 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f000 (usable) [0.00] BIOS-e820: 0009f000 - 000a (reserved) [0.00] BIOS-e820: 000e8000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 6fff (usable) [0.00] BIOS-e820: 6fff - 7000 (ACPI data) [0.00] BIOS-e820: fffbc000 - 0001 (reserved) [0.00] DMI 2.4 present. [0.00] last_pfn = 0x6fff0 max_arch_pfn = 0x4 [0.00] x86 PAT enabled: cpu 0, old 0x0, new 0x7010600070106 [0.00] init_memory_mapping: -6fff [0.00] RAMDISK: 37651000 - 37fef99e [0.00] ACPI: RSDP 000fbdb0 00014 (v00 QEMU ) [0.00] ACPI: RSDT 6fff 00034 (v01 QEMU QEMURSDT 0001 QEMU 0001) [0.00] ACPI: FACP 6fff01b4 00074 (v01 QEMU QEMUFACP 0001 QEMU 0001) [0.00] ACPI: DSDT 6fff0280 01DD4 (v01 BXPC BXDSDT 0001 INTL 20090521) [0.00] ACPI: FACS 6fff0240 00040 [0.00] ACPI: SSDT 6fff2054 009E3 (v01 BXPC BXSSDT 0001 INTL 20090521)
