Re: Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs

[Mark Schneider <ms@it-infrastrukturen.org>]

[-- Attachment #1: Type: text/plain, Size: 5169 bytes --]

Am 24.08.2011 23:02, schrieb Konrad Rzeszutek Wilk:
>> [    0.024001] installing Xen timer for CPU 1
>> [    0.024001] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
>> [    0.024001] IP: [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
>> [    0.024001] PGD 0
>> [    0.024001] Oops: 0000 [#1] SMP
>> [    0.024001] last sysfs file:
>> [    0.024001] CPU 1
>> [    0.024001] Modules linked in:
>> [    0.024001] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 HVM domU
>> [    0.024001] RIP: 0010:[<ffffffff810e7f7a>]  [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
>> [    0.744015] Stuck ??
>> [    0.744015] Booting processor 3 APIC 0x6 ip 0x6000
>> [    0.024001] Initializing CPU#3
>> [    0.024001] RSP: 0018:ffff88020f0b5d88  EFLAGS: 00010046
>> [    0.024001] RAX: 0000000000000001 RBX: 00000000000000d0 RCX: 0000000200000010
>> [    0.024001] RDX: 0000000000000000 RSI: 00000000000000d0 RDI: ffffffff81196c8d
>> [    0.024001] RBP: 0000000000000246 R08: 000000000000000a R09: 0000000000000000
>> [    0.024001] R10: 0000000000000000 R11: 00000000000186a0 R12: ffffffff81453f10
>> [    0.024001] R13: 00000000000000d0 R14: 00000000000000d0 R15: 0000000000000007
>> [    0.024001] FS:  0000000000000000(0000) GS:ffff880008c20000(0000) knlGS:0000000000000000
>> [    0.024001] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
>> [    0.024001] CR2: 0000000000000018 CR3: 0000000001001000 CR4: 00000000000006e0
>> [    0.024001] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> [    0.024001] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>> [    0.024001] Process swapper (pid: 0, threadinfo ffff88020f0b4000, task ffff88020f093880)
>> [    0.024001] Stack:
>> [    0.024001]  ffffffffffffffff ffffffff81196c8d 0000003608c20000 00000000000000d0
>> [    0.024001]<0>   ffff88020f0b5e38 0000000000000007 ffffffff813a0fcd 0000000000000000
>> [    0.024001]<0>   0000000000000000 ffffffff81196c8d 0000000000000000 0000000000000000
>> [    0.024001] Call Trace:
>> [    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
>> [    0.024001]  [<ffffffff81196c8d>] ? kvasprintf+0x41/0x68
>> [    0.024001]  [<ffffffff81196cfd>] ? kasprintf+0x49/0x54
>> [    0.024001]  [<ffffffff8119774b>] ? __bitmap_weight+0x3a/0x7e
>> [    0.024001]  [<ffffffff812f5a8f>] ? set_cpu_sibling_map+0x2f4/0x311
>> [    0.024001]  [<ffffffff8100dee4>] ? xen_setup_timer+0x2c/0xa2
>> [    0.024001]  [<ffffffff8100df71>] ? xen_hvm_setup_cpu_clockevents+0x17/0x1d
>> [    0.024001]  [<ffffffff812f5c6a>] ? start_secondary+0x17c/0x185
>> [    0.024001] Code: 10 74 05 e8 90 33 21 00 9c 58 66 66 90 66 90 48 89 c5 fa 66 66 90 66 66 90 65 8b 04 25 a8 e3 00 00 48 98 49 8b 94 c4 f0 02 00 00<8b>   4a 18 89 4c 24 14 48 8b 1a 48 85 db 74 0c 8b 42 14 48 8b 04
>> [    0.024001] RIP  [<ffffffff810e7f7a>] __kmalloc+0xc0/0x141
>>      
> This looks vagualy familiar. Like this:
> https://lkml.org/lkml/2011/7/8/127
>
> I wonder if the kernel is just compiled with MAX_CPUs of 4 and we try to stuff
> more in and end up well, hitting disaster zone.
>
> Is there a .config of this kernel?
>    
Thank you for your answer Konrad.

I have used the regular debian net-install image for HVM installation as 
follows:
disk        = [ 'phy:/dev/vg_xen/squeeze,ioemu:hda,w',
                      
'file:/ftp/debian-6.0.2.1-amd64-i386-netinst.iso,ioemu:hdc:cdrom,r']

Please have a look at the original kernel config of domU domain (s. 
below and attachment):
root@squeezehvm:~# uname -a
Linux squeezehvm 2.6.32-5-amd64 #1 SMP Tue Jun 14 09:42:28 UTC 2011 
x86_64 GNU/Linux

root@squeezehvm:/boot# grep -i cpu config-2.6.32-5-amd64
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
CONFIG_ARCH_CPU_PROBE_RELEASE=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_GENERIC_CPU=y
CONFIG_X86_CPU=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_NR_CPUS=512
CONFIG_X86_CPUID=m
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_HOTPLUG_CPU=y
CONFIG_ACPI_HOTPLUG_CPU=y
# CPU Frequency scaling
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=m
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
# CPUFreq processor drivers
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
CONFIG_SENSORS_VIA_CPUTEMP=m
CONFIG_CPU5_WDT=m
# on-CPU RTC drivers
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set

Thank you / regards,
Mark

-- 
ms@it-infrastrukturen.org


[-- Attachment #2: config-2.6.32-5-amd64.gz --]
[-- Type: application/gzip, Size: 27081 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel