WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] More questions on Xen

You can tell with an "xm list".  If you have Dom0 and 2 DomU's running,
unless you pinned each dom to the same processor, XEN should have at
least one of three on the second processor.  An example of what a dual
processor box looks like would be:

xen0 root # xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      155    0  r----  231393.8
domU-1             1       31    1  -b---  181150.6    9601
domU-2             2      127    0  -b---  163574.0    9602
domU-3             3       31    1  -b---    785.2    9603
domU-4             4       79    0  -----  151464.4    9604


See the column "CPU".  It shows to which XEN cpu the dom is running on.

B.








On Sun, 2005-02-27 at 07:42, Franck wrote:
> >>>This is OK, each guest only sees one processor. If you start another 
> >>>domain it will use the second one.
> >>
> >>No, i don't think because i'm on my host guest, not in guest.
> >>
> > 
> > What does "xm dmesg" show?  Remember, XEN is sitting between Dom0 and
> > your hardware.  XEN should report 2+ processors on an SMP box, however
> > Dom0 will only "see" one.
> 
> Ok, dmeg look like 2 CPU and assign only CPU0 to dom0
> I've 2 xenU guest running, each one has 1 CPU ?
> How can i find if the 2 CPU are working on the system ?
> 
> 
> xm dmesg
> [...]
> (XEN) CPU0: Before vendor init, caps: 0183fbff 00000000 00000000, vendor = 0
> (XEN) CPU caps: 0183fbff 00000000 00000000 00000000
> (XEN) found SMP MP-table at 000f5ae0
> (XEN) ACPI: RSDP (v000 ABIT                                      ) @ 
> 0x000f7370
> (XEN) ACPI: RSDT (v001 ABIT   AWRDACPI 0x42302e31 AWRD 0x00000000) @ 
> 0x11ff3000
> (XEN) ACPI: FADT (v001 ABIT   AWRDACPI 0x42302e31 AWRD 0x00000000) @ 
> 0x11ff3040
> (XEN) ACPI: MADT (v001 ABIT            0x00000000  0x00000000) @ 0x11ff54c0
> (XEN) ACPI: DSDT (v001 ABIT   AWRDACPI 0x00001000 MSFT 0x0100000c) @ 
> 0x00000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> (XEN) Processor #0 Pentium(tm) Pro APIC version 17
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> (XEN) Processor #1 Pentium(tm) Pro APIC version 17
> (XEN) Using ACPI for processor (LAPIC) configuration information
> (XEN) Intel MultiProcessor Specification v1.4
> (XEN)     Virtual Wire compatibility mode.
> (XEN) OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
> (XEN) I/O APIC #2 Version 17 at 0xFEC00000.
> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
> (XEN) Processors: 2
> (XEN) Using scheduler: Borrowed Virtual Time (bvt)
> (XEN) Initializing CPU#0
> (XEN) Detected 367.508 MHz processor.
> (XEN) CPU0: Before vendor init, caps: 0183fbff 00000000 00000000, vendor = 0
> (XEN) CPU caps: 0183fbff 00000000 00000000 00000000
> (XEN) CPU0 booted
> (XEN) enabled ExtINT on CPU#0
> (XEN) ESR value before enabling vector: 00000000
> (XEN) ESR value after enabling vector: 00000000
> (XEN) Booting processor 1/1 eip 90000
> (XEN) Initializing CPU#1
> (XEN) masked ExtINT on CPU#1
> (XEN) ESR value before enabling vector: 00000000
> (XEN) ESR value after enabling vector: 00000000
> (XEN) CPU1: Before vendor init, caps: 0183fbff 00000000 00000000, vendor = 0
> (XEN) CPU caps: 0183fbff 00000000 00000000 00000000
> (XEN) CPU1 has booted.
> (XEN) Total of 2 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN) Setting 2 in the phys_id_present_map
> (XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
> (XEN) init IO_APIC IRQs
> (XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
> (XEN) Using local APIC timer interrupts.
> (XEN) Calibrating APIC timer for CPU0...
> (XEN) ..... CPU speed is 367.5020 MHz.
> (XEN) ..... Bus speed is 66.8184 MHz.
> (XEN) ..... bus_scale = 0x0000446D
> (XEN) checking TSC synchronization across CPUs: passed.
> (XEN) Time init:
> (XEN) .... System Time: 60875099ns
> (XEN) .... cpu_freq:    00000000:15E7BDE0
> (XEN) .... scale:       00000002:B894E76A
> (XEN) .... Wall Clock:  1109504276s 190000us
> (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfb5c0, last bus=1
> (XEN) PCI: Using configuration type 1
> (XEN) PCI: Probing PCI hardware
> (XEN) PCI: Probing PCI hardware (bus 00)
> (XEN) PCI: Using IRQ router PIIX/ICH [8086/7110] at 00:07.0
> (XEN) PCI->APIC IRQ transform: (B0,I9,P0) -> 19
> (XEN) PCI->APIC IRQ transform: (B0,I13,P0) -> 17
> (XEN) PCI->APIC IRQ transform: (B0,I19,P0) -> 18
> (XEN) PCI->APIC IRQ transform: (B0,I19,P1) -> 18
> (XEN) PCI->APIC IRQ transform: (B1,I0,P0) -> 16
> (XEN) Limiting direct PCI/PCI transfers.
> (XEN) mtrr: v2.0 (20020519)
> (XEN) mtrr: your CPUs had inconsistent fixed MTRR settings
> (XEN) mtrr: probably your BIOS does not setup all CPUs.
> (XEN) mtrr: corrected configuration.
> (XEN) *** LOADING DOMAIN 0 ***
> [...]
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>