Re: [Xen-users] Unable to create guest with more than 2gb of memory

["Marc Tousignant" <myrdhn@xxxxxxxxx>]

> On Tue, 2015-10-06 at 21:42 -0400, Marc Tousignant wrote:
> > I believe I have asked about this before, but never got a response 
> > back on how to fix it.
> > The max memory when running 4.1 is 2048. Anything higher and the 
> > guest will not start.
> > The error I get is
> > xc: error: panic: xc_dom_boot.c:401: xc_dom_gnttab_hvm_seed: failed 
> > to add gnttab to physmap [errno=2]
> > : Internal error
> > libxl: error: libxl_dm.c:1499:device_model_spawn_outcome: domain 10 
> > device model: spawn failed (rc=-3)
> > libxl: error: libxl_create.c:1322:domcreate_devmodel_started: device 
> > model did not start: -3
> > libxl: error: libxl_dm.c:1603:kill_device_model: Device Model 
> > already exited
> > libxl: info: libxl.c:1691:devices_destroy_cb: forked pid 10742 for 
> > destroy of domain 10
> >  
> > If I attempt to set the memory higher after running
> >                 xl mem-set Server2012_1 2049
> 
> xl was preview quality in Xen 4.1, you should either upgrade to 
> something more recent (best option IMHO) or stick with xm in 4.1.
> 
> Note that Xen 4.1 no longer receives even security support.
> 
> Ian.
> 
> ---
> Correction, I am on 4.5.1.
> When I ran xl info I grabbed the number from release instead of 
> xen_version

Ah, easily done!

Please could you post your guest configuration file as well as the relevant 
logs from /var/log/xen/ (usually *guest-name*) and the output of all the xl 
commands you are running but with "-vvv", i.e. "xl -vvv create ..." / "xl -vvv 
mem-set ..." etc.

Also, what sort of guest is it and what OS version (in particular kernel
version) is it running.

Ian.

----
My config. Note: sometine in 3.x I was able to use 8192. Then when I upgraded 
to a later build, forgot which, I had to drop it to 4092 as it would not start 
with higher. And now I cannot start a VM with anything larger than 2048.

# cat /etc/xen/W2k12SQLTest.cfg
builder='hvm'
#memory = 2048
#memory = 4096
memory = 8192

# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
shadow_memory = 8
name = "Server2012_1"
vfb = [ 'type=vnc,vncdisplay=11,vncpasswd=eva1unit' ]
#vif = [ 'mac=00:16:3E:33:5E:F7, bridge=xenbr0' ]
pci=['04:00.0']
acpi = 1
apic = 1
disk = [        'file://RAID/xen/xen_disks/W2k12SQLTest,hda,w',
                'file://RAID/xen/xen_disks/W2k12SQLTest2,hdb,w' ]
#                
'file://RAID/xen/System_ISOs/9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.ISO,hdd:cdrom,r'
 ]
#                'file://RAID/xen/System_ISOs/NICDrivers.iso,hdd:cdrom,r' ]
#                'file://RAID/xen/System_ISOs/cd080802.iso,hdd:cdrom,r' ]

#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="dc"
vncunused=1
sdl=0

#device_model_version = "qemu-xen"

serial='pty'
usbdevice='tablet'
vcpus=2
#cpus = ['14', '15']
#vcpus=4
#cpus = ['12','13','14', '15']
localtime = 1
usb = 1
#usbdevice = "host:0781:5575"

OK, now this is weird... All I did was run an xl create with -vvv and now it is 
working. The error from the original email was from the same guest without 
-vvv, that was the only change. I know this should not have any effect on this.
I stopped several of my other running VM's, modified their configs to the 
higher ram I originally used them with and they are working now too. I didnât 
even need to do the -vvv on them.
All of the guests are widows based, several are Win7, one 2008 and one 2012.

Marc



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users