Re: Dom0 PAE panic when starting xend

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Wed, Mar 11, 2009 at 10:05:46AM +0100, Christoph Egger wrote:
> Yes, the machine boots and I can start xend.
> Now when I want to start a 32bit PAE PV guest, python crashes
> before xend evaluates the guest config file.
> A ktrace is this:
> 
>    370      8 python2.5 CALL  mlock(0xb9bfc000,0x1000)
>    370      8 python2.5 RET   mlock 0
>    370      8 python2.5 CALL  ioctl(0x17,_IOWR('P',0,0x1c),0xb9bfc760)

This is IOCTL_PRIVCMD_HYPERCALL

>    370      8 python2.5 GIO   fd 23 wrote 28 bytes
>        "#\0\0\0\M-T\M-F\M-?\M-9\M-@u\M-g\M-:,\M-%G\M-:\M^E\^Rr\M-;`\M-/|\M-;
> \0\0\0\0"
>    370      8 python2.5 GIO   fd 23 read 28 bytes
>        "#\0\0\0\M-T\M-F\M-?\M-9\M-@u\M-g\M-:,\M-%G\M-:\M^E\^Rr\M-;`\M-/|\M-;
> \0\0\0\0"
>    370      8 python2.5 RET   ioctl 0
>    370      8 python2.5 CALL  munlock(0xb9bfc000,0x1000)
>    370      8 python2.5 RET   munlock 0
>    370      8 python2.5 CALL  mlock(0xb9bfc000,0x1000)
>    370      8 python2.5 RET   mlock 0
>    370      8 python2.5 CALL  ioctl(0x17,_IOWR('P',0,0x1c),0xb9bfc6b8)

This one too

>    370      8 python2.5 GIO   fd 23 wrote 28 bytes
>        "#\0\0\0\M-|\M-F\M-?\M-9\0\M-p\M-$\M-:\^B\0\0\0\M-D\M-aE\M-:
> \^P\0\0\0\M-X\^Ai\M-;"
>    370      8 python2.5 GIO   fd 23 read 28 bytes
>        "#\0\0\0\M-|\M-F\M-?\M-9\0\M-p\M-$\M-:\^B\0\0\0\M-D\M-aE\M-:
> \^P\0\0\0\0\0\0\0"
>    370      8 python2.5 RET   ioctl 0
>    370      8 python2.5 CALL  munlock(0xb9bfc000,0x1000)
>    370      8 python2.5 RET   munlock 0
>    370      8 python2.5 PSIG  SIGSEGV SIG_DFL: code=SEGV_MAPERR, addr=0x55, 
> trap=6)
>    370      7 python2.5 RET   accept -1 errno 4 Interrupted system call
>    370      6 python2.5 RET   accept -1 errno 4 Interrupted system call
>    370      5 python2.5 RET   read -1 errno 4 Interrupted system call
>    370      3 python2.5 RET   __select50 -1 errno 4 Interrupted system call
>    370      2 python2.5 RET   accept -1 errno 4 Interrupted system call
>    370      1 python2.5 RET   __select50 -1 errno 4 Interrupted system call
>    370      4 python2.5 RET   ___lwp_park50 -1 errno 4 Interrupted system call
> 
> I also traced the python execution path and it looks like something
> during a process fork(2) goes wrong. Sounds like there are some
> PAE bugs in our pmap.

Do you see any message from xen in xm dmesg or serial console ?

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--