[Xen-devel] Re: "xm dmesg" report for the most recent vmlinuz-2.6.29-rc5-tip

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

No.  I have F10 and Solaris Nevada (b106) PV DomUs reinstalled under 2.6.29-rc5 ( with APIC issue fixed ) . "yum update" performed  730 MB download at F10 DomU and i setup VNC on F10 PV DomU with Nautilus alive.
Unfortunately, we can't test HVM DomUs due to known issues.

--- On Sun, 2/22/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: "xm dmesg" report for the most recent vmlinuz-2.6.29-rc5-tip
To: bderzhavets@xxxxxxxxx
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Sunday, February 22, 2009, 12:12 PM

Boris Derzhavets wrote:
> 
>  __  __            _____ _  _                      _        _  
   _     
\ \/ /___ _ __   |___ /| || |     _   _ _ __  ___| |_ __ _| |__ | | ___
>   \  // _ \ \047_ \    |_ \| || |_ __| | | | \047_
\/ __| __/ _` | \047_ \| |/ _ \
>   /  \  __/ | | |  ___) |__   _|__| |_| | | | \__ \ || (_| |
|_) | |  __/
>  /_/\_\___|_| |_| |____(_) |_|     \__,_|_|
|_|___/\__\__,_|_.__/|_|\___|
>                                                                        
(XEN) Xen version 3.4-unstable (root@) (gcc version 4.3.2 (Ubuntu
4.3.2-1ubuntu11) ) Sun Feb 22 08:28:39 EST 2009
> (XEN) Latest ChangeSet: Thu Feb 19 11:07:33 2009 +0000 19232:84af3ded5b02
> (XEN) Command line: dom0_mem=1024M
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
> (XEN)  EDID info not retrieved because no DDC retrieval method detected
> (XEN) Disc information:
> (XEN)  Found 0 MBR
 signatures
> (XEN)  Found 2 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009ec00 (usable)
> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
> (XEN)  00000000000e4000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 00000000cff80000 (usable)
> (XEN)  00000000cff80000 - 00000000cff8e000 (ACPI data)
> (XEN)  00000000cff8e000 - 00000000cffe0000 (ACPI NVS)
> (XEN)  00000000cffe0000 - 00000000d0000000 (reserved)
> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> (XEN)  00000000ffe00000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 0000000230000000 (usable)
> (XEN) System RAM: 8191MB (8387704kB)
> (XEN) ACPI: RSDP 000FBB80, 0014 (r0 ACPIAM)
> (XEN) ACPI: RSDT CFF80000, 003C (r1 A_M_I_ OEMRSDT  10000730 MSFT      
97)
> (XEN) ACPI: FACP CFF80200, 0084 (r2 A_M_I_ OEMFACP  10000730 MSFT  
    
97)
> (XEN) ACPI: DSDT CFF805C0, 8E13 (r1  A0840 A0840001        1 INTL
20060113)
> (XEN) ACPI: FACS CFF8E000, 0040
> (XEN) ACPI: APIC CFF80390, 006C (r1 A_M_I_ OEMAPIC  10000730 MSFT      
97)
> (XEN) ACPI: MCFG CFF80400, 003C (r1 A_M_I_ OEMMCFG  10000730 MSFT      
97)
> (XEN) ACPI: OEMB CFF8E040, 0081 (r1 A_M_I_ AMI_OEM  10000730 MSFT      
97)
> (XEN) ACPI: HPET CFF893E0, 0038 (r1 A_M_I_ OEMHPET  10000730 MSFT      
97)
> (XEN) ACPI: OSFR CFF89420, 00B0 (r1 A_M_I_ OEMOSFR  10000730 MSFT      
97)
> (XEN) NUMA turned off
> (XEN) Faking a node at 0000000000000000-0000000230000000
> (XEN) Domain heap initialised
> (XEN) found SMP MP-table at 000ff780
> (XEN) DMI 2.4 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: PM-Timer IO Port: 0x808
> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
> (XEN) ACPI:            
      wakeup_vec[cff8e00c], vec_size[20]
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> (XEN) Processor #0 7:7 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> (XEN) Processor #1 7:7 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
> (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) ACPI: IRQ9 used by override.
> (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
> (XEN) ACPI: HPET id: 0xffffffff
 base: 0xfed00000
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Initializing CPU#0
> (XEN) Detected 3005.653 MHz processor.
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 6144K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU: Processor Core ID: 0
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN) HVM: VMX enabled
> (XEN) MCE: Intel newly family MC Init
> (XEN) Intel machine check reporting enabled on CPU#0.
> (XEN) CPU0: Thermal monitoring enabled (TM2)
> (XEN) CMCI: CPU0 has no CMCI support
> (XEN) CPU0: Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz stepping 06
> (XEN) Booting processor 1/1 eip 8c000
>
 (XEN) Initializing CPU#1
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 6144K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU: Processor Core ID: 1
> (XEN) MCE: Intel newly family MC Init
> (XEN) Intel machine check reporting enabled on CPU#1.
> (XEN) CPU1: Thermal monitoring enabled (TM2)
> (XEN) CMCI: CPU1 has no CMCI support
> (XEN) CPU1: Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz stepping 06
> (XEN) Total of 2 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using new ACK method
> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
> (XEN) checking TSC synchronization across 2 CPUs: passed.
> (XEN) Platform timer is 14.318MHz HPET
> (XEN) Brought up 2 CPUs
> (XEN) microcode.c:73:d32767 microcode: CPU1 resumed
> (XEN) I/O virtualisation disabled
> (XEN) ACPI sleep modes: S3
>
 (XEN) mcheck_poll: Init_mcheck_timer
> (XEN) mcheck_poll: Machine check polling timer started.
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) elf_parse_binary: phdr: paddr=0x200000 memsz=0x494000
> (XEN) elf_parse_binary: phdr: paddr=0x694000 memsz=0x953d4
> (XEN) elf_parse_binary: phdr: paddr=0x72a000 memsz=0x8c8
> (XEN) elf_parse_binary: phdr: paddr=0x72c000 memsz=0x88086
> (XEN) elf_parse_binary: phdr: paddr=0x7b5000 memsz=0x12560
> (XEN) elf_parse_binary: phdr: paddr=0x7c8000 memsz=0x111d20
> (XEN) elf_parse_binary: memory: 0x200000 -> 0x8d9d20
> (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 = 0xffffffff80000000
> (XEN) elf_xen_parse_note: ENTRY = 0xffffffff80756200
> (XEN) elf_xen_parse_note: HYPERCALL_PAGE =
 0xffffffff80209000
> (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_parse_note: unknown xen elf note (0xd)
> (XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
> (XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
> (XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
> (XEN) elf_xen_addr_calc_check: addresses:
> (XEN)     virt_base        = 0xffffffff80000000
> (XEN)     elf_paddr_offset = 0x0
> (XEN)     virt_offset      = 0xffffffff80000000
> (XEN)     virt_kstart      = 0xffffffff80200000
> (XEN)     virt_kend        = 0xffffffff808d9d20
> (XEN)     virt_entry       = 0xffffffff80756200
> (XEN)     p2m_base         = 0xffffffffffffffff
> (XEN)  Xen  kernel: 64-bit, lsb, compat32
> (XEN)  Dom0 kernel: 64-bit,
 PAE, lsb, paddr 0x200000 -> 0x8d9d20
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000210000000->0000000220000000 (196608 pages
to be allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80200000->ffffffff808d9d20
> (XEN)  Init. ramdisk: ffffffff808da000->ffffffff8bc37600
> (XEN)  Phys-Mach map: ffffffff8bc38000->ffffffff8be38000
> (XEN)  Start info:    ffffffff8be38000->ffffffff8be384b4
> (XEN)  Page tables:   ffffffff8be39000->ffffffff8be9c000
> (XEN)  Boot stack:    ffffffff8be9c000->ffffffff8be9d000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff8c000000
> (XEN)  ENTRY ADDRESS: ffffffff80756200
> (XEN) Dom0 has maximum 2 VCPUs
> (XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 ->
0xffffffff80694000
> (XEN) elf_load_binary: phdr 1 at 0xffffffff80694000
 ->
0xffffffff807293d4
> (XEN) elf_load_binary: phdr 2 at 0xffffffff8072a000 ->
0xffffffff8072a8c8
> (XEN) elf_load_binary: phdr 3 at 0xffffffff8072c000 ->
0xffffffff807b4086
> (XEN) elf_load_binary: phdr 4 at 0xffffffff807b5000 ->
0xffffffff807c7560
> (XEN) elf_load_binary: phdr 5 at 0xffffffff807c8000 ->
0xffffffff807c8000
> (XEN) Scrubbing Free RAM:
.......................................................................done.
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: All
> (XEN) Guest Loglevel: All
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times
to switch input to Xen)
> (XEN) Freed 124kB init memory.
> (XEN) io_apic.c:2147:
> (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1
> (XEN) ioapic_guest_write: old_entry=000009f0,
 new_entry=00010900
> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
> (XEN) irq.c:930: dom0: pirq 2 or vector 152 already mapped
> (XEN) io_apic.c:2160:
> (XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16
> (XEN) ioapic_guest_write: old_entry=0000a9a0, new_entry=0001a9a0
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN) io_apic.c:2160:
> (XEN) ioapic_guest_write: apic=0, pin=17, old_irq=17, new_irq=17
> (XEN) ioapic_guest_write: old_entry=0000a9a8, new_entry=0001a9a8
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN) io_apic.c:2160:
> (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18
> (XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN)
 io_apic.c:2160:
> (XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23
> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN) io_apic.c:2160:
> (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18
> (XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN) io_apic.c:2160:
> (XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16
> (XEN) ioapic_guest_write: old_entry=0000a9a0, new_entry=0001a9a0
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN) io_apic.c:2160:
> (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19
> (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0
> (XEN) ioapic_guest_write:
 Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN) io_apic.c:2160:
> (XEN) ioapic_guest_write: apic=0, pin=22, old_irq=22, new_irq=22
> (XEN) ioapic_guest_write: old_entry=0000a9b0, new_entry=0001a9b0
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> 
> 

Yes, I've started seeing this too; it looks like something's trying to
mask the ioapic pins, but I'm not sure what changed.  It doesn't seem to
have any bad effects on my machine.  Does anything actually malfunction for you?

   J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel