Re: [Xen-ia64-devel] Status on booting multiple domains on RHEL4

[Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>]

Hi Dan and All,

I'm trying to boot DomainU on RHEL4.
I cannot also boot DomainU.

I tried to do the following way.

After build and Dom0 boot
1. cp linux-2.6.12-xenU/vmlinux /boot/vmlinux-2.6.12-xenU
2. cd linux-2.6.12-xenU
3. lomount -t ext2 -diskimage /root/xenia64.img -partition 2 /mnt
   (xenia64.img is RHEL3 domain image.)
4. vi /etc/xen/rhel3
   kernel = "/boot/vmlinux-2.6.12-xenU"
   memory = 512
   name = "rhel3"
   nics=0
   disk = [ 'phy:loop0,hda1,w' ]
   root = "/dev/hda1 ro"
   extra = "1"
5. xm create -c rhel3
6. Boot DomainU and Stop the below
   RAMDISK: Couldn't find valid RAM disk image starting at 0.
7. and xm dmesg is the bellow
======================
(XEN) translate_domain_pte: bad mpa=0000000027be4000 (> 
0000000020000000),vadr=e000000027be4000,pteval=0010000027be4661,itir=0000000000000760
(XEN) lookup_domain_mpa: bad mpa 0000000027be4000 (> 0000000020000000
(XEN) translate_domain_pte: bad mpa=0000000027be8000 (> 
0000000020000000),vadr=e000000027be8000,pteval=0010000027be8661,itir=0000000000000760
(XEN) lookup_domain_mpa: bad mpa 0000000027be8000 (> 0000000020000000
(XEN) translate_domain_pte: bad mpa=0000000027bec000 (> 
0000000020000000),vadr=e000000027bec000,pteval=0010000027bec661,itir=0000000000000760
(XEN) lookup_domain_mpa: bad mpa 0000000027bec000 (> 0000000020000000
(XEN) translate_domain_pte: bad mpa=0000000027bf0000 (> 
0000000020000000),vadr=e000000027bf0000,pteval=0010000027bf0661,itir=0000000000000760
(XEN) lookup_domain_mpa: bad mpa 0000000027bf0000 (> 0000000020000000
(XEN) translate_domain_pte: bad mpa=0000000027bf4000 (> 
0000000020000000),vadr=e000000027bf4000,pteval=0010000027bf4661,itir=0000000000000760
(XEN) lookup_domain_mpa: bad mpa 0000000027bf4000 (> 0000000020000000
(XEN) translate_domain_pte: bad mpa=0000000027bf8000 (> 
0000000020000000),vadr=e000000027bf8000,pteval=0010000027bf8661,itir=0000000000000760
(XEN) lookup_domain_mpa: bad mpa 0000000027bf8000 (> 0000000020000000
(XEN) translate_domain_pte: bad mpa=0000000027bfc000 (> 
0000000020000000),vadr=e000000027bfc000,pteval=0010000027bfc661,itir=0000000000000760
(XEN) lookup_domain_mpa: bad mpa 0000000027bfc000 (> 0000000020000000
(XEN) translate_domain_pte: bad mpa=0000010000000044 (> 
0000000020000000),vadr=e000010000000044,pteval=0010010000000661,itir=0000000000000760
(XEN) 4translate_domain_pte: bad mpa=000001000000004c (> 
0000000020000000),vadr=e00001000000004c,pteval=0010010000000661,itir=0000000000000760
(XEN) +04+04+04+0
=======================
I think this error is the same as Dan.

Is this error concerned about "[Xen-ia64-devel] Problem with xen-
unstable cset 7937 (grant tabletransfer fix)" , Dan?

Could anyone advice me?

Best Regards,

Akio Takebe

>With tip, I am able to build and boot dom0 and domU on RHEL3
>with no changes.  When I build for RHEL4 (using Akio's recipe)
>and build dom0 using the generic config file, it boots dom0
>fine but when I try to boot domU, I have lots of problems.
>Has anyone else booted a domU on RHEL4?  
>
>If we can get these resolved so it is possible to boot domU
>cleanly on RHEL4, perhaps we can finally move the development/test
>environment to RHEL4.
>
>I would appreciate it if others would see if they can duplicate
>the problem and perhaps try to track it down further.
>
>P.S. Just in case, I tried moving /lib/tls to /lib/tls.bak
>but saw no difference.
>
>======
>
>First, the call to ia64_pal_cache_flush in arch_set_info_guest
>crashes dom0.  By commenting this out, I get further, to
>
>       Running on Xen! start_info_pfn=0x3ffd lags=0x0
>       xen-event-channel using ir1 233
>       vcpu_get_lid: ...
>
>then a sequence of many many reports of bad mpa from
>translate_domain_pte and lookup_domain_mpa (harmless?).
>The mpa's seem to be increasing by 16K for each one.
>
>Then I get:
>
>       Unable to handle kernel paging request at virtual address
>a0007fffffddb018
>       loop0[3831]: Oops 8813272891392 [1]
>       Modules linked in:
>
>Then a register dump of comm=loop0 with ip at lo_read_actor.
>
>The console has just printed:
>
>       RAMDISK: Couldn't find valid RAM disk image starting at 0.
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel