[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Daily Xen Builds
August 23, 2005, using HG source as of: changeset: 6329:3889ca17ff5867d5efa19eaf25463d59dd6c8c7d tag: tip user: kaf24@xxxxxxxxxxxxxxxxxxxx date: Tue Aug 23 07:30:35 2005 summary: phys_to_machine_mapping array is not an array of longs. x86_32 (no PAE support) SLES 9 SP2 on IBM xSeries 235 (512M RAM) and FC3 on IBM ThinkCentre Builds with workaround* and boots without problems Able to create domU Ran LTP on both dom0 and domU No problems observed ISSUE: * Build break on SLES 9 , Bugzilla #179 * Missing -lcurses * *Workaround is to change LD_LIBS in tools/xenstat/xentop/Makefile to include -lncurses instead of -lcurses Last good changeset for x86_32, non-PAE: *with workaround changeset: 6329:3889ca17ff5867d5efa19eaf25463d59dd6c8c7d tag: tip user: kaf24@xxxxxxxxxxxxxxxxxxxx date: Tue Aug 23 07:30:35 2005 summary: phys_to_machine_mapping array is not an array of longs. x86_32 (PAE) SLES 9 SP2, FC3, and RHEL 4 IBM xSeries 305, and IBM ThinkCentre Dom0 boots without problems; however, We are able to create DomUs ONLY when using *swiotlb=force* as a kernel parameter for dom0 Ran LTP on both Dom0 and DomU ISSUES: DomU boot crashes Dom0, Bugzilla #168 * Workaround: use swiotlb=force as a kernel parameter when booting dom0 * DomU boots up normally if using swiotlb=forceX server will not come up on Dom0 on a FC3 box when Xen built with PAE 'on', Bugzilla #137 Networking issue on FC3 when Xen built with PAE, Bugzilla #173 * DomU unable to get dhcp address * tcpdump shows lots of networking activity being 'heard' * ping from external box shows corrupt packets * DomU has no trouble getting IP address when Xen built non-PAE X server does not come up on FC3 box with PAE support, Bugzilla #137 * X server comes up normally when xen built without PAE support Last good changeset for x86_32, PAE: changeset: 6329:3889ca17ff5867d5efa19eaf25463d59dd6c8c7d tag: tip user: kaf24@xxxxxxxxxxxxxxxxxxxx date: Tue Aug 23 07:30:35 2005 summary: phys_to_machine_mapping array is not an array of longs. x86_64 (SLES 9 SP2 and FC4 on IBM HS20 Blades) Problems when booting up DomU on x86_64 platforms (SLES 9 and FC4) ISSUES: Bugzilla #176 - x86_64 - *UNABLE TO BOOT DOMU* * VFS: Cannot open root device "sdb2" or unknown-block (0,0) * Please append a correct "root=" boot option * Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) * Bugzilla #169 - x86_64 - Unable to handle kernel paging request at ffff8000003e0000 RIP: <ffffffff8015d16c>{unmap_vmas+1084} Last good changeset for x86_64: changeset: 6228:1a94949348ff52863b9fbef4eaf102c7e46a345d tag: tip user: kaf24@xxxxxxxxxxxxxxxxxxxx date: Thu Aug 18 05:41:55 2005 Summary: Fix range_straddles_boundary() check to exclude regions that -- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |