Hi , Can any one please let me know how to capture all the boot messages of the Guest OS into a text file? I do xm create -c /etc/xen/hvm.cfg to boot the guest OS. Thanks Kishore _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-May-19 03:23 UTC
Re: [Xen-users] How to capture boot messages of Guest
On Wed, May 19, 2010 at 7:01 AM, kishore kumar <bodkekumar@gmail.com> wrote:> Hi , > > Can any one please let me know how to capture all the boot messages of the > Guest OS into a text file? > > I do xm create -c /etc/xen/hvm.cfg to boot the guest OS.HVM guest treat Xen console as serial port. You need to configure it to write to serial port. See http://wiki.xensource.com/xenwiki/XenCommonProblems#head-3600f540f48c4ff55ff85ddaf02164b5060c5ec4 for Opensuse example. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Is the serial terminal should be run on Dom 0? or can I connect to windows serial port as well ?? Please clarify this. Thank You. On Tue, May 18, 2010 at 8:23 PM, Fajar A. Nugraha <fajar@fajar.net> wrote:> On Wed, May 19, 2010 at 7:01 AM, kishore kumar <bodkekumar@gmail.com> > wrote: > > Hi , > > > > Can any one please let me know how to capture all the boot messages of > the > > Guest OS into a text file? > > > > I do xm create -c /etc/xen/hvm.cfg to boot the guest OS. > > HVM guest treat Xen console as serial port. You need to configure it > to write to serial port. See > > http://wiki.xensource.com/xenwiki/XenCommonProblems#head-3600f540f48c4ff55ff85ddaf02164b5060c5ec4 > for Opensuse example. > > -- > Fajar >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-May-19 03:57 UTC
Re: [Xen-users] How to capture boot messages of Guest
On Wed, May 19, 2010 at 10:44 AM, kishore kumar <bodkekumar@gmail.com> wrote:> Is the serial terminal should be run on Dom 0?I''m not sure what you mean by "serial terminal". What happens is, when you set domU config correctly (serial=''pty''), everything domU prints to its first serial port (ttyS0/COM1) will be available to xen console. The dom0 itself does not need to have a serial port.> or can I connect to windows > serial port as well ??I don''t know of any way to redirect windows boot messages to serial port. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
my Guest grub.conf is below
serial --unit=0 --speed=115200
terminal --timeout=5 serial console
title Red Hat Enterprise Linux Client (2.6.18-164.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/VolGroup00/LogVol00
console==ttyS0,115200
initrd /initrd-2.6.18-164.el5.img
Below is the Captured boot log from my Guest OS. I dont see all the boot
messages from my captured.
Are there any other options that needs to be given in the Guest grub.conf
file to Capture a very detailed boot messages? (almost all the boot
messages)
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/VolGroup00/LogVol00
console=ttyS0,1
15200
[Linux-bzImage, setup=0x1e00, size=0x1d5c1c]
initrd /initrd-2.6.18-164.el5.img
[Linux-initrd @ 0x37cc0000, 0x32fc6c bytes]
Linux version 2.6.18-164.el5 (mockbuild@x86-003.build.bos.redhat.com) (gcc
version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:48 EDT
2009
Command line: ro root=/dev/VolGroup00/LogVol00 console=ttyS0,115200
BIOS-provided physical RAM map:
BIOS-e820: 0000000000010000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
BIOS-e820: 00000000fc000000 - 0000000100000000 (reserved)
DMI 2.4 present.
No NUMA configuration found
Faking a node at 0000000000000000-0000000040000000
Bootmem setup node 0 0000000000000000-0000000040000000
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
disabling kdump
ACPI: PM-Timer IO Port: 0x1f48
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 7:10 APIC version 20
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-47
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level)
Setting APIC routing to physical flat
Using ACPI (MADT) for SMP configuration information
Nosave address range: 000000000009f000 - 00000000000a0000
Nosave address range: 00000000000a0000 - 00000000000e0000
Nosave address range: 00000000000e0000 - 0000000000100000
Allocating PCI resources starting at 50000000 (gap: 40000000:bc000000)
SMP: Allowing 1 CPUs, 0 hotplug CPUs
Built 1 zonelists. Total pages: 257162
Kernel command line: ro root=/dev/VolGroup00/LogVol00 console=ttyS0,115200
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Checking aperture...
ACPI: DMAR not present
Memory: 1023492k/1048576k available (2547k kernel code, 24632k reserved,
1289k data, 208k init)
Calibrating delay loop (skipped), value calculated using timer frequency..
4800.17 BogoMIPS (lpj=2400087)
Security Framework v1.0.0 initialized
SELinux: Initializing.
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 256K
CPU: L3 cache: 8192K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
SMP alternatives: switching to UP code
Freeing SMP alternatives: 32k freed
ACPI: Core revision 20060707
activating NMI Watchdog ... done.
Using local APIC timer interrupts.
result 6249986
Detected 6.249 MHz APIC timer.
Brought up 1 CPUs
testing NMI watchdog ... <4>WARNING: CPU#0: NMI appears to be stuck
(0->0)!
time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer.
time.c: Detected 2400.087 MHz processor.
checking if image is initramfs... it is
Freeing initrd memory: 3263k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using configuration type 1
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI quirk: region 1f40-1f7f claimed by PIIX4 ACPI
ACPI: PCI Interrupt Link [LNKA] (IRQs *5 10 11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
ACPI: PCI Interrupt Link [LNKD] (IRQs *5 10 11)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn''t work, try "pci=routeirq". If it
helps, post a
report
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
ACPI: DMAR not present
PCI-GART: No AMD northbridge found.
pnp: 00:02: ioport range 0x10c0-0x10e1 has been reserved
pnp: 00:02: ioport range 0xb044-0xb047 has been reserved
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
type=2000 audit(1274274214.835:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
alg: No test for crc32c (crc32c-generic)
ksign: Installing public key data
Loading keyring
- Added public key 4BD2703D74512BB
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Limiting direct PCI/PCI transfers.
PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
Activating ISA DMA hang workarounds.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
�serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
brd: module loaded
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX3: IDE controller at PCI slot 0000:00:01.1
PIIX3: chipset revision 0
PIIX3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xc100-0xc107, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xc108-0xc10f, BIOS settings: hdc:pio, hdd:pio
hda: QEMU HARDDISK, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 512KiB
hda: 65536000 sectors (33554 MB) w/256KiB Cache, CHS=16383/255/63, (U)DMA
hda: cache flushes supported
hda: hda1 hda2
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI: (supports S3 S4 S5)
Initalizing network drop monitor service
Freeing unused kernel memory: 208k freed
Write protecting the kernel read-only data: 496k
Red Hat nash version 5.1.19.6 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
input: AT Translated Set 2 keyboard as /class/input/input0
Creating block device nodes.
Loading ehci-hcd.ko module
input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
Loading ohci-hcd.ko module
Loading uhci-hcd.ko module
USB Universal Host Controller Interface driver v3.0
Loading jbd.ko module
Loading ext3.ko module
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Loading libata.ko module
Loading ata_piix.ko module
Loading dm-mod.ko module
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-devel@redhat.com
Loading dm-log.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Loading dm-mem-cache.ko module
Loading dm-region_hash.ko module
Loading dm-message.ko module
Loading dm-raid45.ko module
device-mapper: dm-raid45: initialized v0.2594l
Waiting for driver initialization.
Scanning and configuring dmraid supported devices
Scanning logical volumes
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
Activating logical volumes
2 logical volume(s) in volume group "VolGroup00" now active
Trying to resume from /dev/VolGroup00/LogVol01
No suspend signature on swap, not resuming.
Creating root device.
Mounting root filesystem.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
SELinux: Disabled at runtime.
type=1404 audit(1274274244.643:2): selinux=0 auid=4294967295 ses=4294967295
INIT: version 2.86 booting
Welcome to Red Hat Enterprise Linux Client
Press ''I'' to enter interactive startup.
Setting clock (utc): Wed May 19 06:04:03 PDT 2010 [ OK ]
Starting udev: [ OK ]
Loading default keymap (us): [ OK ]
Setting hostname localhost.localdomain: [ OK ]
Setting up Logical Volume Management: 2 logical volume(s) in volume group
"VolGroup00" now active
[ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VolGroup00/LogVol00
/dev/VolGroup00/LogVol00: clean, 97808/7645248 files, 855252/7643136 blocks
[/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/hda1
/boot: clean, 34/26104 files, 15741/104388 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: [ OK ]
Enabling local filesystem quotas: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
INIT: Entering runlevel: 5
Entering non-interactive startup
Applying Intel CPU microcode update: [ OK ]
Starting monitoring for VG VolGroup00: 2 logical volume(s) in volume group
"VolGroup00" monitored
[ OK ]
Starting background readahead: [ OK ]
Checking for hardware changes [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Starting auditd: [ OK ]
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
Starting irqbalance: [ OK ]
Starting portmap: [ OK ]
Starting NFS statd: [ OK ]
Starting RPC idmapd: [ OK ]
Starting system message bus: [ OK ]
[ OK ] Bluetooth services:[ OK ]
Mounting other filesystems: [ OK ]
Starting PC/SC smart card daemon (pcscd): [ OK ]
Starting acpi daemon: [ OK ]
Starting HAL daemon: [ OK ]
Starting hidd: [ OK ]
Starting autofs: Loading autofs4: [ OK ]
Starting automount: [ OK ]
[ OK ]
Starting hpiod: [ OK ]
Starting hpssd: [ OK ]
Starting sshd: [ OK ]
Starting cups: [ OK ]
Starting xinetd: [ OK ]
Starting sendmail: [ OK ]
Starting sm-client: [ OK ]
Starting console mouse services: [ OK ]
Starting crond: [ OK ]
Starting xfs: [ OK ]
Starting anacron: [ OK ]
Starting atd: [ OK ]
Starting background readahead: [ OK ]
Starting yum-updatesd: [ OK ]
Starting Avahi daemon... Adding MC addr: 01:00:5e:00:00:fb
Adding MC addr: 01:00:5e:00:00:01
[ OK ]
Setting network parameters... [ OK ]
Starting NetworkManager daemon: [ OK ]
Starting smartd: Adding MC addr: 01:00:5e:00:00:01
[ OK ]
mtrr: type mismatch for f0000000,100000 old: uncachable new: write-combining
mtrr: type mismatch for f0000000,400000 old: uncachable new: write-combining
Red Hat Enterprise Linux Client release 5.4 (Tikanga)
Kernel 2.6.18-164.el5 on an x86_64
localhost.localdomain login:
On Tue, May 18, 2010 at 8:57 PM, Fajar A. Nugraha <fajar@fajar.net> wrote:
> On Wed, May 19, 2010 at 10:44 AM, kishore kumar
<bodkekumar@gmail.com>
> wrote:
> > Is the serial terminal should be run on Dom 0?
>
> I''m not sure what you mean by "serial terminal". What
happens is, when
> you set domU config correctly (serial=''pty''), everything
domU prints
> to its first serial port (ttyS0/COM1) will be available to xen
> console. The dom0 itself does not need to have a serial port.
>
> > or can I connect to windows
> > serial port as well ??
>
> I don''t know of any way to redirect windows boot messages to
serial port.
>
> --
> Fajar
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Miles Fidelman
2010-May-19 22:12 UTC
Re: [Xen-users] How to capture boot messages of Guest
Note that this is based on Debian experience, I''m not sure it lines up exactly with the Red Hat environment. On a PHYSICAL machine, the earliest boot messages only show up on the console. Once you get a little further into the boot process, if you''ve edited /etc/default/bootlogd and set BOOTLOGD_ENABLE=Yes, the later portion of the boot messages will show up in /var/log/boot. The only way to capture the early messages is to either read really fast, or have a terminal that can capture the traffic. On a VIRTUAL machine, you''re in better shape. If you start your vm with "xm create -c vm.cfg, you should see all the messages on your virtual console. You may have to play with the setting of the console= settings (in your vm.cfg file, in menu.lst, and/or in your VM''s /etc/inittab - depending on which version of xen you''re using you may need to set console=hvc0 or some such. Hope this helps, Miles Fidelman kishore kumar wrote:> my Guest grub.conf is below > serial --unit=0 --speed=115200 > terminal --timeout=5 serial console > title Red Hat Enterprise Linux Client (2.6.18-164.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/VolGroup00/LogVol00 > console==ttyS0,115200 > initrd /initrd-2.6.18-164.el5.img > Below is the Captured boot log from my Guest OS. I dont see all the > boot messages from my captured. > Are there any other options that needs to be given in the Guest > grub.conf file to Capture a very detailed boot messages? (almost all > the boot messages) > > root (hd0,0) > > Filesystem type is ext2fs, partition type 0x83 > > kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/VolGroup00/LogVol00 > console=ttyS0,1 > > 15200 > > [Linux-bzImage, setup=0x1e00, size=0x1d5c1c] > > initrd /initrd-2.6.18-164.el5.img > > [Linux-initrd @ 0x37cc0000, 0x32fc6c bytes] > > Linux version 2.6.18-164.el5 (mockbuild@x86-003.build.bos.redhat.com > <mailto:mockbuild@x86-003.build.bos.redhat.com>) (gcc version 4.1.2 > 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:48 EDT 2009 > > Command line: ro root=/dev/VolGroup00/LogVol00 console=ttyS0,115200 > > BIOS-provided physical RAM map: > > BIOS-e820: 0000000000010000 - 000000000009fc00 (usable) > > BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) > > BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) > > BIOS-e820: 0000000000100000 - 0000000040000000 (usable) > > BIOS-e820: 00000000fc000000 - 0000000100000000 (reserved) > > DMI 2.4 present. > > No NUMA configuration found > > Faking a node at 0000000000000000-0000000040000000 > > Bootmem setup node 0 0000000000000000-0000000040000000 > > Memory for crash kernel (0x0 to 0x0) notwithin permissible range > > disabling kdump > > ACPI: PM-Timer IO Port: 0x1f48 > > ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > > Processor #0 7:10 APIC version 20 > > ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) > > IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-47 > > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > > ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level) > > ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level) > > ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level) > > Setting APIC routing to physical flat > > Using ACPI (MADT) for SMP configuration information > > Nosave address range: 000000000009f000 - 00000000000a0000 > > Nosave address range: 00000000000a0000 - 00000000000e0000 > > Nosave address range: 00000000000e0000 - 0000000000100000 > > Allocating PCI resources starting at 50000000 (gap: 40000000:bc000000) > > SMP: Allowing 1 CPUs, 0 hotplug CPUs > > Built 1 zonelists. Total pages: 257162 > > Kernel command line: ro root=/dev/VolGroup00/LogVol00 console=ttyS0,115200 > > Initializing CPU#0 > > PID hash table entries: 4096 (order: 12, 32768 bytes) > > Console: colour VGA+ 80x25 > > Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) > > Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) > > Checking aperture... > > ACPI: DMAR not present > > Memory: 1023492k/1048576k available (2547k kernel code, 24632k > reserved, 1289k data, 208k init) > > Calibrating delay loop (skipped), value calculated using timer > frequency.. 4800.17 BogoMIPS (lpj=2400087) > > Security Framework v1.0.0 initialized > > SELinux: Initializing. > > selinux_register_security: Registering secondary module capability > > Capability LSM initialized as secondary > > Mount-cache hash table entries: 256 > > CPU: L1 I cache: 32K, L1 D cache: 32K > > CPU: L2 cache: 256K > > CPU: L3 cache: 8192K > > CPU: Physical Processor ID: 0 > > CPU: Processor Core ID: 0 > > SMP alternatives: switching to UP code > > Freeing SMP alternatives: 32k freed > > ACPI: Core revision 20060707 > > activating NMI Watchdog ... done. > > Using local APIC timer interrupts. > > result 6249986 > > Detected 6.249 MHz APIC timer. > > Brought up 1 CPUs > > testing NMI watchdog ... <4>WARNING: CPU#0: NMI appears to be stuck > (0->0)! > > time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer. > > time.c: Detected 2400.087 MHz processor. > > checking if image is initramfs... it is > > Freeing initrd memory: 3263k freed > > NET: Registered protocol family 16 > > ACPI: bus type pci registered > > PCI: Using configuration type 1 > > ACPI: Interpreter enabled > > ACPI: Using IOAPIC for interrupt routing > > ACPI: No dock devices found. > > ACPI: PCI Root Bridge [PCI0] (0000:00) > > PCI quirk: region 1f40-1f7f claimed by PIIX4 ACPI > > ACPI: PCI Interrupt Link [LNKA] (IRQs *5 10 11) > > ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11) > > ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11) > > ACPI: PCI Interrupt Link [LNKD] (IRQs *5 10 11) > > Linux Plug and Play Support v0.97 (c) Adam Belay > > pnp: PnP ACPI init > > pnp: PnP ACPI: found 12 devices > > usbcore: registered new driver usbfs > > usbcore: registered new driver hub > > PCI: Using ACPI for IRQ routing > > PCI: If a device doesn''t work, try "pci=routeirq". If it helps, post a > report > > NetLabel: Initializing > > NetLabel: domain hash size = 128 > > NetLabel: protocols = UNLABELED CIPSOv4 > > NetLabel: unlabeled traffic allowed by default > > ACPI: DMAR not present > > PCI-GART: No AMD northbridge found. > > pnp: 00:02: ioport range 0x10c0-0x10e1 has been reserved > > pnp: 00:02: ioport range 0xb044-0xb047 has been reserved > > NET: Registered protocol family 2 > > IP route cache hash table entries: 32768 (order: 6, 262144 bytes) > > TCP established hash table entries: 131072 (order: 9, 2097152 bytes) > > TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) > > TCP: Hash tables configured (established 131072 bind 65536) > > TCP reno registered > > audit: initializing netlink socket (disabled) > > type=2000 audit(1274274214.835:1): initialized > > Total HugeTLB memory allocated, 0 > > VFS: Disk quotas dquot_6.5.1 > > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > > Initializing Cryptographic API > > alg: No test for crc32c (crc32c-generic) > > ksign: Installing public key data > > Loading keyring > > - Added public key 4BD2703D74512BB > > - User ID: Red Hat, Inc. (Kernel Module GPG key) > > io scheduler noop registered > > io scheduler anticipatory registered > > io scheduler deadline registered > > io scheduler cfq registered (default) > > Limiting direct PCI/PCI transfers. > > PCI: PIIX3: Enabling Passive Release on 0000:00:01.0 > > Activating ISA DMA hang workarounds. > > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > > Real Time Clock Driver v1.12ac > > Non-volatile memory driver v1.2 > > Linux agpgart interface v0.101 (c) Dave Jones > > Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled > > �serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > > 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > > brd: module loaded > > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > > ide: Assuming 33MHz system bus speed for PIO modes; override with > idebus=xx > > PIIX3: IDE controller at PCI slot 0000:00:01.1 > > PIIX3: chipset revision 0 > > PIIX3: not 100% native mode: will probe irqs later > > ide0: BM-DMA at 0xc100-0xc107, BIOS settings: hda:pio, hdb:pio > > ide1: BM-DMA at 0xc108-0xc10f, BIOS settings: hdc:pio, hdd:pio > > hda: QEMU HARDDISK, ATA DISK drive > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > > hda: max request size: 512KiB > > hda: 65536000 sectors (33554 MB) w/256KiB Cache, CHS=16383/255/63, (U)DMA > > hda: cache flushes supported > > hda: hda1 hda2 > > ide-floppy driver 0.99.newide > > usbcore: registered new driver hiddev > > usbcore: registered new driver usbhid > > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > > PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 > > serio: i8042 KBD port at 0x60,0x64 irq 1 > > serio: i8042 AUX port at 0x60,0x64 irq 12 > > mice: PS/2 mouse device common for all mice > > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > > md: bitmap version 4.39 > > TCP bic registered > > Initializing IPsec netlink socket > > NET: Registered protocol family 1 > > NET: Registered protocol family 17 > > ACPI: (supports S3 S4 S5) > > Initalizing network drop monitor service > > Freeing unused kernel memory: 208k freed > > Write protecting the kernel read-only data: 496k > > Red Hat nash version 5.1.19.6 starting > > Mounting proc filesystem > > Mounting sysfs filesystem > > Creating /dev > > Creating initial device nodes > > Setting up hotplug. > > input: AT Translated Set 2 keyboard as /class/input/input0 > > Creating block device nodes. > > Loading ehci-hcd.ko module > > input: ImExPS/2 Generic Explorer Mouse as /class/input/input1 > > Loading ohci-hcd.ko module > > Loading uhci-hcd.ko module > > USB Universal Host Controller Interface driver v3.0 > > Loading jbd.ko module > > Loading ext3.ko module > > Loading scsi_mod.ko module > > SCSI subsystem initialized > > Loading sd_mod.ko module > > Loading libata.ko module > > Loading ata_piix.ko module > > Loading dm-mod.ko module > > device-mapper: uevent: version 1.0.3 > > device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: > dm-devel@redhat.com <mailto:dm-devel@redhat.com> > > Loading dm-log.ko module > > Loading dm-mirror.ko module > > Loading dm-zero.ko module > > Loading dm-snapshot.ko module > > Loading dm-mem-cache.ko module > > Loading dm-region_hash.ko module > > Loading dm-message.ko module > > Loading dm-raid45.ko module > > device-mapper: dm-raid45: initialized v0.2594l > > Waiting for driver initialization. > > Scanning and configuring dmraid supported devices > > Scanning logical volumes > > Reading all physical volumes. This may take a while... > > Found volume group "VolGroup00" using metadata type lvm2 > > Activating logical volumes > > 2 logical volume(s) in volume group "VolGroup00" now active > > Trying to resume from /dev/VolGroup00/LogVol01 > > No suspend signature on swap, not resuming. > > Creating root device. > > Mounting root filesystem. > > kjournald starting. Commit interval 5 seconds > > EXT3-fs: mounted filesystem with ordered data mode. > > Setting up other filesystems. > > Setting up new root fs > > no fstab.sys, mounting internal defaults > > Switching to new root and running init. > > unmounting old /dev > > unmounting old /proc > > unmounting old /sys > > SELinux: Disabled at runtime. > > type=1404 audit(1274274244.643:2): selinux=0 auid=4294967295 > ses=4294967295 > > INIT: version 2.86 booting > > Welcome to Red Hat Enterprise Linux Client > > Press ''I'' to enter interactive startup. > > Setting clock (utc): Wed May 19 06:04:03 PDT 2010 [ OK ] > > Starting udev: [ OK ] > > Loading default keymap (us): [ OK ] > > Setting hostname localhost.localdomain: [ OK ] > > Setting up Logical Volume Management: 2 logical volume(s) in volume > group "VolGroup00" now active > > [ OK ] > > Checking filesystems > > Checking all file systems. > > [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VolGroup00/LogVol00 > > /dev/VolGroup00/LogVol00: clean, 97808/7645248 files, 855252/7643136 > blocks > > [/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/hda1 > > /boot: clean, 34/26104 files, 15741/104388 blocks > > [ OK ] > > Remounting root filesystem in read-write mode: [ OK ] > > Mounting local filesystems: [ OK ] > > Enabling local filesystem quotas: [ OK ] > > Enabling /etc/fstab swaps: [ OK ] > > INIT: Entering runlevel: 5 > > Entering non-interactive startup > > Applying Intel CPU microcode update: [ OK ] > > Starting monitoring for VG VolGroup00: 2 logical volume(s) in volume > group "VolGroup00" monitored > > [ OK ] > > Starting background readahead: [ OK ] > > Checking for hardware changes [ OK ] > > Bringing up loopback interface: [ OK ] > > Bringing up interface eth0: [ OK ] > > Starting auditd: [ OK ] > > Starting system logger: [ OK ] > > Starting kernel logger: [ OK ] > > Starting irqbalance: [ OK ] > > Starting portmap: [ OK ] > > Starting NFS statd: [ OK ] > > Starting RPC idmapd: [ OK ] > > Starting system message bus: [ OK ] > > [ OK ] Bluetooth services:[ OK ] > > Mounting other filesystems: [ OK ] > > Starting PC/SC smart card daemon (pcscd): [ OK ] > > Starting acpi daemon: [ OK ] > > Starting HAL daemon: [ OK ] > > Starting hidd: [ OK ] > > Starting autofs: Loading autofs4: [ OK ] > > Starting automount: [ OK ] > > [ OK ] > > Starting hpiod: [ OK ] > > Starting hpssd: [ OK ] > > Starting sshd: [ OK ] > > Starting cups: [ OK ] > > Starting xinetd: [ OK ] > > Starting sendmail: [ OK ] > > Starting sm-client: [ OK ] > > Starting console mouse services: [ OK ] > > Starting crond: [ OK ] > > Starting xfs: [ OK ] > > Starting anacron: [ OK ] > > Starting atd: [ OK ] > > Starting background readahead: [ OK ] > > Starting yum-updatesd: [ OK ] > > Starting Avahi daemon... Adding MC addr: 01:00:5e:00:00:fb > > Adding MC addr: 01:00:5e:00:00:01 > > [ OK ] > > Setting network parameters... [ OK ] > > Starting NetworkManager daemon: [ OK ] > > Starting smartd: Adding MC addr: 01:00:5e:00:00:01 > > [ OK ] > > mtrr: type mismatch for f0000000,100000 old: uncachable new: > write-combining > > mtrr: type mismatch for f0000000,400000 old: uncachable new: > write-combining > > Red Hat Enterprise Linux Client release 5.4 (Tikanga) > > Kernel 2.6.18-164.el5 on an x86_64 > > localhost.localdomain login: > > > > On Tue, May 18, 2010 at 8:57 PM, Fajar A. Nugraha <fajar@fajar.net > <mailto:fajar@fajar.net>> wrote: > > On Wed, May 19, 2010 at 10:44 AM, kishore kumar > <bodkekumar@gmail.com <mailto:bodkekumar@gmail.com>> wrote: > > Is the serial terminal should be run on Dom 0? > > I''m not sure what you mean by "serial terminal". What happens is, when > you set domU config correctly (serial=''pty''), everything domU prints > to its first serial port (ttyS0/COM1) will be available to xen > console. The dom0 itself does not need to have a serial port. > > > or can I connect to windows > > serial port as well ?? > > I don''t know of any way to redirect windows boot messages to > serial port. > > -- > Fajar > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- In theory, there is no difference between theory and practice. In<fnord> practice, there is. .... Yogi Berra _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-May-20 06:05 UTC
Re: [Xen-users] How to capture boot messages of Guest
On Thu, May 20, 2010 at 3:32 AM, kishore kumar <bodkekumar@gmail.com> wrote:> Below is the Captured boot log from my Guest OS. I dont see all the boot > messages from my captured.Which messages do you need? If you want BIOS messages, there''s (currently) no way to capture those. The first messages capturable using serial port is the one that grub outputs, which you already have. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I am basically looking for the debug print messages that are present in 10G SRIOV VF driver. Do I need to recompile the VF driver with debug option ON? How could I print these messages? Any pointers on this could help me. Thank You. On Wed, May 19, 2010 at 11:05 PM, Fajar A. Nugraha <fajar@fajar.net> wrote:> On Thu, May 20, 2010 at 3:32 AM, kishore kumar <bodkekumar@gmail.com> > wrote: > > Below is the Captured boot log from my Guest OS. I dont see all the boot > > messages from my captured. > > Which messages do you need? If you want BIOS messages, there''s > (currently) no way to capture those. The first messages capturable > using serial port is the one that grub outputs, which you already > have. > > -- > Fajar >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-May-21 02:22 UTC
Re: [Xen-users] How to capture boot messages of Guest
On Fri, May 21, 2010 at 1:48 AM, kishore kumar <bodkekumar@gmail.com> wrote:> I am basically looking for the debug print messages that are present in 10G > SRIOV VF driver. Do I need to recompile the VF driver with debug option > ON? How could I print these messages? Any pointers on this could help me.Does it print the messages to vga display? Anything that outputs to Linux console or stdout can be redirected to ttyS0, but not when it explicitly outputs to /dev/tty0 or similar. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
No. It does not print any messages of 10G SRIOV VF driver neither to vga nor to ttyS0. How do I print the debug messages of 10G SRIOV VF driver? Thank You. -----Original Message----- From: Fajar A. Nugraha [mailto:fajar@fajar.net] Sent: Thursday, May 20, 2010 7:22 PM To: kishore kumar Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] How to capture boot messages of Guest On Fri, May 21, 2010 at 1:48 AM, kishore kumar <bodkekumar@gmail.com> wrote:> I am basically looking for the debug print messages that are present in10G> SRIOV VF driver. Do I need to recompile the VF driver with debug option > ON? How could I print these messages? Any pointers on this could helpme. Does it print the messages to vga display? Anything that outputs to Linux console or stdout can be redirected to ttyS0, but not when it explicitly outputs to /dev/tty0 or similar. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Apparently Analagous Threads
- xen guest not booting
- xen guest not booting
- CentOS 5.1 and Xen - mount: could not find filesystem ''/dev/root''
- 64bit guest on top of 64bit hypervisor+dom0 does not boot with virsh while it does with xm command
- my domU from jailtime.org using latests xen kernel freezees