Xen users - Apr 2009 - Config to set CPU affinity and distribute interrupts

Hi,
 
I have some problems to configure the xen I''ve installed (3.3.1). The
computer is a Intel Core 2 Duo, I''m using Ubuntu 8.10 and have linux in
my dom0 and winxp pro in my domU.
I have two cores and I''d like to set the affinity of dom0 to cpu0 and
domU to cpu1 but I haven''t find the way of making this permanent.
I''ve set cpus=1 in the domU config file and everytime I start my
computer I make:
xm vcpu-set 0 1
xm vcpu-pin  0 0 0
After making this I make xm vcpu-list and I can see:
Name          ID VCPU CPU State Time(s) CPU Affinity
Domain-0 0      0      0 r--      51.5 0
Domain-0    0      1      - --p      19.4   any   cpu
winxp             1      0      1 r--      9.8 1
How can I get this without having to enter the previous commands everytime I
restart my computer?
 
Another problem that I have is that when I run my domU everything goes fine but
I can''t go back to my dom0 unless I shut it down. Windows starts in
full screen and the only way of going back is by pressing Alt+Tab. I can see
Linux just for a second and then the Windows screen appears. Why could this
happen? I''ll let some info about my configuration.
CPUINFO:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU L7400 @ 1.50GHz
stepping : 6
cpu MHz : 1500.120
cache size : 4096 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush acpi mmx fxsr sse sse2
ss ht constant_tsc up pni est
bogomips : 3001.82
 
DMESG:
(XEN) Xen version 3.3.1 (root@) (gcc versión 4.3.2 (Ubuntu 4.3.2-1ubuntu12) )
Fri Apr 3 12:12:09 CEST 2009
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: dom0_mem=1024000
(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 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009dc00 (usable)
(XEN) 000000000009dc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007f650000 (usable)
(XEN) 000000007f650000 - 000000007f660000 (ACPI data)
(XEN) 000000007f660000 - 000000007f661000 (ACPI NVS)
(XEN) 000000007f661000 - 0000000080000000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ff000000 - 0000000100000000 (reserved)
(XEN) System RAM: 2037MB (2086836kB)
(XEN) ACPI: RSDP 000F6CF0, 0024 (r2 PTLTD )
(XEN) ACPI: XSDT 7F658B20, 008C (r1 PTLTD XSDT 6040000 LTP 0)
(XEN) ACPI: FACP 7F65FD48, 00F4 (r3 INTEL CALISTGA 6040000 ALAN 1)
(XEN) ACPI: DSDT 7F65A2FE, 59D6 (r1 KTRON MCAL 6040000 INTL 20060113)
(XEN) ACPI: FACS 7F660FC0, 0040
(XEN) ACPI: APIC 7F65FE3C, 0068 (r1 INTEL CALISTGA 6040000 LOHR 5A)
(XEN) ACPI: HPET 7F65FEA4, 0038 (r1 INTEL CALISTGA 6040000 LOHR 5A)
(XEN) ACPI: MCFG 7F65FEDC, 003C (r1 INTEL CALISTGA 6040000 LOHR 5A)
(XEN) ACPI: TCPA 7F65FF18, 0032 (r1 PTLTD CALISTGA 6040000 PTL 1)
(XEN) ACPI: TMOR 7F65FF4A, 0026 (r1 PTLTD 6040000 PTL 3)
(XEN) ACPI: APIC 7F65FF70, 0068 (r1 PTLTD APIC 6040000 LTP 0)
(XEN) ACPI: BOOT 7F65FFD8, 0028 (r1 PTLTD $SBFTBL$ 6040000 LTP 1)
(XEN) ACPI: SSDT 7F659CAF, 064F (r1 SataRe SataPri 1000 INTL 20050624)
(XEN) ACPI: SSDT 7F659613, 069C (r1 SataRe SataSec 1000 INTL 20050624)
(XEN) ACPI: SSDT 7F659138, 025F (r1 PmRef Cpu0Tst 3000 INTL 20050624)
(XEN) ACPI: SSDT 7F659092, 00A6 (r1 PmRef Cpu1Tst 3000 INTL 20050624)
(XEN) ACPI: SSDT 7F658BAC, 04E6 (r1 PmRef CpuPm 3000 INTL 20050624)
(XEN) ACPI: BIOS bug: multiple APIC/MADT found, using 0
(XEN) ACPI: If "acpi_apic_instance=2" works better, notify
linux-acpi@vger.kernel.org
(XEN) Xen heap: 9MB (9752kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 1500.160 MHz processor.
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Core(TM)2 CPU L7400 @ 1.50GHz stepping 06
(XEN) Booting processor 1/1 eip 8c000
(XEN) CPU1: Intel(R) Core(TM)2 CPU L7400 @ 1.50GHz stepping 06
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 32-bit, PAE, lsb
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc04994dc
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (247808 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c04994dc
(XEN) Init. ramdisk: c049a000->c1787000
(XEN) Phys-Mach map: c1787000->c1881000
(XEN) Start info: c1881000->c1881474
(XEN) Page tables: c1882000->c1895000
(XEN) Boot stack: c1895000->c1896000
(XEN) TOTAL: c0000000->c1c00000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: ..........done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch
input to Xen)
(XEN) Freed 100kB init memory.
(XEN) traps.c:2171:d0 Domain attempted WRMSR 0000019a from 00000000:00000002 to
00000000:00000000.
(XEN) traps.c:2171:d0 Domain attempted WRMSR 0000019a from 00000000:00000002 to
00000000:00000000.
(XEN) \047q\047 pressed -> dumping domain info (now=0xA6:793D9493)
(XEN) General information for domain 0:
(XEN) refcnt=3 nr_pages=247296 xenheap_pages=5 dirty_cpus={0}
(XEN) handle=00000000-0000-0000-0000-000000000000 vm_assist=0000000d
(XEN) Rangesets belonging to domain 0:
(XEN) Interrupts { 0-255 }
(XEN) I/O Memory { 0-febff, fec01-fedff, fee01-ffffffff }
(XEN) I/O Ports { 0-1f, 22-3f, 44-60, 62-9f, a2-cfb, d00-ffff }
(XEN) Memory pages belonging to domain 0:
(XEN) DomPage list too long to display
(XEN) XenPage 00000bed: caf=80000002, taf=e8000002
(XEN) XenPage 00000bec: caf=80000001, taf=e8000001
(XEN) XenPage 00000beb: caf=80000001, taf=e8000001
(XEN) XenPage 00000bea: caf=80000001, taf=e8000001
(XEN) XenPage 00000be9: caf=80000002, taf=e8000002
(XEN) VCPU information and callbacks for domain 0:
(XEN) VCPU0: CPU0 [has=T] flags=0 upcall_pend = 00, upcall_mask = 00
dirty_cpus={0} cpu_affinity={0}
(XEN) 100 Hz periodic timer (period 10 ms)
(XEN) Notifying guest (virq 1, port 0, stat 0/-1/0)
(XEN) VCPU1: CPU1 [has=F] flags=2 upcall_pend = 00, upcall_mask = 01
dirty_cpus={} cpu_affinity={0-31}
(XEN) 100 Hz periodic timer (period 10 ms)
(XEN) Notifying guest (virq 1, port 0, stat 0/-1/0)
(XEN) General information for domain 1:
(XEN) refcnt=3 nr_pages=264159 xenheap_pages=5 dirty_cpus={1}
(XEN) handle=1d4c4c87-db5b-083a-0907-a1d34bad46a3 vm_assist=00000000
(XEN) paging assistance: shadow refcounts translate external 
(XEN) Rangesets belonging to domain 1:
(XEN) Interrupts { }
(XEN) I/O Memory { }
(XEN) I/O Ports { }
(XEN) Memory pages belonging to domain 1:
(XEN) DomPage list too long to display
(XEN) XenPage 000001cf: caf=80000001, taf=e8000001
(XEN) XenPage 000001ce: caf=80000001, taf=e8000001
(XEN) XenPage 000001cd: caf=80000001, taf=e8000001
(XEN) XenPage 000001cc: caf=80000001, taf=e8000001
(XEN) XenPage 000001f2: caf=80000001, taf=e8000001
(XEN) VCPU information and callbacks for domain 1:
(XEN) VCPU0: CPU1 [has=T] flags=0 upcall_pend = 00, upcall_mask = 00
dirty_cpus={1} cpu_affinity={1}
(XEN) paging assistance: shadowed 2-on-3
(XEN) No periodic timer
(XEN) Notifying guest (virq 1, port 0, stat 0/-1/0)
 
WINXP.HVM (uncommented lines)
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 1024
name = "winxp"
vcpus=1
cpus = "1"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
disk = [ ''phy:/dev/sda,ioemu:hda,w'' ]
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot="c"
sdl=1
opengl=1
vnc=0
vncpasswd=''''
stdvga=0
serial=''pty''
 
Thanks,
 
Itziar


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

On Mon, Apr 6, 2009 at 1:20 PM, ITZIAR BALENCIAGA <ibalenciaga@aotek.es>
wrote:
> everytime I start my computer I make:
> xm vcpu-set 0 1
> xm vcpu-pin  0 0 0
> How can I get this without having to enter the previous commands everytime
I
> restart my computer?
http://lists.xensource.com/archives/html/xen-users/2009-03/msg00614.html
Look for "dom0_vcpus_pin" and "(dom0-cpus 1)"
>
> Another problem that I have is that when I run my domU everything goes fine
> but I can''t go back to my dom0 unless I shut it down. Windows
starts in full
> screen and the only way of going back is by pressing Alt+Tab. I can see
> Linux just for a second and then the Windows screen appears. Why could this
> happen?
> WINXP.HVM (uncommented lines)
> sdl=1 opengl=1 vnc=0
You''re using sdl. A better way is to use vnc:
-  Change it to :
sdl=0
vnc=1
- startup domU
- determine where domU''s vnc port is using "virsh vncdisplay
winxp"
- connect to it, using something like "vncviewer localhost:n", where
"n" is the number from virsh output.

Regards,

Fajar

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

Hi!
 
first of all sorry if I''m opening a new thread but I don''t
know how to reply to my own post because in my mailbox I don''t get the
messages individually but in groups.
Not write everything again here it is my previous post:
http://lists.xensource.com/archives/html/xen-users/2009-04/msg00132.html
 
I''ve changed my config to 
sdl=0
vnc=1
but when I create my domU with sudo xm create winxp.hvm it says that the domain
winxp was started but no console appears. Another thing is that I tried using
the command virsh list and it founds nothing but if I try xm list it sees the
domains. Do I have to create my domain with virsh to see it? Why don''t
I see even my dom0?
 
In my previous post I also forgot asking about where to change my config
distribute interrupts. What I want to do is a domain to handle just a concrete
interrupt without being disturbed for the others. Those would be handled by the
other domain. I don''t know if I''ve explained myself well but
I''d like to know if that''s possible and how to do it.
 
Thanks,
 
Itziar


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

Someone who can help me please? I don''t know what to do and since I
changed from sdl to vnc I can''t see anything. Anyone knows what could
be happenning?


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

On Mon, Apr 20, 2009 at 3:01 PM, ITZIAR BALENCIAGA <ibalenciaga@aotek.es>
wrote:
> Hi!
>
> first of all sorry if I''m opening a new thread but I
don''t know how to reply
> to my own post because in my mailbox I don''t get the messages
individually
> but in groups.
Then change it. Choose individual email instead of digest. It''s
somewhat selfish to expect others to help you when you don''t even want
to make such small effort.
> I''ve changed my config to
> sdl=0
> vnc=1
> but when I create my domU with sudo xm create winxp.hvm it says that the
> domain winxp was started but no console appears.
It''s not supposed to appear. Look at my previous answer, and you
should see that I told you to
"- determine where domU''s vnc port is using "virsh vncdisplay
winxp"
- connect to it, using something like "vncviewer localhost:n", where
"n" is the number from virsh output."

Note that you can also run "virt-manager" (the GUI is
self-explanatory), or run "virt-viewer domU_name" to connect to
domU''s
vnc console.

then again, the fact that even "virsh list" doesn''t work for
you makes
it somewhat complicated.
> Another thing is that I
> tried using the command virsh list and it founds nothing but if I try xm
> list it sees the domains. Do I have to create my domain with virsh to see
> it? Why don''t I see even my dom0?
>
If "virsh list" shows nothing but "xm list" shows domUs,
then
something is definitely wrong with your setup.
At this point my suggestion is to use a known working configuration.
Something like reinstalling your system from scratch, and use Centos
5.3 with bundled Xen.

Another alternative is to dump virsh/libvirtd altogether. In that
case, you could PROBABLY determine the vnc port to connect using
something like

netstat -anp | grep qemu-dm | grep LISTEN

if it shows something like this

tcp        0      0 127.0.0.1:5901                0.0.0.0:*
       LISTEN      14977/qemu-dm

then you can see the console using this command

vncviewer localhost:1

Regards,

Fajar

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

I am experiencing the same issue. Once I set CPU-Affinity, the virt-manager
can no longer connect to the console of each VM. I use Xen 3.3 as supplied
with Suse 11.

F.Alves

 

From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of ITZIAR
BALENCIAGA
Sent: Tuesday, April 21, 2009 2:21 AM
To: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Config to set CPU affinity and distribute
interrupts

 

Someone who can help me please? I don''t know what to do and since I
changed
from sdl to vnc I can''t see anything. Anyone knows what could be
happenning?



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