thr3ads.net - Xen devel - [Xen-devel] 2.6.28 64-bit domU not booting [Jan 2009]

If this information is useful, please help other people find it:
Share via:

Valtteri Kiviniemi

2009-Jan-05 12:19 UTC

[Xen-devel] 2.6.28 64-bit domU not booting

Hi,

Im using vanilla 2.6.28 kernel from kernel.org and when I try to boot my 
  domU with it, it just disappears without any error or warning.

I have double checked that I have all the necessary options enabled on 
my kernel config.

xend.log says following:

[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) 
XendDomainInfo.create([''vm'', [''name'',
''dataproof''], [''memory'',
''256''],
[''on_poweroff'', ''destroy''],
[''on_reboot'', ''restart''],
[''on_crash'',
''restart''], [''vcpus'',
''1''], [''on_xend_start'',
''ignore''],
[''on_xend_stop'', ''ignore''],
[''image'', [''linux'',
[''kernel'',
''/boot/vmlinux-2.6.28''], [''root'',
''/dev/xvda1 ro''], [''args'',
''xencons=hvc0 console=hvc0'']]], [''device'',
[''vbd'', [''uname'',
''phy:/dev/virtual/dataproof''], [''dev'',
''xvda1''], [''mode'', ''w'']]],
[''device'', [''vbd'',
[''uname'', ''phy:/dev/virtual/dataproofswap''],
[''dev'',
''xvda2''], [''mode'', ''w'']]],
[''device'', [''vif'',
[''bridge'', ''xenbr0''],
[''mac'', ''00:16:3e:50:c7:43'']]]])
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) 
XendDomainInfo.constructDomain
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) Balloon: 2949932 KiB 
free; need 2048; done.
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) Adding Domain: 58
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) 
XendDomainInfo.initDomain: 58 256
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) 
_initDomain:shadow_memory=0x0, memory_static_max=0x10000000, 
memory_static_min=0x0.
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) Balloon: 2949924 KiB 
free; need 263168; done.
[2009-01-05 13:16:31 8052] INFO (__init__:1072) buildDomain os=linux 
dom=58 vcpus=1
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) domid          = 58
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) memsize        = 256
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) image          = 
/boot/vmlinux-2.6.28
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) store_evtchn   = 1
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) console_evtchn = 2
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) cmdline        = 
root=/dev/xvda1 ro xencons=hvc0 console=hvc0
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) ramdisk        [2009-01-05
13:16:31 8052] DEBUG (__init__:1072) vcpus          = 1
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) features       [2009-01-05
13:16:32 8052] INFO (__init__:1072) createDevice: vbd :
{''uuid'':
''24753641-db04-731b-adc1-ed1773bf956d'',
''bootable'': 1,
''driver'': ''paravirtualised'',
''dev'': ''xvda1'', ''uname'':
''phy:/dev/virtual/dataproof'', ''mode'':
''w''}
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
{''virtual-device'': ''51713'',
''device-type'': ''disk'',
''protocol'':
''x86_64-abi'', ''backend-id'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/58/51713''} to 
/local/domain/58/device/vbd/51713.
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
{''domain'': ''dataproof'',
''frontend'':
''/local/domain/58/device/vbd/51713'',
''uuid'':
''24753641-db04-731b-adc1-ed1773bf956d'',
''dev'': ''xvda1'', ''state'':
''1'', ''params'':
''/dev/virtual/dataproof'', ''mode'':
''w'', ''online'': ''1'',
''frontend-id'': ''58'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/58/51713.
[2009-01-05 13:16:32 8052] INFO (__init__:1072) createDevice: vbd : 
{''uuid'':
''a8053c53-719a-e7a7-3389-92cd1610a1f8'',
''bootable'': 0,
''driver'': ''paravirtualised'',
''dev'': ''xvda2'', ''uname'':
''phy:/dev/virtual/dataproofswap'', ''mode'':
''w''}
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
{''virtual-device'': ''51714'',
''device-type'': ''disk'',
''protocol'':
''x86_64-abi'', ''backend-id'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/58/51714''} to 
/local/domain/58/device/vbd/51714.
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
{''domain'': ''dataproof'',
''frontend'':
''/local/domain/58/device/vbd/51714'',
''uuid'':
''a8053c53-719a-e7a7-3389-92cd1610a1f8'',
''dev'': ''xvda2'', ''state'':
''1'', ''params'':
''/dev/virtual/dataproofswap'', ''mode'':
''w'', ''online'': ''1'',
''frontend-id'': ''58'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/58/51714.
[2009-01-05 13:16:32 8052] INFO (__init__:1072) createDevice: vif : 
{''bridge'': ''xenbr0'',
''mac'': ''00:16:3e:50:c7:43'',
''uuid'':
''42ff0ad4-e5fb-4dc1-0436-05580093af2b''}
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
{''mac'': ''00:16:3e:50:c7:43'',
''handle'': ''0'', ''protocol'':
''x86_64-abi'',
''backend-id'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vif/58/0''} to
/local/domain/58/device/vif/0.
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
{''bridge'': ''xenbr0'',
''domain'': ''dataproof'',
''handle'': ''0'', ''uuid'':
''42ff0ad4-e5fb-4dc1-0436-05580093af2b'',
''script'':
''/etc/xen/scripts/vif-bridge'', ''mac'':
''00:16:3e:50:c7:43'',
''frontend-id'': ''58'',
''state'': ''1'', ''online'':
''1'', ''frontend'':
''/local/domain/58/device/vif/0''} to
/local/domain/0/backend/vif/58/0.
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) Storing VM details: 
{''on_xend_stop'': ''ignore'',
''shadow_memory'': ''0'',
''uuid'':
''d7774355-4b1e-18d5-7177-41dc019dbe9c'',
''on_reboot'': ''restart'',
''start_time'': ''1231154192.25'',
''on_poweroff'': ''destroy'',
''on_xend_start'': ''ignore'',
''on_crash'': ''restart'',
''xend/restart_count'':
''0'', ''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''image'': "(linux (kernel
/boot/vmlinux-2.6.28) (args ''root=/dev/xvda1 ro xencons=hvc0 
console=hvc0'') (notes (HV_START_LOW 18446603336221196288) (FEATURES 
''!writable_page_tables|pae_pgdir_above_4gb'') (VIRT_BASE 
18446744071562067968) (GUEST_VERSION 2.6) (PADDR_OFFSET 0) (GUEST_OS 
linux) (HYPERCALL_PAGE 18446744071564201984) (LOADER generic) 
(SUSPEND_CANCEL 1) (PAE_MODE yes) (ENTRY 18446744071568527872) 
(XEN_VERSION xen-3.0)))", ''name'':
''dataproof''}
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) Storing domain details: 
{''console/ring-ref'': ''1934400'',
''image/entry'': ''18446744071568527872'',
''console/port'': ''2'',
''store/ring-ref'': ''1934401'',
''image/loader'':
''generic'', ''vm'':
''/vm/d7774355-4b1e-18d5-7177-41dc019dbe9c'',
''control/platform-feature-multiprocessor-suspend'':
''1'',
''image/hv-start-low'':
''18446603336221196288'', ''image/guest-os'':
''linux'',
''image/virt-base'': ''18446744071562067968'',
''memory/target'': ''262144'',
''image/guest-version'': ''2.6'',
''image/pae-mode'': ''yes'',
''console/limit'':
''1048576'', ''image/paddr-offset'':
''0'', ''image/hypercall-page'':
''18446744071564201984'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
''image/features/pae-pgdir-above-4gb'':
''1'', ''image/features/writable-page-tables'':
''0'', ''console/type'':
''xenconsoled'', ''name'':
''dataproof'', ''domid'':
''58'', ''image/xen-version'':
''xen-3.0'', ''store/port'':
''1''}
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
{''protocol'': ''x86_64-abi'',
''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/console/58/0''} to 
/local/domain/58/device/console/0.
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
{''domain'': ''dataproof'',
''frontend'':
''/local/domain/58/device/console/0'',
''uuid'':
''4ebfb3e4-79bf-27c3-0d58-acf2e0904e0f'',
''frontend-id'': ''58'',
''state'': ''1'', ''location'':
''2'', ''online'': ''1'',
''protocol'': ''vt100''} to
/local/domain/0/backend/console/58/0.
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) 
XendDomainInfo.handleShutdownWatch
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) Waiting for devices vif.
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) Waiting for 0.
[2009-01-05 13:16:32 8052] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vif/58/0/hotplug-status.
[2009-01-05 13:16:33 8052] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vif/58/0/hotplug-status.
[2009-01-05 13:16:33 8052] DEBUG (__init__:1072) hotplugStatusCallback 1.
[2009-01-05 13:16:33 8052] DEBUG (__init__:1072) Waiting for devices vscsi.
[2009-01-05 13:16:33 8052] DEBUG (__init__:1072) Waiting for devices vbd.
[2009-01-05 13:16:33 8052] DEBUG (__init__:1072) Waiting for 51713.
[2009-01-05 13:16:33 8052] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vbd/58/51713/hotplug-status.
[2009-01-05 13:16:33 8052] DEBUG (__init__:1072) hotplugStatusCallback 1.
[2009-01-05 13:16:33 8052] DEBUG (__init__:1072) Waiting for 51714.
[2009-01-05 13:16:33 8052] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vbd/58/51714/hotplug-status.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vbd/58/51714/hotplug-status.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) hotplugStatusCallback 1.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices irq.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices vkbd.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices vfb.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices 
console.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for 0.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices pci.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices 
ioports.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices tap.
[2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices vtpm.
[2009-01-05 13:16:34 8052] INFO (__init__:1072) Domain dataproof (58) 
unpaused.
[2009-01-05 13:16:34 8052] WARNING (__init__:1072) Domain has crashed: 
name=dataproof id=58.

and then it loops for a while until:

[2009-01-05 13:16:35 8052] ERROR (__init__:1072) VM dataproof restarting 
too fast (1.637592 seconds since the last restart).  Refusing to restart 
to avoid loops.

Any suggestions?

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

Valtteri Kiviniemi

2009-Jan-05 12:48 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Oh,

forgot to say that im using Xen 3.3.1-rc1-pre and 2.6.18.8-xen0

Valtteri Kiviniemi kirjoitti:> Hi,
> 
> Im using vanilla 2.6.28 kernel from kernel.org and when I try to boot my 
>  domU with it, it just disappears without any error or warning.
> 
> I have double checked that I have all the necessary options enabled on 
> my kernel config.
> 
> xend.log says following:
> 
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) 
> XendDomainInfo.create([''vm'', [''name'',
''dataproof''], [''memory'',
''256''],
> [''on_poweroff'', ''destroy''],
[''on_reboot'', ''restart''],
[''on_crash'',
> ''restart''], [''vcpus'',
''1''], [''on_xend_start'',
''ignore''],
> [''on_xend_stop'', ''ignore''],
[''image'', [''linux'',
[''kernel'',
> ''/boot/vmlinux-2.6.28''], [''root'',
''/dev/xvda1 ro''], [''args'',
> ''xencons=hvc0 console=hvc0'']]],
[''device'', [''vbd'',
[''uname'',
> ''phy:/dev/virtual/dataproof''], [''dev'',
''xvda1''], [''mode'', ''w'']]],
> [''device'', [''vbd'',
[''uname'', ''phy:/dev/virtual/dataproofswap''],
[''dev'',
> ''xvda2''], [''mode'',
''w'']]], [''device'', [''vif'',
[''bridge'', ''xenbr0''],
> [''mac'', ''00:16:3e:50:c7:43'']]]])
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) 
> XendDomainInfo.constructDomain
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) Balloon: 2949932 KiB 
> free; need 2048; done.
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) Adding Domain: 58
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) 
> XendDomainInfo.initDomain: 58 256
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) 
> _initDomain:shadow_memory=0x0, memory_static_max=0x10000000, 
> memory_static_min=0x0.
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) Balloon: 2949924 KiB 
> free; need 263168; done.
> [2009-01-05 13:16:31 8052] INFO (__init__:1072) buildDomain os=linux 
> dom=58 vcpus=1
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) domid          = 58
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) memsize        = 256
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) image          = 
> /boot/vmlinux-2.6.28
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) store_evtchn   = 1
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) console_evtchn = 2
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) cmdline        = 
> root=/dev/xvda1 ro xencons=hvc0 console=hvc0
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) ramdisk        >
[2009-01-05 13:16:31 8052] DEBUG (__init__:1072) vcpus          = 1
> [2009-01-05 13:16:31 8052] DEBUG (__init__:1072) features       >
[2009-01-05 13:16:32 8052] INFO (__init__:1072) createDevice: vbd :
> {''uuid'':
''24753641-db04-731b-adc1-ed1773bf956d'',
''bootable'': 1,
> ''driver'': ''paravirtualised'',
''dev'': ''xvda1'', ''uname'':
> ''phy:/dev/virtual/dataproof'', ''mode'':
''w''}
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
> {''virtual-device'': ''51713'',
''device-type'': ''disk'',
''protocol'':
> ''x86_64-abi'', ''backend-id'':
''0'', ''state'': ''1'',
''backend'':
> ''/local/domain/0/backend/vbd/58/51713''} to 
> /local/domain/58/device/vbd/51713.
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
> {''domain'': ''dataproof'',
''frontend'':
''/local/domain/58/device/vbd/51713'',
> ''uuid'':
''24753641-db04-731b-adc1-ed1773bf956d'',
''dev'': ''xvda1'', ''state'':
> ''1'', ''params'':
''/dev/virtual/dataproof'', ''mode'':
''w'', ''online'': ''1'',
> ''frontend-id'': ''58'',
''type'': ''phy''} to
> /local/domain/0/backend/vbd/58/51713.
> [2009-01-05 13:16:32 8052] INFO (__init__:1072) createDevice: vbd : 
> {''uuid'':
''a8053c53-719a-e7a7-3389-92cd1610a1f8'',
''bootable'': 0,
> ''driver'': ''paravirtualised'',
''dev'': ''xvda2'', ''uname'':
> ''phy:/dev/virtual/dataproofswap'',
''mode'': ''w''}
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
> {''virtual-device'': ''51714'',
''device-type'': ''disk'',
''protocol'':
> ''x86_64-abi'', ''backend-id'':
''0'', ''state'': ''1'',
''backend'':
> ''/local/domain/0/backend/vbd/58/51714''} to 
> /local/domain/58/device/vbd/51714.
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
> {''domain'': ''dataproof'',
''frontend'':
''/local/domain/58/device/vbd/51714'',
> ''uuid'':
''a8053c53-719a-e7a7-3389-92cd1610a1f8'',
''dev'': ''xvda2'', ''state'':
> ''1'', ''params'':
''/dev/virtual/dataproofswap'', ''mode'':
''w'', ''online'': ''1'',
> ''frontend-id'': ''58'',
''type'': ''phy''} to
> /local/domain/0/backend/vbd/58/51714.
> [2009-01-05 13:16:32 8052] INFO (__init__:1072) createDevice: vif : 
> {''bridge'': ''xenbr0'',
''mac'': ''00:16:3e:50:c7:43'',
''uuid'':
> ''42ff0ad4-e5fb-4dc1-0436-05580093af2b''}
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
> {''mac'': ''00:16:3e:50:c7:43'',
''handle'': ''0'', ''protocol'':
''x86_64-abi'',
> ''backend-id'': ''0'',
''state'': ''1'', ''backend'':
> ''/local/domain/0/backend/vif/58/0''} to
/local/domain/58/device/vif/0.
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
> {''bridge'': ''xenbr0'',
''domain'': ''dataproof'',
''handle'': ''0'', ''uuid'':
> ''42ff0ad4-e5fb-4dc1-0436-05580093af2b'',
''script'':
> ''/etc/xen/scripts/vif-bridge'', ''mac'':
''00:16:3e:50:c7:43'',
> ''frontend-id'': ''58'',
''state'': ''1'', ''online'':
''1'', ''frontend'':
> ''/local/domain/58/device/vif/0''} to
/local/domain/0/backend/vif/58/0.
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) Storing VM details: 
> {''on_xend_stop'': ''ignore'',
''shadow_memory'': ''0'',
''uuid'':
> ''d7774355-4b1e-18d5-7177-41dc019dbe9c'',
''on_reboot'': ''restart'',
> ''start_time'': ''1231154192.25'',
''on_poweroff'': ''destroy'',
> ''on_xend_start'': ''ignore'',
''on_crash'': ''restart'',
''xend/restart_count'':
> ''0'', ''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''image'': "(linux (kernel
> /boot/vmlinux-2.6.28) (args ''root=/dev/xvda1 ro xencons=hvc0 
> console=hvc0'') (notes (HV_START_LOW 18446603336221196288)
(FEATURES
> ''!writable_page_tables|pae_pgdir_above_4gb'') (VIRT_BASE 
> 18446744071562067968) (GUEST_VERSION 2.6) (PADDR_OFFSET 0) (GUEST_OS 
> linux) (HYPERCALL_PAGE 18446744071564201984) (LOADER generic) 
> (SUSPEND_CANCEL 1) (PAE_MODE yes) (ENTRY 18446744071568527872) 
> (XEN_VERSION xen-3.0)))", ''name'':
''dataproof''}
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) Storing domain details: 
> {''console/ring-ref'': ''1934400'',
''image/entry'': ''18446744071568527872'',
> ''console/port'': ''2'',
''store/ring-ref'': ''1934401'',
''image/loader'':
> ''generic'', ''vm'':
''/vm/d7774355-4b1e-18d5-7177-41dc019dbe9c'',
> ''control/platform-feature-multiprocessor-suspend'':
''1'',
> ''image/hv-start-low'':
''18446603336221196288'', ''image/guest-os'':
''linux'',
> ''image/virt-base'':
''18446744071562067968'', ''memory/target'':
''262144'',
> ''image/guest-version'': ''2.6'',
''image/pae-mode'': ''yes'',
''console/limit'':
> ''1048576'', ''image/paddr-offset'':
''0'', ''image/hypercall-page'':
> ''18446744071564201984'',
''image/suspend-cancel'': ''1'',
> ''cpu/0/availability'': ''online'',
''image/features/pae-pgdir-above-4gb'':
> ''1'',
''image/features/writable-page-tables'': ''0'',
''console/type'':
> ''xenconsoled'', ''name'':
''dataproof'', ''domid'':
''58'', ''image/xen-version'':
> ''xen-3.0'', ''store/port'':
''1''}
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
> {''protocol'': ''x86_64-abi'',
''state'': ''1'',
''backend-id'': ''0'',
''backend'':
> ''/local/domain/0/backend/console/58/0''} to 
> /local/domain/58/device/console/0.
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) DevController: writing 
> {''domain'': ''dataproof'',
''frontend'':
''/local/domain/58/device/console/0'',
> ''uuid'':
''4ebfb3e4-79bf-27c3-0d58-acf2e0904e0f'',
''frontend-id'': ''58'',
> ''state'': ''1'',
''location'': ''2'', ''online'':
''1'', ''protocol'': ''vt100''}
to
> /local/domain/0/backend/console/58/0.
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) 
> XendDomainInfo.handleShutdownWatch
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) Waiting for devices vif.
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) Waiting for 0.
> [2009-01-05 13:16:32 8052] DEBUG (__init__:1072) hotplugStatusCallback 
> /local/domain/0/backend/vif/58/0/hotplug-status.
> [2009-01-05 13:16:33 8052] DEBUG (__init__:1072) hotplugStatusCallback 
> /local/domain/0/backend/vif/58/0/hotplug-status.
> [2009-01-05 13:16:33 8052] DEBUG (__init__:1072) hotplugStatusCallback 1.
> [2009-01-05 13:16:33 8052] DEBUG (__init__:1072) Waiting for devices vscsi.
> [2009-01-05 13:16:33 8052] DEBUG (__init__:1072) Waiting for devices vbd.
> [2009-01-05 13:16:33 8052] DEBUG (__init__:1072) Waiting for 51713.
> [2009-01-05 13:16:33 8052] DEBUG (__init__:1072) hotplugStatusCallback 
> /local/domain/0/backend/vbd/58/51713/hotplug-status.
> [2009-01-05 13:16:33 8052] DEBUG (__init__:1072) hotplugStatusCallback 1.
> [2009-01-05 13:16:33 8052] DEBUG (__init__:1072) Waiting for 51714.
> [2009-01-05 13:16:33 8052] DEBUG (__init__:1072) hotplugStatusCallback 
> /local/domain/0/backend/vbd/58/51714/hotplug-status.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) hotplugStatusCallback 
> /local/domain/0/backend/vbd/58/51714/hotplug-status.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) hotplugStatusCallback 1.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices irq.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices vkbd.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices vfb.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices 
> console.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for 0.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices pci.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices 
> ioports.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices tap.
> [2009-01-05 13:16:34 8052] DEBUG (__init__:1072) Waiting for devices vtpm.
> [2009-01-05 13:16:34 8052] INFO (__init__:1072) Domain dataproof (58) 
> unpaused.
> [2009-01-05 13:16:34 8052] WARNING (__init__:1072) Domain has crashed: 
> name=dataproof id=58.
> 
> and then it loops for a while until:
> 
> [2009-01-05 13:16:35 8052] ERROR (__init__:1072) VM dataproof restarting 
> too fast (1.637592 seconds since the last restart).  Refusing to restart 
> to avoid loops.
> 
> Any suggestions?
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Ian Campbell

