[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] xm create error - Unable to allocate memory
Hi Glen, On Sat, May 10, 2008 at 10:52 PM, Glen Eustace <geustace@xxxxxxxxxxxxxx> wrote:
I have had reasonable success with para-virtualised domUs and so tried my first fully virtualised domU today. I am hoping to migrate a Win2k3 server into my Xen environment. Did you notice the cannot allocate memory error? do you have enough free memory? Also some suggestions inline below.
change this kernel= line to: bootloader=/usr/lib64/xen/boot/hvmloade I put lib64, it might just be lib, but since you said you are running 64bit that would probably be the way to go. kernel = "/usr/lib/xen/boot/hvmloader" builder = "hvm" remove this bootloader line bootloader = "/usr/bin/pygrub"
why do you have both of these?
I would consider disabling them (comment them with # if things don't work, you can always add them in later) I would also consider not have these last two unless you need them too. I don't have a lot of experience with windows, especially 2k3, but the suggestions above should at least get you farther and then the windows guest users can help even more if needed or you could search: xen.markmail.org for more suggestions as well.
Try running xm top to see if you have enough RAM to add another one, you could consider giving some guests less RAM if you don't have enough. Regards, Todd _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |