Dear Keir, I've got the boot message of Xen4.0 on fedora11. It is as following. _ __ _ _ ___ ___ \ \/ /___ _ __ | || | / _ \ / _ \ \ // _ \ '_ \ | || |_| | | | | | | / \ __/ | | | |__ _| |_| | |_| | /_/\_\___|_| |_| |_|(_)___(_)___/ (XEN) Xen version 4.0.0 (root@) (gcc 版本 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) ) Thu Apr 29 09:41:18 CST 2010 (XEN) Latest ChangeSet: unavailable (XEN) Command line: console=com1,vga com1=9600,8n1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009a800 (usable) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000cfdffc00 (usable) (XEN) 00000000cfdffc00 - 00000000cfe53c00 (ACPI NVS) (XEN) 00000000cfe53c00 - 00000000cfe55c00 (ACPI data) (XEN) 00000000cfe55c00 - 00000000d0000000 (reserved) (XEN) 00000000e0000000 - 00000000f0000000 (reserved) (XEN) 00000000fec00000 - 00000000fed00400 (reserved) (XEN) 00000000fed20000 - 00000000feda0000 (reserved) (XEN) 00000000fee00000 - 00000000fef00000 (reserved) (XEN) 00000000ffb00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000128000000 (usable) (XEN) System RAM: 3936MB (4031228kB) (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL ) (XEN) ACPI: XSDT 000FC7CB, 009C (r1 DELL B10K 15 ASL 61) (XEN) ACPI: FACP 000FC8FB, 00F4 (r3 DELL B10K 15 ASL 61) (XEN) ACPI: DSDT FFE9CFF8, 54AD (r1 DELL dt_ex 1000 INTL 20050624) (XEN) ACPI: FACS CFDFFC00, 0040 (XEN) ACPI: SSDT FFEA25C4, 00AA (r1 DELL st_ex 1000 INTL 20050624) (XEN) ACPI: APIC 000FC9EF, 0092 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: BOOT 000FCA81, 0028 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: ASF! 000FCAA9, 0096 (r32 DELL B10K 15 ASL 61) (XEN) ACPI: MCFG 000FCB3F, 003E (r1 DELL B10K 15 ASL 61) (XEN) ACPI: HPET 000FCB7D, 0038 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: TCPA 000FCDD9, 0032 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: DMAR 000FCE0B, 00D8 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: SLIC 000FCBB5, 0176 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: SSDT CFDFFC40, 01B7 (r1 DpgPmm Cpu0Ist 11 INTL 20050624) (XEN) ACPI: SSDT CFE00049, 01B7 (r1 DpgPmm Cpu1Ist 11 INTL 20050624) (XEN) ACPI: SSDT CFE00452, 01B7 (r1 DpgPmm Cpu2Ist 11 INTL 20050624) (XEN) ACPI: SSDT CFE0085B, 01B7 (r1 DpgPmm Cpu3Ist 11 INTL 20050624) (XEN) ACPI: SSDT CFE00C64, 0190 (r1 DpgPmm CpuPm 10 INTL 20050624) (XEN) Xen heap: 8MB (8852kB) (XEN) Domain heap initialised (XEN) Processor #0 7:7 APIC version 20 (XEN) Processor #1 7:7 APIC version 20 (XEN) Processor #2 7:7 APIC version 20 (XEN) Processor #3 7:7 APIC version 20 (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2660.072 MHz processor. (XEN) Initing memory sharing. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs disabled. (XEN) HVM: VMX enabled (XEN) xsave_init: cpu0: cntxt_max_size: 0x240 and states: 00000000:00000003 (XEN) xsave_init: using cntxt_size: 0x240 and states: 00000000:00000003 (XEN) Intel VT-d Snoop Control not supported. (XEN) Intel VT-d DMA Passthrough not supported. (XEN) Intel VT-d Queued Invalidation not supported. (XEN) Intel VT-d Interrupt Remapping not supported. (XEN) I/O virtualisation enabled (XEN) I/O virtualisation for PV guests disabled (XEN) xsave_init: cpu1: cntxt_max_size: 0x240 and states: 00000000:00000003 (XEN) xsave_init: cpu2: cntxt_max_size: 0x240 and states: 00000000:00000003 (XEN) xsave_init: cpu3: cntxt_max_size: 0x240 and states: 00000000:00000003 (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) checking TSC synchronization across 4 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 4 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 32-bit, PAE, lsb (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0xbfb000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (960235 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0400000->c0bfb000 (XEN) Init. ramdisk: c0bfb000->c1329e00 (XEN) Phys-Mach map: c132a000->c16dbbac (XEN) Start info: c16dc000->c16dc47c (XEN) Page tables: c16dd000->c16ee000 (XEN) Boot stack: c16ee000->c16ef000 (XEN) TOTAL: c0000000->c1800000 (XEN) ENTRY ADDRESS: c098d000 (XEN) Dom0 has maximum 4 VCPUs (XEN) Scrubbing Free RAM: .done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 136kB init memory. mapping kernel into physical memory about to get started... (XEN) traps.c:2309:d0 Domain attempted WRMSR 000002ff from 00000000:00000c06 to 00000000:00000000. (XEN) traps.c:2309:d0 Domain attempted WRMSR 00000277 from 00000501:00070406 to 00070106:00070106. My grub.conf is: title Xen(2.6.31.13) root (hd0,10) kernel /boot/xen.gz console=com1,vga com1=9600,8n1 module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset module /boot/initrd-2.6.31.13.img Would you give me more suggestions. Thank you. Best wishes. gavin 2010/4/28 Keir Fraser > Some other options: add noreboot to Xen command line and see if anything > else does get printed before reboot. And/or connect a serial line and have > Xen log to serial console and see if any other diagnostic messages are > visible from that. > > -- Keir > > On 28/04/2010 06:38, "Keir Fraser" wrote: > > > Probably something to do with dom0 building then. I would try a different > > dom0 kernel just to see if that works better. But probably there is a bug > > here that a developer will need to be able to reproduce to fix. > > > > -- Keir > > > > On 28/04/2010 14:35, "BEI GUAN" wrote: > > > >> Hello Keir, > >> > >> Thank you very much for your reply. As you said, I just change my > grub.conf > >> as > >> following. But it also did not work. The screen just stopped when > message > >> "(XEN) Dom0 has maximum 4 VCPUs" was printed, which is just before the > >> message > >> "Scrubbing Free RAM:". And then system reboot. > >> > >> title Xen-4.0 (Linux kernel 2.6.31.13) > >> root (hd0,10) > >> kernel /boot/xen-4.0.gz no-bootscrub dom0_mem=1024M loglvl=all > >> guest_loglvl=all > >> module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset > >> module /boot/initrd-2.6.31.13.img > >> > >> Thank you. Best wishes. > >> > >> Gavin Guan > >> > >> > >> > >> > >> 2010/4/28 Keir Fraser > >>> Do things work if you add no-bootscrub to the Xen command line? > >>> > >>> -- Keir > >>> > >>> On 28/04/2010 13:49, "BEI GUAN" wrote: > >>> > >>>> Dear Pasi, > >>>> > >>>> I have the same problem as ilish had when I installed xen 4.0 on > fedora 11 > >>>> today. I rebooted the Xen. The screen just stopped at "Scrubbing Free > >>>> RAM:", > >>>> and then the computer reboot again. My grub.conf as following. > >>>> > >>>> title Xen-4.0 (Linux kernel 2.6.31.13) > >>>> root (hd0,10) > >>>> kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all > >>>> module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset > >>>> module /boot/initrd-2.6.31.13.img > >>>> > >>>> I also made "root=/dev/sda11" and "root=LABEL=/" and to try. However, > I > >>>> still > >>>> doesn't work. Your any reply is appreciated. > >>>> > >>>> Thank you very much. > >>>> > >>>> Gavin Guan > >>>> > >>>> > >>>> > >>>> > >>>> 2010/4/23 Pasi Kärkkäinen > >>>>> On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish wrote: > >>>>>> Hi everyone, > >>>>>> > >>>>>> I am working on a project whose goal is evaluating the > performance of > >>>>>> the > >>>>>> vTPM Manager. For this project I am using Xen 4.1, Kernel > 2.6.31.13 > >>>>>> with > >>>>>> Fedora11. I I finished all installation and configuration parts. > Now I > >>>>>> need to boot the system with Xen but while booting, it is > freezing at > >>>>>> the > >>>>>> step "scrubbing free ram". What can be cause this problem and how > can > >>>>>> I > >>>>>> figure it out? I really appreciate if you can help me. > >>>>>> > >>>>> > >>>>> Please paste your grub.conf. > >>>>> > >>>>> Also please check this wiki page: > >>>>> http://wiki.xensource.com/xenwiki/XenSerialConsole > >>>>> > >>>>> and: > >>>>> http://wiki.xensource.com/xenwiki/XenParavirtOps > >>>>> > >>>>> -- Pasi > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Xen-devel mailing list > >>>>> Xen-devel@lists.xensource.com > >>>>> http://lists.xensource.com/xen-devel > >>>> > >>>> > >>> > >>> > >> > >> > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > >