Ok, I tested with the new 2.6.32.12: (.config same)
Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.12
Still pv_ops dom0 is not working properly.
There are still call trace and other errors. The kernel does boot up
but it takes again a long time to get the login prompt (about 3 mins).
This is far longer than when I used 2.6.31.6 pv_ops dom0. Networking
does not start properly (only see 'lo' and 'virbr0'), so I have to
restart it manually and then I see my bridge 'br0' and 'eth0'.
Can't find device "br0"
/etc/xen/scripts/network-bridge: line 240: "sigerr" command not found.
And it is trying unsuccessfully to start some laptop feature like
S99powernap (unknown job) and also S28-libvirt-bin fails (maybe network
related?).
Case 2: pv_ops domU kernel 2.6.32.12 (no xen dom0):
Now the straight linux kernel (no xen dom0) boots right up and goes to
login prompt in normal timeframe. Networking starts correctly. Things
look pretty normal.
Observation:
I'm getting slightly different output on console and serial console.
Some errors show on one but not the other. Shouldn't these be identical?
I'm attaching both serial console outputs.
menu.lst is same as before (just .12 instead of .10)
-Gerry
AMD_pvops_dom0_console_2.6.32.12.txt
Description: Text document
AMD_pvops_domU_console_2.6.32.12.txt
Description: Text document
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
| 
Home