I have a 2 way machine. Soliciting folks opinion on whether it makes sense to smp enable DOM0 so that IO handling can be balanced over both CPU''s... Opinions? Thanks, Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I have a 2 way machine. Soliciting folks opinion on whether > it makes sense to smp enable DOM0 so that IO handling can be > balanced over both CPU''s...Its generally not helpful to have an SMP dom0. In high IO situations it''s typically best to dedicate a hyperthread or core to dom0. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>> I have a 2 way machine. Soliciting folks opinion on whether >> it makes sense to smp enable DOM0 so that IO handling can be >> balanced over both CPU''s... > >Its generally not helpful to have an SMP dom0. In high IO situations >it''s typically best to dedicate a hyperthread or core to dom0. > >IanHow does one make the dedication of a CPU to dom0? Seems like pincpu is the control mechanism, but if I understand pincpu correctly, it doesn''t prevent other domains from sharing the chosen CPU. It pegs the domain to the CPU, but not the reverse. Also, how can one distinguish an ht CPU vs a core CPU? Alan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> >> I have a 2 way machine. Soliciting folks opinion on > whether it makes > >> sense to smp enable DOM0 so that IO handling can be balanced over > >> both CPU''s... > > > >Its generally not helpful to have an SMP dom0. In high IO situations > >it''s typically best to dedicate a hyperthread or core to dom0.> How does one make the dedication of a CPU to dom0? Seems > like pincpu is > the control mechanism, but if I understand pincpu correctly, > it doesn''t > prevent other domains from sharing the chosen CPU. It pegs > the domain to > the CPU, but not the reverse.If you create a pincpu mask for the over domains/VCPUs that doesn''t include the CPU in question, they won''t use it. I guess a shorthand command for this would be useful.> Also, how can one distinguish an ht CPU vs a core CPU?All hyperthreads of a core are enumerated before moving on to the next core; All cores are enumerated before the next socket. We''ve proposed changing the CPU naming convention to a ''.'' seperated form to make this more explicit. I thought Ryan may have even knocked up a patch for this at one point (?) Ryan, if so, please can you dust off and resend. As I recall, the key fix it needed was that it should be xend (not xm) that does the translation from the dot''ed form into CPU numbers. Thanks, Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Also, how can one distinguish an ht CPU vs a core CPU? > > All hyperthreads of a core are enumerated before moving on to > the next core; All cores are enumerated before the next > socket. We''ve proposed changing the CPU naming convention to > a ''.'' seperated form to make this more explicit.Just to be clear: Imagine a 2 socket box with dual core hyperthreaded Xeons: cpu# thread core socket 0 0 0 0 1 1 0 0 2 0 1 0 3 1 1 0 4 0 0 1 5 1 0 1 6 0 1 1 7 1 1 1 Best, Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi folks.
I use Fedora Core 4, and I am new to Xen. I have installed Xen packages
from FC4 yum repository, and it is not working. I believe I''m missing
some very basic configuration detail. These are my packages:
xen-2-20050522
kernel-xenU-2.6.12-1.1398_FC4
kernel-xen0-2.6.12-1.1398_FC4
The only configuration I''ve made was to modify grub.conf like this:
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.12-1.1398_FC4xen0)
root (hd0,0)
kernel /xen.gz dom0_mem=262144
module /vmlinuz-2.6.12-1.1398_FC4xen0 ro root=LABEL=/ 3
module /initrd-2.6.12-1.1398_FC4xen0.img
title Fedora Core (2.6.12-1.1398_FC4)
root (hd0,0)
kernel /vmlinuz-2.6.12-1.1398_FC4 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.12-1.1398_FC4.img
My problem is, when I''m booting up with Xen dom0 kernel, my system
simply hangs up when enabling eth0. If I boot I tryed to boot step by
step, skipping the eth0 enabling script, and it works fine.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi folks Never mind. This post has been on my Draft folder for some time, and I sent it today by mistake. I already has it fixed. Sorry! Danilo Gimenez Em Seg, 2005-08-08 às 11:20 -0300, Danilo Gimenez escreveu:> Hi folks. > > I use Fedora Core 4, and I am new to Xen. I have installed Xen > packages from FC4 yum repository, and it is not working. I believe I''m > missing some very basic configuration detail. These are my packages: > > xen-2-20050522 > kernel-xenU-2.6.12-1.1398_FC4 > kernel-xen0-2.6.12-1.1398_FC4 > > The only configuration I''ve made was to modify grub.conf, adding a > "dom0_mem" tag, and replacing "rhgb quiet" by "3" (in order to boot on > runlevel 3). My grub.conf now seems like this: > > default=1 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title Fedora Core (2.6.12-1.1398_FC4xen0) > root (hd0,0) > kernel /xen.gz dom0_mem=262144 > module /vmlinuz-2.6.12-1.1398_FC4xen0 ro root=LABEL=/ 3 > module /initrd-2.6.12-1.1398_FC4xen0.img > title Fedora Core (2.6.12-1.1398_FC4) > root (hd0,0) > kernel /vmlinuz-2.6.12-1.1398_FC4 ro root=LABEL=/ rhgb quiet > initrd /initrd-2.6.12-1.1398_FC4.img > > My problem is, when I''m booting up with Xen dom0 kernel, my system > simply hangs up when enabling eth0. IF I try to boot step-by-step, and > choose NOT to enable eth0, all works fine. Even lo0 is up! Then I''m > able to run "service xend start", and even to create a domain. If I > try to run "ifup eth0" on Dom0, my system hangs up again... > > In other words, I just do not have any eth0 on Dom0... What am I > missing? > > This is a "xm info" output: > > system : Linux > host : myhost33.mydomain.com.br > release : 2.6.12-1.1398_FC4xen0 > version : #1 SMP Fri Jul 15 01:53:34 EDT 2005 > machine : i686 > cores : 1 > hyperthreads_per_core : 1 > cpu_mhz : 801 > memory : 767 > free_memory : 496 > > And this is a "xm dmesg" result: > > ERROR: cannot use unconfigured serial port COM1 > __ __ _____ ___ _ _ > \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | > \ // _ \ ''_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ | > / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ | > /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_| > > http://www.cl.cam.ac.uk/netos/xen > University of Cambridge Computer Laboratory > > Xen version 3.0-devel (bhcompile@build.redhat.com) (gcc version 4.0.0 > 20050519 (Red Hat 4.0.0-8)) Mon May 23 07:47:32 EDT 2005 > Latest ChangeSet: information unavailable > > (XEN) Physical RAM map: > (XEN) 0000000000000000 - 000000000009fc00 (usable) > (XEN) 000000000009fc00 - 00000000000a0000 (reserved) > (XEN) 00000000000f0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 000000002ffec000 (usable) > (XEN) 000000002ffec000 - 000000002ffef000 (ACPI data) > (XEN) 000000002ffef000 - 000000002ffff000 (reserved) > (XEN) 000000002ffff000 - 0000000030000000 (ACPI NVS) > (XEN) 00000000ffff0000 - 0000000100000000 (reserved) > (XEN) System RAM: 767MB (785964kB) > (XEN) Xen heap: 10MB (10760kB) > (XEN) CPU0: Before vendor init, caps: 0383f9ff 00000000 00000000, > vendor = 0 > (XEN) CPU caps: 0383f9ff 00000000 00000000 00000000 > (XEN) ACPI: RSDP (v000 ASUS ) @ > 0x000f6920 > (XEN) ACPI: RSDT (v001 ASUS CUV4X 0x30303031 MSFT 0x31313031) @ > 0x2ffec000 > (XEN) ACPI: FADT (v001 ASUS CUV4X 0x30303031 MSFT 0x31313031) @ > 0x2ffec080 > (XEN) ACPI: BOOT (v001 ASUS CUV4X 0x30303031 MSFT 0x31313031) @ > 0x2ffec040 > (XEN) ACPI: DSDT (v001 ASUS CUV4X 0x00001000 MSFT 0x0100000b) @ > 0x00000000 > (XEN) Local APIC disabled by BIOS -- reenabling. > (XEN) Found and enabled local APIC! > (XEN) Using scheduler: Borrowed Virtual Time (bvt) > (XEN) Initializing CPU#0 > (XEN) Detected 801.827 MHz processor. > (XEN) CPU0 booted > (XEN) SMP motherboard not detected. > (XEN) enabled ExtINT on CPU#0 > (XEN) Using local APIC timer interrupts. > (XEN) Calibrating APIC timer for CPU0... > (XEN) ..... CPU clock speed is 801.8309 MHz. > (XEN) ..... host bus clock speed is 100.2287 MHz. > (XEN) ..... bus_scale = 0x000066A2 > (XEN) Time init: > (XEN) .... System Time: 10544007ns > (XEN) .... cpu_freq: 00000000:2FCAEA70 > (XEN) .... scale: 00000001:3F454BEF > (XEN) .... Wall Clock: 1123510226s 20000us > (XEN) PCI: PCI BIOS revision 2.10 entry at 0xf0cc0, 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 VIA [1106/0686] at 00:04.0 > (XEN) PCI: Disabling Via external APIC routing > (XEN) mtrr: v2.0 (20020519) > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen-ELF header found: > ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,LOADER=generic'' > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 10000000->20000000 > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: c0100000->c0471658 > (XEN) Init. ramdisk: c0472000->c06ad400 > (XEN) Phys-Mach map: c06ae000->c06ee000 > (XEN) Page tables: c06ee000->c06f1000 > (XEN) Start info: c06f1000->c06f2000 > (XEN) Boot stack: c06f2000->c06f3000 > (XEN) TOTAL: c0000000->c0800000 > (XEN) ENTRY ADDRESS: c0100000 > (XEN) Initrd len 0x23b400, start at 0xc0472000 > (XEN) Scrubbing Free RAM: ........done. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch > input to Xen). > (XEN) PCI: Found IRQ 9 for device 00:10.0 > (XEN) PCI: Found IRQ 10 for device 00:04.5 > (XEN) PCI: Found IRQ 9 for device 00:04.2 > (XEN) PCI: Sharing IRQ 9 with 00:04.3 > (XEN) PCI: Found IRQ 9 for device 00:04.3 > (XEN) PCI: Sharing IRQ 9 with 00:04.2 > > Thanks in advance, > Danilo Gimenez_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
* Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> [2005-08-08 08:58]:> > > >> I have a 2 way machine. Soliciting folks opinion on > > whether it makes > > >> sense to smp enable DOM0 so that IO handling can be balanced over > > >> both CPU''s... > > > > > >Its generally not helpful to have an SMP dom0. In high IO situations > > >it''s typically best to dedicate a hyperthread or core to dom0. > > > How does one make the dedication of a CPU to dom0? Seems > > like pincpu is > > the control mechanism, but if I understand pincpu correctly, > > it doesn''t > > prevent other domains from sharing the chosen CPU. It pegs > > the domain to > > the CPU, but not the reverse. > > If you create a pincpu mask for the over domains/VCPUs that doesn''t > include the CPU in question, they won''t use it. I guess a shorthand > command for this would be useful.Something like: xm dedicate DOM CPU which would generate the appropriate pincpu ops to push all other doms'' vcpus off of CPU.> > > Also, how can one distinguish an ht CPU vs a core CPU? > > All hyperthreads of a core are enumerated before moving on to the next > core; All cores are enumerated before the next socket. We''ve proposed > changing the CPU naming convention to a ''.'' seperated form to make this > more explicit. > > I thought Ryan may have even knocked up a patch for this at one point > (?) > Ryan, if so, please can you dust off and resend. As I recall, the key > fix it needed was that it should be xend (not xm) that does the > translation from the dot''ed form into CPU numbers.Certainly it will be easier to do so in xend, but I''m more concerned with the hypervisor being responsible responsible for choosing the vcpu to cpu mapping. I''d like to see dom creation support the passing of a cpumap and have the hypervisor cycle through the physical cpus marked therein. This would remove the logic of mapping vcpus to cpus from the hypervisor and let the dom creation tools build whatever algorithm for distributing vcpus across cpus as it sees fit. If you are interested in this it means changing the hypercall interface and so it should be done for 3.0, however I don''t want to push for significant changes so close to the testing freeze as I want to help close features down rather than create new ones. -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@us.ibm.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users