Fedora xen - Oct 2007 - virt-manager "Cannot allocate memory" creating Win2K3 HVM

Configuration of dom0 is as follows
8GB memory
2 x dual core Xeon
kernel-xen.x86_64 2.6.20-2931.fc7
xen.x86_64 3.1.0-2.fc7
xen-libs.x86_64 3.1.0-2.fc7
libvirt.x86_64 0.3.2-1.fc7
virt-manager-0.4.0-2.fc7

I''m trying to install a win2K3 32bit HVM domU
using /cd.iso file local to dom0
LVM partition /dev/vgmirror/win2k3 as domU disk
bridged eth0 network
1024MB memory for domU (have tried with lower memory)

Fails with POST operation failed: (xend.err "Error creating domain:
(12, ''Cannot allocate memory'')")

Rebooting the dom0 is to be avoided if possible due to other paravirt
domU guests running, any suggestions or extra info that might help?

I have managed to successfully create a win2K3 64bit HVM domU on an
identical dom0 server.

On 05/10/2007, Andy Burns <fedora.lists@burns.me.uk> wrote:
> Rebooting the dom0 is to be avoided if possible
Couldn''t think of anything else, so I did have to reboot, started a
couple of important domU guests and then installed the Win2K3 ok.

One question about windows HVM installation, given that virt-manager
has the hint that windows is the os being installed, why does the
installer delete the CD-DROM driver after the text part of install?
this guarantees that the GUI part will fail due to being unable to
copy remaining files from CD, the error message windows gives is none
to helpful either (can''t blame xen/virt-manager for that I guess)

My way around this problem is to virsh dumpxml the domU to a file
while the text part of install is on-going, then when it reboots I
virsh undefine it  and virsh define it back from the file again.

Is there any prospect of this being handled in a more user-friendly
way with FC8?