On Thu, May 06, 2010 at 10:22:03PM -0400, Gerry Reno wrote:
> On 05/06/2010 08:21 PM, Gerry Reno wrote:
>> Ok, I tested with the new 188.8.131.52: (.config same)
>> Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 184.108.40.206
>> 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 220.127.116.11 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 18.104.22.168 (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.
>> I'm getting slightly different output on console and serial console.
>> Some errors show on one but not the other. Shouldn't these be
>> I'm attaching both serial console outputs.
>> menu.lst is same as before (just .12 instead of .10)
> And I'm attaching the syslog from Case 1 (pv_ops dom0).
You should be posting two things:
1) xm dmesg
Aka the full boot log, from both Xen hypervisor and dom0 Linux kernel.
Xen-devel mailing listXen-devel@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-devel