search for: e010

...t;ff111584>]CPU: 4 (XEN) EIP: e008:[<ff111584>] timer_softirq_action+0x64/0x140 (XEN) EFLAGS: 00010006 CONTEXT: hypervisor (XEN) eax: 0dee319b ebx: ffff4d85 ecx: 00000000 edx: 000000c0 (XEN) esi: ff1e9a00 edi: 00000480 ebp: ffbd2080 esp: ffbd1f68 (XEN) cr0: 8005003b cr3: 00178000 (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ffbd1f68: (XEN) idle_loop+0x38/0x80 (XEN) EFLAGS: 00010246 (XEN) CR3: 00000000 (XEN) eax: 00000600 ebx: ffbc5fb4 ecx: 00000000 edx: 00000600 (XEN) esi: 00000600 edi: 00000600 ebp: 00000000 esp: ffbc5fa8 (XEN) ds: e010 es: e...

...~]# (XEN) CPU: 1 >(XEN) EIP: e008:[<ff1282f3>] do_page_fault+0x53/0x410 >(XEN) EFLAGS: 00010213 >(XEN) CR3: 00000000 >(XEN) eax: 00000000 ebx: 00000000 ecx: 00000073 edx: ff1ddfb4 >(XEN) esi: ff1dd0e8 edi: 0000000c ebp: 00000000 esp: ff1dd0b4 >(XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 >(XEN) ************************************ >(XEN) CPU1 DOUBLE FAULT -- system shutdown >(XEN) System needs manual reset. >(XEN) ************************************ > _______________________________________________ Xen-devel mailing list...

...omain vs179 [root@tst122 ~]# (XEN) CPU: 1 (XEN) EIP: e008:[<ff1282f3>] do_page_fault+0x53/0x410 (XEN) EFLAGS: 00010213 (XEN) CR3: 00000000 (XEN) eax: 00000000 ebx: 00000000 ecx: 00000073 edx: ff1ddfb4 (XEN) esi: ff1dd0e8 edi: 0000000c ebp: 00000000 esp: ff1dd0b4 (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 (XEN) ************************************ (XEN) CPU1 DOUBLE FAULT -- system shutdown (XEN) System needs manual reset. (XEN) ************************************ _______________________________________________ Xen-devel mailing list Xen-devel@lists.x...

...XEN) EIP: e008:[<0fff0000>] ??? (XEN) EFLAGS: 00010092 CONTEXT: hypervisor (XEN) eax: ffb80280 ebx: 00000004 ecx: 00000000 edx: 00000004 (XEN) esi: ff32bf8c edi: ff32bfb8 ebp: ff32bf88 esp: ff32becc (XEN) cr0: 8005003b cr4: 000006f0 cr3: d1480000 cr2: 0fff0000 (XEN) ds: e010 es: e010 fs: 00d8 gs: 00e0 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ff32becc: (XEN) ff15004d 00000004 00000004 00000000 ffbd8000 00000000 feda8970 00000000 (XEN) 0000000b ffb80280 ff32bfb4 ff32bfb4 ffb80280 ff14e079 00000004 2f69696d (XEN) 6cb90e00 0000006e c3246050 39194...

...;ff146c26>] amd_mcheck_init+0x26/0xe0 (XEN) EFLAGS: 00010082 CONTEXT: hypervisor (XEN) eax: 00000000 ebx: ff1d8080 ecx: 00000179 edx: 00000179 (XEN) esi: ff197200 edi: ff197224 ebp: ff1dfea8 esp: ff1dfe90 (XEN) cr0: 8005003b cr4: 00000090 cr3: 001e3000 cr2: 00000000 (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ff1dfe90: (XEN) ff18fe1c 0188a93d 000005a2 ff1d8080 ff197200 ff197224 ff1dfed8 ff1464cc (XEN) ff197200 00000001 ff1dfed8 ff1b3fbe fc561fe8 00000001 ff197208 ff1d8080 (XEN) ff1dffb4 fff00000 ff1dffa8 ff1ad...

...ff1288ad>] clear_fault_bits+0x2d/0xc0 (XEN) EFLAGS: 00010206 CONTEXT: hypervisor (XEN) eax: fff7aff8 ebx: 00000000 ecx: ffffffff edx: ffffffff (XEN) esi: 00000098 edi: ffbcc858 ebp: fff77000 esp: ff227e0c (XEN) cr0: 8005003b cr4: 000026f0 cr3: 00100120 cr2: fff7aff8 (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ff227e0c: (XEN) 00000098 00000098 ffbcc858 ffbcc884 ff12971b ffbcc858 00000246 00000000 (XEN) ff1c53bc ffbcc858 00000000 ff1c53d4 ff227e6c 00004c00 ff272660 00000206 (XEN) ff1c9fd6 ff1c9fd6 ffbb8008 00000...

...: 0 (XEN) EIP: e008:[<ff14ad8d>] free_shadow_page+0xd5/0x2ef (XEN) EFLAGS: 00010282 CONTEXT: hypervisor (XEN) eax: ff1a9818 ebx: ffffffff ecx: 00002a03 edx: 00002a03 (XEN) esi: 00000007 edi: ff1bdfac ebp: ff1bdb6c esp: ff1bdb24 (XEN) cr0: 80050033 cr3: 7a93e000 (XEN) ds: e010 es: e010 fs: 0000 gs: 0033 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ff1bdb24: (XEN) ff19d28d ff19d23c 0000018b ff19d23c ff1bdfb4 ff1bdba8 00000082 40000000 (XEN) ffffffff ff1bdfb4 ff1bdb6c ff11ea04 fca88308 00047535 ffbd0080 ffffffff (XEN) 40000000 ffbd6080 ff1bdb9c ff14b...

Hi, I am trying to release domU pages from page_list and xenpage_list after domU shutdown while retaining the rest of the domain information. To achieve this in __domain_finalise_shutdown i call domain_relinquish_resources. This is failing to release pages from page_list for type PGT_l2_page_tables and crashing dom0. To be specific, while testing on mini-os i saw that when

I''m having trouble switching into user mode with my domU kernel -- everytime I call __HYPERVISOR_iret, the hypervisor calls into my kernel via the registered callback handler. None of the bits in the event channel pending arrays are set. If I return via the iret call, the hypervisor immediately calls back into the handler. The user RIP never changes, so it is clearly not making forward

We (Michael Fetterman, George Dunlap and I) have been working over the last while on a full replacement for Xen''s shadow pagetable support. This mail contains some design notes, below; a patch against xen-unstable, giving a snapshot of the current state of the new shadow code, is at http://www.cl.cam.ac.uk/~tjd21/shadow2.patch Comments on both are welcome, although the code is not

...responding. (XEN) Inquiring remote APIC #6... (XEN) ... APIC #6 ID: failed (XEN) ... APIC #6 VERSION: failed (XEN) ... APIC #6 SPIV: failed (XEN) CPU #6 not responding - cannot use it. (XEN) BUG at domain.c:78 (XEN) ----[ Xen-3.0.3-1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e010:[<ffff8300001180f4>] __bug+0x24/0x30 (XEN) RFLAGS: 0000000000010086 CONTEXT: hypervisor (XEN) rax: 0000000000000000 rbx: 000000000000004e rcx: 00000000000015b6 (XEN) rdx: 000000000000000a rsi: 000000000000000a rdi: ffff8300001bf013 (XEN) rbp: ffff830000ffb080 rsp: ffff8300001b7d78...

...6b>] do_IRQ+0xe8/0x299 (XEN) EFLAGS: 00010002 CONTEXT: hypervisor (XEN) eax: 00000001 ebx: 00000001 ecx: ff1c8200 edx: 00000001 (XEN) esi: ff274580 edi: 000000d8 ebp: ff1ebe9c esp: ff1ebe74 (XEN) cr0: 8005003b cr4: 000026f0 cr3: 00bccd00 cr2: b74fd1f4 (XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ff1ebe74: (XEN) 000000d8 ff1a5c20 ff1ebe9c ff208300 00000000 00000014 ff1c83fe 00000000 (XEN) 0000e010 0000e010 00e14143 ff1267e6 ff1ebea8 00000000 0000000a 00000000 (XEN) 00000286 0000001...

...0fffffffd r11: ffff82c4c02254e0^M (XEN) r12: ffff82c4c031a510 r13: ffff82c4c0242ab4 r14: ffff82c4c0242aa0^M (XEN) r15: ffff82c4c0319848 cr0: 000000008005003b cr4: 00000000000426f0^M (XEN) cr3: 00000000bd871000 cr2: 00000000004800d1^M (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008^M (XEN) Xen stack trace from rsp=ffff82c4c02c7d80:^M (XEN) ffff82c4c02c7d90 ffff8300bb5fb000 ffff82c4c02c7da0 ffff82c4c0104703^M (XEN) ffff82c4c02c7dc0 ffff82c4c01ce55f ffff8300bb5fb210 ffff830438087000^M (XEN) ffff82c4c02c7e20 ffff82c4c01ce5de ffff82c400000000 0000000000000003^...

...0200000000000000 r11: 0080000000000000 (XEN) r12: ffff82f602e4b0a0 r13: 00007d0a00000000 r14: 0180000000000000 (XEN) r15: 000000000000017c cr0: 0000000080050033 cr4: 00000000000026f0 (XEN) cr3: 000000019fc73000 cr2: ffff8315ffffffe4 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) Xen stack trace from rsp=ffff8304265c7888: (XEN) 0000000000000001 ffff82c48037a4c0 000000000000017c 000000000000001 (XEN) ffff8301725870b0 ffff830203200000 ffff82f602e4b080 000000000000000 (XEN) 0000000000000001 000000000007f43a 0000000000000000 ffff82c48011548 (XEN) 00...

...l functions use bitopts.h functions to manipulate this member, and on x86_64 these functions use u64 instructions, which will overflow the page boundary, and possibly the end of memory as we see here: (XEN) &page->u.inuse.type_info = 0xffff828402fffffc (XEN) CPU: 0 (XEN) EIP: e010:[<ffff830000129089>] <registers and stack ommitted> (XEN) Pagetable walk from ffff828403000000: (XEN) L4 = 00000000016a5063 (XEN) L3 = 00000000016a6063 (XEN) L2 = 0000000000000000 **************************************** Panic on CPU0: CPU0 FATAL...

Hi Jan, After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times. Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times. (It also stalls on shutdown BTW) I have

...ffff82c48020d040 r11: 0000000000000217 (XEN) r12: 0000000000000149 r13: ffff83023ff7caa0 r14: ffff83023ff2fe10 (XEN) r15: 0000000000000009 cr0: 0000000080050033 cr4: 00000000000026f0 (XEN) cr3: 0000000236c1a000 cr2: 0000003e746f8050 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) Xen stack trace from rsp=ffff83023ff2fd08: (XEN) 800000023510b067 000000000023510b 000883023fecc000 ffff83023ff7cb38 (XEN) ffff83020000c000 ffff83023ff2ff18 ffff83023ff2ff18 00000000000da00c (XEN) 00000000da00c000 000000a23ff2fd68 0000000000000000 00000000da00c000 (XEN)...