2009-Jan-05 14:24 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Mon, 2009-01-05 at 14:19 +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> Im using vanilla 2.6.28 kernel from kernel.org and when I try to boot my 
>   domU with it, it just disappears without any error or warning.
Can you build a debug=y hypervisor and add earlyprintk=xen to the domU
command line?
> I have double checked that I have all the necessary options enabled on 
> my kernel config.
Can you supply the config pls.

Ian.



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

Valtteri Kiviniemi

2009-Jan-05 18:11 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

I don''t have the opportunity of rebuilding my hypervisor right now, but
here is the .config:

http://pastebin.com/m181cf183

Is there something wrong with the config or am I missing something there?

- Valtteri Kiviniemi

Ian Campbell kirjoitti:> On Mon, 2009-01-05 at 14:19 +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> Im using vanilla 2.6.28 kernel from kernel.org and when I try to boot
my
>>   domU with it, it just disappears without any error or warning.
> 
> Can you build a debug=y hypervisor and add earlyprintk=xen to the domU
> command line?
> 
>> I have double checked that I have all the necessary options enabled on 
>> my kernel config.
> 
> Can you supply the config pls.
> 
> Ian.
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

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

Ian Campbell

2009-Jan-06 09:54 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Mon, 2009-01-05 at 20:11 +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> I don''t have the opportunity of rebuilding my hypervisor right
now, but
> here is the .config:
> 
> http://pastebin.com/m181cf183
> 
> Is there something wrong with the config or am I missing something there?
No I think your config is ok, I successfully built and booted 2.6.28 as
a 64 bit domU on my test system using it. My command line was
"root=/dev/xvda1 ro 4 console=hvc0 earlyprintk=xen"

Do you get anything on the Xen console (xm dmesg) when you try to start
the guest?

> 
> - Valtteri Kiviniemi
> 
> Ian Campbell kirjoitti:
> > On Mon, 2009-01-05 at 14:19 +0200, Valtteri Kiviniemi wrote:
> >> Hi,
> >>
> >> Im using vanilla 2.6.28 kernel from kernel.org and when I try to
boot my
> >>   domU with it, it just disappears without any error or warning.
> > 
> > Can you build a debug=y hypervisor and add earlyprintk=xen to the domU
> > command line?
> > 
> >> I have double checked that I have all the necessary options
enabled on
> >> my kernel config.
> > 
> > Can you supply the config pls.
> > 
> > Ian.
> > 
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

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

Valtteri Kiviniemi

2009-Jan-06 14:37 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

No it does not print anything, just disappears immediately.

This is what I get in xm dmesg after trying to launch the domU with 2.6.28

http://pastebin.com/m6ab14265

- Valtteri Kiviniemi

Ian Campbell kirjoitti:> On Mon, 2009-01-05 at 20:11 +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> I don''t have the opportunity of rebuilding my hypervisor right
now, but
>> here is the .config:
>>
>> http://pastebin.com/m181cf183
>>
>> Is there something wrong with the config or am I missing something
there?
> 
> No I think your config is ok, I successfully built and booted 2.6.28 as
> a 64 bit domU on my test system using it. My command line was
> "root=/dev/xvda1 ro 4 console=hvc0 earlyprintk=xen"
> 
> Do you get anything on the Xen console (xm dmesg) when you try to start
> the guest?
> 
> 
>> - Valtteri Kiviniemi
>>
>> Ian Campbell kirjoitti:
>>> On Mon, 2009-01-05 at 14:19 +0200, Valtteri Kiviniemi wrote:
>>>> Hi,
>>>>
>>>> Im using vanilla 2.6.28 kernel from kernel.org and when I try
to boot my
>>>>   domU with it, it just disappears without any error or
warning.
>>> Can you build a debug=y hypervisor and add earlyprintk=xen to the
domU
>>> command line?
>>>
>>>> I have double checked that I have all the necessary options
enabled on
>>>> my kernel config.
>>> Can you supply the config pls.
>>>
>>> Ian.
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2009-Jan-06 14:50 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Mon, Jan 05, 2009 at 02:48:09PM +0200, Valtteri Kiviniemi
wrote:> Oh,
> 
> forgot to say that im using Xen 3.3.1-rc1-pre and 2.6.18.8-xen0
>
Maybe you should update to Xen 3.3.1 final and build it with debug enabled.. 
with debug enabled in xen you get the domU kernel output in xen log (when you
pass domU kernel earlyprintk=xen option).

That might help seeing what''s happening/wrong.

-- Pasi

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

Ian Campbell

2009-Jan-06 14:56 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Tue, 2009-01-06 at 16:37 +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> No it does not print anything, just disappears immediately.
> 
> This is what I get in xm dmesg after trying to launch the domU with 2.6.28
> 
> http://pastebin.com/m6ab14265
Since they aren''t huge please just paste the messages inline or attach
them rather than sending me off to some website.

Looks like a hypercall has failed and the kernel has done a BUG():

(XEN) mm.c:1482:d71 Bad L1 flags 800000
(XEN) traps.c:437:d71 Unhandled invalid opcode fault/trap [#6] on VCPU 0
[ec=0000]
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 71 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.3.1-rc1-pre  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e033:[<ffffffff8020a7aa>]
(XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
(XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 0000000000000008
(XEN) rdx: 0000000000000000   rsi: 80000001d9ddd061   rdi: ffffffff80622000
(XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 0000000000001000
(XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 00000000000026b0
(XEN) cr3: 00000001d9cef000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffffffff80599f58:
(XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa 000000010000e030
(XEN)    0000000000010082 ffffffff80599f98 000000000000e02b ffffffff8020a7a6
(XEN)    ffffffff8020c18c 0000000000000200 0000000000000008 ffffffff805c4d3f
(XEN)    ffffffff80710000 0000000000010000 0000000000000008 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000 ffffffff8068f000
(XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000 ffffffff80693000
(XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000 ffffffff80697000
(XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000 ffffffff8069b000
(XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000 ffffffff8069f000
(XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000 ffffffff806a3000
(XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000 ffffffff806a7000
(XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000 ffffffff806ab000
(XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000 ffffffff806af000
(XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000 ffffffff806b3000
(XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000 ffffffff806b7000
(XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000 ffffffff806bb000
(XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000 ffffffff806bf000
(XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000 ffffffff806c3000
(XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000 ffffffff806c7000

What does ffffffff8020a7aa correspond to in your kernel? Do any of the
other values on the stack correspond to interesting functions? I usually
pipe such stack traces into "| gdb-disas vmlinux" (attached, needs
kernel with debug info), of course it would be better to update to 3.3.1
final and build with debugging enabled to see the actual stack trace
from the domU kernel.

> - Valtteri Kiviniemi
> 
> Ian Campbell kirjoitti:
> > On Mon, 2009-01-05 at 20:11 +0200, Valtteri Kiviniemi wrote:
> >> Hi,
> >>
> >> I don''t have the opportunity of rebuilding my hypervisor
right now, but
> >> here is the .config:
> >>
> >> http://pastebin.com/m181cf183
> >>
> >> Is there something wrong with the config or am I missing something
there?
> > 
> > No I think your config is ok, I successfully built and booted 2.6.28
as
> > a 64 bit domU on my test system using it. My command line was
> > "root=/dev/xvda1 ro 4 console=hvc0 earlyprintk=xen"
> > 
> > Do you get anything on the Xen console (xm dmesg) when you try to
start
> > the guest?
> > 
> > 
> >> - Valtteri Kiviniemi
> >>
> >> Ian Campbell kirjoitti:
> >>> On Mon, 2009-01-05 at 14:19 +0200, Valtteri Kiviniemi wrote:
> >>>> Hi,
> >>>>
> >>>> Im using vanilla 2.6.28 kernel from kernel.org and when I
try to boot my
> >>>>   domU with it, it just disappears without any error or
warning.
> >>> Can you build a debug=y hypervisor and add earlyprintk=xen to
the domU
> >>> command line?
> >>>
> >>>> I have double checked that I have all the necessary
options enabled on
> >>>> my kernel config.
> >>> Can you supply the config pls.
> >>>
> >>> Ian.
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Xen-devel mailing list
> >>> Xen-devel@lists.xensource.com
> >>> http://lists.xensource.com/xen-devel
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel

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

Valtteri Kiviniemi

2009-Jan-06 14:59 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

Yeah I''ll upgrade to the newest Xen with debug enabled later, so
I''ll
will post the results then.


- Valtteri Kiviniemi

Ian Campbell kirjoitti:> On Tue, 2009-01-06 at 16:37 +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> No it does not print anything, just disappears immediately.
>>
>> This is what I get in xm dmesg after trying to launch the domU with
2.6.28
>>
>> http://pastebin.com/m6ab14265
> 
> Since they aren''t huge please just paste the messages inline or
attach
> them rather than sending me off to some website.
> 
> Looks like a hypercall has failed and the kernel has done a BUG():
> 
> (XEN) mm.c:1482:d71 Bad L1 flags 800000
> (XEN) traps.c:437:d71 Unhandled invalid opcode fault/trap [#6] on VCPU 0
[ec=0000]
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 71 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-3.3.1-rc1-pre  x86_64  debug=n  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 0000000000000008
> (XEN) rdx: 0000000000000000   rsi: 80000001d9ddd061   rdi: ffffffff80622000
> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  0000000000000000
> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 0000000000001000
> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 00000000000026b0
> (XEN) cr3: 00000001d9cef000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
> (XEN) Guest stack trace from rsp=ffffffff80599f58:
> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa
000000010000e030
> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b
ffffffff8020a7a6
> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008
ffffffff805c4d3f
> (XEN)    ffffffff80710000 0000000000010000 0000000000000008
0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000
ffffffff8068f000
> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000
ffffffff80693000
> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000
ffffffff80697000
> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000
ffffffff8069b000
> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000
ffffffff8069f000
> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000
ffffffff806a3000
> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000
ffffffff806a7000
> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000
ffffffff806ab000
> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000
ffffffff806af000
> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000
ffffffff806b3000
> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000
ffffffff806b7000
> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000
ffffffff806bb000
> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000
ffffffff806bf000
> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000
ffffffff806c3000
> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000
ffffffff806c7000
> 
> What does ffffffff8020a7aa correspond to in your kernel? Do any of the
> other values on the stack correspond to interesting functions? I usually
> pipe such stack traces into "| gdb-disas vmlinux" (attached,
needs
> kernel with debug info), of course it would be better to update to 3.3.1
> final and build with debugging enabled to see the actual stack trace
> from the domU kernel.
> 
> 
>> - Valtteri Kiviniemi
>>
>> Ian Campbell kirjoitti:
>>> On Mon, 2009-01-05 at 20:11 +0200, Valtteri Kiviniemi wrote:
>>>> Hi,
>>>>
>>>> I don''t have the opportunity of rebuilding my
hypervisor right now, but
>>>> here is the .config:
>>>>
>>>> http://pastebin.com/m181cf183
>>>>
>>>> Is there something wrong with the config or am I missing
something there?
>>> No I think your config is ok, I successfully built and booted
2.6.28 as
>>> a 64 bit domU on my test system using it. My command line was
>>> "root=/dev/xvda1 ro 4 console=hvc0 earlyprintk=xen"
>>>
>>> Do you get anything on the Xen console (xm dmesg) when you try to
start
>>> the guest?
>>>
>>>
>>>> - Valtteri Kiviniemi
>>>>
>>>> Ian Campbell kirjoitti:
>>>>> On Mon, 2009-01-05 at 14:19 +0200, Valtteri Kiviniemi
wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Im using vanilla 2.6.28 kernel from kernel.org and when
I try to boot my
>>>>>>   domU with it, it just disappears without any error or
warning.
>>>>> Can you build a debug=y hypervisor and add earlyprintk=xen
to the domU
>>>>> command line?
>>>>>
>>>>>> I have double checked that I have all the necessary
options enabled on
>>>>>> my kernel config.
>>>>> Can you supply the config pls.
>>>>>
>>>>> Ian.
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xensource.com
>>>>> http://lists.xensource.com/xen-devel
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Valtteri Kiviniemi

2009-Jan-07 13:28 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

I have now upgraded to the latest Xen with debug=y and I dont still get 
any specific error messages or how do I use the debug?

In xm dmesg I have now this:

root@xen-1:/# xm dmesg
(XEN) mm.c:1482:d5 Bad L1 flags 800000
(XEN) traps.c:437:d5 Unhandled invalid opcode fault/trap [#6] on VCPU 0 
[ec=0000]
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 5 (vcpu#0) crashed on cpu#2:
(XEN) ----[ Xen-3.3.1  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    2
(XEN) RIP:    e033:[<ffffffff8020a7aa>]
(XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
(XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 0000000000000008
(XEN) rdx: 00000000deadbeef   rsi: 00000000deadbeef   rdi: 00000000deadbeef
(XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 0000000000001000
(XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 00000000000026b0
(XEN) cr3: 000000021a1bc000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffffffff80599f58:
(XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa 000000010000e030
(XEN)    0000000000010082 ffffffff80599f98 000000000000e02b ffffffff8020a7a6
(XEN)    ffffffff8020c18c 0000000000000200 0000000000000008 ffffffff805c4d3f
(XEN)    ffffffff80710000 0000000000010000 0000000000000008 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000 ffffffff8068f000
(XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000 ffffffff80693000
(XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000 ffffffff80697000
(XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000 ffffffff8069b000
(XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000 ffffffff8069f000
(XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000 ffffffff806a3000
(XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000 ffffffff806a7000
(XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000 ffffffff806ab000
(XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000 ffffffff806af000
(XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000 ffffffff806b3000
(XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000 ffffffff806b7000
(XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000 ffffffff806bb000
(XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000 ffffffff806bf000
(XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000 ffffffff806c3000
(XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000 ffffffff806c7000
(XEN) mm.c:1482:d6 Bad L1 flags 800000
(XEN) traps.c:437:d6 Unhandled invalid opcode fault/trap [#6] on VCPU 0 
[ec=0000]
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 6 (vcpu#0) crashed on cpu#3:
(XEN) ----[ Xen-3.3.1  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    3
(XEN) RIP:    e033:[<ffffffff8020a7aa>]
(XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
(XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 0000000000000008
(XEN) rdx: 00000000deadbeef   rsi: 00000000deadbeef   rdi: 00000000deadbeef
(XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 0000000000001000
(XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 00000000000026b0
(XEN) cr3: 0000000219dbc000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffffffff80599f58:
(XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa 000000010000e030
(XEN)    0000000000010082 ffffffff80599f98 000000000000e02b ffffffff8020a7a6
(XEN)    ffffffff8020c18c 0000000000000200 0000000000000008 ffffffff805c4d3f
(XEN)    ffffffff80710000 0000000000010000 0000000000000008 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000 ffffffff8068f000
(XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000 ffffffff80693000
(XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000 ffffffff80697000
(XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000 ffffffff8069b000
(XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000 ffffffff8069f000
(XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000 ffffffff806a3000
(XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000 ffffffff806a7000
(XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000 ffffffff806ab000
(XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000 ffffffff806af000
(XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000 ffffffff806b3000
(XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000 ffffffff806b7000
(XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000 ffffffff806bb000
(XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000 ffffffff806bf000
(XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000 ffffffff806c3000
(XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000 ffffffff806c7000


- Valtteri Kiviniemi

Valtteri Kiviniemi kirjoitti:> Hi,
> 
> Yeah I''ll upgrade to the newest Xen with debug enabled later, so
I''ll
> will post the results then.
> 
> 
> - Valtteri Kiviniemi
> 
> Ian Campbell kirjoitti:
>> On Tue, 2009-01-06 at 16:37 +0200, Valtteri Kiviniemi wrote:
>>> Hi,
>>>
>>> No it does not print anything, just disappears immediately.
>>>
>>> This is what I get in xm dmesg after trying to launch the domU with
>>> 2.6.28
>>>
>>> http://pastebin.com/m6ab14265
>>
>> Since they aren''t huge please just paste the messages inline
or attach
>> them rather than sending me off to some website.
>>
>> Looks like a hypercall has failed and the kernel has done a BUG():
>>
>> (XEN) mm.c:1482:d71 Bad L1 flags 800000
>> (XEN) traps.c:437:d71 Unhandled invalid opcode fault/trap [#6] on VCPU 
>> 0 [ec=0000]
>> (XEN) domain_crash_sync called from entry.S
>> (XEN) Domain 71 (vcpu#0) crashed on cpu#0:
>> (XEN) ----[ Xen-3.3.1-rc1-pre  x86_64  debug=n  Not tainted ]----
>> (XEN) CPU:    0
>> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
>> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
>> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 
>> 0000000000000008
>> (XEN) rdx: 0000000000000000   rsi: 80000001d9ddd061   rdi: 
>> ffffffff80622000
>> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  
>> 0000000000000000
>> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 
>> 0000000000000000
>> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 
>> 0000000000001000
>> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 
>> 00000000000026b0
>> (XEN) cr3: 00000001d9cef000   cr2: 0000000000000000
>> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
>> (XEN) Guest stack trace from rsp=ffffffff80599f58:
>> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa 
>> 000000010000e030
>> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b 
>> ffffffff8020a7a6
>> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008 
>> ffffffff805c4d3f
>> (XEN)    ffffffff80710000 0000000000010000 0000000000000008 
>> 0000000000000000
>> (XEN)    0000000000000000 0000000000000000 0000000000000000 
>> 0000000000000000
>> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000 
>> ffffffff8068f000
>> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000 
>> ffffffff80693000
>> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000 
>> ffffffff80697000
>> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000 
>> ffffffff8069b000
>> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000 
>> ffffffff8069f000
>> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000 
>> ffffffff806a3000
>> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000 
>> ffffffff806a7000
>> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000 
>> ffffffff806ab000
>> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000 
>> ffffffff806af000
>> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000 
>> ffffffff806b3000
>> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000 
>> ffffffff806b7000
>> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000 
>> ffffffff806bb000
>> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000 
>> ffffffff806bf000
>> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000 
>> ffffffff806c3000
>> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000 
>> ffffffff806c7000
>>
>> What does ffffffff8020a7aa correspond to in your kernel? Do any of the
>> other values on the stack correspond to interesting functions? I
usually
>> pipe such stack traces into "| gdb-disas vmlinux" (attached,
needs
>> kernel with debug info), of course it would be better to update to
3.3.1
>> final and build with debugging enabled to see the actual stack trace
>> from the domU kernel.
>>
>>
>>> - Valtteri Kiviniemi
>>>
>>> Ian Campbell kirjoitti:
>>>> On Mon, 2009-01-05 at 20:11 +0200, Valtteri Kiviniemi wrote:
>>>>> Hi,
>>>>>
>>>>> I don''t have the opportunity of rebuilding my
hypervisor right now,
>>>>> but
>>>>> here is the .config:
>>>>>
>>>>> http://pastebin.com/m181cf183
>>>>>
>>>>> Is there something wrong with the config or am I missing
something
>>>>> there?
>>>> No I think your config is ok, I successfully built and booted
2.6.28 as
>>>> a 64 bit domU on my test system using it. My command line was
>>>> "root=/dev/xvda1 ro 4 console=hvc0 earlyprintk=xen"
>>>>
>>>> Do you get anything on the Xen console (xm dmesg) when you try
to start
>>>> the guest?
>>>>
>>>>
>>>>> - Valtteri Kiviniemi
>>>>>
>>>>> Ian Campbell kirjoitti:
>>>>>> On Mon, 2009-01-05 at 14:19 +0200, Valtteri Kiviniemi
wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Im using vanilla 2.6.28 kernel from kernel.org and
when I try to
>>>>>>> boot my   domU with it, it just disappears without
any error or
>>>>>>> warning.
>>>>>> Can you build a debug=y hypervisor and add
earlyprintk=xen to the
>>>>>> domU
>>>>>> command line?
>>>>>>
>>>>>>> I have double checked that I have all the necessary
options
>>>>>>> enabled on my kernel config.
>>>>>> Can you supply the config pls.
>>>>>>
>>>>>> Ian.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Xen-devel mailing list
>>>>>> Xen-devel@lists.xensource.com
>>>>>> http://lists.xensource.com/xen-devel
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xensource.com
>>>>> http://lists.xensource.com/xen-devel
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Ian Campbell

2009-Jan-07 13:33 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Wed, 2009-01-07 at 15:28 +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> I have now upgraded to the latest Xen with debug=y and I dont still get 
> any specific error messages or how do I use the debug?
Looks like it is crashing really very early before even earlyprintk. I
guess you need to decode the RIP and any likely looking return addresses
on the stack manually as I described in a previous mail.

Ian.> 
> In xm dmesg I have now this:
> 
> root@xen-1:/# xm dmesg
> (XEN) mm.c:1482:d5 Bad L1 flags 800000
> (XEN) traps.c:437:d5 Unhandled invalid opcode fault/trap [#6] on VCPU 0 
> [ec=0000]
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 5 (vcpu#0) crashed on cpu#2:
> (XEN) ----[ Xen-3.3.1  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    2
> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 0000000000000008
> (XEN) rdx: 00000000deadbeef   rsi: 00000000deadbeef   rdi: 00000000deadbeef
> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  0000000000000000
> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 0000000000001000
> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 00000000000026b0
> (XEN) cr3: 000000021a1bc000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
> (XEN) Guest stack trace from rsp=ffffffff80599f58:
> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa
000000010000e030
> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b
ffffffff8020a7a6
> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008
ffffffff805c4d3f
> (XEN)    ffffffff80710000 0000000000010000 0000000000000008
0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000
ffffffff8068f000
> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000
ffffffff80693000
> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000
ffffffff80697000
> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000
ffffffff8069b000
> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000
ffffffff8069f000
> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000
ffffffff806a3000
> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000
ffffffff806a7000
> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000
ffffffff806ab000
> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000
ffffffff806af000
> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000
ffffffff806b3000
> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000
ffffffff806b7000
> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000
ffffffff806bb000
> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000
ffffffff806bf000
> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000
ffffffff806c3000
> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000
ffffffff806c7000
> (XEN) mm.c:1482:d6 Bad L1 flags 800000
> (XEN) traps.c:437:d6 Unhandled invalid opcode fault/trap [#6] on VCPU 0 
> [ec=0000]
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 6 (vcpu#0) crashed on cpu#3:
> (XEN) ----[ Xen-3.3.1  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    3
> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 0000000000000008
> (XEN) rdx: 00000000deadbeef   rsi: 00000000deadbeef   rdi: 00000000deadbeef
> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  0000000000000000
> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 0000000000001000
> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 00000000000026b0
> (XEN) cr3: 0000000219dbc000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
> (XEN) Guest stack trace from rsp=ffffffff80599f58:
> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa
000000010000e030
> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b
ffffffff8020a7a6
> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008
ffffffff805c4d3f
> (XEN)    ffffffff80710000 0000000000010000 0000000000000008
0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000
ffffffff8068f000
> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000
ffffffff80693000
> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000
ffffffff80697000
> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000
ffffffff8069b000
> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000
ffffffff8069f000
> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000
ffffffff806a3000
> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000
ffffffff806a7000
> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000
ffffffff806ab000
> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000
ffffffff806af000
> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000
ffffffff806b3000
> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000
ffffffff806b7000
> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000
ffffffff806bb000
> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000
ffffffff806bf000
> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000
ffffffff806c3000
> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000
ffffffff806c7000
> 
> 
> - Valtteri Kiviniemi
> 
> Valtteri Kiviniemi kirjoitti:
> > Hi,
> > 
> > Yeah I''ll upgrade to the newest Xen with debug enabled later,
so I''ll
> > will post the results then.
> > 
> > 
> > - Valtteri Kiviniemi
> > 
> > Ian Campbell kirjoitti:
> >> On Tue, 2009-01-06 at 16:37 +0200, Valtteri Kiviniemi wrote:
> >>> Hi,
> >>>
> >>> No it does not print anything, just disappears immediately.
> >>>
> >>> This is what I get in xm dmesg after trying to launch the domU
with
> >>> 2.6.28
> >>>
> >>> http://pastebin.com/m6ab14265
> >>
> >> Since they aren''t huge please just paste the messages
inline or attach
> >> them rather than sending me off to some website.
> >>
> >> Looks like a hypercall has failed and the kernel has done a BUG():
> >>
> >> (XEN) mm.c:1482:d71 Bad L1 flags 800000
> >> (XEN) traps.c:437:d71 Unhandled invalid opcode fault/trap [#6] on
VCPU
> >> 0 [ec=0000]
> >> (XEN) domain_crash_sync called from entry.S
> >> (XEN) Domain 71 (vcpu#0) crashed on cpu#0:
> >> (XEN) ----[ Xen-3.3.1-rc1-pre  x86_64  debug=n  Not tainted ]----
> >> (XEN) CPU:    0
> >> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
> >> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
> >> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 
> >> 0000000000000008
> >> (XEN) rdx: 0000000000000000   rsi: 80000001d9ddd061   rdi: 
> >> ffffffff80622000
> >> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  
> >> 0000000000000000
> >> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 
> >> 0000000000000000
> >> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 
> >> 0000000000001000
> >> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 
> >> 00000000000026b0
> >> (XEN) cr3: 00000001d9cef000   cr2: 0000000000000000
> >> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs:
e033
> >> (XEN) Guest stack trace from rsp=ffffffff80599f58:
> >> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa 
> >> 000000010000e030
> >> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b 
> >> ffffffff8020a7a6
> >> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008 
> >> ffffffff805c4d3f
> >> (XEN)    ffffffff80710000 0000000000010000 0000000000000008 
> >> 0000000000000000
> >> (XEN)    0000000000000000 0000000000000000 0000000000000000 
> >> 0000000000000000
> >> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000 
> >> ffffffff8068f000
> >> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000 
> >> ffffffff80693000
> >> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000 
> >> ffffffff80697000
> >> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000 
> >> ffffffff8069b000
> >> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000 
> >> ffffffff8069f000
> >> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000 
> >> ffffffff806a3000
> >> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000 
> >> ffffffff806a7000
> >> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000 
> >> ffffffff806ab000
> >> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000 
> >> ffffffff806af000
> >> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000 
> >> ffffffff806b3000
> >> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000 
> >> ffffffff806b7000
> >> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000 
> >> ffffffff806bb000
> >> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000 
> >> ffffffff806bf000
> >> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000 
> >> ffffffff806c3000
> >> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000 
> >> ffffffff806c7000
> >>
> >> What does ffffffff8020a7aa correspond to in your kernel? Do any of
the
> >> other values on the stack correspond to interesting functions? I
usually
> >> pipe such stack traces into "| gdb-disas vmlinux"
(attached, needs
> >> kernel with debug info), of course it would be better to update to
3.3.1
> >> final and build with debugging enabled to see the actual stack
trace
> >> from the domU kernel.
> >>
> >>
> >>> - Valtteri Kiviniemi
> >>>
> >>> Ian Campbell kirjoitti:
> >>>> On Mon, 2009-01-05 at 20:11 +0200, Valtteri Kiviniemi
wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I don''t have the opportunity of rebuilding my
hypervisor right now,
> >>>>> but
> >>>>> here is the .config:
> >>>>>
> >>>>> http://pastebin.com/m181cf183
> >>>>>
> >>>>> Is there something wrong with the config or am I
missing something
> >>>>> there?
> >>>> No I think your config is ok, I successfully built and
booted 2.6.28 as
> >>>> a 64 bit domU on my test system using it. My command line
was
> >>>> "root=/dev/xvda1 ro 4 console=hvc0
earlyprintk=xen"
> >>>>
> >>>> Do you get anything on the Xen console (xm dmesg) when you
try to start
> >>>> the guest?
> >>>>
> >>>>
> >>>>> - Valtteri Kiviniemi
> >>>>>
> >>>>> Ian Campbell kirjoitti:
> >>>>>> On Mon, 2009-01-05 at 14:19 +0200, Valtteri
Kiviniemi wrote:
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> Im using vanilla 2.6.28 kernel from kernel.org
and when I try to
> >>>>>>> boot my   domU with it, it just disappears
without any error or
> >>>>>>> warning.
> >>>>>> Can you build a debug=y hypervisor and add
earlyprintk=xen to the
> >>>>>> domU
> >>>>>> command line?
> >>>>>>
> >>>>>>> I have double checked that I have all the
necessary options
> >>>>>>> enabled on my kernel config.
> >>>>>> Can you supply the config pls.
> >>>>>>
> >>>>>> Ian.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Xen-devel mailing list
> >>>>>> Xen-devel@lists.xensource.com
> >>>>>> http://lists.xensource.com/xen-devel
> >>>>> _______________________________________________
> >>>>> Xen-devel mailing list
> >>>>> Xen-devel@lists.xensource.com
> >>>>> http://lists.xensource.com/xen-devel
> >>>>
> >>>> _______________________________________________
> >>>> Xen-devel mailing list
> >>>> Xen-devel@lists.xensource.com
> >>>> http://lists.xensource.com/xen-devel
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel

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

Valtteri Kiviniemi

2009-Jan-07 13:39 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

Nice, I dont think that i have the necessary skillz for that :) but thnx 
anyway

- Valtteri Kiviniemi

Ian Campbell kirjoitti:> On Wed, 2009-01-07 at 15:28 +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> I have now upgraded to the latest Xen with debug=y and I dont still get
>> any specific error messages or how do I use the debug?
> 
> Looks like it is crashing really very early before even earlyprintk. I
> guess you need to decode the RIP and any likely looking return addresses
> on the stack manually as I described in a previous mail.
> 
> Ian.
>> In xm dmesg I have now this:
>>
>> root@xen-1:/# xm dmesg
>> (XEN) mm.c:1482:d5 Bad L1 flags 800000
>> (XEN) traps.c:437:d5 Unhandled invalid opcode fault/trap [#6] on VCPU 0
>> [ec=0000]
>> (XEN) domain_crash_sync called from entry.S
>> (XEN) Domain 5 (vcpu#0) crashed on cpu#2:
>> (XEN) ----[ Xen-3.3.1  x86_64  debug=y  Not tainted ]----
>> (XEN) CPU:    2
>> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
>> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
>> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx:
0000000000000008
>> (XEN) rdx: 00000000deadbeef   rsi: 00000000deadbeef   rdi:
00000000deadbeef
>> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8: 
0000000000000000
>> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11:
0000000000000000
>> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14:
0000000000001000
>> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4:
00000000000026b0
>> (XEN) cr3: 000000021a1bc000   cr2: 0000000000000000
>> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
>> (XEN) Guest stack trace from rsp=ffffffff80599f58:
>> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa
000000010000e030
>> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b
ffffffff8020a7a6
>> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008
ffffffff805c4d3f
>> (XEN)    ffffffff80710000 0000000000010000 0000000000000008
0000000000000000
>> (XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
>> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000
ffffffff8068f000
>> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000
ffffffff80693000
>> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000
ffffffff80697000
>> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000
ffffffff8069b000
>> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000
ffffffff8069f000
>> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000
ffffffff806a3000
>> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000
ffffffff806a7000
>> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000
ffffffff806ab000
>> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000
ffffffff806af000
>> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000
ffffffff806b3000
>> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000
ffffffff806b7000
>> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000
ffffffff806bb000
>> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000
ffffffff806bf000
>> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000
ffffffff806c3000
>> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000
ffffffff806c7000
>> (XEN) mm.c:1482:d6 Bad L1 flags 800000
>> (XEN) traps.c:437:d6 Unhandled invalid opcode fault/trap [#6] on VCPU 0
>> [ec=0000]
>> (XEN) domain_crash_sync called from entry.S
>> (XEN) Domain 6 (vcpu#0) crashed on cpu#3:
>> (XEN) ----[ Xen-3.3.1  x86_64  debug=y  Not tainted ]----
>> (XEN) CPU:    3
>> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
>> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
>> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx:
0000000000000008
>> (XEN) rdx: 00000000deadbeef   rsi: 00000000deadbeef   rdi:
00000000deadbeef
>> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8: 
0000000000000000
>> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11:
0000000000000000
>> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14:
0000000000001000
>> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4:
00000000000026b0
>> (XEN) cr3: 0000000219dbc000   cr2: 0000000000000000
>> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
>> (XEN) Guest stack trace from rsp=ffffffff80599f58:
>> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa
000000010000e030
>> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b
ffffffff8020a7a6
>> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008
ffffffff805c4d3f
>> (XEN)    ffffffff80710000 0000000000010000 0000000000000008
0000000000000000
>> (XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
>> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000
ffffffff8068f000
>> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000
ffffffff80693000
>> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000
ffffffff80697000
>> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000
ffffffff8069b000
>> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000
ffffffff8069f000
>> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000
ffffffff806a3000
>> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000
ffffffff806a7000
>> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000
ffffffff806ab000
>> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000
ffffffff806af000
>> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000
ffffffff806b3000
>> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000
ffffffff806b7000
>> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000
ffffffff806bb000
>> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000
ffffffff806bf000
>> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000
ffffffff806c3000
>> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000
ffffffff806c7000
>>
>>
>> - Valtteri Kiviniemi
>>
>> Valtteri Kiviniemi kirjoitti:
>>> Hi,
>>>
>>> Yeah I''ll upgrade to the newest Xen with debug enabled
later, so I''ll
>>> will post the results then.
>>>
>>>
>>> - Valtteri Kiviniemi
>>>
>>> Ian Campbell kirjoitti:
>>>> On Tue, 2009-01-06 at 16:37 +0200, Valtteri Kiviniemi wrote:
>>>>> Hi,
>>>>>
>>>>> No it does not print anything, just disappears immediately.
>>>>>
>>>>> This is what I get in xm dmesg after trying to launch the
domU with
>>>>> 2.6.28
>>>>>
>>>>> http://pastebin.com/m6ab14265
>>>> Since they aren''t huge please just paste the messages
inline or attach
>>>> them rather than sending me off to some website.
>>>>
>>>> Looks like a hypercall has failed and the kernel has done a
BUG():
>>>>
>>>> (XEN) mm.c:1482:d71 Bad L1 flags 800000
>>>> (XEN) traps.c:437:d71 Unhandled invalid opcode fault/trap [#6]
on VCPU
>>>> 0 [ec=0000]
>>>> (XEN) domain_crash_sync called from entry.S
>>>> (XEN) Domain 71 (vcpu#0) crashed on cpu#0:
>>>> (XEN) ----[ Xen-3.3.1-rc1-pre  x86_64  debug=n  Not tainted
]----
>>>> (XEN) CPU:    0
>>>> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
>>>> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
>>>> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 
>>>> 0000000000000008
>>>> (XEN) rdx: 0000000000000000   rsi: 80000001d9ddd061   rdi: 
>>>> ffffffff80622000
>>>> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  
>>>> 0000000000000000
>>>> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 
>>>> 0000000000000000
>>>> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 
>>>> 0000000000001000
>>>> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 
>>>> 00000000000026b0
>>>> (XEN) cr3: 00000001d9cef000   cr2: 0000000000000000
>>>> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b  
cs: e033
>>>> (XEN) Guest stack trace from rsp=ffffffff80599f58:
>>>> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa 
>>>> 000000010000e030
>>>> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b 
>>>> ffffffff8020a7a6
>>>> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008 
>>>> ffffffff805c4d3f
>>>> (XEN)    ffffffff80710000 0000000000010000 0000000000000008 
>>>> 0000000000000000
>>>> (XEN)    0000000000000000 0000000000000000 0000000000000000 
>>>> 0000000000000000
>>>> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000 
>>>> ffffffff8068f000
>>>> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000 
>>>> ffffffff80693000
>>>> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000 
>>>> ffffffff80697000
>>>> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000 
>>>> ffffffff8069b000
>>>> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000 
>>>> ffffffff8069f000
>>>> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000 
>>>> ffffffff806a3000
>>>> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000 
>>>> ffffffff806a7000
>>>> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000 
>>>> ffffffff806ab000
>>>> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000 
>>>> ffffffff806af000
>>>> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000 
>>>> ffffffff806b3000
>>>> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000 
>>>> ffffffff806b7000
>>>> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000 
>>>> ffffffff806bb000
>>>> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000 
>>>> ffffffff806bf000
>>>> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000 
>>>> ffffffff806c3000
>>>> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000 
>>>> ffffffff806c7000
>>>>
>>>> What does ffffffff8020a7aa correspond to in your kernel? Do any
of the
>>>> other values on the stack correspond to interesting functions?
I usually
>>>> pipe such stack traces into "| gdb-disas vmlinux"
(attached, needs
>>>> kernel with debug info), of course it would be better to update
to 3.3.1
>>>> final and build with debugging enabled to see the actual stack
trace
>>>> from the domU kernel.
>>>>
>>>>
>>>>> - Valtteri Kiviniemi
>>>>>
>>>>> Ian Campbell kirjoitti:
>>>>>> On Mon, 2009-01-05 at 20:11 +0200, Valtteri Kiviniemi
wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I don''t have the opportunity of rebuilding
my hypervisor right now,
>>>>>>> but
>>>>>>> here is the .config:
>>>>>>>
>>>>>>> http://pastebin.com/m181cf183
>>>>>>>
>>>>>>> Is there something wrong with the config or am I
missing something
>>>>>>> there?
>>>>>> No I think your config is ok, I successfully built and
booted 2.6.28 as
>>>>>> a 64 bit domU on my test system using it. My command
line was
>>>>>> "root=/dev/xvda1 ro 4 console=hvc0
earlyprintk=xen"
>>>>>>
>>>>>> Do you get anything on the Xen console (xm dmesg) when
you try to start
>>>>>> the guest?
>>>>>>
>>>>>>
>>>>>>> - Valtteri Kiviniemi
>>>>>>>
>>>>>>> Ian Campbell kirjoitti:
>>>>>>>> On Mon, 2009-01-05 at 14:19 +0200, Valtteri
Kiviniemi wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> Im using vanilla 2.6.28 kernel from
kernel.org and when I try to
>>>>>>>>> boot my   domU with it, it just disappears
without any error or
>>>>>>>>> warning.
>>>>>>>> Can you build a debug=y hypervisor and add
earlyprintk=xen to the
>>>>>>>> domU
>>>>>>>> command line?
>>>>>>>>
>>>>>>>>> I have double checked that I have all the
necessary options
>>>>>>>>> enabled on my kernel config.
>>>>>>>> Can you supply the config pls.
>>>>>>>>
>>>>>>>> Ian.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Xen-devel mailing list
>>>>>>>> Xen-devel@lists.xensource.com
>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>> _______________________________________________
>>>>>>> Xen-devel mailing list
>>>>>>> Xen-devel@lists.xensource.com
>>>>>>> http://lists.xensource.com/xen-devel
>>>>>> _______________________________________________
>>>>>> Xen-devel mailing list
>>>>>> Xen-devel@lists.xensource.com
>>>>>> http://lists.xensource.com/xen-devel
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Valtteri Kiviniemi

2009-Jan-07 14:25 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

This is indeed a very strange problem. I just disabled _everything_ in 
the kernel menuconfig. No drivers, no filesystems, no nothing. I even 
disabled all in processor types and features.

Still the same error message. So it''s probably a bug or something 
because its not just working no matter what options are enabled/disabled 
in kernel.

- Valtteri Kiviniemi

Valtteri Kiviniemi kirjoitti:> Hi,
> 
> Nice, I dont think that i have the necessary skillz for that :) but thnx 
> anyway
> 
> - Valtteri Kiviniemi
> 
> Ian Campbell kirjoitti:
>> On Wed, 2009-01-07 at 15:28 +0200, Valtteri Kiviniemi wrote:
>>> Hi,
>>>
>>> I have now upgraded to the latest Xen with debug=y and I dont still
>>> get any specific error messages or how do I use the debug?
>>
>> Looks like it is crashing really very early before even earlyprintk. I
>> guess you need to decode the RIP and any likely looking return
addresses
>> on the stack manually as I described in a previous mail.
>>
>> Ian.
>>> In xm dmesg I have now this:
>>>
>>> root@xen-1:/# xm dmesg
>>> (XEN) mm.c:1482:d5 Bad L1 flags 800000
>>> (XEN) traps.c:437:d5 Unhandled invalid opcode fault/trap [#6] on
VCPU
>>> 0 [ec=0000]
>>> (XEN) domain_crash_sync called from entry.S
>>> (XEN) Domain 5 (vcpu#0) crashed on cpu#2:
>>> (XEN) ----[ Xen-3.3.1  x86_64  debug=y  Not tainted ]----
>>> (XEN) CPU:    2
>>> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
>>> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
>>> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 
>>> 0000000000000008
>>> (XEN) rdx: 00000000deadbeef   rsi: 00000000deadbeef   rdi: 
>>> 00000000deadbeef
>>> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  
>>> 0000000000000000
>>> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 
>>> 0000000000000000
>>> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 
>>> 0000000000001000
>>> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 
>>> 00000000000026b0
>>> (XEN) cr3: 000000021a1bc000   cr2: 0000000000000000
>>> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs:
e033
>>> (XEN) Guest stack trace from rsp=ffffffff80599f58:
>>> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa 
>>> 000000010000e030
>>> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b 
>>> ffffffff8020a7a6
>>> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008 
>>> ffffffff805c4d3f
>>> (XEN)    ffffffff80710000 0000000000010000 0000000000000008 
>>> 0000000000000000
>>> (XEN)    0000000000000000 0000000000000000 0000000000000000 
>>> 0000000000000000
>>> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000 
>>> ffffffff8068f000
>>> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000 
>>> ffffffff80693000
>>> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000 
>>> ffffffff80697000
>>> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000 
>>> ffffffff8069b000
>>> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000 
>>> ffffffff8069f000
>>> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000 
>>> ffffffff806a3000
>>> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000 
>>> ffffffff806a7000
>>> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000 
>>> ffffffff806ab000
>>> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000 
>>> ffffffff806af000
>>> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000 
>>> ffffffff806b3000
>>> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000 
>>> ffffffff806b7000
>>> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000 
>>> ffffffff806bb000
>>> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000 
>>> ffffffff806bf000
>>> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000 
>>> ffffffff806c3000
>>> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000 
>>> ffffffff806c7000
>>> (XEN) mm.c:1482:d6 Bad L1 flags 800000
>>> (XEN) traps.c:437:d6 Unhandled invalid opcode fault/trap [#6] on
VCPU
>>> 0 [ec=0000]
>>> (XEN) domain_crash_sync called from entry.S
>>> (XEN) Domain 6 (vcpu#0) crashed on cpu#3:
>>> (XEN) ----[ Xen-3.3.1  x86_64  debug=y  Not tainted ]----
>>> (XEN) CPU:    3
>>> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
>>> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
>>> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 
>>> 0000000000000008
>>> (XEN) rdx: 00000000deadbeef   rsi: 00000000deadbeef   rdi: 
>>> 00000000deadbeef
>>> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  
>>> 0000000000000000
>>> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 
>>> 0000000000000000
>>> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 
>>> 0000000000001000
>>> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 
>>> 00000000000026b0
>>> (XEN) cr3: 0000000219dbc000   cr2: 0000000000000000
>>> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs:
e033
>>> (XEN) Guest stack trace from rsp=ffffffff80599f58:
>>> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa 
>>> 000000010000e030
>>> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b 
>>> ffffffff8020a7a6
>>> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008 
>>> ffffffff805c4d3f
>>> (XEN)    ffffffff80710000 0000000000010000 0000000000000008 
>>> 0000000000000000
>>> (XEN)    0000000000000000 0000000000000000 0000000000000000 
>>> 0000000000000000
>>> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000 
>>> ffffffff8068f000
>>> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000 
>>> ffffffff80693000
>>> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000 
>>> ffffffff80697000
>>> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000 
>>> ffffffff8069b000
>>> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000 
>>> ffffffff8069f000
>>> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000 
>>> ffffffff806a3000
>>> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000 
>>> ffffffff806a7000
>>> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000 
>>> ffffffff806ab000
>>> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000 
>>> ffffffff806af000
>>> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000 
>>> ffffffff806b3000
>>> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000 
>>> ffffffff806b7000
>>> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000 
>>> ffffffff806bb000
>>> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000 
>>> ffffffff806bf000
>>> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000 
>>> ffffffff806c3000
>>> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000 
>>> ffffffff806c7000
>>>
>>>
>>> - Valtteri Kiviniemi
>>>
>>> Valtteri Kiviniemi kirjoitti:
>>>> Hi,
>>>>
>>>> Yeah I''ll upgrade to the newest Xen with debug enabled
later, so
>>>> I''ll will post the results then.
>>>>
>>>>
>>>> - Valtteri Kiviniemi
>>>>
>>>> Ian Campbell kirjoitti:
>>>>> On Tue, 2009-01-06 at 16:37 +0200, Valtteri Kiviniemi
wrote:
>>>>>> Hi,
>>>>>>
>>>>>> No it does not print anything, just disappears
immediately.
>>>>>>
>>>>>> This is what I get in xm dmesg after trying to launch
the domU
>>>>>> with 2.6.28
>>>>>>
>>>>>> http://pastebin.com/m6ab14265
>>>>> Since they aren''t huge please just paste the
messages inline or attach
>>>>> them rather than sending me off to some website.
>>>>>
>>>>> Looks like a hypercall has failed and the kernel has done a
BUG():
>>>>>
>>>>> (XEN) mm.c:1482:d71 Bad L1 flags 800000
>>>>> (XEN) traps.c:437:d71 Unhandled invalid opcode fault/trap
[#6] on
>>>>> VCPU 0 [ec=0000]
>>>>> (XEN) domain_crash_sync called from entry.S
>>>>> (XEN) Domain 71 (vcpu#0) crashed on cpu#0:
>>>>> (XEN) ----[ Xen-3.3.1-rc1-pre  x86_64  debug=n  Not tainted
]----
>>>>> (XEN) CPU:    0
>>>>> (XEN) RIP:    e033:[<ffffffff8020a7aa>]
>>>>> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
>>>>> (XEN) rax: 00000000ffffffea   rbx: 8000000000000161   rcx: 
>>>>> 0000000000000008
>>>>> (XEN) rdx: 0000000000000000   rsi: 80000001d9ddd061   rdi: 
>>>>> ffffffff80622000
>>>>> (XEN) rbp: 0000000001000000   rsp: ffffffff80599f58   r8:  
>>>>> 0000000000000000
>>>>> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 
>>>>> 0000000000000000
>>>>> (XEN) r12: ffffffff80622000   r13: 0000000000000200   r14: 
>>>>> 0000000000001000
>>>>> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 
>>>>> 00000000000026b0
>>>>> (XEN) cr3: 00000001d9cef000   cr2: 0000000000000000
>>>>> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b 
cs: e033
>>>>> (XEN) Guest stack trace from rsp=ffffffff80599f58:
>>>>> (XEN)    0000000000000008 0000000000000000 ffffffff8020a7aa
>>>>> 000000010000e030
>>>>> (XEN)    0000000000010082 ffffffff80599f98 000000000000e02b
>>>>> ffffffff8020a7a6
>>>>> (XEN)    ffffffff8020c18c 0000000000000200 0000000000000008
>>>>> ffffffff805c4d3f
>>>>> (XEN)    ffffffff80710000 0000000000010000 0000000000000008
>>>>> 0000000000000000
>>>>> (XEN)    0000000000000000 0000000000000000 0000000000000000
>>>>> 0000000000000000
>>>>> (XEN)    0000000000000000 ffffffff8068d000 ffffffff8068e000
>>>>> ffffffff8068f000
>>>>> (XEN)    ffffffff80690000 ffffffff80691000 ffffffff80692000
>>>>> ffffffff80693000
>>>>> (XEN)    ffffffff80694000 ffffffff80695000 ffffffff80696000
>>>>> ffffffff80697000
>>>>> (XEN)    ffffffff80698000 ffffffff80699000 ffffffff8069a000
>>>>> ffffffff8069b000
>>>>> (XEN)    ffffffff8069c000 ffffffff8069d000 ffffffff8069e000
>>>>> ffffffff8069f000
>>>>> (XEN)    ffffffff806a0000 ffffffff806a1000 ffffffff806a2000
>>>>> ffffffff806a3000
>>>>> (XEN)    ffffffff806a4000 ffffffff806a5000 ffffffff806a6000
>>>>> ffffffff806a7000
>>>>> (XEN)    ffffffff806a8000 ffffffff806a9000 ffffffff806aa000
>>>>> ffffffff806ab000
>>>>> (XEN)    ffffffff806ac000 ffffffff806ad000 ffffffff806ae000
>>>>> ffffffff806af000
>>>>> (XEN)    ffffffff806b0000 ffffffff806b1000 ffffffff806b2000
>>>>> ffffffff806b3000
>>>>> (XEN)    ffffffff806b4000 ffffffff806b5000 ffffffff806b6000
>>>>> ffffffff806b7000
>>>>> (XEN)    ffffffff806b8000 ffffffff806b9000 ffffffff806ba000
>>>>> ffffffff806bb000
>>>>> (XEN)    ffffffff806bc000 ffffffff806bd000 ffffffff806be000
>>>>> ffffffff806bf000
>>>>> (XEN)    ffffffff806c0000 ffffffff806c1000 ffffffff806c2000
>>>>> ffffffff806c3000
>>>>> (XEN)    ffffffff806c4000 ffffffff806c5000 ffffffff806c6000
>>>>> ffffffff806c7000
>>>>>
>>>>> What does ffffffff8020a7aa correspond to in your kernel? Do
any of the
>>>>> other values on the stack correspond to interesting
functions? I
>>>>> usually
>>>>> pipe such stack traces into "| gdb-disas vmlinux"
(attached, needs
>>>>> kernel with debug info), of course it would be better to
update to
>>>>> 3.3.1
>>>>> final and build with debugging enabled to see the actual
stack trace
>>>>> from the domU kernel.
>>>>>
>>>>>
>>>>>> - Valtteri Kiviniemi
>>>>>>
>>>>>> Ian Campbell kirjoitti:
>>>>>>> On Mon, 2009-01-05 at 20:11 +0200, Valtteri
Kiviniemi wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I don''t have the opportunity of
rebuilding my hypervisor right
>>>>>>>> now, but
>>>>>>>> here is the .config:
>>>>>>>>
>>>>>>>> http://pastebin.com/m181cf183
>>>>>>>>
>>>>>>>> Is there something wrong with the config or am
I missing
>>>>>>>> something there?
>>>>>>> No I think your config is ok, I successfully built
and booted
>>>>>>> 2.6.28 as
>>>>>>> a 64 bit domU on my test system using it. My
command line was
>>>>>>> "root=/dev/xvda1 ro 4 console=hvc0
earlyprintk=xen"
>>>>>>>
>>>>>>> Do you get anything on the Xen console (xm dmesg)
when you try to
>>>>>>> start
>>>>>>> the guest?
>>>>>>>
>>>>>>>
>>>>>>>> - Valtteri Kiviniemi
>>>>>>>>
>>>>>>>> Ian Campbell kirjoitti:
>>>>>>>>> On Mon, 2009-01-05 at 14:19 +0200, Valtteri
Kiviniemi wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> Im using vanilla 2.6.28 kernel from
kernel.org and when I try
>>>>>>>>>> to boot my   domU with it, it just
disappears without any
>>>>>>>>>> error or warning.
>>>>>>>>> Can you build a debug=y hypervisor and add
earlyprintk=xen to
>>>>>>>>> the domU
>>>>>>>>> command line?
>>>>>>>>>
>>>>>>>>>> I have double checked that I have all
the necessary options
>>>>>>>>>> enabled on my kernel config.
>>>>>>>>> Can you supply the config pls.
>>>>>>>>>
>>>>>>>>> Ian.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
_______________________________________________
>>>>>>>>> Xen-devel mailing list
>>>>>>>>> Xen-devel@lists.xensource.com
>>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>>> _______________________________________________
>>>>>>>> Xen-devel mailing list
>>>>>>>> Xen-devel@lists.xensource.com
>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>> _______________________________________________
>>>>>>> Xen-devel mailing list
>>>>>>> Xen-devel@lists.xensource.com
>>>>>>> http://lists.xensource.com/xen-devel
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2009-Jan-07 15:25 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Wed, Jan 07, 2009 at 04:25:25PM +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> This is indeed a very strange problem. I just disabled _everything_ in 
> the kernel menuconfig. No drivers, no filesystems, no nothing. I even 
> disabled all in processor types and features.
> 
> Still the same error message. So it''s probably a bug or something 
> because its not just working no matter what options are enabled/disabled 
> in kernel.
>
Can you please post your domU config file? 

-- Pasi

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

Valtteri Kiviniemi

2009-Jan-07 16:19 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

Here is my two .config files

This is the one with the same options enabled as my 2.6.18.8-xenU:

-------------------------------------------------------

#
# Automatically generated make config: don''t edit
# Linux kernel version: 2.6.28
# Mon Jan  5 19:52:54 2009
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_CGROUPS is not set
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_GROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
CONFIG_MARKERS=y
CONFIG_HAVE_OPROFILE=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_MODULES is not set
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_IO_TRACE is not set
CONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_INTEGRITY is not set
CONFIG_BLOCK_COMPAT=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_CLASSIC_RCU=y
# CONFIG_FREEZER is not set

#
# Processor type and features
#
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_VSMP is not set
CONFIG_PARAVIRT_GUEST=y
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=32
# CONFIG_KVM_CLOCK is not set
# CONFIG_KVM_GUEST is not set
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
CONFIG_MCORE2=y
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_CPU=y
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_P6_NOP=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR_64=y
# CONFIG_X86_DS is not set
CONFIG_HPET_TIMER=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
CONFIG_NR_CPUS=4
# CONFIG_SCHED_SMT is not set
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_MCE is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=y
# CONFIG_MICROCODE_INTEL is not set
# CONFIG_MICROCODE_AMD is not set
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
# CONFIG_NUMA is not set
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_UNEVICTABLE_LRU=y
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_X86_RESERVE_LOW_64K=y
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y
CONFIG_SECCOMP=y
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
# CONFIG_SCHED_HRTICK is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x200000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x200000
# CONFIG_HOTPLUG_CPU is not set
CONFIG_COMPAT_VDSO=y
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management and ACPI options
#
# CONFIG_PM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_IDLE is not set

#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
# CONFIG_PCIEASPM is not set
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
CONFIG_PCI_LEGACY=y
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_K8_NB=y
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=y
CONFIG_NET_KEY=y
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
CONFIG_INET_XFRM_TUNNEL=y
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
# CONFIG_INET_DIAG is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_QUEUE=y
CONFIG_NETFILTER_NETLINK_LOG=y
# CONFIG_NF_CONNTRACK is not set
CONFIG_NETFILTER_XTABLES=y
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=y
# CONFIG_NETFILTER_XT_TARGET_DSCP is not set
CONFIG_NETFILTER_XT_TARGET_MARK=y
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y
# CONFIG_NETFILTER_XT_TARGET_RATEEST is not set
# CONFIG_NETFILTER_XT_TARGET_TRACE is not set
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set
# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set
CONFIG_NETFILTER_XT_MATCH_COMMENT=y
CONFIG_NETFILTER_XT_MATCH_DCCP=y
# CONFIG_NETFILTER_XT_MATCH_DSCP is not set
CONFIG_NETFILTER_XT_MATCH_ESP=y
# CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_IPRANGE is not set
CONFIG_NETFILTER_XT_MATCH_LENGTH=y
CONFIG_NETFILTER_XT_MATCH_LIMIT=y
CONFIG_NETFILTER_XT_MATCH_MAC=y
CONFIG_NETFILTER_XT_MATCH_MARK=y
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=y
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
CONFIG_NETFILTER_XT_MATCH_POLICY=y
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=y
CONFIG_NETFILTER_XT_MATCH_QUOTA=y
# CONFIG_NETFILTER_XT_MATCH_RATEEST is not set
CONFIG_NETFILTER_XT_MATCH_REALM=y
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
# CONFIG_NETFILTER_XT_MATCH_SCTP is not set
CONFIG_NETFILTER_XT_MATCH_STATISTIC=y
CONFIG_NETFILTER_XT_MATCH_STRING=y
CONFIG_NETFILTER_XT_MATCH_TCPMSS=y
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
# CONFIG_IP_VS is not set

#
# IP: Netfilter Configuration
#
# CONFIG_NF_DEFRAG_IPV4 is not set
CONFIG_IP_NF_QUEUE=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_ADDRTYPE=y
CONFIG_IP_NF_MATCH_AH=y
CONFIG_IP_NF_MATCH_ECN=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_IP_NF_TARGET_TTL=y
CONFIG_IP_NF_RAW=y
CONFIG_IP_NF_ARPTABLES=y
CONFIG_IP_NF_ARPFILTER=y
CONFIG_IP_NF_ARP_MANGLE=y
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set
CONFIG_NET_CLS_ROUTE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_PHONET is not set
# CONFIG_WIRELESS is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
CONFIG_FW_LOADER=y
# CONFIG_FIRMWARE_IN_KERNEL is not set
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
# CONFIG_VIRTIO_BLK is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_SGI_XP is not set
# CONFIG_HP_ILO is not set
# CONFIG_SGI_GRU is not set
# CONFIG_C2PORT is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=y
CONFIG_CHR_DEV_SCH=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
# CONFIG_SCSI_LOWLEVEL is not set
# CONFIG_SCSI_DH is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_SATA_PMP=y
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y
# CONFIG_SATA_SVW is not set
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_SCH is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID10=y
CONFIG_MD_RAID456=y
CONFIG_MD_RAID5_RESHAPE=y
CONFIG_MD_MULTIPATH=y
CONFIG_MD_FAULTY=y
CONFIG_BLK_DEV_DM=y
CONFIG_DM_DEBUG=y
CONFIG_DM_CRYPT=y
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
CONFIG_DM_ZERO=y
CONFIG_DM_MULTIPATH=y
CONFIG_DM_DELAY=y
CONFIG_DM_UEVENT=y
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#

#
# Enable only one of the two stacks, unless you know what you are doing
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_ARCNET is not set
# CONFIG_NET_ETHERNET is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_IWLWIFI_LEDS is not set
# CONFIG_WAN is not set
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_VIRTIO_NET is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
# CONFIG_DEVKMEM is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
CONFIG_FIX_EARLYCON_MEM=y

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
# CONFIG_I2C is not set
# CONFIG_SPI is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_THERMAL is not set
# CONFIG_THERMAL_HWMON is not set
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_REGULATOR is not set

#
# Multimedia devices
#

#
# Multimedia core support
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_VIDEO_MEDIA is not set

#
# Multimedia drivers
#
# CONFIG_DAB is not set

#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_DRM is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
# CONFIG_SOUND is not set
# CONFIG_HID_SUPPORT is not set
# CONFIG_USB_SUPPORT is not set
# CONFIG_UWB is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_UIO is not set
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
# CONFIG_STAGING is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
# CONFIG_DMIID is not set
# CONFIG_ISCSI_IBFT_FIND is not set

#
# File systems
#
# CONFIG_EXT2_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
# CONFIG_EXT4DEV_COMPAT is not set
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
CONFIG_JBD=y
CONFIG_JBD2=y
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_REGISTER_V4 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=2048
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y

#
# Tracers
#
# CONFIG_SYSPROF_TRACER is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_DYNAMIC_PRINTK_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_OPTIMIZE_INLINING is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_XOR_BLOCKS=y
CONFIG_ASYNC_CORE=y
CONFIG_ASYNC_MEMCPY=y
CONFIG_ASYNC_XOR=y
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=y

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set

#
# Block modes
#
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set

#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CRC32C_INTEL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set

#
# Ciphers
#
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_X86_64 is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_LZO is not set

#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
# CONFIG_KVM is not set
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
CONFIG_VIRTIO_PCI=y
# CONFIG_VIRTIO_BALLOON is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
# CONFIG_CRC_CCITT is not set
CONFIG_CRC16=y
# CONFIG_CRC_T10DIF is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=y
CONFIG_TEXTSEARCH_BM=y
CONFIG_TEXTSEARCH_FSM=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

-------------------------------------------------------

And this is the one where all the options in the menuconfig are disabled:

-------------------------------------------------------

#
# Automatically generated make config: don''t edit
# Linux kernel version: 2.6.28
# Wed Jan  7 16:19:31 2009
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
# CONFIG_EXPERIMENTAL is not set
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
# CONFIG_SWAP is not set
# CONFIG_SYSVIPC is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_CGROUPS is not set
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_SYSFS_DEPRECATED_V2 is not set
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
# CONFIG_COMPAT_BRK is not set
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
# CONFIG_MARKERS is not set
CONFIG_HAVE_OPROFILE=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_MODULES is not set
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
CONFIG_BLOCK_COMPAT=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_CLASSIC_RCU=y
CONFIG_FREEZER=y

#
# Processor type and features
#
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_SMP is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_VSMP is not set
CONFIG_PARAVIRT_GUEST=y
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=32
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_KVM_CLOCK is not set
# CONFIG_KVM_GUEST is not set
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
CONFIG_MCORE2=y
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_CPU=y
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_P6_NOP=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR_64=y
# CONFIG_X86_DS is not set
CONFIG_HPET_TIMER=y
CONFIG_DMI=y
# CONFIG_IOMMU_HELPER is not set
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_MCE is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
# CONFIG_SPARSEMEM_VMEMMAP is not set
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
# CONFIG_UNEVICTABLE_LRU is not set
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
# CONFIG_X86_RESERVE_LOW_64K is not set
# CONFIG_MTRR is not set
# CONFIG_SECCOMP is not set
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
# CONFIG_SCHED_HRTICK is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x200000
CONFIG_PHYSICAL_ALIGN=0x200000
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management and ACPI options
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP=y
# CONFIG_SUSPEND is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_IDLE is not set

#
# Memory power savings
#

#
# Bus options (PCI etc.)
#
# CONFIG_PCI is not set
# CONFIG_ARCH_SUPPORTS_MSI is not set
CONFIG_ISA_DMA_API=y
# CONFIG_PCCARD is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
CONFIG_XFRM_IPCOMP=y
CONFIG_NET_KEY=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_SYN_COOKIES is not set
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
CONFIG_INET_XFRM_TUNNEL=y
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
# CONFIG_INET_DIAG is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_QUEUE=y
CONFIG_NETFILTER_NETLINK_LOG=y
# CONFIG_NF_CONNTRACK is not set
CONFIG_NETFILTER_XTABLES=y
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=y
# CONFIG_NETFILTER_XT_TARGET_DSCP is not set
CONFIG_NETFILTER_XT_TARGET_MARK=y
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y
# CONFIG_NETFILTER_XT_TARGET_RATEEST is not set
# CONFIG_NETFILTER_XT_TARGET_TRACE is not set
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set
CONFIG_NETFILTER_XT_MATCH_COMMENT=y
CONFIG_NETFILTER_XT_MATCH_DCCP=y
# CONFIG_NETFILTER_XT_MATCH_DSCP is not set
CONFIG_NETFILTER_XT_MATCH_ESP=y
# CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_IPRANGE is not set
CONFIG_NETFILTER_XT_MATCH_LENGTH=y
CONFIG_NETFILTER_XT_MATCH_LIMIT=y
CONFIG_NETFILTER_XT_MATCH_MAC=y
CONFIG_NETFILTER_XT_MATCH_MARK=y
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=y
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
CONFIG_NETFILTER_XT_MATCH_POLICY=y
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=y
CONFIG_NETFILTER_XT_MATCH_QUOTA=y
# CONFIG_NETFILTER_XT_MATCH_RATEEST is not set
CONFIG_NETFILTER_XT_MATCH_REALM=y
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
CONFIG_NETFILTER_XT_MATCH_STATISTIC=y
CONFIG_NETFILTER_XT_MATCH_STRING=y
CONFIG_NETFILTER_XT_MATCH_TCPMSS=y
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
# CONFIG_IP_VS is not set

#
# IP: Netfilter Configuration
#
# CONFIG_NF_DEFRAG_IPV4 is not set
CONFIG_IP_NF_QUEUE=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_ADDRTYPE=y
CONFIG_IP_NF_MATCH_AH=y
CONFIG_IP_NF_MATCH_ECN=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_IP_NF_TARGET_TTL=y
CONFIG_IP_NF_RAW=y
CONFIG_IP_NF_ARPTABLES=y
CONFIG_IP_NF_ARPFILTER=y
CONFIG_IP_NF_ARP_MANGLE=y
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_NET_SCHED is not set
CONFIG_NET_CLS_ROUTE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_PHONET is not set
# CONFIG_WIRELESS is not set
# CONFIG_RFKILL is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
CONFIG_FW_LOADER=y
# CONFIG_FIRMWARE_IN_KERNEL is not set
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
# CONFIG_BLK_DEV_HD is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
# CONFIG_SCSI is not set
# CONFIG_SCSI_DMA is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_ATA is not set
# CONFIG_MD is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NET_ETHERNET is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_IWLWIFI_LEDS is not set
# CONFIG_WAN is not set
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
# CONFIG_DEVKMEM is not set
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
CONFIG_FIX_EARLYCON_MEM=y

#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_R3964 is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_I2C is not set
# CONFIG_SPI is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_THERMAL is not set
# CONFIG_THERMAL_HWMON is not set
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_REGULATOR is not set

#
# Multimedia devices
#

#
# Multimedia core support
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_VIDEO_MEDIA is not set

#
# Multimedia drivers
#
# CONFIG_DAB is not set

#
# Graphics support
#
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
# CONFIG_SOUND is not set
# CONFIG_HID_SUPPORT is not set
# CONFIG_USB_SUPPORT is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_UIO is not set
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
# CONFIG_STAGING is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
# CONFIG_DMIID is not set
# CONFIG_ISCSI_IBFT_FIND is not set

#
# File systems
#
# CONFIG_EXT2_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
# CONFIG_EXT4_FS is not set
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
# CONFIG_XFS_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_DNOTIFY is not set
# CONFIG_INOTIFY is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_HFSPLUS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_NETWORK_FILESYSTEMS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_NLS is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=2048
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_KERNEL is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y

#
# Tracers
#
# CONFIG_SYSPROF_TRACER is not set
# CONFIG_DYNAMIC_PRINTK_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_OPTIMIZE_INLINING is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=y

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set

#
# Block modes
#
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_PCBC is not set

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y

#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CRC32C_INTEL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set

#
# Ciphers
#
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_X86_64 is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_LZO is not set

#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_HW=y
CONFIG_HAVE_KVM=y
# CONFIG_VIRTUALIZATION is not set

#
# Library routines
#
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
# CONFIG_CRC_T10DIF is not set
# CONFIG_CRC_ITU_T is not set
# CONFIG_CRC32 is not set
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=y
CONFIG_TEXTSEARCH_BM=y
CONFIG_TEXTSEARCH_FSM=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

-------------------------------------------------------

I''ll try later on to build the kernel with ~all the option enabled and
I
try to make initrd and see if it makes any difference.

I also did some digging with google and I found out that theres some 
other people too who are getting the same error with different versions 
of kernel, but they were dead ends (no solution found).


- Valtteri Kiviniemi

Pasi Kärkkäinen kirjoitti:> On Wed, Jan 07, 2009 at 04:25:25PM +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> This is indeed a very strange problem. I just disabled _everything_ in 
>> the kernel menuconfig. No drivers, no filesystems, no nothing. I even 
>> disabled all in processor types and features.
>>
>> Still the same error message. So it''s probably a bug or
something
>> because its not just working no matter what options are
enabled/disabled
>> in kernel.
>>
> 
> Can you please post your domU config file? 
> 
> -- Pasi
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2009-Jan-07 16:23 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Wed, Jan 07, 2009 at 06:19:10PM +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> Here is my two .config files
>
Uhm, I meant _Xen_ domU cfgfile :) not kernel. 

-- Pasi
 

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

Valtteri Kiviniemi

2009-Jan-07 16:25 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

Whoops :)

Here you go:

kernel = "/boot/vmlinux-2.6.28"
builder = "linux"
memory = "256"
name = "dataproof"
vcpus = "4"
vif = [''mac=00:16:3e:50:c7:43, bridge=xenbr0'']
disk = [ ''phy:/dev/virtual/dataproof,xvda1,w'',
         ''phy:/dev/virtual/dataproof-swap,xvda2,w'']
root = "/dev/xvda1 ro"
extra = "console=hvc0 earlyprintk=xen"
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''


- Valtteri Kiviniemi

Pasi Kärkkäinen kirjoitti:> On Wed, Jan 07, 2009 at 06:19:10PM +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> Here is my two .config files
>>
> 
> Uhm, I meant _Xen_ domU cfgfile :) not kernel. 
> 
> -- Pasi
>  

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

Pasi Kärkkäinen

2009-Jan-07 17:15 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Wed, Jan 07, 2009 at 06:25:40PM +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> Whoops :)
> 
> Here you go:
> 
> kernel = "/boot/vmlinux-2.6.28"
> builder = "linux"
> memory = "256"
> name = "dataproof"
> vcpus = "4"
> vif = [''mac=00:16:3e:50:c7:43, bridge=xenbr0'']
> disk = [ ''phy:/dev/virtual/dataproof,xvda1,w'',
>         ''phy:/dev/virtual/dataproof-swap,xvda2,w'']
> root = "/dev/xvda1 ro"
> extra = "console=hvc0 earlyprintk=xen"
> on_poweroff = ''destroy''
> on_reboot = ''restart''
> on_crash = ''restart''
>
Does vcpus=1 change anything? 

Or only having disk = [ ''phy:/dev/virtual/dataproof,xvda,w'' ]
?

-- Pasi
 > 
> - Valtteri Kiviniemi
> 
> Pasi Kärkkäinen kirjoitti:
> >On Wed, Jan 07, 2009 at 06:19:10PM +0200, Valtteri Kiviniemi wrote:
> >>Hi,
> >>
> >>Here is my two .config files
> >>
> >
> >Uhm, I meant _Xen_ domU cfgfile :) not kernel. 
> >
> >-- Pasi
> > 
> 
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Valtteri Kiviniemi

2009-Jan-07 18:06 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

Changing vcpus to one and using only xvda disk produces this error:

root@xen-1:~# xm create dataproof.cfg -c
Using config file "/etc/xen/dataproof.cfg".
Started domain dataproof
Unexpected error: exceptions.OSError

Please report to xen-devel@lists.xensource.com
Traceback (most recent call last):
   File "/usr/sbin/xm", line 10, in ?
     main.main(sys.argv)
   File "//usr/lib64/python/xen/xm/main.py", line 2884, in main
     _, rc = _run_cmd(cmd, cmd_name, args)
   File "//usr/lib64/python/xen/xm/main.py", line 2908, in _run_cmd
     return True, cmd(args)
   File "<string>", line 1, in <lambda>
   File "//usr/lib64/python/xen/xm/main.py", line 1376, in
xm_importcommand
     cmd.main([command] + args)
   File "//usr/lib64/python/xen/xm/create.py", line 1328, in main
     do_console(sxp.child_value(config, ''name'', -1))
   File "//usr/lib64/python/xen/xm/create.py", line 1355, in
do_console
     (p, rv) = os.waitpid(cpid, os.WNOHANG)
OSError: [Errno 10] No child processes

and when running it again it produces this error:

root@xen-1:~# xm create dataproof.cfg -c
Using config file "/etc/xen/dataproof.cfg".
Started domain dataproof
xenconsole: Could not open tty `/dev/pts/5'': No such file or directory

and third time

root@xen-1:~# xm create dataproof.cfg -c
Using config file "/etc/xen/dataproof.cfg".
Started domain dataproof

and then it just crashes like before


- Valtteri Kiviniemi

Pasi Kärkkäinen kirjoitti:> On Wed, Jan 07, 2009 at 06:25:40PM +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> Whoops :)
>>
>> Here you go:
>>
>> kernel = "/boot/vmlinux-2.6.28"
>> builder = "linux"
>> memory = "256"
>> name = "dataproof"
>> vcpus = "4"
>> vif = [''mac=00:16:3e:50:c7:43, bridge=xenbr0'']
>> disk = [ ''phy:/dev/virtual/dataproof,xvda1,w'',
>>         ''phy:/dev/virtual/dataproof-swap,xvda2,w'']
>> root = "/dev/xvda1 ro"
>> extra = "console=hvc0 earlyprintk=xen"
>> on_poweroff = ''destroy''
>> on_reboot = ''restart''
>> on_crash = ''restart''
>>
> 
> Does vcpus=1 change anything? 
> 
> Or only having disk = [
''phy:/dev/virtual/dataproof,xvda,w'' ] ?
> 
> -- Pasi
>  
>> - Valtteri Kiviniemi
>>
>> Pasi Kärkkäinen kirjoitti:
>>> On Wed, Jan 07, 2009 at 06:19:10PM +0200, Valtteri Kiviniemi wrote:
>>>> Hi,
>>>>
>>>> Here is my two .config files
>>>>
>>> Uhm, I meant _Xen_ domU cfgfile :) not kernel. 
>>>
>>> -- Pasi
>>>
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2009-Jan-07 18:17 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Wed, Jan 07, 2009 at 08:06:31PM +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> Changing vcpus to one and using only xvda disk produces this error:
> 
> root@xen-1:~# xm create dataproof.cfg -c
> Using config file "/etc/xen/dataproof.cfg".
> Started domain dataproof
> Unexpected error: exceptions.OSError
> 
> Please report to xen-devel@lists.xensource.com
> Traceback (most recent call last):
>   File "/usr/sbin/xm", line 10, in ?
>     main.main(sys.argv)
>   File "//usr/lib64/python/xen/xm/main.py", line 2884, in main
>     _, rc = _run_cmd(cmd, cmd_name, args)
>   File "//usr/lib64/python/xen/xm/main.py", line 2908, in
_run_cmd
>     return True, cmd(args)
>   File "<string>", line 1, in <lambda>
>   File "//usr/lib64/python/xen/xm/main.py", line 1376, in
xm_importcommand
>     cmd.main([command] + args)
>   File "//usr/lib64/python/xen/xm/create.py", line 1328, in main
>     do_console(sxp.child_value(config, ''name'', -1))
>   File "//usr/lib64/python/xen/xm/create.py", line 1355, in
do_console
>     (p, rv) = os.waitpid(cpid, os.WNOHANG)
> OSError: [Errno 10] No child processes
> 
> and when running it again it produces this error:
> 
> root@xen-1:~# xm create dataproof.cfg -c
> Using config file "/etc/xen/dataproof.cfg".
> Started domain dataproof
> xenconsole: Could not open tty `/dev/pts/5'': No such file or
directory
> 
> and third time
> 
> root@xen-1:~# xm create dataproof.cfg -c
> Using config file "/etc/xen/dataproof.cfg".
> Started domain dataproof
> 
> and then it just crashes like before
> 
Hmm.. does 2.6.27.x pv_ops domU work for you? 

-- Pasi

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

Valtteri Kiviniemi

2009-Jan-07 18:20 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

Do you mean kernel.org vanilla 2.6.27.x or 
http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg ?

Vanilla 2.6.27 is making the same error message and crash and that 
(Novells?) patched 2.6.27 I don''t seem to get compile properly


- Valtteri Kiviniemi

Pasi Kärkkäinen kirjoitti:> On Wed, Jan 07, 2009 at 08:06:31PM +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> Changing vcpus to one and using only xvda disk produces this error:
>>
>> root@xen-1:~# xm create dataproof.cfg -c
>> Using config file "/etc/xen/dataproof.cfg".
>> Started domain dataproof
>> Unexpected error: exceptions.OSError
>>
>> Please report to xen-devel@lists.xensource.com
>> Traceback (most recent call last):
>>   File "/usr/sbin/xm", line 10, in ?
>>     main.main(sys.argv)
>>   File "//usr/lib64/python/xen/xm/main.py", line 2884, in
main
>>     _, rc = _run_cmd(cmd, cmd_name, args)
>>   File "//usr/lib64/python/xen/xm/main.py", line 2908, in
_run_cmd
>>     return True, cmd(args)
>>   File "<string>", line 1, in <lambda>
>>   File "//usr/lib64/python/xen/xm/main.py", line 1376, in
xm_importcommand
>>     cmd.main([command] + args)
>>   File "//usr/lib64/python/xen/xm/create.py", line 1328, in
main
>>     do_console(sxp.child_value(config, ''name'', -1))
>>   File "//usr/lib64/python/xen/xm/create.py", line 1355, in
do_console
>>     (p, rv) = os.waitpid(cpid, os.WNOHANG)
>> OSError: [Errno 10] No child processes
>>
>> and when running it again it produces this error:
>>
>> root@xen-1:~# xm create dataproof.cfg -c
>> Using config file "/etc/xen/dataproof.cfg".
>> Started domain dataproof
>> xenconsole: Could not open tty `/dev/pts/5'': No such file or
directory
>>
>> and third time
>>
>> root@xen-1:~# xm create dataproof.cfg -c
>> Using config file "/etc/xen/dataproof.cfg".
>> Started domain dataproof
>>
>> and then it just crashes like before
>>
> 
> Hmm.. does 2.6.27.x pv_ops domU work for you? 
> 
> -- Pasi
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2009-Jan-07 19:26 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Wed, Jan 07, 2009 at 08:20:08PM +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> Do you mean kernel.org vanilla 2.6.27.x or 
> http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg ?
> 
Yeah, I meant vanilla (pv_ops).

Does any domU work for you? :) 
> Vanilla 2.6.27 is making the same error message and crash and that 
> (Novells?) patched 2.6.27 I don''t seem to get compile properly
> 
I haven''t used that myself so can''t help with this.. 

-- Pasi

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

Valtteri Kiviniemi

2009-Jan-07 19:34 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

No one of the pv_ops kernels that I have tried works, but the Xen''s 
2.6.18.8 is working fine.

So the problem is just the mainline pv_ops support, it just wont work.

- Valtteri Kiviniemi

Pasi Kärkkäinen kirjoitti:> On Wed, Jan 07, 2009 at 08:20:08PM +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> Do you mean kernel.org vanilla 2.6.27.x or 
>> http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg ?
>>
> 
> Yeah, I meant vanilla (pv_ops).
> 
> Does any domU work for you? :) 
> 
>> Vanilla 2.6.27 is making the same error message and crash and that 
>> (Novells?) patched 2.6.27 I don''t seem to get compile properly
>>
> 
> I haven''t used that myself so can''t help with this.. 
> 
> -- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2009-Jan-07 19:38 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Wed, Jan 07, 2009 at 09:34:43PM +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> No one of the pv_ops kernels that I have tried works, but the
Xen''s
> 2.6.18.8 is working fine.
> 
> So the problem is just the mainline pv_ops support, it just wont work.
> 
Are you using the "vmlinux" file as a domU kernel from the compiled
mainline kernel?

-- Pasi

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

Valtteri Kiviniemi

2009-Jan-07 19:42 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

Yes with 2.6.28 im using the vmlinux

- Valtteri Kiviniemi

Pasi Kärkkäinen kirjoitti:> On Wed, Jan 07, 2009 at 09:34:43PM +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> No one of the pv_ops kernels that I have tried works, but the
Xen''s
>> 2.6.18.8 is working fine.
>>
>> So the problem is just the mainline pv_ops support, it just wont work.
>>
> 
> Are you using the "vmlinux" file as a domU kernel from the
compiled mainline kernel?
> 
> -- Pasi
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2009-Jan-07 19:47 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

On Wed, Jan 07, 2009 at 09:42:34PM +0200, Valtteri Kiviniemi
wrote:> Hi,
> 
> Yes with 2.6.28 im using the vmlinux
>
Does 32 bit PAE pv_ops/mainline kernel work? 
 
-- Pasi

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

Valtteri Kiviniemi

2009-Jan-07 19:51 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

I was just thinking about testing that. But that''s not really a
solution
because all of my virtuals have 64bit installation..

Is there any way how to debug the crash output further to get some 
information about which is crashin the domU?

There has to be some (maybe even simple) reason why it''s crashing...

- Valtteri Kiviniemi

Pasi Kärkkäinen kirjoitti:> On Wed, Jan 07, 2009 at 09:42:34PM +0200, Valtteri Kiviniemi wrote:
>> Hi,
>>
>> Yes with 2.6.28 im using the vmlinux
>>
> 
> Does 32 bit PAE pv_ops/mainline kernel work? 
>  
> -- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Valtteri Kiviniemi

2009-Jan-11 00:39 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

I just tested 2.6.29-rc1 kernel and this problem is still happening.


- Valtteri Kiviniemi

Valtteri Kiviniemi kirjoitti:> Hi,
> 
> I was just thinking about testing that. But that''s not really a
solution
> because all of my virtuals have 64bit installation..
> 
> Is there any way how to debug the crash output further to get some 
> information about which is crashin the domU?
> 
> There has to be some (maybe even simple) reason why it''s
crashing...
> 
> - Valtteri Kiviniemi
> 
> Pasi Kärkkäinen kirjoitti:
>> On Wed, Jan 07, 2009 at 09:42:34PM +0200, Valtteri Kiviniemi wrote:
>>> Hi,
>>>
>>> Yes with 2.6.28 im using the vmlinux
>>>
>>
>> Does 32 bit PAE pv_ops/mainline kernel work?  
>> -- Pasi
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Jeremy Fitzhardinge

2009-Jan-16 19:16 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Valtteri Kiviniemi wrote:> Hi,
>
> I just tested 2.6.29-rc1 kernel and this problem is still happening.
If you can get the RIP out of the Xen dump, and then do
$ gdb vmlinux
(gdb) x/i RIP

it will at least give us some idea of where to look.

Have you tried different memory sizes?

You can boot a 32-bit PAE guest on a 64-bit host, which would be an 
interesting test.

    J

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

Valtteri Kiviniemi

2009-Jan-18 18:11 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

I''ll test the 32-bit PAE guest later.. I have tried different memory 
sizes with no success.

The RIP does not match in any symbols

root@xen-1:/boot# gdb vmlinux-2.6.29-rc1
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) x/i ffffffff8020abe7
No symbol "ffffffff8020abe7" in current context.
(gdb) file /boot/vmlinux-2.6.29-rc1
Load new symbol table from "/boot/vmlinux-test"? (y or n) y
Reading symbols from /boot/vmlinux-2.6.29-rc1...done.
(gdb) x/i ffffffff8020abe7
No symbol "ffffffff8020abe7" in current context.
(gdb)

- Valtteri Kiviniemi

Jeremy Fitzhardinge kirjoitti:> Valtteri Kiviniemi wrote:
>> Hi,
>>
>> I just tested 2.6.29-rc1 kernel and this problem is still happening.
> 
> If you can get the RIP out of the Xen dump, and then do
> $ gdb vmlinux
> (gdb) x/i RIP
> 
> it will at least give us some idea of where to look.
> 
> Have you tried different memory sizes?
> 
> You can boot a 32-bit PAE guest on a 64-bit host, which would be an 
> interesting test.
> 
>    J
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Jeremy Fitzhardinge

2009-Jan-20 19:16 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Valtteri Kiviniemi wrote:> Hi,
>
> I''ll test the 32-bit PAE guest later.. I have tried different
memory
> sizes with no success.
>
> The RIP does not match in any symbols
>
> root@xen-1:/boot# gdb vmlinux-2.6.29-rc1
> GNU gdb 6.8-debian
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show 
> copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu"...
> (gdb) x/i ffffffff8020abe7
> No symbol "ffffffff8020abe7" in current context.
> (gdb) file /boot/vmlinux-2.6.29-rc1
> Load new symbol table from "/boot/vmlinux-test"? (y or n) y
> Reading symbols from /boot/vmlinux-2.6.29-rc1...done.
> (gdb) x/i ffffffff8020abe7
> No symbol "ffffffff8020abe7" in current context.
> (gdb)
You''ll need to put a "0x" on the front of the hex number:
"x/i
0xffffffff8020abe7"

    J

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

Valtteri Kiviniemi

2009-Jan-20 21:39 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Hi,

Oh, ok.

So now its givig me:

0xffffffff8020abe7 <set_page_prot+73>:  ud2a

- Valtteri Kiviniemi

Jeremy Fitzhardinge kirjoitti:> Valtteri Kiviniemi wrote:
>> Hi,
>>
>> I''ll test the 32-bit PAE guest later.. I have tried different
memory
>> sizes with no success.
>>
>> The RIP does not match in any symbols
>>
>> root@xen-1:/boot# gdb vmlinux-2.6.29-rc1
>> GNU gdb 6.8-debian
>> Copyright (C) 2008 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later 
>> <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show 
>> copying"
>> and "show warranty" for details.
>> This GDB was configured as "x86_64-linux-gnu"...
>> (gdb) x/i ffffffff8020abe7
>> No symbol "ffffffff8020abe7" in current context.
>> (gdb) file /boot/vmlinux-2.6.29-rc1
>> Load new symbol table from "/boot/vmlinux-test"? (y or n) y
>> Reading symbols from /boot/vmlinux-2.6.29-rc1...done.
>> (gdb) x/i ffffffff8020abe7
>> No symbol "ffffffff8020abe7" in current context.
>> (gdb)
> 
> You''ll need to put a "0x" on the front of the hex
number: "x/i
> 0xffffffff8020abe7"
> 
>    J
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

dbaxps

2009-Feb-01 15:13 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Valtteri Kiviniemi wrote:> 
>>Hi,
> 
>>Do you mean kernel.org vanilla 2.6.27.x or 
>>http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg ?
> 
>>Vanilla 2.6.27 is making the same error message and crash and that 
>>(Novells?) patched 2.6.27 I don''t seem to get compile properly
> 
> Novell''s patched kernel 2.6.27.5 gets properly compiled and  works
stable
> under Xen Hypervisor 3.3.0 & 3.3.1 
> (except shutdown Xen Host, just reboots smoothly to another CentOS 5.2
> instance on same host):-
> http://lxer.com/module/newswire/view/114358/index.html
> http://lxer.com/module/newswire/view/115378/index.html
> 
> 
> - Valtteri Kiviniemi
> 
> Pasi Kärkkäinen kirjoitti:
>> On Wed, Jan 07, 2009 at 08:06:31PM +0200, Valtteri Kiviniemi wrote:
>>> Hi,
>>>
>>> Changing vcpus to one and using only xvda disk produces this error:
>>>
>>> root@xen-1:~# xm create dataproof.cfg -c
>>> Using config file "/etc/xen/dataproof.cfg".
>>> Started domain dataproof
>>> Unexpected error: exceptions.OSError
>>>
>>> Please report to xen-devel@lists.xensource.com
>>> Traceback (most recent call last):
>>>   File "/usr/sbin/xm", line 10, in ?
>>>     main.main(sys.argv)
>>>   File "//usr/lib64/python/xen/xm/main.py", line 2884, in
main
>>>     _, rc = _run_cmd(cmd, cmd_name, args)
>>>   File "//usr/lib64/python/xen/xm/main.py", line 2908, in
_run_cmd
>>>     return True, cmd(args)
>>>   File "<string>", line 1, in <lambda>
>>>   File "//usr/lib64/python/xen/xm/main.py", line 1376, in
>>> xm_importcommand
>>>     cmd.main([command] + args)
>>>   File "//usr/lib64/python/xen/xm/create.py", line 1328,
in main
>>>     do_console(sxp.child_value(config, ''name'',
-1))
>>>   File "//usr/lib64/python/xen/xm/create.py", line 1355,
in do_console
>>>     (p, rv) = os.waitpid(cpid, os.WNOHANG)
>>> OSError: [Errno 10] No child processes
>>>
>>> and when running it again it produces this error:
>>>
>>> root@xen-1:~# xm create dataproof.cfg -c
>>> Using config file "/etc/xen/dataproof.cfg".
>>> Started domain dataproof
>>> xenconsole: Could not open tty `/dev/pts/5'': No such file
or directory
>>>
>>> and third time
>>>
>>> root@xen-1:~# xm create dataproof.cfg -c
>>> Using config file "/etc/xen/dataproof.cfg".
>>> Started domain dataproof
>>>
>>> and then it just crashes like before
>>>
>> 
>> Hmm.. does 2.6.27.x pv_ops domU work for you? 
>> 
>> -- Pasi
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://www.nabble.com/2.6.28-64-bit-domU-not-booting-tp21290067p21776232.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


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

Chris Lalancette

2009-Mar-27 10:37 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Valtteri Kiviniemi wrote:> Hi,
> 
> Im using vanilla 2.6.28 kernel from kernel.org and when I try to boot my 
>   domU with it, it just disappears without any error or warning.
Just to dig up this old thread: we''ve been seeing the same thing.  I
*think* it
comes down to the NX bit (or the lack thereof); on machines without NX, the
early pagetable setup is trying to use the NX bit in the PTE flags, and the
hypervisor is telling it to go away.  The Red Hat bugzilla entry that
I''ve filed
has more analysis:

https://bugzilla.redhat.com/show_bug.cgi?id=492523

Valtteri, can you give the output of "cat /proc/cpuinfo | grep flags",
so we can
confirm that it''s probably the same issue?

And it looks like Ian Campbell actually posted a patch upstream
(http://lkml.indiana.edu/hypermail/linux/kernel/0901.3/02668.html) that should
fix this, but I don''t see it in any of the upstream trees.  Ian,
Jeremy, do you
guys know what the status is there?  It would be good to get into 2.6.30, and
probably backport to the stable trees as well.

-- 
Chris Lalancette

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

Jeremy Fitzhardinge

2009-Mar-27 18:34 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Chris Lalancette wrote:> Just to dig up this old thread: we''ve been seeing the same thing. 
I *think* it
> comes down to the NX bit (or the lack thereof); on machines without NX, the
> early pagetable setup is trying to use the NX bit in the PTE flags, and the
> hypervisor is telling it to go away.  The Red Hat bugzilla entry that
I''ve filed
> has more analysis:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=492523
>
> Valtteri, can you give the output of "cat /proc/cpuinfo | grep
flags", so we can
> confirm that it''s probably the same issue?
>
> And it looks like Ian Campbell actually posted a patch upstream
> (http://lkml.indiana.edu/hypermail/linux/kernel/0901.3/02668.html) that
should
> fix this, but I don''t see it in any of the upstream trees.  Ian,
Jeremy, do you
> guys know what the status is there?  It would be good to get into 2.6.30,
and
> probably backport to the stable trees as well.
>   
Hm, yes, it does seem to have got lost.  But I wonder if a simpler fix 
isn''t just test for NX early and set __supported_pte_mask accordingly.
Does this work?

    J

From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Fri, 27 Mar 2009 11:29:02 -0700
Subject: [PATCH] xen: set _PAGE_NX in __supported_pte_mask before pagetable
construction

Many 32-bit and some 64-bit machines don''t support the NX flag in ptes.
Check for NX before constructing the kernel pagetables.

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index 992be7f..f8c9e49 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -42,6 +42,7 @@
 #include <asm/xen/hypervisor.h>
 #include <asm/fixmap.h>
 #include <asm/processor.h>
+#include <asm/proto.h>
 #include <asm/msr-index.h>
 #include <asm/setup.h>
 #include <asm/desc.h>
@@ -1003,6 +1004,13 @@ asmlinkage void __init xen_start_kernel(void)
 
 	__supported_pte_mask |= _PAGE_IOMAP;
 
+	/* Work out if we support NX */
+#ifdef CONFIG_X86_64
+	check_efer();
+#else
+	set_nx();
+#endif
+
 	/* Don''t do the full vcpu_info placement stuff until we have a
 	   possible map and a non-dummy shared_info. */
 	per_cpu(xen_vcpu, 0) = &HYPERVISOR_shared_info->vcpu_info[0];





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

Chris Lalancette

2009-Mar-30 09:19 UTC

head link

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Jeremy Fitzhardinge wrote:> Chris Lalancette wrote:
>> Just to dig up this old thread: we''ve been seeing the same
thing.  I *think* it
>> comes down to the NX bit (or the lack thereof); on machines without NX,
the
>> early pagetable setup is trying to use the NX bit in the PTE flags, and
the
>> hypervisor is telling it to go away.  The Red Hat bugzilla entry that
I''ve filed
>> has more analysis:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=492523
>>
>> Valtteri, can you give the output of "cat /proc/cpuinfo | grep
flags", so we can
>> confirm that it''s probably the same issue?
>>
>> And it looks like Ian Campbell actually posted a patch upstream
>> (http://lkml.indiana.edu/hypermail/linux/kernel/0901.3/02668.html) that
should
>> fix this, but I don''t see it in any of the upstream trees. 
Ian, Jeremy, do you
>> guys know what the status is there?  It would be good to get into
2.6.30, and
>> probably backport to the stable trees as well.
>>   
> 
> Hm, yes, it does seem to have got lost.  But I wonder if a simpler fix 
> isn''t just test for NX early and set __supported_pte_mask
accordingly.
> Does this work?
> 
>     J
> 
> From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> Date: Fri, 27 Mar 2009 11:29:02 -0700
> Subject: [PATCH] xen: set _PAGE_NX in __supported_pte_mask before pagetable
construction
> 
> Many 32-bit and some 64-bit machines don''t support the NX flag in
ptes.
> Check for NX before constructing the kernel pagetables.
> 
> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> 
> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
> index 992be7f..f8c9e49 100644
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -42,6 +42,7 @@
>  #include <asm/xen/hypervisor.h>
>  #include <asm/fixmap.h>
>  #include <asm/processor.h>
> +#include <asm/proto.h>
>  #include <asm/msr-index.h>
>  #include <asm/setup.h>
>  #include <asm/desc.h>
> @@ -1003,6 +1004,13 @@ asmlinkage void __init xen_start_kernel(void)
>  
>  	__supported_pte_mask |= _PAGE_IOMAP;
>  
> +	/* Work out if we support NX */
> +#ifdef CONFIG_X86_64
> +	check_efer();
> +#else
> +	set_nx();
> +#endif
> +
>  	/* Don''t do the full vcpu_info placement stuff until we have a
>  	   possible map and a non-dummy shared_info. */
>  	per_cpu(xen_vcpu, 0) = &HYPERVISOR_shared_info->vcpu_info[0];
Yep, much happier this way (although I only tested out x86_64, not i386).

Tested-by: Chris Lalancette <clalance@redhat.com>

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

Xen devel - Jan 2009 - 2.6.28 64-bit domU not booting

[Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting

Re: [Xen-devel] 2.6.28 64-bit domU not booting