Hi, YongKang and Tristan I suspect this error may be happened by too early destroy. Please try to create domU after waiting about 20 sec.
1. boot Xen0 2. create XenU 3. sleep 20 3. destroy xenU 4. sleep 20 5. create 2nd XenU 6. sleep 20 7. destroy 2nd XenU Best Regards, Akio and Kan >Hi all, > >I am very glad to see xm destroy xenU will release memory. >But when I try this feature, I found I couldn't create 2nd xenU successfully. > >I do the following steps: >1. boot Xen0 >2. create XenU >3. After xenU boot up, use poweroff in xenU to kill xenU. >4. create 2nd XenU >5. when 2nd XenU boot up to "start udev", xenU stop to boot and serial port > kept reporting "bad hyperprivop". (please see the attachment) > >If I destroy the 2nd xenU, the whole system seems hang. I catch this issue >in Cset 9268. > >Best Regards, >Yongkang (Kangkang) モタソオ > > >-------------------------------text/plain------------------------------- >_______________________________________________ >Xen-ia64-devel mailing list >Xen-ia64-devel@lists.xensource.com >http://lists.xensource.com/xen-ia64-devel _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
