xen-devel
RE: [Xen-devel] Daily Xen Build
David,
I am able to boot Xen and Dom0 on my x86_64 Dell and ES7000 box running
SLES9 SP2. When I try to bring up DomUs I run into Bug 176. Only
difference is that now I see a lot of the following messages during the
DomU boot.
xen_net: Initialising virtual ethernet driver.
xen_net (probe_interfaces:1304) >
xen_net (probe_interfaces:1307) > wait_i=0
xen_net (probe_interfaces:1310) > schedule_timeout...
xen_net (probe_interfaces:1307) > wait_i=1
xen_net (probe_interfaces:1310) > schedule_timeout...
xen_net (probe_interfaces:1307) > wait_i=2
Aravindh
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of David F Barrera
> Sent: Wednesday, August 24, 2005 11:16 AM
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] Daily Xen Build
>
>
> August 24, 2005, using HG source as of:
>
> changeset: 6375:603f55eaa690ef8d47e54bdb57e20fb3266d8f56
> tag: tip
> user: kaf24@xxxxxxxxxxxxxxxxxxxx
> date: Wed Aug 24 05:48:24 2005
> summary: Initialise syscall32 vsyscall page early, as it may be
> needed
>
>
> x86_32 (no PAE support)
> =======================
>
> SLES 9 SP2 on IBM xSeries 235 (512M RAM), 335 (2GB RAM) and FC3 on IBM
> ThinkCentre (1GB RAM)
>
> ISSUE:
>
> Creating DomU causes Dom0 to crash
> * SLES 9, RHEL 4 and FC3 boxen, PAE and non-PAE.
> * Creating DomU without networking does NOT cause crash.
> * Bugzilla #188
>
> 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, FC4, and RHEL 4 IBM xSeries 305, 335, and IBM ThinkCentre
>
>
> ISSUES:
> Creating DomU with networking crashes Dom0, Bugzilla #188
>
> DomU boot crashes Dom0, Bugzilla #168
> * Workaround: use swiotlb=force as a kernel parameter when
> booting dom0
> * DomU boots up normally if using swiotlb=force
>
> X 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 (severe) booting up Dom0 on x86_64 platforms (SLES 9 and FC4)
>
> ISSUES:
>
> Bugzilla Bug 187- Dom0 will not boot on x86_64 machines, SLES 9 SP2
and
> FC4.
> * Unable to handle kernel paging request at ffff800000373fc0 RIP:
> <ffffffff80120499>{__ioremap+105}
>
>
> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|