FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 08-22-2008, 07:32 AM
Rik Theys
 
Default Bug#496028: linux-2.6: host kernel oopses when adding a cpu to a kvm virtual machine

Package: linux-2.6
Version: 2.6.26-3
Severity: normal


I'm running a kvm virtual machine (with CentOS 5.2 as the guest OS, but it doesn't seem to
matter) on a Lenny host (using the 2.6.26 kernel and kvm from unstable). When I try to
hot-add a cpu to the virtual machine, the host kernel oopses and becomes unresponsive after
a few minutes/seconds.

I'm not sure this is a kernel or kvm bug.

I've added the cpu to the virtual machine by logging in on the kvm monitor interface of
the virtual machine and entering: cpu_set 1 online

I'm not 100% sure this is the correct way to hot-add a CPU. I can't seem to find the
documented way to do this using google. Also asked on #kvm but got no response.

The kvm virtual machine was started with the following command:

kvm -m 1024 -smp 1 -monitor tcp:localhost:8888,server,nowait -localtime -drive file=/test2-local.img,if=ide,boot=on -net nic,macaddr=00:16:3e:00:00:02,vlan=0, -net tap,script=/etc/kvm/kvm-ifup,vlan=0 -vnc 127.0.0.1:1 -daemonize

I've noticed some kvm fixes in upstreams 2.6.26.3 release but am not sure they fix this issue.

Here's the oops I get:

Message from syslogd@lo at Fri Aug 22 09:24:16 2008 ...
lo kernel: [89264.841448] Oops: 0002 [1] SMP

Message from syslogd@lo at Fri Aug 22 09:24:16 2008 ...
lo kernel: [89264.842569] Code: 48 89 df 48 83 c3 48 e8 51 86 ff ff 4c 89 e7 48 29 d8 48 89 c3 e8 8c bf eb df 48 c1 e8 0c 48 c1 eb 06 48 6b c0 38 48 8b 44 28 10 <0f> ab 58 40 45 85 ff 0f 85 e8 00 00 00 49 8b 04 24 48 3b 05 63

Message from syslogd@lo at Fri Aug 22 09:24:16 2008 ...
lo kernel: [89264.842778] CR2: 0000000000000040
Aug 22 09:24:16 lo kernel: [89264.841352] BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
Aug 22 09:24:16 lo kernel: [89264.841389] IP: [<ffffffffa03663ed>] :kvm:mmu_set_spte+0x209/0x340
Aug 22 09:24:16 lo kernel: [89264.841428] PGD 7d839067 PUD 4447b067 PMD 0
Aug 22 09:24:16 lo kernel: [89264.841448] Oops: 0002 [1] SMP
Aug 22 09:24:16 lo kernel: [89264.841466] CPU 0
Aug 22 09:24:16 lo kernel: [89264.841479] Modules linked in: tun kvm_intel kvm video output ac battery cpufreq_ondemand cpufreq_userspace cpufreq_powersave cpufreq_stats freq_table cpufreq_conservative ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi scsi_transport_iscsi bridge ipv6 loop psmouse snd_hda_intel i2c_i801 intel_agp button evdev serio_raw parport_pc parport snd_pcm snd_timer snd soundcore snd_page_alloc i2c_core iTCO_wdt dcdbas pcspkr ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sg sr_mod cdrom sd_mod ata_generic usbhid hid ff_memless ata_piix libata scsi_mod dock floppy ide_pci_generic ide_core tg3 ehci_hcd uhci_hcd thermal processor fan thermal_sys
Aug 22 09:24:16 lo kernel: [89264.841772] Pid: 3579, comm: kvm Not tainted 2.6.26-1-amd64 #1
Aug 22 09:24:16 lo kernel: [89264.841788] RIP: 0010:[<ffffffffa03663ed>] [<ffffffffa03663ed>] :kvm:mmu_set_spte+0x209/0x340
Aug 22 09:24:16 lo kernel: [89264.841827] RSP: 0018:ffff81007add5b38 EFLAGS: 00010212
Aug 22 09:24:16 lo kernel: [89264.841843] RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffff81007ad78080
Aug 22 09:24:16 lo kernel: [89264.841862] RDX: 0000000000040000 RSI: 000000000003fff2 RDI: ffff8100790b8030
Aug 22 09:24:16 lo kernel: [89264.841880] RBP: ffffe20000000000 R08: 0000000000000001 R09: 0000000000000009
Aug 22 09:24:16 lo kernel: [89264.841899] R10: ffff810032893410 R11: ffffffffa0381fa3 R12: ffff8100790b8030
Aug 22 09:24:16 lo kernel: [89264.841917] R13: ffff81007adf00c0 R14: fffffffffffff001 R15: 0000000000000000
Aug 22 09:24:16 lo kernel: [89264.841937] FS: 00000000513c1950(0000) GS:ffffffff8053b000(0000) knlGS:0000000000000000
Aug 22 09:24:16 lo kernel: [89264.841964] CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
Aug 22 09:24:16 lo kernel: [89264.841980] CR2: 0000000000000040 CR3: 000000007d95d000 CR4: 00000000000026e0
Aug 22 09:24:16 lo kernel: [89264.841999] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 22 09:24:16 lo kernel: [89264.842017] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 22 09:24:16 lo kernel: [89264.842036] Process kvm (pid: 3579, threadinfo ffff81007add4000, task ffff810037878ee0)
Aug 22 09:24:16 lo kernel: [89264.842063] Stack: 0000000000000000 0000000000000001 0000000000000009 ffff81007adf00c0
Aug 22 09:24:16 lo kernel: [89264.842099] 0000000000000007 000000000000000b ffff8100790b8030 ffffffffa03681b0
Aug 22 09:24:16 lo kernel: [89264.842134] 0000000000000040 ffff81007add5c54 ffffffff00000000 000000000003fff2
Aug 22 09:24:16 lo kernel: [89264.842158] Call Trace:
Aug 22 09:24:16 lo kernel: [89264.842193] [<ffffffffa03681b0>] ? :kvmaging64_page_fault+0x37f/0x3d1
Aug 22 09:24:16 lo kernel: [89264.842231] [<ffffffffa0366bc4>] ? :kvm:kvm_mmu_page_fault+0x19/0x81
Aug 22 09:24:16 lo kernel: [89264.842259] [<ffffffffa03642be>] ? :kvm:kvm_arch_vcpu_ioctl_run+0x463/0x615
Aug 22 09:24:16 lo kernel: [89264.842289] [<ffffffffa035f6ce>] ? :kvm:kvm_vcpu_ioctl+0xf3/0x3a9
Aug 22 09:24:16 lo kernel: [89264.842313] [<ffffffff8022ad5c>] ? __wake_up+0x38/0x4f
Aug 22 09:24:16 lo kernel: [89264.842333] [<ffffffff802f4467>] ? avc_has_perm+0x49/0x5b
Aug 22 09:24:16 lo kernel: [89264.842351] [<ffffffff8024f962>] ? futex_wake+0xbb/0xfa
Aug 22 09:24:16 lo kernel: [89264.842372] [<ffffffff802f508d>] ? inode_has_perm+0x65/0x72
Aug 22 09:24:16 lo kernel: [89264.842390] [<ffffffff80248bb6>] ? ktime_get_ts+0x22/0x4b
Aug 22 09:24:16 lo kernel: [89264.842407] [<ffffffff8023e078>] ? __dequeue_signal+0x19/0x15a
Aug 22 09:24:16 lo kernel: [89264.842429] [<ffffffffa0381f4f>] ? :kvm_intel:handle_io+0x0/0x54
Aug 22 09:24:16 lo kernel: [89264.842449] [<ffffffff802f5134>] ? file_has_perm+0x9a/0xa9
Aug 22 09:24:16 lo kernel: [89264.842469] [<ffffffff802a635d>] ? vfs_ioctl+0x21/0x6b
Aug 22 09:24:16 lo kernel: [89264.842487] [<ffffffff802a65ef>] ? do_vfs_ioctl+0x248/0x261
Aug 22 09:24:16 lo kernel: [89264.842506] [<ffffffff802a6659>] ? sys_ioctl+0x51/0x70
Aug 22 09:24:16 lo kernel: [89264.842525] [<ffffffff8020be9a>] ? system_call_after_swapgs+0x8a/0x8f
Aug 22 09:24:16 lo kernel: [89264.842546]
Aug 22 09:24:16 lo kernel: [89264.842557]
Aug 22 09:24:16 lo kernel: [89264.842569] Code: 48 89 df 48 83 c3 48 e8 51 86 ff ff 4c 89 e7 48 29 d8 48 89 c3 e8 8c bf eb df 48 c1 e8 0c 48 c1 eb 06 48 6b c0 38 48 8b 44 28 10 <0f> ab 58 40 45 85 ff 0f 85 e8 00 00 00 49 8b 04 24 48 3b 05 63
Aug 22 09:24:16 lo kernel: [89264.842736] RIP [<ffffffffa03663ed>] :kvm:mmu_set_spte+0x209/0x340
Aug 22 09:24:16 lo kernel: [89264.842764] RSP <ffff81007add5b38>
Aug 22 09:24:16 lo kernel: [89264.842778] CR2: 0000000000000040
Aug 22 09:24:16 lo kernel: [89264.843115] ---[ end trace 56cf2d3ddd54c88c ]---

Regards,

Rik



-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 08-22-2008, 05:42 PM
maximilian attems
 
Default Bug#496028: linux-2.6: host kernel oopses when adding a cpu to a kvm virtual machine

On Fri, 22 Aug 2008, Rik Theys wrote:

> Package: linux-2.6
> Version: 2.6.26-3
> Severity: normal
>
>
> I'm running a kvm virtual machine (with CentOS 5.2 as the guest OS, but it doesn't seem to
> matter) on a Lenny host (using the 2.6.26 kernel and kvm from unstable). When I try to
> hot-add a cpu to the virtual machine, the host kernel oopses and becomes unresponsive after
> a few minutes/seconds.
>
> I'm not sure this is a kernel or kvm bug.
>
> I've added the cpu to the virtual machine by logging in on the kvm monitor interface of
> the virtual machine and entering: cpu_set 1 online
>
> I'm not 100% sure this is the correct way to hot-add a CPU. I can't seem to find the
> documented way to do this using google. Also asked on #kvm but got no response.
>
> The kvm virtual machine was started with the following command:
>
> kvm -m 1024 -smp 1 -monitor tcp:localhost:8888,server,nowait -localtime -drive file=/test2-local.img,if=ide,boot=on -net nic,macaddr=00:16:3e:00:00:02,vlan=0, -net tap,script=/etc/kvm/kvm-ifup,vlan=0 -vnc 127.0.0.1:1 -daemonize
>
> I've noticed some kvm fixes in upstreams 2.6.26.3 release but am not sure they fix this issue.

right please try out sid snapshots, see apt lines
-> http://wiki.debian.org/DebianKernel
they carry 2.6.26.3



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 08-22-2008, 09:18 PM
rtheys
 
Default Bug#496028: linux-2.6: host kernel oopses when adding a cpu to a kvm virtual machine

Hi,

Quoting maximilian attems <max@stro.at>:
> On Fri, 22 Aug 2008, Rik Theys wrote:
> > I've noticed some kvm fixes in upstreams 2.6.26.3 release but am
> not sure they fix this issue.
>
> right please try out sid snapshots, see apt lines
> -> http://wiki.debian.org/DebianKernel
> they carry 2.6.26.3

I've tried the kernel targetted for sid and the kernel no longer oopses when I enter the
command, but kvm segfaults now. So instead of oopsing the host kernel, the virtual
machine now dies. I'm also not sure the command I enter is supposed to work as I can't
find any documentation about it. I guess you can reassign this bug to kvm when the new
kernel enters unstable/lenny.

Regards,

Rik


Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 07:22 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org