On Mon, Dec 27, 2010 at 07:27:56PM +0300, Vasiliy G Tolstov wrote:
> On Mon, 27 Dec 2010 10:08:47 -0500, Konrad Rzeszutek Wilk
> <konrad.wilk@xxxxxxxxxx> wrote:
> > On Mon, Dec 20, 2010 at 02:47:24PM +0100, Daniel Kiper wrote:
> >> Features and fixes:
> >> - HVM mode is supported now,
> >> - migration from mod_timer() to schedule_delayed_work(),
> >> - removal of driver_pages (I do not have seen any
> >> references to it),
> >> - protect before CPU exhaust by event/x process during
> >> errors by adding some delays in scheduling next event,
> >> - some other minor fixes.
>
> I have apply this patch to bare 2.6.36.2 kernel from kernel.org. If
> memory=maxmemory pv guest run's on migrating fine.
> If on already running domU i have xm mem-max xxx 1024 (before that it
> has 768) and do xm mem-set 1024 guest now have 1024 memory, but after
> that it can't migrate to another host.
>
> Step to try to start guest with memory=512 and maxmemory=1024 it boot
> fine, xm mem-set work's fine, but.. it can't migrate. Sorry but nothing
> on screen , how can i help to debug this problem?
You can play with 'xenctx' to see where the guest is stuck. You can also
look in the 'xm dmesg' to see if there is something odd. Lastly, if you
mean by 'can't migrate to another host' as the command hangs stops, look
at the error code (or in /var/log/xen files) and also look in the source
code.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home