...PU: 1 (XEN) EIP: e008:[<ff119c79>] update_queues+0x38e/0x41e (XEN) EFLAGS: 00010092 CONTEXT: hypervisor (XEN) eax: ff1b02b8 ebx: 00000001 ecx: ffbf4000 edx: 00000000 (XEN) esi: ffffffff edi: ffffffff ebp: ffbf9e80 esp: ffbf9dc8 (XEN) cr0: 8005003b cr3: db1e3000 (XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ffbf9dc8: (XEN) ff1988f5 ff1988e8 00000246 ff1988e8 00000000 ff1d6b00 43f0e910 0000008d (XEN) 43f0e910 00000002 ffbf9e60 ff11afea 00000001 00000001 43f0ece2 0000008d (XEN) 2b275387 000003d4 ffbc5180 ffbc5...

There is a BUG_ON() at xen/arch/x86/physdev.c:169 which appears to be dependent upon guest behavior (should close event channel before un-mapping pirq), rather than on internal hypervisor state. In 2.6.18, this likely goes unnoticed because pci_device_shutdown() only calls all the driver shutdown routines. In newer kernels, however, it also calls pci_msi_shutdown() and pci_msix_shutdown(), which

Hello. I can''t start Virtual Machine, have the message: Waiting for root file system ... done. Gave up waiting for root device. Common problems ..... ALERT! /dev/xvda2 does not exist. Dropping to a shell! I have installed Xen 4 in a debian squeeze: # uname -a 2.6.32-5-xen-amd64 #1 SMP Wed Jan 12 05:46:49 UTC 2011 x86_64 GNU/Linux xen-hypervisor-4.0-amd64 4.0.1-2