qemu-e2k/backends
Hu Tao d42e2de7bc hostmem-ram: don't exit qemu if size of memory-backend-ram is way too big
When using monitor command object_add to add a memory backend whose
size is way too big to allocate memory for it, qemu just exits. In
the case we'd better give an error message and keep guest running.

The problem can be reproduced as follows:

1. run qemu
2. (monitor)object_add memory-backend-ram,size=100000G,id=ram0

Reviewed-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2014-09-09 13:41:44 +02:00
..
baum.c qemu-char: introduce qemu_chr_alloc 2014-06-23 11:12:28 -04:00
hostmem-file.c hostmem: add property to map memory with MAP_SHARED 2014-06-19 18:44:20 +03:00
hostmem-ram.c hostmem-ram: don't exit qemu if size of memory-backend-ram is way too big 2014-09-09 13:41:44 +02:00
hostmem.c hostmem: set MPOL_MF_MOVE 2014-08-20 21:15:56 +02:00
Makefile.objs backends: Introduce chr-testdev 2014-08-06 17:53:05 +02:00
msmouse.c qemu-char: introduce qemu_chr_alloc 2014-06-23 11:12:28 -04:00
rng-egd.c rng-egd: offset the point when repeatedly read from the buffer 2013-11-21 07:55:37 -08:00
rng-random.c rng-random: NULL check not needed before g_free() 2014-06-24 20:01:24 +04:00
rng.c qom: Clean up fragile use of error_is_set() in set() methods 2014-05-05 19:08:49 +02:00
testdev.c backends: Introduce chr-testdev 2014-08-06 17:53:05 +02:00
tpm.c qom: Clean up fragile use of error_is_set() in set() methods 2014-05-05 19:08:49 +02:00