On Tue, Oct 27, 2009 at 05:22:56PM +0200, Valtteri Kiviniemi wrote:
> Hi,
>
> We are testing the latest xen-unstable and found an interesting bug.
> dom0 detects cpu speed correctly but when booting domU it detects it
> incorrectly:
>
It's not a bug, it's a feature :)
See: http://lists.xensource.com/archives/html/xen-devel/2009-10/msg01097.html
-- Pasi
> "Detected 1000.000 MHz processor."
>
> domU config:
>
> kernel = "/boot/bzImage-domU"
> builder = "linux"
> memory = "512"
> name = "test"
> vcpus = "8"
> cpus = [ "0", "1", "2", "3", "4", "5", "6", "7" ]
> vif = [ "mac=00:50:56:14:89:13, bridge=eth0" ]
> disk = [ "phy:/dev/virtuals/test,xvda1,w",
> "phy:/dev/backups/test,xvda2,w" ]
> root = "/dev/xvda1 ro"
> extra = "console=hvc0"
> on_poweroff = "destroy"
> on_reboot = "restart"
> on_crash = "restart"
>
> cpu info from domU:
>
> test:~# cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Xeon(R) CPU E5420 @ 2.50GHz
> stepping : 6
> cpu MHz : 1000.000
> cache size : 6144 KB
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu de tsc msr pae cx8 sep cmov clflush mmx fxsr sse
> sse2 ss ht syscall nx lm constant_tsc rep_good pni ssse3 cx16 sse4_1
> hypervisor lahf_lm
> bogomips : 2000.00
> clflush size : 64
> cache_alignment : 64
> address sizes : 38 bits physical, 48 bits virtual
> power management:
>
> domU's boot output:
>
> Linux version 2.6.31.4-domU-00396-g9cf89da (root@xen) (gcc version 4.3.4
> (Debian 4.3.4-5) ) #15 SMP Mon Oct 26 19:25:50 EET 2009
> Command line: root=/dev/xvda1 ro console=hvc0
> KERNEL supported cpus:
> Intel GenuineIntel
> AMD AuthenticAMD
> Centaur CentaurHauls
> released 0 pages of unused memory
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 00000000000a0000 (usable)
> Xen: 00000000000a0000 - 0000000000100000 (reserved)
> Xen: 0000000000100000 - 0000000020000000 (usable)
> DMI not present or invalid.
> last_pfn = 0x20000 max_arch_pfn = 0x400000000
> init_memory_mapping: 0000000000000000-0000000020000000
> (6 early reservations) ==> bootmem [0000000000 - 0020000000]
> #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 -
> 0000001000]
> #1 [00015fe000 - 000160d000] XEN PAGETABLES ==> [00015fe000 -
> 000160d000]
> #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 -
> 0000008000]
> #3 [0001000000 - 00014da804] TEXT DATA BSS ==> [0001000000 -
> 00014da804]
> #4 [00014fb000 - 00015fe000] XEN START INFO ==> [00014fb000 -
> 00015fe000]
> #5 [0000100000 - 00001f0000] PGTABLE ==> [0000100000 -
> 00001f0000]
> Zone PFN ranges:
> DMA 0x00000000 -> 0x00001000
> DMA32 0x00001000 -> 0x00100000
> Normal 0x00100000 -> 0x00100000
> Movable zone start PFN for each node
> early_node_map[2] active PFN ranges
> 0: 0x00000000 -> 0x000000a0
> 0: 0x00000100 -> 0x00020000
> SMP: Allowing 8 CPUs, 0 hotplug CPUs
> No local APIC present
> APIC: disable apic facility
> Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000)
> NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
> PERCPU: Allocated 19 4k pages, static data 74976 bytes
> Xen: using vcpu_info placement
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 128941
> Kernel command line: root=/dev/xvda1 ro console=hvc0
> PID hash table entries: 2048 (order: 11, 16384 bytes)
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Initializing CPU#0
> Memory: 507316k/524288k available (2788k kernel code, 384k absent,
> 15860k reserved, 1353k data, 328k init)
> SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
> NR_IRQS:512
> Detected 1000.000 MHz processor.
> Console: colour dummy device 80x25
> console [tty0] enabled
> console [hvc0] enabled
> installing Xen timer for CPU 0
> Calibrating delay loop (skipped), value calculated using timer
> frequency.. 2000.00 BogoMIPS (lpj=10000000)
> Mount-cache hash table entries: 256
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> SMP alternatives: switching to UP code
> installing Xen timer for CPU 1
> SMP alternatives: switching to SMP code
> Initializing CPU#1
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> installing Xen timer for CPU 2
> Initializing CPU#2
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> installing Xen timer for CPU 3
> Initializing CPU#3
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> installing Xen timer for CPU 4
> Initializing CPU#4
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> installing Xen timer for CPU 5
> Initializing CPU#5
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> installing Xen timer for CPU 6
> Initializing CPU#6
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> installing Xen timer for CPU 7
> Initializing CPU#7
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> Brought up 8 CPUs
> Booting paravirtualized kernel on Xen
> Xen version: 3.5-unstable (preserve-AD)
> Using V2 grant tables.
> Grant table initialized
> NET: Registered protocol family 16
> xenbus_probe wake_waiting
> xenbus_probe_init ok
> bio: create slab <bio-0> at 0
> xenbus_probe_frontend_init bus registered ok
> xenbus_probe_devices device
> xenbus_probe_devices 1/3 vbd
> xenbus_probe_device_type type vbd
> xenbus_probe_device_type 1/2 51713
> xenbus_probe_device_type 2/2 51714
> xenbus_probe_device_type done
> xenbus_probe_devices 2/3 vif
> xenbus_probe_device_type type vif
> xenbus_probe_device_type 1/1 0
> xenbus_probe_device_type done
> xenbus_probe_devices 3/3 console
> xenbus_probe_device_type type console
> xenbus_probe_device_type 1/1 0
> xenbus_probe_device_type done
> xenbus_probe_devices done
> frontend_probe_and_watch devices probed ok
> frontend_probe_and_watch watch add ok ok
> frontend_probe_and_watch all done
> xen_balloon: Initialising balloon driver.
> SCSI subsystem initialized
> NET: Registered protocol family 2
> IP route cache hash table entries: 16384 (order: 5, 131072 bytes)
> TCP established hash table entries: 65536 (order: 8, 1048576 bytes)
> TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
> TCP: Hash tables configured (established 65536 bind 65536)
> TCP reno registered
> NET: Registered protocol family 1
> platform rtc_cmos: registered platform RTC device (no PNP device found)
> Installing knfsd (copyright (C) 1996 okir@xxxxxxxxxxxx).
> fuse init (API version 7.12)
> SGI XFS with ACLs, security attributes, realtime, large block/inode
> numbers, no debug enabled
> SGI XFS Quota Management subsystem
> msgmni has been set to 992
> alg: No test for stdrng (krng)
> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
> io scheduler noop registered
> io scheduler cfq registered (default)
> Event-channel device installed.
> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> blkfront: xvda1: barriers enabled
> Initialising Xen virtual ethernet driver.
> blkfront: xvda2: barriers enabled
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> Netfilter messages via NETLINK v0.30.
> nf_conntrack version 0.5.0 (4096 buckets, 16384 max)
> CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
> nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
> sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
> ctnetlink v0.93: registering with nfnetlink.
> NF_TPROXY: Transparent proxy support initialized, version 4.1.0
> NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
> xt_time: kernel timezone is -0000
> ip_tables: (C) 2000-2006 Netfilter Core Team
> ClusterIP Version 0.8 loaded successfully
> TCP cubic registered
> Initializing XFRM netlink socket
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> 802.1Q VLAN Support v1.8 Ben Greear <greearb@xxxxxxxxxxxxxxx>
> All bugs added by David S. Miller <davem@xxxxxxxxxx>
> registered taskstats version 1
> XENBUS: Device with no driver: device/console/0
> XFS mounting filesystem xvda1
> VFS: Mounted root (xfs filesystem) readonly on device 202:1.
> Freeing unused kernel memory: 328k freed
> INIT: version 2.86 booting
> Starting the hotplug events dispatcher: udevd.
> Synthesizing the initial hotplug events...done.
> Waiting for /dev to be fully populated...done.
> Activating swap...done.
> Checking root file system...fsck from util-linux-ng 2.16.1
> /sbin/fsck.xfs: XFS file system.
> done.
> Cleaning up ifupdown....
> Checking file systems...fsck from util-linux-ng 2.16.1
> /sbin/fsck.xfs: XFS file system.
> done.
> Setting up networking....
> Mounting local filesystems...XFS mounting filesystem xvda2
> done.
> Activating swapfile swap...done.
> Cleaning up temporary files....
> Configuring network interfaces...if-up.d/mountnfs[eth0]: waiting for
> interface eth0:1 before doing NFS mounts ... (warning).
> done.
> Setting kernel variables (/etc/sysctl.conf)...done.
> Starting portmap daemon....
> Starting NFS common utilities: statd.
> Cleaning up temporary files....
> INIT: Entering runlevel: 2
> Starting Zabbix agent: zabbix_agentd
> Starting NFS common utilities: statd.
> Starting enhanced syslogd: rsyslogd.
> Starting web server: apache2.
> Starting periodic command scheduler: cron.
> Starting MTA: exim4.
> Starting ident daemon: oidentd.
> Starting OpenBSD Secure Shell server: sshd.
>
> Debian GNU/Linux squeeze/sid test hvc0
>
> test login:
>
> - Valtteri Kiviniemi
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home