From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Subject: PV-GRUB crashes with FC11 PV guest.
Date: Wed, 16 Sep 2009 11:01:43 -0400 [thread overview]
Message-ID: <20090916150143.GA23612@phenom.dumpdata.com> (raw)
This is with cs 20189. I hadn't tried to bisect builds
to narrow this down.
tst070 login:
Fedora release 11 (Leonidas)
Kernel 2.6.31-xen-01396-g12e8537 on an x86_64 (/dev/hvc0)
tst070 login: [ 407.456209] device vif2.0 entered promiscuous mode
[ 407.470978] eth1: port 2(vif2.0) entering forwarding state
Bootstrapping...
Xen Minimal OS!
start_info: 0xaa0000(VA)
nr_pages: 0x20000
shared_inf: 0x7f810000(MA)
pt_base: 0xaa3000(VA)
nr_pt_frames: 0x9
mfn_list: 0x9a0000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: (hd0,0)/grub/menu.lst
stack: 0x95f9a0-0x97f9a0
MM: Init
_text: 0x0(VA)
_etext: 0x64c8c(VA)
_erodata: 0x89000(VA)
_edata: 0x91b20(VA)
stack start: 0x95f9a0(VA)
_end: 0x99ffa8(VA)
start_pfn: aaf
max_pfn: 20000
Mapping memory range 0xc00000 - 0x20000000
setting 0x0-0x89000 readonly
skipped 0x1000
MM: Initialise page allocator for ba9000(ba9000)-20000000(20000000)
MM: done
Demand map pfns at 20001000-2020001000.
Heap resides at 2020002000-4020002000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x20001000.
Initialising scheduler
Thread "Idle": pointer: 0x2020002050, stack: 0xcc0000
Initialising xenbus
Thread "xenstore": pointer: 0x2020002800, stack: 0xcd0000
Dummy main: start_info=0x97faa0
Thread "main": pointer: 0x2020002fb0, stack: 0xce0000
vbd 768 is hd0
******************* BLKFRONT for device/vbd/768 **********
backend at /local/domain/0/backend/vbd/2/768
[ 407.988989] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
Failed to read /local/domain/0/backend/vbd/2/768/feature-flush-cache.
76389075 sectors of 512 bytes
**************************
Thread "kbdfront": pointer: 0x2020130010, stack: 0xcf0000
******************* FBFRONT for device/vfb/0 **********
******************* KBDFRONT for device/vkbd/0 **********
Failed to read device/vfb/0/backend-id.
Failed to read device/vkbd/0/backend-id.
error writing initialized: ENOENT
GPF rip: 0x54d6b, error_code=0
Thread: main
RIP: e030:[<0000000000054d6b>]
RSP: e02b:0000000000cefcc8 EFLAGS: 00010212
RAX: 0000000000000000 RBX: 0000002020002ff0 RCX: 0000000000091200
RDX: 0000000000001000 RSI: 2f302f6e69616d6f RDI: 00000000000919e0
RBP: 0000000000cefcd8 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000008 R11: 000000000006cd80 R12: 2f302f6e69616d6f
R13: 0000000000cefd8c R14: 0000000000007118 R15: 0000000000cefd30
base is 0xcefcd8 caller is 0x55e2c
base is 0xcefcf8 caller is 0x417bb
base is 0xcefd18 caller is 0x4240c
base is 0xcefdc8 caller is 0x384d
base is 0xcefe78 caller is 0xdb4b
base is 0xcefe88 caller is 0x10eb1
base is 0xceff48 caller is 0x41c3
base is 0xceff58 caller is 0x47928
base is 0xceffe8 caller is 0x33da
cefcb0: c8 fc ce 00 00 00 00 00 2b e0 00 00 00 00 00 00
cefcc0: 6b 4d 05 00 00 00 00 00 6f 6d 61 69 6e 2f 30 2f
cefcd0: 90 fd ce 00 00 00 00 00 f8 fc ce 00 00 00 00 00
cefce0: 2c 5e 05 00 00 00 00 00 cb e6 06 00 00 00 00 00
cefcc0: 6b 4d 05 00 00 00 00 00 6f 6d 61 69 6e 2f 30 2f
cefcd0: 90 fd ce 00 00 00 00 00 f8 fc ce 00 00 00 00 00
cefce0: 2c 5e 05 00 00 00 00 00 cb e6 06 00 00 00 00 00
cefcf0: 90 3d 00 20 20 00 00 00 18 fd ce 00 00 00 00 00
54d50: 55 48 85 f6 48 89 e5 41 54 49 89 f4 53 48 89 fb
54d60: 0f 84 bc 02 00 00 e8 85 1c 00 00 4d 8b 44 24 f8
54d70: 49 8d 54 24 f0 be c0 11 09 00 4c 89 c7 48 83 e7
54d80: fe 48 8d 04 3a 48 8b 48 08 48 83 e1 fc 48 39 05
[ 409.769670] eth1: port 2(vif2.0) entering disabled state
[ 409.777601] eth1: port 2(vif2.0) entering disabled state
The .xm file is rather simple:
disk = [ 'phy:/dev/sda4,hda,w' ]
extra = "(hd0,0)/grub/menu.lst"
kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
memory = 512
name = "FC11"
vif = [ 'mac=00:16:3e:00:00:11, bridge=eth1' ]
If try to use kernel and ramdisk extracted from the disk, the
guest boots up fine:
[ 420.424372] device vif3.0 entered promiscuous mode
[ 420.439713] eth1: port 2(vif3.0) entering forwarding state
mapping kernel into physical memory
about to get started...
(XEN) domain.c:592:d3 Attempt to change CR4 flags 00000660 -> 00000620
[ 421.498616] blkback: ring-ref 8, event-channel 9, protocol 1 (x86_64-abi)
[ 426.849150] alloc irq_desc for 119 on node 0
[ 426.849623] alloc kstat_irqs on node 0
[ 431.220055] vif3.0: no IPv6 routers present
(XEN) traps.c:2264:d3 Domain attempted WRMSR 000000000000008b from 00000017:00000000 to 00000000:00000000.
next reply other threads:[~2009-09-16 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 15:01 Konrad Rzeszutek Wilk [this message]
2009-09-17 4:53 ` PV-GRUB crashes with FC11 PV guest Jeremy Fitzhardinge
2009-09-17 4:56 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090916150143.GA23612@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.