DispVM with more than 4GB memory doesn't work

[marmarek]

Reported by marmarek on 10 Jun 2013 02:05 UTC
When DispVM have maxmem about 4GB or more xl restore fails with:

xc: error: Failed to allocate memory for batch.!: Internal error
[...]
xc: error: Failed to allocate memory for batch.!: Internal error
libxl: error: libxl_dom.c:310"libxl__domain_restore_common restoring
domain: Resource temporarily unavailable cannot (re-)build domain: -3
libxl: error: libxl.c:711:libxl_domain_destroy non-existent domain 4
Error starting VM 

Migrated-From: https://wiki.qubes-os.org/ticket/732

[marmarek]

Comment by marmarek on 10 Jun 2013 02:07 UTC
Workaround is set maxmem to some smaller value (like 3GB):

qvm-prefs -s fedora-18-x64-dvm maxmem 3072
qvm-create-default-dvm fedora-18-x64 --default-script

[marmarek]

Comment by marmarek on 10 Jun 2013 02:07 UTC
Workaround is set maxmem to some smaller value (like 3GB):

qvm-prefs -s fedora-18-x64-dvm maxmem 3072
qvm-create-default-dvm fedora-18-x64 --default-script

[marmarek]

Comment by joanna on 1 Aug 2013 12:58 UTC
This doesn't seem to be the problem anymore, at least with VM kernel 3.9.2:

[~](joanna@dom0)$ qvm-prefs fedora-18-x64-dvm
name              : fedora-18-x64-dvm
label             : gray
type              : AppVM
template          : fedora-18-x64
netvm             : firewallvm
updateable?       : False
installed by RPM? : False
include in backups: True
dir               : /var/lib/qubes/appvms/fedora-18-x64-dvm
config            : /var/lib/qubes/appvms/fedora-18-x64-dvm/fedora-18-x64-dvm.conf
pcidevs           : []
root img          : /var/lib/qubes/vm-templates/fedora-18-x64/root.img
root volatile img : /var/lib/qubes/appvms/fedora-18-x64-dvm/volatile.img
private img       : /var/lib/qubes/appvms/fedora-18-x64-dvm/private.img
vcpus             : 1
memory            : 400
maxmem            : 4037
MAC               : 00:16:3E:5E:6C:1A (auto)
kernel            : 3.9.2-1 (default)
kernelopts        :  (default)
debug             : off
default user      : user
qrexec timeout    : 60

[marmarek]

Comment by joanna on 1 Aug 2013 12:58 UTC
This doesn't seem to be the problem anymore, at least with VM kernel 3.9.2:

[~](joanna@dom0)$ qvm-prefs fedora-18-x64-dvm
name              : fedora-18-x64-dvm
label             : gray
type              : AppVM
template          : fedora-18-x64
netvm             : firewallvm
updateable?       : False
installed by RPM? : False
include in backups: True
dir               : /var/lib/qubes/appvms/fedora-18-x64-dvm
config            : /var/lib/qubes/appvms/fedora-18-x64-dvm/fedora-18-x64-dvm.conf
pcidevs           : []
root img          : /var/lib/qubes/vm-templates/fedora-18-x64/root.img
root volatile img : /var/lib/qubes/appvms/fedora-18-x64-dvm/volatile.img
private img       : /var/lib/qubes/appvms/fedora-18-x64-dvm/private.img
vcpus             : 1
memory            : 400
maxmem            : 4037
MAC               : 00:16:3E:5E:6C:1A (auto)
kernel            : 3.9.2-1 (default)
kernelopts        :  (default)
debug             : off
default user      : user
qrexec timeout    : 60

[marmarek]

Comment by marmarek on 2 Aug 2013 02:10 UTC
This doesn't prove anything, 4037 is less than 4GB (4096).
When I set maxmem to 8000, it still crashes with the same error as above, also with 3.9.2 VM kernel. I don't think it is kernel related - error occurs at VM restore time, before jumping to VM kernel code, so rather some xen issue (not sure what - hypervisor or toolstack).

[marmarek]

Comment by marmarek on 2 Aug 2013 02:10 UTC
This doesn't prove anything, 4037 is less than 4GB (4096).
When I set maxmem to 8000, it still crashes with the same error as above, also with 3.9.2 VM kernel. I don't think it is kernel related - error occurs at VM restore time, before jumping to VM kernel code, so rather some xen issue (not sure what - hypervisor or toolstack).

[marmarek]

Modified by marmarek on 2 Aug 2013 02:40 UTC

[marmarek]

Modified by marmarek on 2 Aug 2013 02:40 UTC

[marmarek]

Comment by marmarek on 14 Mar 2014 14:41 UTC
Currently we have workaround for this: *-dvm have maxmem set to 4000MB (so less than 4GB). This isn't our bug, but hopefully some day new Xen will have it fixed.

[marmarek]

Comment by marmarek on 14 Mar 2014 14:41 UTC
Currently we have workaround for this: *-dvm have maxmem set to 4000MB (so less than 4GB). This isn't our bug, but hopefully some day new Xen will have it fixed.

[marmarek]

Comment by marmarek on 16 Apr 2014 15:09 UTC
Perhaps related commit:
http://git.qubes-os.org/?p=marmarek/core-admin.git;a=commit;h=e2f3446f227d4637f87cfa52cdd0ff87dae62858

[marmarek]

Comment by marmarek on 16 Apr 2014 15:09 UTC
Perhaps related commit:
http://git.qubes-os.org/?p=marmarek/core-admin.git;a=commit;h=e2f3446f227d4637f87cfa52cdd0ff87dae62858