[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-ia64-devel] Status on booting multiple domains on RHEL4
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
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |