[Xen-devel] changeset: 6987, old issue's still around, and major pita seems fixed

[Ted Kaczmarek <tedkaz@xxxxxxxxxxxxx>]

Both of these are not easy to reproduce. Also noticed that at some point
mac addresses for vif in configs no longer accepts upper case letters. 
Not a big deal if that is desired, but something for the release/config
notes.


1) domU crash
Modules linked in:
CPU:    1
EIP:    0061:[<c0331541>]    Not tainted VLI
EFLAGS: 00000246   (2.6.12-xenU)
EIP is at start_secondary+0x41/0xc0
eax: 00000000   ebx: 00000000   ecx: 00000007   edx: c0030000
esi: 00000000   edi: 00000000   ebp: 00000000   esp: c0030fb8
ds: 007b   es: 007b   ss: 0069
Process swapper (pid: 0, threadinfo=c0030000 task=c0034550)
Stack: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
       00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
       00000000 00000000
Call Trace:
Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc <cc> cc
cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
 <0>Kernel panic - not syncing: Attempted to kill the idle task!

2) vanishing memory
After hosing a domU I  was unable to reclaim the memory that was
assigned to it even after destroying it, restart of xend had no affects.

So far I have not been able to reproduce the Unable to read
memory/target, start getting those pint glasses chilled :-)

Best Regards,

Ted





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