seeking help for xen0/U .config

seeking help for xen0/U .config

[woody marvel]

Can someone post their successful .config for xen0 and xenU using FC3 on 
intel x86 w/ide hdd? My make ARCH=xen oldconfig gives numerous kernel 
options that are new for dom0 and I am not sure if I have them set 
correctly in the build. Thanks.

-- 
Woody Marvel		LTC Open Source Projects
tel: 503-578-3833/775-3833	email: marvel@us.ibm.com



-------------------------------------------------------
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://productguide.itmanagersjournal.com/

Re: seeking help for xen0/U .config

[Adam Sulmicki]

> Can someone post their successful .config for xen0 and xenU using FC3 on 
> intel x86 w/ide hdd? My make ARCH=xen oldconfig gives numerous kernel options 
> that are new for dom0 and I am not sure if I have them set correctly in the 
> build.

uh, default config files as distributed with xen 2.0 works just fine for 
me.




-------------------------------------------------------
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://productguide.itmanagersjournal.com/

RE: seeking help for xen0/U .config

[Sun, Ning]

 

where can i find the config file

 


-----Original Message-----
From: xen-devel-admin@lists.sourceforge.net
[mailto:xen-devel-admin@lists.sourceforge.net] On Behalf Of Adam
Sulmicki
Sent: Wednesday, December 22, 2004 9:22 AM
To: woody marvel
Cc: xen dev
Subject: Re: [Xen-devel] seeking help for xen0/U .config

> Can someone post their successful .config for xen0 and xenU using FC3 
> on intel x86 w/ide hdd? My make ARCH=xen oldconfig gives numerous 
> kernel options that are new for dom0 and I am not sure if I have them 
> set correctly in the build.

uh, default config files as distributed with xen 2.0 works just fine for
me.




-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
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://productguide.itmanagersjournal.com/

RE: seeking help for xen0/U .config

[Adam Sulmicki]

>> Can someone post their successful .config for xen0 and xenU using FC3
>> on intel x86 w/ide hdd? My make ARCH=xen oldconfig gives numerous
>> kernel options that are new for dom0 and I am not sure if I have them
>> set correctly in the build.
>
> uh, default config files as distributed with xen 2.0 works just fine for
> me.

> where can i find the config file

well they are at

# ls -1 linux-2.6.9-xen-sparse/arch/xen/configs/xen*
 	linux-2.6.9-xen-sparse/arch/xen/configs/xen0_defconfig
 	linux-2.6.9-xen-sparse/arch/xen/configs/xenU_defconfig

.. but makefile will just use them automagically if you do "make world" 
(and there are no old .config files lying around).


-------------------------------------------------------
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://productguide.itmanagersjournal.com/

xen 2.0 testing idle_loop -and -03

[Adam Sulmicki]

hello,
 	I'm playing with xen 2.0 testing. I noticed few issues so far

1) extreme slowness
2) won't boot on p3 with compiled for for cyrix
3) "idle_loop" gets optimized away

===========================================================================
===========================================================================
1) it is extremely slow. top shows that about 90% of time is spent in wait 
states (this is with compiling kernel)... seems like it might have been 
low memory situation.. but I did not have such problems with xen 2.0 
release.. (using dom0_mem=65536)

Cpu(s):  6.0% us,  1.6% sy,  0.0% ni,  0.0% id, 92.4% wa,  0.0% hi,  0.0% si

tops shows that 45mb out of 60mb are used but.. but it is nto clear what 
ofer.. it not programs, it does not seems like those are buffers either

===========================================================================
===========================================================================
2) does not boot whith Processor family set to "cyrix III/VIA-C3"

