Re: [Xen-users] Unable to restore a windows 2008 on xen 4.0.1

[Matthieu Patou <mat+Informatique.xen@xxxxxxxxx>]

On 08/06/2011 13:01, Fajar A. Nugraha wrote:
> On Wed, Jun 8, 2011 at 3:57 PM, Matthieu Patou
> <mat+Informatique.xen@xxxxxxxxx>  wrote:
> > Hello,
> >
> > Since a couple of month I setup my debian squeeze to save and restore domain
> > upon reboots
> >
> > This works great for all the linux domains but for the windows one it's not
> > I always have the 33 extents of order 0 error.
> >
> > Here is an extract of the xen output log
> > [2011-06-08 12:49:29 1514] DEBUG (image:891) args: isa, val: 0
> > [2011-06-08 12:49:29 1514] DEBUG (image:891) args: acpi, val: 1
> > [2011-06-08 12:49:29 1514] DEBUG (image:891) args: usb, val: 1
> > [2011-06-08 12:49:29 1514] DEBUG (image:891) args: usbdevice, val:
> > host:04b9:0300
> > [2011-06-08 12:49:29 1514] DEBUG (image:891) args: gfx_passthru, val: None
> > [2011-06-08 12:49:29 1514] INFO (image:822) Need to create platform
> > device.[domid:6]
> > [2011-06-08 12:49:29 1514] DEBUG (XendCheckpoint:286) restore:shadow=0x12,
> > _static_max=0x7d000000, _static_min=0x0,
> > [2011-06-08 12:49:29 1514] DEBUG (XendCheckpoint:305) [xc_restore]:
> > /usr/lib/xen-4.0/bin/xc_restore 51 6 3 4 1 1 1 0
> > [2011-06-08 12:49:29 1514] INFO (XendCheckpoint:423) xc_domain_restore
> > start: p2m_size = 100000
> > [2011-06-08 12:49:29 1514] INFO (XendCheckpoint:423) Reloading memory pages:
> >    0%
> > [2011-06-08 12:49:53 1514] INFO (XendCheckpoint:423) Failed allocation for
> > dom 6: 33 extents of order 0
> > [2011-06-08 12:49:53 1514] INFO (XendCheckpoint:423) ERROR Internal error:
> > Failed to allocate memory for batch.!
> > [2011-06-08 12:49:53 1514] INFO (XendCheckpoint:423)
> > [2011-06-08 12:49:55 1514] INFO (XendCheckpoint:423) Restore exit with rc=1
> > [2011-06-08 12:49:55 1514] DEBUG (XendDomainInfo:3053)
> > XendDomainInfo.destroy: domid=6
> > [2011-06-08 12:49:55 1514] ERROR (XendDomainInfo:3067)
> > XendDomainInfo.destroy: domain destruction failed.
> Just a guess, are you perhaps letting dom0 memory balloon as needed?
> Try adding dom0_mem on grub.cfg / menu.lst, something like this:
>
>         kernel /xen.gz dom0_mem=2000M
I just tried and unfortunatly  it's the same problem.

Matthieu

>

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