[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [WORKAROUND] Re: current Xen3 (446aa56ca4fe) unable to reboot XenU ("cannot allocate memory")

To: xen-devel@xxxxxxxxxxxxxxxxxxx
From: Charles Duffy <cduffy@xxxxxxxxxxx>
Date: Mon, 17 Oct 2005 19:02:06 -0500
Delivery-date: Tue, 18 Oct 2005 00:01:04 +0000
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Setting dom0_mem such that it's not necessary to balloon out on therestart appears to work around this issue, such that the DomU issuccessfully restarted by xend.



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

References:
- [Xen-devel] current Xen3 (446aa56ca4fe) unable to reboot XenU ("cannot allocate memory")
  - From: Charles Duffy

Prev by Date: [Xen-devel] patch: event channel fixups
Next by Date: Re: [Xen-devel] peth1: received packet with own address as source address
Previous by thread: [Xen-devel] current Xen3 (446aa56ca4fe) unable to reboot XenU ("cannot allocate memory")
Next by thread: [Xen-devel] XEN) (file=irq.c, line=224) Cannot bind IRQ 4
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.