Fedora 16 Xen Dom0 problem
by Marko Ristola
Hi.
I think that I hit to the following bug on 3.0 kernel on current Fedora 16.
I can't get over it to boot Dom0 under Xen.
Regards,
Marko Ristola
Subject: Re: [Xen-devel] Re: xen 4.1.1 with current linus tree as dom0 [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0
http://lists.xensource.com/archives/html/xen-devel/2011-08/msg00113.html
Here is my console output:
---- snip ----
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[3] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x00040000
[ 0.000000] 0: 0x00100000 -> 0x0017fff0
(XEN) mm.c:907:d0 Error getting mfn 1b78 (pfn 5555555555555555) from L1 entry 8000000001b78465 for l1e_owner=0, pg_owner=0
(XEN) mm.c:4967:d0 ptwr_emulate: could not get_page_from_l1e()
[ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 0.000000] IP: [<ffffffff8100643d>] __xen_set_pte+0x51/0x5b
[ 0.000000] PGD 0
[ 0.000000] Oops: 0003 [#1] SMP
[ 0.000000] CPU 0
[ 0.000000] Modules linked in:
[ 0.000000]
[ 0.000000] Pid: 0, comm: swapper Not tainted 3.1.0-0.rc0.git19.1.fc17.x86_64 #1 FUJITSU SIEMENS A8NE-FM/A8NE-FM
[ 0.000000] RIP: e030:[<ffffffff8100643d>] [<ffffffff8100643d>] __xen_set_pte+0x51/0x5b
[ 0.000000] RSP: e02b:ffffffff81a01da8 EFLAGS: 00010096
[ 0.000000] RAX: 00000000ffffffff RBX: ffff880001e37ff8 RCX: ffffffff829ab000
[ 0.000000] RDX: 0000000010000001 RSI: 8000000001b78465 RDI: ffff880001e37ff8
[ 0.000000] RBP: ffffffff81a01dc8 R08: 0000000000000000 R09: 0000000000007ff0
[ 0.000000] R10: 0000000000007ff0 R11: 0000000000007ff0 R12: 8000000001b78465
[ 0.000000] R13: 0000000040000000 R14: ffffffffffffffff R15: 0000000000000000
[ 0.000000] FS: 0000000000000000(0000) GS:ffffffff81b79000(0000) knlGS:0000000000000000
[ 0.000000] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.000000] CR2: 0000000000000000 CR3: 0000000001a04000 CR4: 0000000000000660
[ 0.000000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 0.000000] DR3: 0000000000000000 DR6: 0000000000000000 DR7: 0000000000000000
[ 0.000000] Process swapper (pid: 0, threadinfo ffffffff81a00000, task ffffffff81a0c020)
[ 0.000000] Stack:
[ 0.000000] ffffffff829ab000 ffffffff829ab000 ffff880001e37ff8 8000000001b78465
[ 0.000000] ffffffff81a01df8 ffffffff81006562 0000000000007ff0 ffffffffff5ff000
[ 0.000000] 8000000001b78465 0000000040000000 ffffffff81a01e08 ffffffff81032db4
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff81006562>] xen_set_pte+0x75/0x95
[ 0.000000] [<ffffffff81032db4>] set_pte+0x10/0x12
[ 0.000000] [<ffffffff810332dd>] set_pte_vaddr_pud+0x3c/0x4b
[ 0.000000] [<ffffffff81033361>] set_pte_vaddr+0x75/0x7a
[ 0.000000] [<ffffffff810367ef>] __native_set_fixmap+0x27/0x2f
[ 0.000000] [<ffffffff81005119>] xen_set_fixmap+0x8c/0xbb
[ 0.000000] [<ffffffff81d54324>] map_vsyscall+0x50/0x55
[ 0.000000] [<ffffffff81d53a72>] setup_arch+0xa7e/0xb2f
[ 0.000000] [<ffffffff814e9583>] ? printk+0x51/0x53
[ 0.000000] [<ffffffff81d4e8a3>] start_kernel+0xe1/0x3ea
[ 0.000000] [<ffffffff81d4e2c4>] x86_64_start_reservations+0xaf/0xb3
[ 0.000000] [<ffffffff81d50f0f>] xen_start_kernel+0x57f/0x586
[ 0.000000] Code: df e8 18 04 03 00 48 89 c7 e8 7c ee ff ff 48 8d 7d e0 48 89 45 e0 4c 89 65 e8 e8 fd f4 ff ff bf 01 00 00 00 e8 a4 f7 ff ff eb 03 <4c> 89 23 58 5a 5b 41 5c 5d c3 55 48 89 e5 41 57 41 56 41 55 41
[ 0.000000] RIP [<ffffffff8100643d>] __xen_set_pte+0x51/0x5b
[ 0.000000] RSP <ffffffff81a01da8>
[ 0.000000] CR2: 0000000000000000
[ 0.000000] ---[ end trace a7919e7f17c0a725 ]---
[ 0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
--- snip ---
12 years, 9 months
Xl and /dev/null
by W. Michael Petullo
The old xm command allowed for a domain to be configured from and
command line using "xm create /dev/null kernel=x ..." Xl does not seem
to support this:
$ sudo xl create /dev/null
libxl: error: libxl_utils.c:328:libxl_read_file_contents /dev/null is not a plain file: Success
Failed to read config file: /dev/null: Inappropriate ioctl for device
Does anyone know the preferred technique to create a domain without an
existing domain configuration file (i.e., purely from the command line)?
--
Mike
:wq
12 years, 9 months