Le Vendredi 29 Septembre 2006 05:15, Alex Williamson a écrit :
> On Thu, 2006-09-28 at 13:33 +0200, Tristan Gingold wrote:
> > Hi,
> >
> > thanks to Alex and Akio for more torough testing.
> >
> > I have fixed the xentop issue.
> > I think I have also fixed the network issue: during the tests I never hit
> > it.
> >
> > My tests were booting dom0+2*dom_U (using netbk, blkbk and netloop as
> > modules), and doing ping+wget from domU_1.
>
> Hi Tristan,
>
> Thanks, looks a lot better. I've completed hundreds of reboot cycles
> now. The next problem is that domain saving is broken. I get this when
> trying to save a domain:
>
> (XEN) xencomm_paddr_to_maddr: called with bad memory address:
> 0xe00000003a527e20 - iip=a0000001000690a0
>
> The save file never gets bigger than appended below. I also get a few
> new warnings when creating VTi domains, but they don't seem to hurt
> anything:
>
> privcmd_hypercall: unknown hcall (34)
> xencomm_privcmd_memory_op: unknown memory op 6
Hi,
thank you for heavy testing. I have updated the patch. These issues are
fixed. I was able to do a local live migration.
Tristan.
xen-xcom-a4.diffs
Description: Text Data
xen-xcom-b3.diffs
Description: Text Data
xen-xcom-c3.diffs
Description: Text Data
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
| 
Home