(XEN) Scrubbing Free RAM: ..done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen).
(XEN) BUG at domain.c:140
(XEN) CPU:    0
(XEN) EIP:    0808:[<fc505f9e>]
(XEN) EFLAGS: 00210296
(XEN) eax: 00000000   ebx: fc5fd9e0   ecx: 00200046   edx: 000003f8
(XEN) esi: 000e0002   edi: c0102000   ebp: 00000fc0   esp: fc503f9c
(XEN) ds: 0810   es: 0810   fs: 0810   gs: 0810   ss: 0810
(XEN) Stack trace from ESP=fc503f9c:
(XEN) fc52cd19 fc52cd5a 0000008c 000e0002 [fc505ec0] fc5fd9e0 000e0002 0000003f
(XEN) 00000517 00000000 c0512000 c0102000 00000fc0 c0464000 000e0000 00000000
(XEN) 00000819 00210246 c0000004 00000821 00000821 00000821 00000000 00000000
(XEN)        fc5fd9e0
(XEN) Call Trace from ESP=fc503f9c: [<fc505ec0>]

****************************************
CPU0 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
Aieee! CPU0 is toast...
****************************************

Reboot in five seconds...

===========================================================================
===========================================================================
3) using -03 makes the "idle_loop" being optimized away.

removing the "-O3" flag while compiling the domain.o fixes the probelm.

['make xen' in today's bk pull of xen-2.0-testing.bk ..... ]

ld --oformat elf32-i386  -T x86_32/xen.lds -N \
     boot/x86_32.o /usr/src/cm/xen/xen-2.0-testing.bk/xen/common/common.o 
/usr/src/cm/xen/xen-2.0-testing.bk/xen/drivers/char/driver.o 
/usr/src/cm/xen/xen-2.0-testing.bk/xen/drivers/acpi/driver.o 
/usr/src/cm/xen/xen-2.0-testing.bk/xen/drivers/pci/driver.o 
/usr/src/cm/xen/xen-2.0-testing.bk/xen/arch/x86/arch.o -o 
/usr/src/cm/xen/xen-2.0-testing.bk/xen/xen-syms
/usr/src/cm/xen/xen-2.0-testing.bk/xen/arch/x86/arch.o(.text+0xa90): In 
function `continue_idle_task':
: undefined reference to `idle_loop'
make[2]: *** [default] Error 1
make[2]: Leaving directory `/usr/src/cm/xen/xen-2.0-testing.bk/xen/arch/x86'
make[1]: *** [/usr/src/cm/xen/xen-2.0-testing.bk/xen/xen] Error 2
make[1]: Leaving directory `/usr/src/cm/xen/xen-2.0-testing.bk/xen'
make: *** [xen] Error 2

redbull:/usr/src/cm/xen/xen-2.0-testing.bk #

redbull:/usr/src/cm/xen/xen-2.0-testing.bk # cd xen/arch/x86/

# compile with "-O3"

redbull:/usr/src/cm/xen/xen-2.0-testing.bk/xen/arch/x86 # gcc -nostdinc 
-fno-builtin -fno-common -fno-strict-aliasing -iwithprefix include -Wall 
-Werror -pipe -I/usr/src/cm/xen/xen-2.0-testing.bk/xen/include 
-Wno-pointer-arith -Wredundant-decls -O3 -fomit-frame-pointer -msoft-float 
-m32 -march=i586 -DNDEBUG -c domain.c -o domain.o
redbull:/usr/src/cm/xen/xen-2.0-testing.bk/xen/arch/x86 # gcc -nostdinc 
-fno-builtin -fno-common -fno-strict-aliasing -iwithprefix include -Wall 
-Werror -pipe -I/usr/src/cm/xen/xen-2.0-testing.bk/xen/include 
-Wno-pointer-arith -Wredundant-decls -O3 -fomit-frame-pointer -msoft-float 
-m32 -march=i586 -DNDEBUG -c domain.c -o domain.o

redbull:/usr/src/cm/xen/xen-2.0-testing.bk/xen/arch/x86 # nm domain.o | 
grep -iw idle_loop
          U idle_loop

# compile with-out "-O3"

redbull:/usr/src/cm/xen/xen-2.0-testing.bk/xen/arch/x86 # gcc -nostdinc 
-fno-builtin -fno-common -fno-strict-aliasing -iwithprefix include -Wall 
-Werror -pipe -I/usr/src/cm/xen/xen-2.0-testing.bk/xen/include 
-Wno-pointer-arith -Wredundant-decls -O0 -fomit-frame-pointer -msoft-float 
-m32 -march=i586 -DNDEBUG -c domain.c -o domain.o

redbull:/usr/src/cm/xen/xen-2.0-testing.bk/xen/arch/x86 # nm domain.o | 
grep -iw idle_loop
00000020 t idle_loop

===========================================================================
===========================================================================



-------------------------------------------------------
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://productguide.itmanagersjournal.com/

Re: xen 2.0 testing idle_loop -and -03

[Keir Fraser]

> 
> hello,
>  	I'm playing with xen 2.0 testing. I noticed few issues so far
> 
> 1) extreme slowness

Is this in DOM0 or some other domain? If it looks like I/O slowness,
have any network or disc microbenchmarks (e.g., net/disc bandwidth or
latency) got much worse?

> 2) won't boot on p3 with compiled for for cyrix

Has that ever worked? I did recently fix a problem with
CONFIG_X86_USE_3DNOW, so were you testing a very up to date version of
the repository? If you are totally stuck send me your .config and I
can build and test.

> 3) "idle_loop" gets optimized away

Okay I fixed this now.

I did a push from -testing to teh stable tree yesterday
(v2.0.2). There are already a couple more fixes added to the -testing
tree since then so I expect we will end up doing a 2.0.3 release
fairly soon (there are a few other problems we would like to get fixed
first, so it will probably be early in the new year).

 -- Keir


-------------------------------------------------------
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://productguide.itmanagersjournal.com/

Re: xen 2.0 testing idle_loop -and -03

[Keir Fraser]

> >> 1) extreme slowness
> >
> > Is this in DOM0 or some other domain? If it looks like I/O slowness,
> > have any network or disc microbenchmarks (e.g., net/disc bandwidth or
> > latency) got much worse?
> 
> dom0, i tried to compile kernel and it was like 10-100 times slower... but 
> I got impression that it was because the disk was heavily trashing.. it 
> seemed like the 45 out of the 65mb disappeared somewhere, and the 
> remainining 15 was just not enough to compile kernel (in fact oom-killer 
> killed my sshd twice).

'cat /proc/xen/balloon' will tell you how much memory your domain has.
You'll see the current allocation is somewhat less than the 'requested
target'. This is because the backend I/O drivers steal some kernel
address space and the RAM that was mapped in that space is freed back
to Xen. I wouldn't expect the current allocation to be more than maybe
6MB lower than the 64MB target though.

Also, what does 'cat /proc/meminfo' look like?

> >> 2) won't boot on p3 with compiled for for cyrix
> >
> > Has that ever worked? I did recently fix a problem with
> > CONFIG_X86_USE_3DNOW, so were you testing a very up to date version of
> > the repository? If you are totally stuck send me your .config and I
> > can build and test.
> 
> yeah, it worked just fine on xen 2.0 release. I could compile kernel with 
> CONFIG_MCYRIXIII and then run the same kernel on both P3 and via (with 
> some special patches). This time the kernel bombed on P3 (have not tried 
> it on via).
> 
> the repository was as of yesterday.

I'll try building with CYRIXIII selected. If that works for me then I
guess it must be something else in your config.

 -- Keir


-------------------------------------------------------
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://productguide.itmanagersjournal.com/

Re: xen 2.0 testing idle_loop -and -03

[Adam Sulmicki]

>> 1) extreme slowness
>
> Is this in DOM0 or some other domain? If it looks like I/O slowness,
> have any network or disc microbenchmarks (e.g., net/disc bandwidth or
> latency) got much worse?

dom0, i tried to compile kernel and it was like 10-100 times slower... but 
I got impression that it was because the disk was heavily trashing.. it 
seemed like the 45 out of the 65mb disappeared somewhere, and the 
remainining 15 was just not enough to compile kernel (in fact oom-killer 
killed my sshd twice).

