I''m having problems booting Xen/ia64 on the machines here.
Everything seemed fine when I built Xen except for the
CHK include/linux/compile.h
ERROR: ia64_monarch_init_handler: 186 slots, total region length = 0
1 error detected in 11382 functions.
make: [unwcheck] Error 1 (ignored)
at the end of compiling domain 0, which shouldn''t cause any problems.
I''ve then applied the privify tool to the vmlinux kernel.
Then I''ve put the resulting xenolinux and xen binaries into
/boot/efi/efi/redhat/, made a symlink "ln -s /boot/efi/efi/redhat/xen
/boot/xen", and put the following in /etc/elilo.conf:
default=xen
image=xen
label=xen
initrd=xenlinux
read-only
append="nomca console=simcons console=ttyS0 console=tty0
root=/dev/sda2"
However, when I boot nothing happens. This is the output:
Loading xen...Loading Linux... ..done
Loading initrd xenlinux...done
BTW, how far into the future do you think unprivileged domains are?
Hvard
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel
Magenheimer, Dan (HP Labs Fort Collins)
2005-Jan-11 18:21 UTC
[Xen-devel] RE: Booting Xen/ia64
> I''m having problems booting Xen/ia64 on the machines here. > > Everything seemed fine when I built Xen except for the > > CHK include/linux/compile.h > ERROR: ia64_monarch_init_handler: 186 slots, total region length = 0 > 1 error detected in 11382 functions. > make: [unwcheck] Error 1 (ignored) > > at the end of compiling domain 0, which shouldn''t cause any problems.Correct, no problem. This shows up also just building standard Linux/ia64.> I''ve then applied the privify tool to the vmlinux kernel. > > Then I''ve put the resulting xenolinux and xen binaries into > /boot/efi/efi/redhat/, made a symlink "ln -s > /boot/efi/efi/redhat/xen /boot/xen", and put the following in > /etc/elilo.conf: > > default=xen > > image=xen > label=xen > initrd=xenlinux > read-only > append="nomca console=simcons console=ttyS0 > console=tty0 root=/dev/sda2" > > However, when I boot nothing happens. This is the output: > > Loading xen...Loading Linux... ..done > > Loading initrd xenlinux...doneIs this on a serial output or on a video screen? If the latter, try hooking up a serial output (and verify that it works with regular Linux). It''s possible that Xen is booting xenlinux fine and you may eventually see xenlinux output on the video screen. If not, are you sure "root=/dev/sda2" works for booting standard Linux? What hardware are you using? I have been working with another Xen/ia64 developer (I''ll leave it up to him to post and identify himself if he wishes) on a serial problem; Xen/ia64 has a hack for serial output that apparently does not work on his box. I''m looking into a more generic solution (which got added to Linux/ia64 at 2.6.10).> BTW, how far into the future do you think unprivileged domains are?I''m visiting Cambridge next week so should know more after that. Dan ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Tue, Jan 11, 2005 at 10:21:53AM -0800, Magenheimer, Dan (HP Labs Fort Collins) wrote:> > > I''ve then applied the privify tool to the vmlinux kernel. > > > > Then I''ve put the resulting xenolinux and xen binaries into > > /boot/efi/efi/redhat/, made a symlink "ln -s > > /boot/efi/efi/redhat/xen /boot/xen", and put the following in > > /etc/elilo.conf: > > > > default=xen > > > > image=xen > > label=xen > > initrd=xenlinux > > read-only > > append="nomca console=simcons console=ttyS0 > > console=tty0 root=/dev/sda2" > > > > However, when I boot nothing happens. This is the output: > > > > Loading xen...Loading Linux... ..done > > > > Loading initrd xenlinux...done > > Is this on a serial output or on a video screen? If the latter, > try hooking up a serial output (and verify that it works with > regular Linux). It''s possible that Xen is booting xenlinux > fine and you may eventually see xenlinux output on the video > screen. If not, are you sure "root=/dev/sda2" works for booting > standard Linux? >This is on both serial and video. And yes, "root=/dev/sda2" works with standard Linux.> What hardware are you using? I have been working with another > Xen/ia64 developer (I''ll leave it up to him to post and identify > himself if he wishes) on a serial problem; Xen/ia64 has a hack for > serial output that apparently does not work on his box. I''m > looking into a more generic solution (which got added to Linux/ia64 > at 2.6.10).It''s an rx2600. Hvard ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Magenheimer, Dan (HP Labs Fort Collins)
2005-Jan-11 19:01 UTC
[Xen-devel] RE: Booting Xen/ia64
> This is on both serial and video. And yes, "root=/dev/sda2" > works with standard Linux. > > It''s an rx2600.Hmmm... mysterious. This is the same box I am using and the same bits. Perhaps a baud rate problem on the serial port? The hack I mentioned assumes 115200. (This can be configured via the EFI shell.) When I am running Linux, I use "console=ttyS0,115200" but I don''t know if specifying a different baud rate for Xen/ia64 will work (yet). Otherwise could be different firmware versions, but one wouldn''t expect that to cause this kind of a problem. When you boot real Linux with the same console= are you getting boot output on the VGA display? Dan ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Magenheimer, Dan (HP Labs Fort Collins)
2005-Jan-12 02:29 UTC
[Xen-devel] RE: Booting Xen/ia64
Just to rule out compiler/build differences, I posted the actual bits I am using successfully on an rx2600 on the ftp site, called xenlinux.good and xen.good. (Rename or add a new entry in elilo.conf). For me, these bits spew plenty of early output to the serial port but nothing to the VGA after elilo until Xenlinux starts booting, after which Xenlinux (domain0) boots all the way to the RedHat login screen. Also, I am using Serial A (top serial port). I seem to recall some traffic on linux-ia64 that Serial A and Serial B are mapped to ttyS0 and ttyS1 somewhat dynamically so it may be possible that Linux (and elilo) are talking to a different port than Xen. Dan> -----Original Message----- > From: Håvard Bjerke [mailto:havarbj@idi.ntnu.no] > Sent: Tuesday, January 11, 2005 11:42 AM > To: Magenheimer, Dan (HP Labs Fort Collins) > Cc: xen-devel@lists.sourceforge.net; andreas.hirstius@cern.ch > Subject: Re: Booting Xen/ia64 > > On Tue, Jan 11, 2005 at 10:21:53AM -0800, Magenheimer, Dan > (HP Labs Fort Collins) wrote: > > > > > I''ve then applied the privify tool to the vmlinux kernel. > > > > > > Then I''ve put the resulting xenolinux and xen binaries into > > > /boot/efi/efi/redhat/, made a symlink "ln -s > > > /boot/efi/efi/redhat/xen /boot/xen", and put the following in > > > /etc/elilo.conf: > > > > > > default=xen > > > > > > image=xen > > > label=xen > > > initrd=xenlinux > > > read-only > > > append="nomca console=simcons console=ttyS0 > > > console=tty0 root=/dev/sda2" > > > > > > However, when I boot nothing happens. This is the output: > > > > > > Loading xen...Loading Linux... ..done > > > > > > > Loading initrd xenlinux...done > > > > Is this on a serial output or on a video screen? If the latter, > > try hooking up a serial output (and verify that it works with > > regular Linux). It''s possible that Xen is booting xenlinux > > fine and you may eventually see xenlinux output on the video > > screen. If not, are you sure "root=/dev/sda2" works for booting > > standard Linux? > > > > This is on both serial and video. And yes, "root=/dev/sda2" > works with standard Linux. > > > What hardware are you using? I have been working with another > > Xen/ia64 developer (I''ll leave it up to him to post and identify > > himself if he wishes) on a serial problem; Xen/ia64 has a hack for > > serial output that apparently does not work on his box. I''m > > looking into a more generic solution (which got added to Linux/ia64 > > at 2.6.10). > > It''s an rx2600. > > > Håvard >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Hi, On our boxes the access to the serial console is done via the management processor, so the baud rate is limited to 9600 :-( If this a problem, I can use another serial port on the machine. One of the firmware versions might be a problem, since the machine is quite old (more than 2 years). But the latest available firmware (2.31) is installed... Here is a dump of "info fw" in the EFI shell: FIRMWARE INFORMATION Firmware Revision: 2.31 [4411] PAL_A Revision: 7.31/5.37 PAL_B Revision: 5.65 SAL Spec Revision: 3.01 SAL_A Revision: 2.00 SAL_B Revision: 2.31 EFI Spec Revision: 1.10 EFI Intel Drop Revision: 14.61 EFI Build Revision: 1.22 POSSE Revision: 0.10 ACPI Revision: 7.00 BMC Revision 1.52 IPMI Revision: 1.00 SMBIOS Revision: 2.3.2a Management Processor Revision: E.02.10 With standard Linux the output goes to both consoles, except the part where the services start up. Andreas Magenheimer, Dan (HP Labs Fort Collins) wrote:>>This is on both serial and video. And yes, "root=/dev/sda2" >>works with standard Linux. >> >>It''s an rx2600. >> >> > >Hmmm... mysterious. This is the same box I am using and the >same bits. Perhaps a baud rate problem on the serial port? >The hack I mentioned assumes 115200. (This can be configured >via the EFI shell.) When I am running Linux, I use >"console=ttyS0,115200" but I don''t know if specifying a >different baud rate for Xen/ia64 will work (yet). > >Otherwise could be different firmware versions, but one wouldn''t >expect that to cause this kind of a problem. > >When you boot real Linux with the same console= are you getting >boot output on the VGA display? > >Dan > > >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
We tried the *.good binaries, and we''re making progress. But something is wrong with the timer: Starting: Scientific Linux CERN ELILO boot: Loading xen.good...Loading Linux... ..done Loading initrd xenlinux.good...done Linux version 2.6.9 (djm@sportsman) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-34)) #1 SMP Tue Dec 7 21:25:04 MST 2004 EFI v1.00 by Xen/ia64: SALsystab=0x8000178 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000 warning: unable to switch EFI into virtual mode (status=9223372036854775811) No I/O port range found in EFI memory map, falling back to AR.KR0 I/O port base = 0x0 SAL 0.1: Xen/ia64 Xen/ia64 version 0.0 get_max_cacheline_size: ia64_pal_cache_summary() failed (status=-1) PAL_VM_PAGE_SIZE failed with status=-1;defaulting to architected purge page-sizes. cpu_init: PAL VM summary failed, assuming 18 RID bits ACPI: Local APIC address c0000000fee00000 GSI 36 (level, low) -> CPU 0 (0x0000) vector 48 2 CPUs available, 2 CPUs total PCDP: 0xe00000003fb2c000 GSI 82 (level, low) -> CPU 0 (0x0000) vector 49 PCDP: serial console at MMIO 0xf8030000 (ttyS0, options 960Built 1 zonelists Kernel command line: BOOT_IMAGE=scsi0:EFI\redhat\xen.good nomca console=simcons console=ttyS0 console=tty0 rv/sda2 ro PID hash table entries: 2048 (order: 11, 65536 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 6, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 5, 524288 bytes) Memory: 507520k/523264k availab(6783k code, 15392k reserved, 3281k data, 208k init) McKinley Errata 9 workaround not needed; disabling it Mount-cache hash tatries: 1024 (order: 0, 16384 bytes) Boot processor id 0x0/0x0 task migration cache decay timeout: 10 msecs. ************* SYSTEM ALERT ************** SYSTEM NAME: moplapro05 12 Jan 2005 08:19:04 Alert Level 3: Warning Keyword: BOOT_SLAVE_NO_FINAL_WAKEUP_VECTOR Slave wakeup before vector registered Logged by: System Firmware 1 Data: Implementation dependent data field 0x7680005B01E00750 0000000000000001 A: ack read of this entry - X: Disable all future alert messages Anything else skip redisplay the log entry ->Choice:x ***************************************** CAUTION: System Alerts have been disabled. This will re-enable with a re-boot or power-on of the system. To re-enable system alerts now, you may use the AC (Alert Display Configuration) command. ************* SYSTEM ALERT ************** Alert messages are now disabled. Enter Commands Interface AC command to enable them again ***************************************** Processor 0x1/0x100 is stuck. Brought up 1 CPUs Total of 1 processors activated (1305.32 BogoMIPS). NET: Registered protocol family 16 ACPI: Subsystem revision 20040816 ACPI: Interpreter enabled ACPI: Using IOSAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (00:00) ACPI: PCI Root Bridge [PCI1] (00:20) ACPI: PCI Root Bridge [PCI2] (00:40) ACPI: PCI Root Bridge [PCI3] (00:60) ACPI: PCI Root Bridge [PCI4] (00:80) ACPI: PCI Root Bridge [PCI6] (00:c0) ACPI: PCI Root Bridge [PCI7] (00:e0) SCSI subsystem initialized usbcore: registered new driver hub PCI: Using ACPI for IRQ routing GSI 16 (level, low) -> CPU 0 (0x0000) vector 50 ACPI: PCI interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 50 GSI 17 (level, low) -> CPU 0 (0x0000) vector 51 ACPI: PCI interrupt 0000:00:01.1[B] -> GSI 17 (level, low) -> IRQ 51 GSI 18 (level, low) -> CPU 0 (0x0000) vector 52 ACPI: PCI interrupt 0000:00:01.2[C] -> GSI 18 (level, low) -> IRQ 52 GSI 21 (level, low) -> CPU 0 (0x0000) vector 53 ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 21 (level, low) -> IRQ 53 GSI 20 (level, low) -> CPU 0 (0x0000) vector 54 ACPI: PCI interrupt 0000:00:03.0[A] -> GSI 20 (level, low) -> IRQ 54 GSI 27 (level, low) -> CPU 0 (0x0000) vector 55 ACPI: PCI interrupt 0000:20A] -> GSI 27 (level, low) -> IRQ 55 GSI 28 (level, low) -> CPU 0 (0x0000) vector 56 ACPI: PCI interrupt 0000:20:01.1[B] -> GSIevel, low) -> IRQ 56 GSI 29 (level, low) -> CPU 0 (0x0000) vector 57 ACPI: PCI interrupt 0000:20:02.0[A] -> GSI 29 (level, low> IRQ 57 GSI 60 (level, low) -> CPU 0 (0x0000) vector 58 ACPI: PCI interrupt 0000:81:00.0[A] -> GSI 60 (level, low) -> IRQ 58 : PCI interrupt 0000:e0:01.0[A] -> GSI 82 (level, low) -> IRQ 49 ACPI: PCI interrupt 0000:e0:01.1[A] -> GSI 82 (level, low) -> GSI 83 (level, low) -> CPU 0 (0x0000) vector 59 ACPI: PCI interrupt 0000:e0:02.0[A] -> GSI 83 (level, low) -> IRQ 59 IOC: zx1 2.2 HPA 0xfed01000 IOVA space 1024Mb at 0x40000000 perfmon: version 2.0 IRQ 238 perfmon: Generic PMU detected, 8 PMCsMDs, 4 counters (32 bits) PAL Information Facility v0.5 perfmon: added sampling format default_format perfmon_default_smpl: d_format v2.0 registered Total HugeTLB memory allocated, 0 Installing knfsd (copyright (C) 1996 okir@monad.swb.de). InitializiCryptographic API pci_hotplug: PCI Hot Plug PCI Core version: 0.5 acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.4 radeonfb_pci_register BEGIN ACPI: PCI interrupt 0000:e0:02.0[A] -> GSI 83 (level, low) -> IRQ 59 radeonfb: probed DDR SGRAM 16videoram radeonfb: mapped 16384k videoram radeonfb: Found Intel x86 BIOS ROM Image radeonfb: Retreived PLL infos from BIOS radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=166.00 Mhz, System=166.00 MHz 1 chips in connector info - chip 1 has 2 connectors * connector 0 of type 2 (CRT) : 2300 * connector 1 of type 3 (DVI-I) : 3201 Starting monitor auto detection... radeonfb: I2C (port 1) ... not found radeonfb: I2C (port 2) ... not found radeonfb: I2C (port 3) ... found CRT display radeonfb: I2C (port 4) ... not found radeonfb: I2C (port 2) ... not found radeonfb: I2C (port 4) ... not found radeonfb: I2C (port 3) ... found CRT display radeonfb: Monitor 1 type CRT found radeonfb: EDID probed radeonfb: Monitor 2 type no found EDID checksum failed, aborting EDID checksum failed, aborting hStart = 664, hEnd = 760, hTotal = 800 vStart = 491, vEnd = 493, vTotal = 525 h_total_disp = 0x4f0063 hsync_strt_wid = 0x8c02a2 v_total_disp = 0x1df020c vsync_strt_wid = 0x8201ea pixclock = 39721 freq = 2517 post div = 0x3 fb_div = 0x1bf ppll_div_3 = 0x301bf lvds_gen_cntl: 08000008 Console: switching to colour frame buffer device 80x30 radeonfb: ATI Radeon QY DDR SGRAM 16 MB radeonfb_pci_register END ACPI: Power Button (FF) [PWRF] ACPI: Sleep Button (FF) [SLPF] ACPI: Processor [CPU0] (supports C1) ACPI: Thermal Zone [THM0] (27 C) EFI Time Services Driver v0.4 Linux agpgart interface v0.100 (c) Dave Jones ACPI: PCI interrupt 0000:e0:02.0[A] -> GSI 83 (level, low) -> IRQ 59 [drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled Oops: timer tick before it''s due (itc=5ded434d11,itm=5ded50805d) Oops: timer tick before it''s due (itc=5dedf3b2f6,itm=5dedfed84f) Oops: timer tick before it''s due (itc=5deea05221,itm=5deead3041) Oops: timer tick before it''s due (itc=5def4c3e1a,itm=5def4e1ef9) Oops: timer tick before it''s due (itc=5deff261ef,itm=5deffc76eb) Oops: timer tick before it''s due (itc=5df094b391,itm=5df09d65a3) Oops: timer tick before it''s due (itc=5df131d882,itm=5df13e545b) Oops: timer tick before it''s due (itc=5df1cf08a9,itm=5df1d1d9d9) Oops: timer tick before it''s due (itc=5df26c44b5,itm=5df272c891) Oops: timer tick before it''s due (itc=5df309a628,itm=5df313b749) [...] and so on... ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Never mind the last message. I wasn''t reading the READMEs properly :) We finally have Xen booting after changing the serial. Now, to figure out why MY binaries don''t work.. Is it because I''m using 2.6.7? Do you have the patches for 2.6.9? Hvard ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Never mind the last message. I wasn''t reading the READMEs properly :Yes, that "Timer tick before it''s due" seems to be harmless for now but it is a mystery. I''ve looked into it a few times without making any progress.> We finally have Xen booting after changing the serial.Great!> Now, to figure out why MY binaries don''t work.. Is it because I''m using > 2.6.7? Do you have the patches for 2.6.9?I only have xen patches from 2.6.7, but I''ve built xenlinux out of several versions (with only CONFIG changes, no patches). Did you try your binaries with the changed serial? If so, how far did it get? (no output or did a few messages get printed) Can you put your xen binary somewhere where I can ftp it? If its an early-on problem I can probably get some clues from putting your xen in ski. Dan ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Wed, Jan 12, 2005 at 07:30:49AM -0600, dan.magenheimer@hp.com wrote:> Can you put your xen binary somewhere where I can ftp it? > If its an early-on problem I can probably get some clues from > putting your xen in ski.Here: http://idi.ntnu.no/~havarbj/tmp/xen http://idi.ntnu.no/~havarbj/tmp/xenlinux Hvard ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Wed, Jan 12, 2005 at 07:30:49AM -0600, dan.magenheimer@hp.com wrote:> Did you try your binaries with the changed serial? If so, > how far did it get? (no output or did a few messages get printed)This is how far it gets when using my own built xen and your xenlinux.good binary: (XEN) domain mem: type=40631872, attr=0x10000008000761, range=[0xfffc00000a6bfc30-0xfffc0000126bfc30) (128MB) (XEN) About to call init_trace_bufs() (XEN) get_time_delta: called, not implemented (XEN) About to call startup_cpu_idle_loop() (XEN) get_time_delta: called, not implemented (XEN) update_dom_time: called, not implemented, skipping (XEN) current=fffc0000026b8000,shared_info=fffc00003f59c000 (XEN) next=fffc000004074000,shared_info=0 (XEN) schedule_tail: change to rr7 not yet implemented (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero (XEN) **** vcpu_set_itv(65536): vitm=0, setting to 0 (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero (XEN) *** CALLED SAL_SET_VECTORS. IGNORED... (XEN) vcpu_enable_timer(1000000): interval set to 69882928 cycles Linux version 2.6.9 (djm@sportsman) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-34)) #1 SMP Tue Dec 7 21:25:04 MST 2004 EFI v1.00 by Xen/ia64: SALsystab=0x8000178 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000 warning: unable to switch EFI into virtual mode (status=9223372036854775811) No I/O port range found in EFI memory map, falling back to AR.KR0 I/O port base = 0x3fffffc000000 SAL 0.1: Xen/ia64 Xen/ia64 version 0.0 get_max_cacheline_size: ia64_pal_cache_summary() failed (status=-1) PAL_VM_PAGE_SIZE failed with status=-1;defaulting to architected purge page-sizes. cpu_init: PAL VM summary failed, assuming 18 RID bits ACPI: Local APIC address c0000000fee00000 GSI 36 (level, low) -> CPU 0 (0x0000) vector 48 2 CPUs available, 2 CPUs total PCDP: v0 at 0xe00000003fb2c000 GSI 34 (edge, high) -> CPU 0 (0x0000) vector 49 PCDP: serial console at MMIO 0xff5e0000 (ttyS0, options 9600n8) Built 1 zonelists Kernel command line: BOOT_IMAGE=scsi0:EFI\redhat\xen nomca console=ttyS0 console=tty0 root=/dev/sda2 ro PID hash table entries: 2048 (order: 11, 65536 bytes) Console: colour VGA+ 80x25 (XEN) Delivering first extint to domain: ifa=0000000000000000, isr=0000020000000000, itir=0000000000000000, iip=a0000001007c0cf0 (XEN) psr.ic off, delivering fault=5300,iip=a000000100003040,isr=00000a0400000000,PSCB.iip=a0000001007c0cf0 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Magenheimer, Dan (HP Labs Fort Collins)
2005-Jan-12 22:39 UTC
[Xen-devel] RE: Booting Xen/ia64
Got your bits and have reproduced the problem, on hardware but not on the simulator so it will take a bit of work to track it down. The difference between your bits (not working) and mine (working) is a mystery so far so I may start there.> -----Original Message----- > From: Håvard Bjerke [mailto:havarbj@idi.ntnu.no] > Sent: Wednesday, January 12, 2005 9:53 AM > To: Magenheimer, Dan (HP Labs Fort Collins) > Cc: xen-devel@lists.sourceforge.net > Subject: Re: Booting Xen/ia64 > > On Wed, Jan 12, 2005 at 07:30:49AM -0600, > dan.magenheimer@hp.com wrote: > > Did you try your binaries with the changed serial? If so, > > how far did it get? (no output or did a few messages get printed) > > This is how far it gets when using my own built xen and your > xenlinux.good binary: > > (XEN) domain mem: type=40631872, attr=0x10000008000761, > range=[0xfffc00000a6bfc30-0xfffc0000126bfc30) (128MB) > (XEN) About to call init_trace_bufs() > (XEN) get_time_delta: called, not implemented > (XEN) About to call startup_cpu_idle_loop() > (XEN) get_time_delta: called, not implemented > (XEN) update_dom_time: called, not implemented, skipping > (XEN) current=fffc0000026b8000,shared_info=fffc00003f59c000 > (XEN) next=fffc000004074000,shared_info=0 > (XEN) schedule_tail: change to rr7 not yet implemented > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > (XEN) **** vcpu_set_itv(65536): vitm=0, setting to 0 > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > (XEN) *** CALLED SAL_SET_VECTORS. IGNORED... > (XEN) vcpu_enable_timer(1000000): interval set to 69882928 cycles > Linux version 2.6.9 (djm@sportsman) (gcc version 3.2.3 > 20030502 (Red Hat Linux 3.2.3-34)) #1 SMP Tue Dec 7 21:25:04 MST 2004 > EFI v1.00 by Xen/ia64: SALsystab=0x8000178 ACPI > 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000 > warning: unable to switch EFI into virtual mode > (status=9223372036854775811) > No I/O port range found in EFI memory map, falling back to AR.KR0 > I/O port base = 0x3fffffc000000 > SAL 0.1: Xen/ia64 Xen/ia64 version 0.0 > get_max_cacheline_size: ia64_pal_cache_summary() failed (status=-1) > PAL_VM_PAGE_SIZE failed with status=-1;defaulting to > architected purge page-sizes. > cpu_init: PAL VM summary failed, assuming 18 RID bits > ACPI: Local APIC address c0000000fee00000 > GSI 36 (level, low) -> CPU 0 (0x0000) vector 48 > 2 CPUs available, 2 CPUs total > PCDP: v0 at 0xe00000003fb2c000 > GSI 34 (edge, high) -> CPU 0 (0x0000) vector 49 > PCDP: serial console at MMIO 0xff5e0000 (ttyS0, options 9600n8) > Built 1 zonelists > Kernel command line: BOOT_IMAGE=scsi0:EFI\redhat\xen nomca > console=ttyS0 console=tty0 root=/dev/sda2 ro > PID hash table entries: 2048 (order: 11, 65536 bytes) > Console: colour VGA+ 80x25 > (XEN) Delivering first extint to domain: > ifa=0000000000000000, isr=0000020000000000, > itir=0000000000000000, iip=a0000001007c0cf0 > (XEN) psr.ic off, delivering > fault=5300,iip=a000000100003040,isr=00000a0400000000,PSCB.iip> a0000001007c0cf0 > >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Magenheimer, Dan (HP Labs Fort Collins)
2005-Jan-14 19:21 UTC
[Xen-devel] RE: Booting Xen/ia64
Just wanted to let you know I am still working on your problem. (I was tied up with other commitments most of yesterday.) Just to verify, I rebuilt everything from the ftp site to ensure I had the same xen/xenlinux bits as you and was able to successfully boot and run. I''m wondering if we might be seeing compiler or hardware differences? Now that you have serial port output, could you rebuild from the ftp bits and let me know if you are still having problems. And if you still have problems, could you send me the serial output (as you did below). Regarding the output below, after studying it a bit, I realize it is a result of an unprivified xenlinux.> -----Original Message----- > From: Håvard Bjerke [mailto:havarbj@idi.ntnu.no] > Sent: Wednesday, January 12, 2005 9:53 AM > To: Magenheimer, Dan (HP Labs Fort Collins) > Cc: xen-devel@lists.sourceforge.net > Subject: Re: Booting Xen/ia64 > > On Wed, Jan 12, 2005 at 07:30:49AM -0600, > dan.magenheimer@hp.com wrote: > > Did you try your binaries with the changed serial? If so, > > how far did it get? (no output or did a few messages get printed) > > This is how far it gets when using my own built xen and your > xenlinux.good binary: > > (XEN) domain mem: type=40631872, attr=0x10000008000761, > range=[0xfffc00000a6bfc30-0xfffc0000126bfc30) (128MB) > (XEN) About to call init_trace_bufs() > (XEN) get_time_delta: called, not implemented > (XEN) About to call startup_cpu_idle_loop() > (XEN) get_time_delta: called, not implemented > (XEN) update_dom_time: called, not implemented, skipping > (XEN) current=fffc0000026b8000,shared_info=fffc00003f59c000 > (XEN) next=fffc000004074000,shared_info=0 > (XEN) schedule_tail: change to rr7 not yet implemented > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > (XEN) **** vcpu_set_itv(65536): vitm=0, setting to 0 > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > (XEN) *** CALLED SAL_SET_VECTORS. IGNORED... > (XEN) vcpu_enable_timer(1000000): interval set to 69882928 cycles > Linux version 2.6.9 (djm@sportsman) (gcc version 3.2.3 > 20030502 (Red Hat Linux 3.2.3-34)) #1 SMP Tue Dec 7 21:25:04 MST 2004 > EFI v1.00 by Xen/ia64: SALsystab=0x8000178 ACPI > 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000 > warning: unable to switch EFI into virtual mode > (status=9223372036854775811) > No I/O port range found in EFI memory map, falling back to AR.KR0 > I/O port base = 0x3fffffc000000 > SAL 0.1: Xen/ia64 Xen/ia64 version 0.0 > get_max_cacheline_size: ia64_pal_cache_summary() failed (status=-1) > PAL_VM_PAGE_SIZE failed with status=-1;defaulting to > architected purge page-sizes. > cpu_init: PAL VM summary failed, assuming 18 RID bits > ACPI: Local APIC address c0000000fee00000 > GSI 36 (level, low) -> CPU 0 (0x0000) vector 48 > 2 CPUs available, 2 CPUs total > PCDP: v0 at 0xe00000003fb2c000 > GSI 34 (edge, high) -> CPU 0 (0x0000) vector 49 > PCDP: serial console at MMIO 0xff5e0000 (ttyS0, options 9600n8) > Built 1 zonelists > Kernel command line: BOOT_IMAGE=scsi0:EFI\redhat\xen nomca > console=ttyS0 console=tty0 root=/dev/sda2 ro > PID hash table entries: 2048 (order: 11, 65536 bytes) > Console: colour VGA+ 80x25 > (XEN) Delivering first extint to domain: > ifa=0000000000000000, isr=0000020000000000, > itir=0000000000000000, iip=a0000001007c0cf0 > (XEN) psr.ic off, delivering > fault=5300,iip=a000000100003040,isr=00000a0400000000,PSCB.iip> a0000001007c0cf0 > >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I tried to build again, freshly from ftp, and this is how far it booted: Loading.: Scientific Linux CERN Starting: Scientific Linux CERN ELILO boot: Loading xen...Loading Linux... ..done Loading initrd xenlinux...done Linux version 2.6.9 (root@oplapro05) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-42)) #1 SMP Mon Jan 17 10:03:22 EFI v1.00 by Xen/ia64: SALsystab=0x8000178 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000 warning: unable to switch EFI into virtual mode (status=9223372036854775811) No I/O port range found in EFI memory map, falling back to AR.KR0 I/O port base = 0x0 SAL 0.1: Xen/ia64 Xen/ia64 version 0.0 get_max_cacheline_size: ia64_pal_cache_summary() failed (status=-1) PAL_VM_PAGE_SIZE failed with status=-1;defaulting to architected purge page-sizes. cpu_init: PAL VM summary failed, assuming 18 RID bits ACPI: Local APIC address c0000000fee00000 GSI 36 (level, low) -> CPU 0 (0x0000) vector 48 2 CPUs available, 2 CPUs total PCDPt 0xe00000003fb2c000 GSI 82 (level, low) -> CPU 0 (0x0000) vector 49 PCDP: serial console at MMIO 0xf8030000 (ttyS0, options 9 Built 1 zonelists Kernel command line: BOOT_IMAGE=scsi0:EFI\redhat\xen nomca console=ttyS0 console=tty0 root=/dev/sda2 ro P table entries: 1024 (order: 10, 32768 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 5, 524288 bytes) Inode-cache hash table entries: 32768 (order: 4, 262144 bytes) Memory: 508288k/523264k available (6786k code, 14592rved, 3278k data, 208k init) McKinley Errata 9 workaround not needed; disabling it Mount-cache hash table entries: 1024 (order 0, 16384 bytes) Boot processor id 0x0/0x0 task migration cache decay timeout: 10 msecs. ************* SYSTEM ALERT ************** SYSTEM NAME: moplapro05 17 Jan 2005 10:21:59 Alert Level 3: Warning Keyword: BOOT_SLAVE_NO_FINAL_WAKEUP_VECTOR Slave wakeup before vector registered Logged by: System Firmware 1 Data: Implementation dependent data field 0x7680005B01E01F50 0000000000000001 A: ack read of this entry - X: Disable all future alert messages Anything else skip redisplay the log entry ->Choice:Timeout! ***************************************** Your *.good binaries still boot fine, and we''re using the same gcc version:>gcc --versiongcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-42) Hvard On Fri, Jan 14, 2005 at 11:21:27AM -0800, Magenheimer, Dan (HP Labs Fort Collins) wrote:> Just wanted to let you know I am still working on your problem. > (I was tied up with other commitments most of yesterday.) > > Just to verify, I rebuilt everything from the ftp site to ensure > I had the same xen/xenlinux bits as you and was able to successfully > boot and run. I''m wondering if we might be seeing compiler > or hardware differences? Now that you have serial port output, > could you rebuild from the ftp bits and let me know if you > are still having problems. And if you still have problems, > could you send me the serial output (as you did below). > > Regarding the output below, after studying it a bit, I realize > it is a result of an unprivified xenlinux. > > > -----Original Message----- > > From: Hvard Bjerke [mailto:havarbj@idi.ntnu.no] > > Sent: Wednesday, January 12, 2005 9:53 AM > > To: Magenheimer, Dan (HP Labs Fort Collins) > > Cc: xen-devel@lists.sourceforge.net > > Subject: Re: Booting Xen/ia64 > > > > On Wed, Jan 12, 2005 at 07:30:49AM -0600, > > dan.magenheimer@hp.com wrote: > > > Did you try your binaries with the changed serial? If so, > > > how far did it get? (no output or did a few messages get printed) > > > > This is how far it gets when using my own built xen and your > > xenlinux.good binary: > > > > (XEN) domain mem: type=40631872, attr=0x10000008000761, > > range=[0xfffc00000a6bfc30-0xfffc0000126bfc30) (128MB) > > (XEN) About to call init_trace_bufs() > > (XEN) get_time_delta: called, not implemented > > (XEN) About to call startup_cpu_idle_loop() > > (XEN) get_time_delta: called, not implemented > > (XEN) update_dom_time: called, not implemented, skipping > > (XEN) current=fffc0000026b8000,shared_info=fffc00003f59c000 > > (XEN) next=fffc000004074000,shared_info=0 > > (XEN) schedule_tail: change to rr7 not yet implemented > > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > > (XEN) **** vcpu_set_itv(65536): vitm=0, setting to 0 > > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > > (XEN) *** CALLED SAL_SET_VECTORS. IGNORED... > > (XEN) vcpu_enable_timer(1000000): interval set to 69882928 cycles > > Linux version 2.6.9 (djm@sportsman) (gcc version 3.2.3 > > 20030502 (Red Hat Linux 3.2.3-34)) #1 SMP Tue Dec 7 21:25:04 MST 2004 > > EFI v1.00 by Xen/ia64: SALsystab=0x8000178 ACPI > > 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000 > > warning: unable to switch EFI into virtual mode > > (status=9223372036854775811) > > No I/O port range found in EFI memory map, falling back to AR.KR0 > > I/O port base = 0x3fffffc000000 > > SAL 0.1: Xen/ia64 Xen/ia64 version 0.0 > > get_max_cacheline_size: ia64_pal_cache_summary() failed (status=-1) > > PAL_VM_PAGE_SIZE failed with status=-1;defaulting to > > architected purge page-sizes. > > cpu_init: PAL VM summary failed, assuming 18 RID bits > > ACPI: Local APIC address c0000000fee00000 > > GSI 36 (level, low) -> CPU 0 (0x0000) vector 48 > > 2 CPUs available, 2 CPUs total > > PCDP: v0 at 0xe00000003fb2c000 > > GSI 34 (edge, high) -> CPU 0 (0x0000) vector 49 > > PCDP: serial console at MMIO 0xff5e0000 (ttyS0, options 9600n8) > > Built 1 zonelists > > Kernel command line: BOOT_IMAGE=scsi0:EFI\redhat\xen nomca > > console=ttyS0 console=tty0 root=/dev/sda2 ro > > PID hash table entries: 2048 (order: 11, 65536 bytes) > > Console: colour VGA+ 80x25 > > (XEN) Delivering first extint to domain: > > ifa=0000000000000000, isr=0000020000000000, > > itir=0000000000000000, iip=a0000001007c0cf0 > > (XEN) psr.ic off, delivering > > fault=5300,iip=a000000100003040,isr=00000a0400000000,PSCB.iip> > a0000001007c0cf0 > > > >-- Hvard K. F. Bjerke http://www.idi.ntnu.no/~havarbj/ ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Magenheimer, Dan (HP Labs Fort Collins)
2005-Jan-17 18:51 UTC
[Xen-devel] RE: Booting Xen/ia64
I''ve asked for info on this from an HP-internal mailing list. Today is a US Holiday so I may not get a reply until tomorrow. I think the problem is that firmware is considering lack of response from the second CPU to be a boot error. On my machine, it is not, but my machine has older firmware. On my machine, I get a pause for several seconds at this point and then the boot continues. It looks like yours is expecting user input... perhaps if you have a USB keyboard connected, firmware will accept input from it? Dan> -----Original Message----- > From: Håvard Bjerke [mailto:Havard.Bjerke@idi.ntnu.no] > Sent: Monday, January 17, 2005 3:44 AM > To: Magenheimer, Dan (HP Labs Fort Collins) > Cc: xen-devel@lists.sourceforge.net > Subject: Re: Booting Xen/ia64 > > I tried to build again, freshly from ftp, and this is how far > it booted: > > Loading.: Scientific Linux CERN > Starting: Scientific Linux CERN > > ELILO boot: Loading xen...Loading Linux... ..done > Loading initrd xenlinux...done > Linux version 2.6.9 (root@oplapro05) (gcc version 3.2.3 > 20030502 (Red Hat Linux 3.2.3-42)) #1 SMP Mon Jan 17 10:03:22 > EFI v1.00 by Xen/ia64: SALsystab=0x8000178 ACPI > 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000 > warning: unable to switch EFI into virtual mode > (status=9223372036854775811) > No I/O port range found in EFI memory map, falling back to AR.KR0 > I/O port base = 0x0 > SAL 0.1: Xen/ia64 Xen/ia64 version 0.0 > get_max_cacheline_size: ia64_pal_cache_summary() failed (status=-1) > PAL_VM_PAGE_SIZE failed with status=-1;defaulting to > architected purge page-sizes. > cpu_init: PAL VM summary failed, assuming 18 RID bits > ACPI: Local APIC address c0000000fee00000 > GSI 36 (level, low) -> CPU 0 (0x0000) vector 48 > 2 CPUs available, 2 CPUs total > PCDPt 0xe00000003fb2c000 > GSI 82 (level, low) -> CPU 0 (0x0000) vector 49 > PCDP: serial console at MMIO 0xf8030000 (ttyS0, options 9 > Built 1 zonelists > Kernel command line: BOOT_IMAGE=scsi0:EFI\redhat\xen nomca > console=ttyS0 console=tty0 root=/dev/sda2 ro > P table entries: 1024 (order: 10, 32768 bytes) > Console: colour VGA+ 80x25 > Dentry cache hash table entries: 65536 (order: 5, 524288 bytes) > Inode-cache hash table entries: 32768 (order: 4, 262144 bytes) > Memory: 508288k/523264k available (6786k code, 14592rved, > 3278k data, 208k init) > McKinley Errata 9 workaround not needed; disabling it > Mount-cache hash table entries: 1024 (order 0, 16384 bytes) > Boot processor id 0x0/0x0 > task migration cache decay timeout: 10 msecs. > > ************* SYSTEM ALERT ************** > SYSTEM NAME: moplapro05 > > 17 Jan 2005 10:21:59 > Alert Level 3: Warning > Keyword: BOOT_SLAVE_NO_FINAL_WAKEUP_VECTOR > Slave wakeup before vector registered > Logged by: System Firmware 1 > Data: Implementation dependent data field > 0x7680005B01E01F50 0000000000000001 > > A: ack read of this entry - X: Disable all future alert messages > Anything else skip redisplay the log entry > ->Choice:Timeout! > ***************************************** > > > Your *.good binaries still boot fine, and we''re using the > same gcc version: > > >gcc --version > gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-42) > > > Håvard > > On Fri, Jan 14, 2005 at 11:21:27AM -0800, Magenheimer, Dan > (HP Labs Fort Collins) wrote: > > Just wanted to let you know I am still working on your problem. > > (I was tied up with other commitments most of yesterday.) > > > > Just to verify, I rebuilt everything from the ftp site to ensure > > I had the same xen/xenlinux bits as you and was able to successfully > > boot and run. I''m wondering if we might be seeing compiler > > or hardware differences? Now that you have serial port output, > > could you rebuild from the ftp bits and let me know if you > > are still having problems. And if you still have problems, > > could you send me the serial output (as you did below). > > > > Regarding the output below, after studying it a bit, I realize > > it is a result of an unprivified xenlinux. > > > > > -----Original Message----- > > > From: Håvard Bjerke [mailto:havarbj@idi.ntnu.no] > > > Sent: Wednesday, January 12, 2005 9:53 AM > > > To: Magenheimer, Dan (HP Labs Fort Collins) > > > Cc: xen-devel@lists.sourceforge.net > > > Subject: Re: Booting Xen/ia64 > > > > > > On Wed, Jan 12, 2005 at 07:30:49AM -0600, > > > dan.magenheimer@hp.com wrote: > > > > Did you try your binaries with the changed serial? If so, > > > > how far did it get? (no output or did a few messages > get printed) > > > > > > This is how far it gets when using my own built xen and your > > > xenlinux.good binary: > > > > > > (XEN) domain mem: type=40631872, attr=0x10000008000761, > > > range=[0xfffc00000a6bfc30-0xfffc0000126bfc30) (128MB) > > > (XEN) About to call init_trace_bufs() > > > (XEN) get_time_delta: called, not implemented > > > (XEN) About to call startup_cpu_idle_loop() > > > (XEN) get_time_delta: called, not implemented > > > (XEN) update_dom_time: called, not implemented, skipping > > > (XEN) current=fffc0000026b8000,shared_info=fffc00003f59c000 > > > (XEN) next=fffc000004074000,shared_info=0 > > > (XEN) schedule_tail: change to rr7 not yet implemented > > > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > > > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > > > (XEN) **** vcpu_set_itv(65536): vitm=0, setting to 0 > > > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > > > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > > > (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero > > > (XEN) *** CALLED SAL_SET_VECTORS. IGNORED... > > > (XEN) vcpu_enable_timer(1000000): interval set to 69882928 cycles > > > Linux version 2.6.9 (djm@sportsman) (gcc version 3.2.3 > > > 20030502 (Red Hat Linux 3.2.3-34)) #1 SMP Tue Dec 7 > 21:25:04 MST 2004 > > > EFI v1.00 by Xen/ia64: SALsystab=0x8000178 ACPI > > > 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000 > > > warning: unable to switch EFI into virtual mode > > > (status=9223372036854775811) > > > No I/O port range found in EFI memory map, falling back to AR.KR0 > > > I/O port base = 0x3fffffc000000 > > > SAL 0.1: Xen/ia64 Xen/ia64 version 0.0 > > > get_max_cacheline_size: ia64_pal_cache_summary() failed > (status=-1) > > > PAL_VM_PAGE_SIZE failed with status=-1;defaulting to > > > architected purge page-sizes. > > > cpu_init: PAL VM summary failed, assuming 18 RID bits > > > ACPI: Local APIC address c0000000fee00000 > > > GSI 36 (level, low) -> CPU 0 (0x0000) vector 48 > > > 2 CPUs available, 2 CPUs total > > > PCDP: v0 at 0xe00000003fb2c000 > > > GSI 34 (edge, high) -> CPU 0 (0x0000) vector 49 > > > PCDP: serial console at MMIO 0xff5e0000 (ttyS0, options 9600n8) > > > Built 1 zonelists > > > Kernel command line: BOOT_IMAGE=scsi0:EFI\redhat\xen nomca > > > console=ttyS0 console=tty0 root=/dev/sda2 ro > > > PID hash table entries: 2048 (order: 11, 65536 bytes) > > > Console: colour VGA+ 80x25 > > > (XEN) Delivering first extint to domain: > > > ifa=0000000000000000, isr=0000020000000000, > > > itir=0000000000000000, iip=a0000001007c0cf0 > > > (XEN) psr.ic off, delivering > > > fault=5300,iip=a000000100003040,isr=00000a0400000000,PSCB.iip> > > a0000001007c0cf0 > > > > > > > > -- > Håvard K. F. Bjerke > http://www.idi.ntnu.no/~havarbj/ >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel