Trying to get Xen going on Fedora 9. Xen was installed from the
distro RPMs. Xen version is 3.2.0 and the linux-xen version is
2.6.25.3.
Xen seems to come up fine, but the system just hangs at the
point where booting of Dom0 should start. There is absolutely
no output from Dom0.
I configured Xen to log to a serial port and captured the output
below. Any suggestions on how to continue debugging this are
welcome.
MV
-----
__ __ _____ ____ ___
\ \/ /___ _ __ |___ / |___ \ / _ \
\ // _ \ ''_ \ |_ \ __) || | | |
/ \ __/ | | | ___) | / __/ | |_| |
/_/\_\___|_| |_| |____(_)_____(_)___/
(XEN) Xen version 3.2.0 (mockbuild@[unknown]) (gcc version 4.3.0
20080428 (Red Hat 4.3.0-8) (GCC) ) Tue May 13 11:43:44 EDT 2008
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: com1=115200,8n1 console=com1 conswitch=ax
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 2 seconds
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e6000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007ffc0000 (usable)
(XEN) 000000007ffc0000 - 000000007ffce000 (ACPI data)
(XEN) 000000007ffce000 - 000000007fff0000 (ACPI NVS)
(XEN) 000000007fff0000 - 0000000080000000 (reserved)
(XEN) 00000000ffb80000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096508kB)
(XEN) Xen heap: 9MB (10068kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) PAE enabled, limit: 16 GB
(XEN) Processor #0 15:3 APIC version 20
(XEN) Processor #1 15:3 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, 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 3000.212 MHz processor.
(XEN) CPU0: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 04
(XEN) Booting processor 1/1 eip 8c000
(XEN) CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 04
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) Platform timer overflows in 234 jiffies.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Brought up 2 CPUs
(XEN) AMD IOMMU: Disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x400000 memsz=0x320000
(XEN) elf_parse_binary: phdr: paddr=0x720000 memsz=0x145000
(XEN) elf_parse_binary: memory: 0x400000 -> 0x865000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xc0000000
(XEN) elf_xen_parse_note: ENTRY = 0xc075e000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xc07ab000
(XEN) elf_xen_parse_note: FEATURES = "!
writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_addr_calc_check: ELF_PADDR_OFFSET unset, using 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xc0000000
(XEN) elf_paddr_offset = 0x0
(XEN) virt_offset = 0xc0000000
(XEN) virt_kstart = 0xc0400000
(XEN) virt_kend = 0xc0865000
(XEN) virt_entry = 0xc075e000
(XEN) Xen kernel: 32-bit, PAE, lsb
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0x865000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (477028
pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0400000->c0865000
(XEN) Init. ramdisk: c0865000->c0e7c400
(XEN) Phys-Mach map: c0e7d000->c1056d90
(XEN) Start info: c1057000->c1057474
(XEN) Page tables: c1058000->c1067000
(XEN) Boot stack: c1067000->c1068000
(XEN) TOTAL: c0000000->c1400000
(XEN) ENTRY ADDRESS: c075e000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xc0400000 -> 0xc0720000
(XEN) elf_load_binary: phdr 1 at 0xc0720000 -> 0xc07a7d08
(XEN) Initrd len 0x617400, start at 0xc0865000
(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) *** Serial input -> Xen (type ''CTRL-a'' three times to
switch input to DOM0)
(XEN) Freed 96kB init memory.
(XEN) traps.c:1946:d0 Domain attempted WRMSR 00000400 from
00000000:0000ffff to ffffffff:ffffffff.
(XEN) traps.c:1946:d0 Domain attempted WRMSR 00000404 from
00000000:00018000 to ffffffff:ffffffff.
(XEN) traps.c:1946:d0 Domain attempted WRMSR 00000408 from
00000000:00000080 to ffffffff:ffffffff.
(XEN) traps.c:1946:d0 Domain attempted WRMSR 0000040c from
00000000:0000007e to ffffffff:ffffffff.
(XEN) traps.c:1946:d0 Domain attempted WRMSR 00000400 from
00000000:0000ffff to ffffffff:ffffffff.
(XEN) traps.c:1946:d0 Domain attempted WRMSR 00000404 from
00000000:00018000 to ffffffff:ffffffff.
(XEN) traps.c:1946:d0 Domain attempted WRMSR 00000408 from
00000000:00000080 to ffffffff:ffffffff.
(XEN) traps.c:1946:d0 Domain attempted WRMSR 0000040c from
00000000:0000007e to ffffffff:ffffffff.
(XEN) traps.c:1838:d0 Attempt to change unmodifiable CR0 flags.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Saturday June 14 2008 02:37:26 pm Martin Vuille wrote:> Trying to get Xen going on Fedora 9. Xen was installed from the > distro RPMs. Xen version is 3.2.0 and the linux-xen version is > 2.6.25.3. > > Xen seems to come up fine, but the system just hangs at the > point where booting of Dom0 should start. There is absolutely > no output from Dom0.Yep. F9 is in transition, and does not currently support dom0. See: http://fedoraproject.org/wiki/Features/XenPvopsDom0 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
The Fedora 9 Xen RPMs can only be run as a DomU. You will have to use another distro for Dom0. On Sat, 2008-06-14 at 14:37 -0400, Martin Vuille wrote:> Trying to get Xen going on Fedora 9. Xen was installed from the > distro RPMs. Xen version is 3.2.0 and the linux-xen version is > 2.6.25.3. > > Xen seems to come up fine, but the system just hangs at the > point where booting of Dom0 should start. There is absolutely > no output from Dom0. > > I configured Xen to log to a serial port and captured the output > below. Any suggestions on how to continue debugging this are > welcome. > > MV > > ----- > __ __ _____ ____ ___ > \ \/ /___ _ __ |___ / |___ \ / _ \ > \ // _ \ ''_ \ |_ \ __) || | | | > / \ __/ | | | ___) | / __/ | |_| | > /_/\_\___|_| |_| |____(_)_____(_)___/ > > (XEN) Xen version 3.2.0 (mockbuild@[unknown]) (gcc version 4.3.0 > 20080428 (Red Hat 4.3.0-8) (GCC) ) Tue May 13 11:43:44 EDT 2008 > (XEN) Latest ChangeSet: unavailable > (XEN) Command line: com1=115200,8n1 console=com1 conswitch=ax > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 2 seconds > (XEN) Disc information: > (XEN) Found 2 MBR signatures > (XEN) Found 2 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009fc00 (usable) > (XEN) 000000000009fc00 - 00000000000a0000 (reserved) > (XEN) 00000000000e6000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 000000007ffc0000 (usable) > (XEN) 000000007ffc0000 - 000000007ffce000 (ACPI data) > (XEN) 000000007ffce000 - 000000007fff0000 (ACPI NVS) > (XEN) 000000007fff0000 - 0000000080000000 (reserved) > (XEN) 00000000ffb80000 - 0000000100000000 (reserved) > (XEN) System RAM: 2047MB (2096508kB) > (XEN) Xen heap: 9MB (10068kB) > (XEN) Domain heap initialised: DMA width 32 bits > (XEN) PAE enabled, limit: 16 GB > (XEN) Processor #0 15:3 APIC version 20 > (XEN) Processor #1 15:3 APIC version 20 > (XEN) IOAPIC[0]: apic_id 2, 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 3000.212 MHz processor. > (XEN) CPU0: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 04 > (XEN) Booting processor 1/1 eip 8c000 > (XEN) CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 04 > (XEN) Total of 2 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) Platform timer overflows in 234 jiffies. > (XEN) Platform timer is 3.579MHz ACPI PM Timer > (XEN) Brought up 2 CPUs > (XEN) AMD IOMMU: Disabled > (XEN) *** LOADING DOMAIN 0 *** > (XEN) elf_parse_binary: phdr: paddr=0x400000 memsz=0x320000 > (XEN) elf_parse_binary: phdr: paddr=0x720000 memsz=0x145000 > (XEN) elf_parse_binary: memory: 0x400000 -> 0x865000 > (XEN) elf_xen_parse_note: GUEST_OS = "linux" > (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6" > (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" > (XEN) elf_xen_parse_note: VIRT_BASE = 0xc0000000 > (XEN) elf_xen_parse_note: ENTRY = 0xc075e000 > (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xc07ab000 > (XEN) elf_xen_parse_note: FEATURES = "! > writable_page_tables|pae_pgdir_above_4gb" > (XEN) elf_xen_parse_note: PAE_MODE = "yes" > (XEN) elf_xen_parse_note: LOADER = "generic" > (XEN) elf_xen_addr_calc_check: ELF_PADDR_OFFSET unset, using 0x0 > (XEN) elf_xen_addr_calc_check: addresses: > (XEN) virt_base = 0xc0000000 > (XEN) elf_paddr_offset = 0x0 > (XEN) virt_offset = 0xc0000000 > (XEN) virt_kstart = 0xc0400000 > (XEN) virt_kend = 0xc0865000 > (XEN) virt_entry = 0xc075e000 > (XEN) Xen kernel: 32-bit, PAE, lsb > (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0x865000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (477028 > pages to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: c0400000->c0865000 > (XEN) Init. ramdisk: c0865000->c0e7c400 > (XEN) Phys-Mach map: c0e7d000->c1056d90 > (XEN) Start info: c1057000->c1057474 > (XEN) Page tables: c1058000->c1067000 > (XEN) Boot stack: c1067000->c1068000 > (XEN) TOTAL: c0000000->c1400000 > (XEN) ENTRY ADDRESS: c075e000 > (XEN) Dom0 has maximum 2 VCPUs > (XEN) elf_load_binary: phdr 0 at 0xc0400000 -> 0xc0720000 > (XEN) elf_load_binary: phdr 1 at 0xc0720000 -> 0xc07a7d08 > (XEN) Initrd len 0x617400, start at 0xc0865000 > (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) *** Serial input -> Xen (type ''CTRL-a'' three times to > switch input to DOM0) > (XEN) Freed 96kB init memory. > (XEN) traps.c:1946:d0 Domain attempted WRMSR 00000400 from > 00000000:0000ffff to ffffffff:ffffffff. > (XEN) traps.c:1946:d0 Domain attempted WRMSR 00000404 from > 00000000:00018000 to ffffffff:ffffffff. > (XEN) traps.c:1946:d0 Domain attempted WRMSR 00000408 from > 00000000:00000080 to ffffffff:ffffffff. > (XEN) traps.c:1946:d0 Domain attempted WRMSR 0000040c from > 00000000:0000007e to ffffffff:ffffffff. > (XEN) traps.c:1946:d0 Domain attempted WRMSR 00000400 from > 00000000:0000ffff to ffffffff:ffffffff. > (XEN) traps.c:1946:d0 Domain attempted WRMSR 00000404 from > 00000000:00018000 to ffffffff:ffffffff. > (XEN) traps.c:1946:d0 Domain attempted WRMSR 00000408 from > 00000000:00000080 to ffffffff:ffffffff. > (XEN) traps.c:1946:d0 Domain attempted WRMSR 0000040c from > 00000000:0000007e to ffffffff:ffffffff. > (XEN) traps.c:1838:d0 Attempt to change unmodifiable CR0 flags. > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
jim burns <jim_burn@bellsouth.net> wrote in news:200806141549.28914.jim_burn@bellsouth.net:> On Saturday June 14 2008 02:37:26 pm Martin Vuille wrote: >> Trying to get Xen going on Fedora 9. Xen was installed from >> the distro RPMs. Xen version is 3.2.0 and the linux-xen >> version is 2.6.25.3. >> >> Xen seems to come up fine, but the system just hangs at the >> point where booting of Dom0 should start. There is >> absolutely no output from Dom0. > > Yep. F9 is in transition, and does not currently support > dom0. See: > > http://fedoraproject.org/wiki/Features/XenPvopsDom0Aha! Mystery explained. Thanks for the heads-up guys. Never occurred to me to check that :-( MV _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Yep. F9 is in transition, and does not currently support > > dom0. See: > > > > http://fedoraproject.org/wiki/Features/XenPvopsDom0 > > Aha! Mystery explained. Thanks for the heads-up guys. > > Never occurred to me to check that :-(Presumably the linux-xen is provided just for use in domUs. In the meantime you could probably try using a dom0-capable linux-xen from F8, for instance (or build your own). Cheers, Mark -- Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wednesday June 18 2008 06:10:27 pm Mark Williamson wrote:> Presumably the linux-xen is provided just for use in domUs.Correct.> In the > meantime you could probably try using a dom0-capable linux-xen from F8, for > instance (or build your own).You would have trouble using an F8 kernel-xen in an F9 install - it would get removed on every (2nd) kernel-xen update. You would probably need to copy the /boot & /lib/modules files for that kernel, and copy them back after the 2nd update removes the F8 kernel-xen, so that it is not in the rpm database anymore. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
jim burns <jim_burn@bellsouth.net> wrote in news:200806181847.53982.jim_burn@bellsouth.net:> On Wednesday June 18 2008 06:10:27 pm Mark Williamson wrote: >> Presumably the linux-xen is provided just for use in domUs. > Correct. > >> In the >> meantime you could probably try using a dom0-capable >> linux-xen from F8, for instance (or build your own). > > You would have trouble using an F8 kernel-xen in an F9 > install - it would get removed on every (2nd) kernel-xen > update. You would probably need to copy the /boot & > /lib/modules files for that kernel, and copy them back after > the 2nd update removes the F8 kernel-xen, so that it is not > in the rpm database anymore. >This was a fresh install of Fedora 9 on a new system, so I just started from scratch with Fedora 8 and I''ve got it working now. MV _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > In the > > meantime you could probably try using a dom0-capable linux-xen from F8, > > for instance (or build your own). > > You would have trouble using an F8 kernel-xen in an F9 install - it would > get removed on every (2nd) kernel-xen update. You would probably need to > copy the /boot & /lib/modules files for that kernel, and copy them back > after the 2nd update removes the F8 kernel-xen, so that it is not in the > rpm database anymore. >Hrmmm. I see what you mean - not ideal. Surely there must be a yum flag one could tweak to make upgrading Do The Right Thing...? I don''t know enough yum-foo to say what this would be though! Cheers, Mark -- Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wednesday June 18 2008 10:04:49 pm Mark Williamson wrote:> Hrmmm. I see what you mean - not ideal. > > Surely there must be a yum flag one could tweak to make upgrading Do The > Right Thing...? I don''t know enough yum-foo to say what this would be > though!Sure - ''yum update -x kernel-xen''. You could make it an alias: alias yumu=''yum update -x kernel-xen'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
That''s a step in the right direction, I suppose! All we''d need now is a switch in the yum.conf to make it permanent. Cheers, Mark On Thursday 19 June 2008, jim burns wrote:> On Wednesday June 18 2008 10:04:49 pm Mark Williamson wrote: > > Hrmmm. I see what you mean - not ideal. > > > > Surely there must be a yum flag one could tweak to make upgrading Do The > > Right Thing...? I don''t know enough yum-foo to say what this would be > > though! > > Sure - ''yum update -x kernel-xen''. You could make it an alias: > > alias yumu=''yum update -x kernel-xen'' > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Question: How can I dedicate one CPU for Dom0 only and also how can I remove that CPU so it is not available to the other VM''s? Is there a configuration file somewhere? I need top network IO performance for my VM''s, since each one is a VOIP softswitch. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson wrote:> That''s a step in the right direction, I suppose! All we''d need now is a > switch in the yum.conf to make it permanent. > >exclude=kernel-xen will do. Although, AFAIK, the recommended way is to stick with F8 dom0 for now. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson wrote:>>> In the >>> meantime you could probably try using a dom0-capable linux-xen from F8, >>> for instance (or build your own). >>> >> You would have trouble using an F8 kernel-xen in an F9 install - it would >> get removed on every (2nd) kernel-xen update. You would probably need to >> copy the /boot & /lib/modules files for that kernel, and copy them back >> after the 2nd update removes the F8 kernel-xen, so that it is not in the >> rpm database anymore. >> >> > > Hrmmm. I see what you mean - not ideal. > >I believe that yum won''t remove the kernel you''re running. So when I had problems with a new kernel on my old laptop I told grub to default to the old, working one and yum left it in place and removed the newer non-working kernels as they were updated. jch _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday June 19 2008 06:24:57 am John Haxby wrote:> I believe that yum won''t remove the kernel you''re running. So when I > had problems with a new kernel on my old laptop I told grub to default > to the old, working one and yum left it in place and removed the newer > non-working kernels as they were updated.Nope - I''ve had yum remove a running kernel on me, when the newer ones had problems I didn''t want to deal with yet. I may not have had that kernel as the default, tho'', as I''ve always had the default setting in /etc/sysconfig/kernel of UPDATEDEFAULT=yes. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Jun 19, 2008 at 3:04 AM, Mark Williamson < mark.williamson@cl.cam.ac.uk> wrote:> > > In the > > > meantime you could probably try using a dom0-capable linux-xen from F8, > > > for instance (or build your own). > > > > You would have trouble using an F8 kernel-xen in an F9 install - it would > > get removed on every (2nd) kernel-xen update. You would probably need to > > copy the /boot & /lib/modules files for that kernel, and copy them back > > after the 2nd update removes the F8 kernel-xen, so that it is not in the > > rpm database anymore. > > >Although setting the proper yum options to exclude kernel-xen is a better solution for the scenario here, I just felt I should point out there''s a sometimes useful option to rpm, "--justdb", that can be used to do the above without moving/copying things around. That is, "rpm -e --justdb kernel-xen" would remove it from the rpm database but leave the actual files alone. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users