>> 2) won't boot on p3 with compiled for for cyrix
>
> Has that ever worked? I did recently fix a problem with
> CONFIG_X86_USE_3DNOW, so were you testing a very up to date version of
> the repository? If you are totally stuck send me your .config and I
> can build and test.

yeah, it worked just fine on xen 2.0 release. I could compile kernel with 
CONFIG_MCYRIXIII and then run the same kernel on both P3 and via (with 
some special patches). This time the kernel bombed on P3 (have not tried 
it on via).

the repository was as of yesterday.

>> 3) "idle_loop" gets optimized away
>
> Okay I fixed this now.
>
> I did a push from -testing to teh stable tree yesterday
> (v2.0.2). There are already a couple more fixes added to the -testing
> tree since then so I expect we will end up doing a 2.0.3 release
> fairly soon (there are a few other problems we would like to get fixed
> first, so it will probably be early in the new year).

cool



-------------------------------------------------------
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://productguide.itmanagersjournal.com/

Re: xen 2.0 testing idle_loop -and -03

[Adam Sulmicki]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1540 bytes --]


>>>> 1) extreme slowness

> 'cat /proc/xen/balloon' will tell you how much memory your domain has.
> You'll see the current allocation is somewhat less than the 'requested
> target'. This is because the backend I/O drivers steal some kernel
> address space and the RAM that was mapped in that space is freed back
> to Xen. I wouldn't expect the current allocation to be more than maybe
> 6MB lower than the 64MB target though.
>
> Also, what does 'cat /proc/meminfo' look like?

attached meminfo, balloon and output of both, all of them right after 
starting dom0

also attached outout of dmesg which shows oom-killer in action (already!) 
as well as output of "echo m > /proc/sysrq-trigger"

>>>> 2) won't boot on p3 with compiled for for cyrix
>>>
>>> Has that ever worked? I did recently fix a problem with
>>> CONFIG_X86_USE_3DNOW, so were you testing a very up to date version of
>>> the repository? If you are totally stuck send me your .config and I
>>> can build and test.
>>
>> yeah, it worked just fine on xen 2.0 release. I could compile kernel with
>> CONFIG_MCYRIXIII and then run the same kernel on both P3 and via (with
>> some special patches). This time the kernel bombed on P3 (have not tried
>> it on via).
>>
>> the repository was as of yesterday.
>
> I'll try building with CYRIXIII selected. If that works for me then I
> guess it must be something else in your config.

FWIW, I just d/l pristine tree and used almost default config (except the 
cyrix setting) just especially to see if it is somethin with my config.

