search for: start_kernel

...while 2.6.38 or older kernels were ok. After digging deeply into this, I think I found the issue. However, if that is true, it seems rather lucky if pv spinlocks in HVM worked for anybody. The xen_hvm_smp_init() call will change the smp_ops hooks. One of which is smp_prepare_cpus. This is done in start_kernel and at this point in time, there is no change to the pv_lock_ops and they point to the ticket versions. Later in start_kernel, check_bugs is called and part of that takes the pv_lock_ops and patches the kernel with the correct jumps. _After_ that, the kernel_init is called and that in turn does the...

...of work porting it to > >> ARM (Ian''s GSoC idea this year). > >> > >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to > >> the guest through ESI register. And Mini-OS would use this structure as the > >> argument of start_kernel. However, I didn''t see codes handle the > >> start_info_t on ARM side. Instead, I see a more standard protocal when > >> booting ARM''s dom0, which follows linux kernel bootstrap rules: > >> > >> r0 = 0, r1 = machine nr, r2 = atags or dtb point...

...hyper+0x9d/0xc0 (early) [<ffffffff81c5e8ac>] ? early_ioremap_init+0x98/0x133 (early) [<ffffffff81c45221>] ? setup_arch+0x40/0xca6 (early) [<ffffffff8107e0ee>] ? vprintk_default+0xe/0x10 (early) [<ffffffff8154b0cd>] ? printk+0x4f/0x52 (early) [<ffffffff81c3fdda>] ? start_kernel+0xdc/0x43b (early) [<ffffffff81c47eb0>] ? reserve_early+0x30/0x39 (early) [<ffffffff81c3f33a>] ? x86_64_start_reservations+0x125/0x129 (early) [<ffffffff81c4309c>] ? xen_start_kernel+0x4fe/0x505 (early) ------------[ cut here ]------------ (early) WARNING: at arch/x86/xen/multi...

This patch series is against 2.6.20; some things are in flux, so there might be issues as other things flow into the latest -git tree. >From the documentation: Lguest is designed to be a minimal hypervisor for the Linux kernel, for Linux developers and users to experiment with virtualization with the minimum of complexity. Nonetheless, it should have sufficient features to make it useful for

This patch series is against 2.6.20; some things are in flux, so there might be issues as other things flow into the latest -git tree. >From the documentation: Lguest is designed to be a minimal hypervisor for the Linux kernel, for Linux developers and users to experiment with virtualization with the minimum of complexity. Nonetheless, it should have sufficient features to make it useful for

The current code simply calls "start_kernel" directly if we're under a hypervisor and no paravirt_ops backend wants us, because paravirt.c registers that as a backend. This was always a vain hope; start_kernel won't get far without setup. It's also impossible for paravirt_ops backends which don't sit in the arch/i386/ke...

The current code simply calls "start_kernel" directly if we're under a hypervisor and no paravirt_ops backend wants us, because paravirt.c registers that as a backend. This was always a vain hope; start_kernel won't get far without setup. It's also impossible for paravirt_ops backends which don't sit in the arch/i386/ke...

...2>] __memcpy_fromio+0x12 [<ffffffff812b7869>] __memcpy_fromio+0x9 [<ffffffff81c80153>] dmi_scan_machine+0x139 [<ffffffff81c45605>] setup_arch+0x424 [<ffffffff8107e0ee>] vprintk_default+0xe [<ffffffff8154b0cd>] printk+0x4f [<ffffffff81c3fdda>] start_kernel+0xdc [<ffffffff81c3f33a>] x86_64_start_reservations+0x125 [<ffffffff81c4309c>] xen_start_kernel+0x4fe And my domU has similar boot messages as Sarah Newman's: (early) Initializing cgroup subsys cpuset (early) Initializing cgroup subsys cpu (early) Linux version 2.6.32-696....

Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12. Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed on F12 before loading under Xen 3.4.1. Dmesg log looks similar to Michael Yuong''s ''rc7.git4''  kernel for F12. Boris. --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris

...all+132/192] evtchn_do_upcall+0x84/0xc0 Dec 8 12:19:27 server kernel: [hypervisor_callback+44/52] hypervisor_callback+0x2c/0x34 Dec 8 12:19:27 server kernel: [xen_idle+97/127] xen_idle+0x61/0x7f Dec 8 12:19:27 server kernel: [cpu_idle+76/97] cpu_idle+0x4c/0x61 Dec 8 12:19:27 server kernel: [start_kernel+370/372] start_kernel+0x172/0x174 Dec 8 12:19:27 server kernel: Mem-info: Dec 8 12:19:27 server kernel: DMA per-cpu: Dec 8 12:19:27 server kernel: cpu 0 hot: high 90, batch 15 used:14 Dec 8 12:19:27 server kernel: cpu 0 cold: high 30, batch 7 used:25 Dec 8 12:19:27 server kernel: cpu 1 hot: hi...

...[<ffffffff81c2bfd1>] ? mtrr_cleanup+0x8c/0x3fd [<ffffffff81c2ae47>] ? get_mtrr_state+0x2ec/0x2fb [<ffffffff81c2a988>] ? mtrr_bp_init+0x1ab/0x1d2 [<ffffffff81c254d8>] ? setup_arch+0x4b8/0xaea [<ffffffff814ec4c5>] ? printk+0x41/0x44 [<ffffffff81c1fc2e>] ? start_kernel+0xdc/0x430 [<ffffffff81c1f33a>] ? x86_64_start_reservations+0x125/0x129 [<ffffffff81c1f438>] ? x86_64_start_kernel+0xfa/0x109 ---[ end trace a7919e7f17c0a725 ]--- ------------[ cut here ]------------ WARNING: at kernel/sched.c:5914 thread_return+0x232/0x79d() (Tainted: G W...

When I came into work this morning the console had the following: bio_endio __end_that_request_first scsi_end_request scsi_io_completion scsi_finish_command scsi_softirq __do_softirq do_softirg do_irq command_interrupt default_idle cpu_idle start_kernel Panic I am running software RAID-1 on this machine. I had 2 IDE disks and the machine when down once in a while with similiar messages. I switched to brand new 300 GIG SATA drives and now I am seeing the same kernel panic. What might be the problem here? THanks for any suggestions. Machine has...

...rch/i386/lguest/lguest.c Tue Mar 20 11:34:07 2007 +1100 @@ -136,7 +136,7 @@ static struct notifier_block paniced = { .notifier_call = lguest_panic }; -static char *lguest_memory_setup(void) +static __init char *lguest_memory_setup(void) { /* We do this here because lockcheck barfs if before start_kernel */ atomic_notifier_chain_register(&panic_notifier_list, &paniced); @@ -549,7 +549,8 @@ static __attribute_used__ __init void lg start_kernel(); } -asm("lguest_maybe_init:\n" +asm(".section .init.text\n" + "lguest_maybe_init:\n" " cmpl $&quot...

...rch/i386/lguest/lguest.c Tue Mar 20 11:34:07 2007 +1100 @@ -136,7 +136,7 @@ static struct notifier_block paniced = { .notifier_call = lguest_panic }; -static char *lguest_memory_setup(void) +static __init char *lguest_memory_setup(void) { /* We do this here because lockcheck barfs if before start_kernel */ atomic_notifier_chain_register(&panic_notifier_list, &paniced); @@ -549,7 +549,8 @@ static __attribute_used__ __init void lg start_kernel(); } -asm("lguest_maybe_init:\n" +asm(".section .init.text\n" + "lguest_maybe_init:\n" " cmpl $&quot...

.../0xf0 [ 162.493834] gic_handle_irq+0x58/0xa8 [ 162.498464] el1_irq+0xb4/0x130 [ 162.500621] arch_cpu_idle+0x18/0x28 [ 162.504729] default_idle_call+0x1c/0x34 [ 162.508005] do_idle+0x17c/0x1f0 [ 162.510184] cpu_startup_entry+0x20/0x28 [ 162.515050] rest_init+0x250/0x260 [ 162.518228] start_kernel+0x3f0/0x41c [ 162.522987] BUG: sleeping function called from invalid context at mm/mempool.c:320 [ 162.533762] in_atomic(): 1, irqs_disabled(): 128, pid: 0, name: swapper/0 [ 162.540375] INFO: lockdep is turned off. [ 162.542696] irq event stamp: 3670810 [ 162.544963] hardirqs last enabled at...

.../0xf0 [ 162.493834] gic_handle_irq+0x58/0xa8 [ 162.498464] el1_irq+0xb4/0x130 [ 162.500621] arch_cpu_idle+0x18/0x28 [ 162.504729] default_idle_call+0x1c/0x34 [ 162.508005] do_idle+0x17c/0x1f0 [ 162.510184] cpu_startup_entry+0x20/0x28 [ 162.515050] rest_init+0x250/0x260 [ 162.518228] start_kernel+0x3f0/0x41c [ 162.522987] BUG: sleeping function called from invalid context at mm/mempool.c:320 [ 162.533762] in_atomic(): 1, irqs_disabled(): 128, pid: 0, name: swapper/0 [ 162.540375] INFO: lockdep is turned off. [ 162.542696] irq event stamp: 3670810 [ 162.544963] hardirqs last enabled at...

...ffff810052bb>] ? xen_timer_interrupt+0x0/0x17a [ 0.000000] [<ffffffff810055ee>] xen_setup_timer+0x59/0x9d [ 0.000000] [<ffffffff81731b68>] xen_time_init+0x7b/0x89 [ 0.000000] [<ffffffff81731ead>] x86_late_time_init+0xa/0x11 [ 0.000000] [<ffffffff8172eb49>] start_kernel+0x30b/0x38d [ 0.000000] [<ffffffff8172e2c6>] x86_64_start_reservations+0xb1/0xb5 [ 0.000000] [<ffffffff817313e8>] xen_start_kernel+0x508/0x50f [ 0.000000] Code: Bad RIP value. [ 0.000000] RIP [<(null)>] (null) [ 0.000000] RSP <ffffffff81601d70> [ 0.000...

...ffff810052bb>] ? xen_timer_interrupt+0x0/0x17a [ 0.000000] [<ffffffff810055ee>] xen_setup_timer+0x59/0x9d [ 0.000000] [<ffffffff81731b68>] xen_time_init+0x7b/0x89 [ 0.000000] [<ffffffff81731ead>] x86_late_time_init+0xa/0x11 [ 0.000000] [<ffffffff8172eb49>] start_kernel+0x30b/0x38d [ 0.000000] [<ffffffff8172e2c6>] x86_64_start_reservations+0xb1/0xb5 [ 0.000000] [<ffffffff817313e8>] xen_start_kernel+0x508/0x50f [ 0.000000] Code: Bad RIP value. [ 0.000000] RIP [<(null)>] (null) [ 0.000000] RSP <ffffffff81601d70> [ 0.000...

...10:00 xenmaster kernel: [<ffffffff8026e4e5>] raw_safe_halt+0x84/0xa8 Apr 18 01:10:00 xenmaster kernel: [<ffffffff8026ba22>] xen_idle+0x38/0x4a Apr 18 01:10:00 xenmaster kernel: [<ffffffff8024a803>] cpu_idle+0x97/0xba Apr 18 01:10:00 xenmaster kernel: [<ffffffff80634b09>] start_kernel+0x21f/0x224 Apr 18 01:10:00 xenmaster kernel: [<ffffffff806341e5>] _sinittext+0x1e5/0x1eb Apr 18 01:10:00 xenmaster kernel: Apr 18 01:10:00 xenmaster kernel: BUG: warning at drivers/ata/libata-core.c:4923/ata_qc_issue() (Tainted: G ) Apr 18 01:10:00 xenmaster kernel: Apr 18 01:10:00 xenm...

Just gave 3.0 a spin. Had been running 2.0.7 for the past 3 months or so without problems (aside from intermittent failure during live migration). Anyway, 3.0 seems to have an issue with my machine. It starts up the 4 domains that I''ve got defined (was running 6 user domains with 2.0.7, but two of those were running 2.4 kernels which I can''t seem to build with Xen 3.0 yet, and