[-- Attachment #2: Type: TEXT/PLAIN, Size: 165 bytes --]

Current allocation:    60416 kB
Requested target:      65536 kB
Low-mem balloon:           0 kB
High-mem balloon:          0 kB
Xen hard limit:          ??? kB

[-- Attachment #3: Type: TEXT/PLAIN, Size: 594 bytes --]

MemTotal:        60992 kB
MemFree:         10000 kB
Buffers:          1208 kB
Cached:           8020 kB
SwapCached:       1468 kB
Active:           7416 kB
Inactive:         5048 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:        60992 kB
LowFree:         10000 kB
SwapTotal:      257032 kB
SwapFree:       254328 kB
Dirty:               4 kB
Writeback:           0 kB
Mapped:           4912 kB
Slab:            32912 kB
Committed_AS:    11344 kB
PageTables:        328 kB
VmallocTotal:   908256 kB
VmallocUsed:       216 kB
VmallocChunk:   908036 kB

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #4: Type: TEXT/PLAIN; charset=X-UNKNOWN; name=t1, Size: 4598 bytes --]

^[[H^[[2J^[[?7l^[[m\x0ftop - 04:45:12 up 3 min,  1 user,  load average: 3.29, 3.03, 1.27^[[m\x0f^[[39;49m^[[K
Tasks:^[[m\x0f^[[39;49m^[[1m  34 ^[[m\x0f^[[39;49mtotal,^[[m\x0f^[[39;49m^[[1m   1 ^[[m\x0f^[[39;49mrunning,^[[m\x0f^[[39;49m^[[1m  33 ^[[m\x0f^[[39;49msleeping,^[[m\x0f^[[39;49m^[[1m   0 ^[[m\x0f^[[39;49mstopped,^[[m\x0f^[[39;49m^[[1m   0 ^[[m\x0f^[[39;49mzombie^[[m\x0f^[[39;49m^[[K
Cpu(s):^[[m\x0f^[[39;49m^[[1m  5.5% ^[[m\x0f^[[39;49mus,^[[m\x0f^[[39;49m^[[1m 12.9% ^[[m\x0f^[[39;49msy,^[[m\x0f^[[39;49m^[[1m  0.0% ^[[m\x0f^[[39;49mni,^[[m\x0f^[[39;49m^[[1m 59.7% ^[[m\x0f^[[39;49mid,^[[m\x0f^[[39;49m^[[1m 21.6% ^[[m\x0f^[[39;49mwa,^[[m\x0f^[[39;49m^[[1m  0.0% ^[[m\x0f^[[39;49mhi,^[[m\x0f^[[39;49m^[[1m  0.4% ^[[m\x0f^[[39;49msi^[[m\x0f^[[39;49m^[[K
Mem: ^[[m\x0f^[[39;49m^[[1m    60992k ^[[m\x0f^[[39;49mtotal,^[[m\x0f^[[39;49m^[[1m    51888k ^[[m\x0f^[[39;49mused,^[[m\x0f^[[39;49m^[[1m     9104k ^[[m\x0f^[[39;49mfree,^[[m\x0f^[[39;49m^[[1m     1304k ^[[m\x0f^[[39;49mbuffers^[[m\x0f^[[39;49m^[[K
Swap:^[[m\x0f^[[39;49m^[[1m   257032k ^[[m\x0f^[[39;49mtotal,^[[m\x0f^[[39;49m^[[1m     2700k ^[[m\x0f^[[39;49mused,^[[m\x0f^[[39;49m^[[1m   254332k ^[[m\x0f^[[39;49mfree,^[[m\x0f^[[39;49m^[[1m     8312k ^[[m\x0f^[[39;49mcached^[[m\x0f^[[39;49m^[[K
^[[6;1H
^[[7m  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            ^[[m\x0f^[[39;49m^[[K
^[[m\x0f    1 root      16   0   588   68  444 S  0.0  0.1   0:02.12 init               ^[[m\x0f^[[39;49m^[[K
^[[m\x0f    2 root      34  19     0    0    0 S  0.0  0.0   0:00.39 ksoftirqd/0        ^[[m\x0f^[[39;49m^[[K
^[[m\x0f    3 root       5 -10     0    0    0 S  0.0  0.0   0:00.00 events/0           ^[[m\x0f^[[39;49m^[[K
^[[m\x0f    4 root       5 -10     0    0    0 S  0.0  0.0   0:00.06 khelper            ^[[m\x0f^[[39;49m^[[K
^[[m\x0f    5 root       5 -10     0    0    0 S  0.0  0.0   0:00.00 kblockd/0          ^[[m\x0f^[[39;49m^[[K
^[[m\x0f   35 root      15   0     0    0    0 S  0.0  0.0   0:00.01 pdflush            ^[[m\x0f^[[39;49m^[[K
^[[m\x0f   37 root       7 -10     0    0    0 S  0.0  0.0   0:00.00 aio/0              ^[[m\x0f^[[39;49m^[[K
^[[m\x0f   36 root      15   0     0    0    0 S  0.0  0.0   0:01.14 kswapd0            ^[[m\x0f^[[39;49m^[[K
^[[m\x0f  619 root      21   0     0    0    0 S  0.0  0.0   0:00.00 kseriod            ^[[m\x0f^[[39;49m^[[K
^[[m\x0f  651 root      20   0     0    0    0 S  0.0  0.0   0:00.00 xenblkd            ^[[m\x0f^[[39;49m^[[K
^[[m\x0f  658 root       6 -10     0    0    0 S  0.0  0.0   0:00.00 ata/0              ^[[m\x0f^[[39;49m^[[K
^[[m\x0f  665 root       6 -10     0    0    0 S  0.0  0.0   0:00.00 kmirrord/0         ^[[m\x0f^[[39;49m^[[K
^[[m\x0f  667 root      15   0     0    0    0 S  0.0  0.0   0:00.14 kjournald          ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2039 root      16   0  1392    0 1192 S  0.0  0.0   0:00.00 hwscand            ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2312 root      16   0  1420  180 1252 S  0.0  0.3   0:02.59 syslogd            ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2319 root      16   0  2256  288 1356 S  0.0  0.5   0:00.13 klogd              ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2378 root      18   0  1384    0 1228 S  0.0  0.0   0:00.00 resmgrd            ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2438 root      16   0  4624  536 4252 S  0.0  0.9   0:00.26 sshd               ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2467 root      18   0  1572    0 1384 S  0.0  0.0   0:00.00 rpc.mountd         ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2484 root      16   0  1568  172 1392 S  0.0  0.3   0:00.00 cron               ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2494 root      18   0  1552    0 1380 S  0.0  0.0   0:00.00 mingetty           ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2495 root      18   0  1552    0 1380 S  0.0  0.0   0:00.00 mingetty           ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2496 root      18   0  1552    0 1380 S  0.0  0.0   0:00.07 mingetty           ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2497 root      18   0  1552    0 1380 S  0.0  0.0   0:00.07 mingetty           ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2498 root      18   0  1552    0 1380 S  0.0  0.0   0:00.07 mingetty           ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2499 root      18   0  1552    0 1380 S  0.0  0.0   0:00.04 mingetty           ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2500 root      17   0  1356    0 1196 S  0.0  0.0   0:00.05 agetty             ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 2927 root      15   0     0    0    0 S  0.0  0.0   0:00.00 pdflush            ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 3050 root      16   0  7632 1808 4460 S  0.0  3.0   0:00.02 sshd               ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 3052 sulmicki  16   0  7780 1932 4460 S  0.0  3.2   0:00.02 sshd               ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 3057 sulmicki  16   0  4260 1844 3412 S  0.0  3.0   0:00.05 bash               ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 3077 root      17   0  3464 1236 2848 S  0.0  2.0   0:00.01 su                 ^[[m\x0f^[[39;49m^[[K
^[[m\x0f 3082 root      16   0  3892 1852 3412 S  0.0  3.0   0:00.12 bash               ^[[m\x0f^[[39;49m^[[K
^[[m\x0f^[[1m 3121 root      15   0  1928  928 1712 R  0.0  1.5   0:00.01 top                ^[[m\x0f^[[39;49m^[[K
^[[J^[[6;1H^[[K^[[70;1H^[[?12l^[[?25h^[[?7h

[-- Attachment #5: Type: TEXT/PLAIN, Size: 8800 bytes --]

Linux version 2.6.9-xen0 (root@redbull) (gcc version 3.3.3 (SuSE Linux)) #4 Tue Dec 21 15:18:49 MST 2004
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000004000000 (usable)
64MB LOWMEM available.
On node 0 totalpages: 16384
  DMA zone: 16384 pages, LIFO batch:4
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
DMI not present.
Built 1 zonelists
Kernel command line: root=/dev/hda1 console=tty0 console=ttyS0 debug
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 865.949 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 60496k/65536k available (2702k kernel code, 4944k reserved, 832k data, 400k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 1730.15 BogoMIPS (lpj=8650752)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff 00000000 00000000 00000000
CPU: After vendor identify, caps:  0383fbff 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps:        0383dbf1 00000000 00000000 00000040
CPU: Intel(R) Pentium(R) III Mobile CPU       866MHz stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
NET: Registered protocol family 16
PCI: Using configuration type Xen
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Probing PCI hardware (bus 01)
PCI: Probing PCI hardware (bus 02)
PCI: Probing PCI hardware
Initializing Cryptographic API
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
HP CISS Driver (v 2.6.2)
Intel(R) PRO/1000 Network Driver - version 5.3.19-k2
Copyright (c) 1999-2004 Intel Corporation.
pcnet32.c:v1.30i 06.28.2004 tsbogend@alpha.franken.de
e100: Intel(R) PRO/100 Network Driver, 3.0.27-k2-NAPI
e100: Copyright(c) 1999-2004 Intel Corporation
PCI: Obtained IRQ 10 for device 0000:02:08.0
e100: eth0: e100_probe: addr 0xc0200000, irq 10, MAC addr 00:D0:59:33:6E:E0
Xen virtual console successfully installed as ttyS
Event-channel device installed.
Initialising Xen netif backend
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH3M: IDE controller at PCI slot 0000:00:1f.1
PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
PCI: Obtained IRQ 11 for device 0000:00:1f.1
ICH3M: chipset revision 1
ICH3M: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x1868-0x186f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: IC25N020ATCX04-0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: LG CD-ROM CRN-8245B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide2...
ide2: Wait for ready failed before probe !
Probing IDE interface ide3...
ide3: Wait for ready failed before probe !
Probing IDE interface ide4...
ide4: Wait for ready failed before probe !
Probing IDE interface ide5...
ide5: Wait for ready failed before probe !
hda: max request size: 128KiB
hda: 39070080 sectors (20003 MB) w/1768KiB Cache, CHS=38760/16/63, UDMA(100)
hda: cache flushes not supported
 hda: hda1 hda2
hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Red Hat/Adaptec aacraid driver (1.1.2-lk2 Dec 21 2004)
3ware Storage Controller device driver for Linux v1.26.00.039.
3w-xxxx: No cards found.
libata version 1.02 loaded.
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
input: PS/2 Generic Mouse on isa0060/serio1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: automatically using best checksumming function: pIII_sse
   pIII_sse  :  1254.400 MB/sec
raid5: using function: pIII_sse (1254.400 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm@uk.sistina.com
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing unused kernel memory: 400k freed
EXT3 (no)acl options not supported
EXT3 (no)acl options not supported
EXT3 FS on hda1, internal journal
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Adding 257032k swap on /dev/hda2.  Priority:42 extents:1
pcmcia_core: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
pcmcia_core: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
yenta_socket: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
pcmcia_core: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
ds: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
pcmcia_core: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
yenta_socket: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
pcmcia_core: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
yenta_socket: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
exportfs: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
nfsd: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
exportfs: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
nfsd: version magic '2.6.9-xen0 preempt CYRIXIII gcc-3.3' should be '2.6.9-xen0 preempt PENTIUM4 gcc-3.3'
oom-killer: gfp_mask=0x1d2
DMA per-cpu:
cpu 0 hot: low 8, high 24, batch 4
cpu 0 cold: low 0, high 8, batch 4
Normal per-cpu: empty
HighMem per-cpu: empty

Free pages:        2016kB (0kB HighMem)
Active:3 inactive:2495 dirty:2 writeback:2179 unstable:0 free:504 slab:10589 mapped:317 pagetables:611
DMA free:2016kB min:256kB low:512kB high:768kB active:12kB inactive:9980kB present:65536kB
protections[]: 0 0 0
Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB
protections[]: 0 0 0
HighMem free:0kB min:128kB low:256kB high:384kB active:0kB inactive:0kB present:0kB
protections[]: 0 0 0
DMA: 298*4kB 69*8kB 5*16kB 0*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2016kB
Normal: empty
HighMem: empty
Swap cache: add 5097, delete 2902, find 1213/1298, race 0+0
Out of Memory: Killed process 2377 (portmap).
SysRq : Show Memory
Mem-info:
DMA per-cpu:
cpu 0 hot: low 8, high 24, batch 4
cpu 0 cold: low 0, high 8, batch 4
Normal per-cpu: empty
HighMem per-cpu: empty

Free pages:        5272kB (0kB HighMem)
Active:2420 inactive:1473 dirty:1 writeback:0 unstable:0 free:1318 slab:8621 mapped:1220 pagetables:79
DMA free:5272kB min:256kB low:512kB high:768kB active:9680kB inactive:5892kB present:65536kB
protections[]: 0 0 0
Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB
protections[]: 0 0 0
HighMem free:0kB min:128kB low:256kB high:384kB active:0kB inactive:0kB present:0kB
protections[]: 0 0 0
DMA: 48*4kB 37*8kB 245*16kB 21*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 5272kB
Normal: empty
HighMem: empty
Swap cache: add 11470, delete 11088, find 4705/6038, race 1+1
Free swap:       254332kB
16384 pages of RAM
0 pages of HIGHMEM
1136 reserved pages
2318 pages shared
382 pages swap cached

Re: xen 2.0 testing idle_loop -and -03

[Adam Sulmicki]

>> 3) "idle_loop" gets optimized away
>
> Okay I fixed this now.

> I did a push from -testing to teh stable tree yesterday
> (v2.0.2). There are already a couple more fixes added to the -testing
> tree since then so I expect we will end up doing a 2.0.3 release
> fairly soon (there are a few other problems we would like to get fixed
> first, so it will probably be early in the new year).

I just did a pull it seems I already had the fixes from yesterday.

as for idle_loop. "__attribute_used__" ? Somehow I supsect Plan9 compiler 
does not support that and Ron won't be very happy about it.

In fact i had little luck of finding gcc documentation on it on web.



-------------------------------------------------------
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://productguide.itmanagersjournal.com/

Re: xen 2.0 testing idle_loop -and -03

[Keir Fraser]

> attached meminfo, balloon and output of both, all of them right after 
> starting dom0

meminfo and balloon dumps look healthy and you do have a swap partition.

> also attached outout of dmesg which shows oom-killer in action (already!) 
> as well as output of "echo m > /proc/sysrq-trigger"

Weird. Do you have to do anything on DOM0 to get the messages, or do
they just start coming out after a while? Maybe there's a memory leak
somewhere... I haven't seen anything like this though.

> FWIW, I just d/l pristine tree and used almost default config (except the 
> cyrix setting) just especially to see if it is somethin with my config.

Did it work for you? I've just done the same and I was able to boot a
xen-2.0-testing linux-2.6.9-xen0 configured for CYRIXIII on an Athlon
box with no problems.

Can you make your failing config and/or vmlinuz file available?

 -- Keir


-------------------------------------------------------
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://productguide.itmanagersjournal.com/

Re: xen 2.0 testing idle_loop -and -03

[Keir Fraser]

> 2) won't boot on p3 with compiled for for cyrix
>    does not boot whith Processor family set to "cyrix III/VIA-C3"

I looked into this. I don't know how it could ever have worked for
you in the past -- the crash is occurring because the kernel is
compiled with 3DNOW-specific instructions (in particular a
3dnow-specific PREFETCH instruction) that Intel CPUs simply do not
support. The system therefore crashes with an entirely legitimate
"invalid opcode" fault.

If you really want a kernel that will work on both Cyrix/C3 and P3,
try selecting "Pentium-Pro" as processor type. If that fails I can
look at allowing configuration of "Pentium Classic".

 -- Keir


-------------------------------------------------------
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://productguide.itmanagersjournal.com/

Re: xen 2.0 testing idle_loop -and -03

[Ronald G. Minnich]

On Wed, 22 Dec 2004, Adam Sulmicki wrote:

> as for idle_loop. "__attribute_used__" ? Somehow I supsect Plan9 compiler does
> not support that and Ron won't be very happy about it.

not to worry adam. plan 9 c doesn't support a lot of this gcc stuff so I 
have sed scripts to optimize it all away :-)

ron


-------------------------------------------------------
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://productguide.itmanagersjournal.com/