On Fri, 2015-02-06 at 22:15 +0100, Paolo Bonzini wrote:
> Mostly the same as v2;
We've got something screwy going on with MemoryListeners, I did some
hotplug testing with this and I hit the following segfault:
Program received signal SIGSEGV, Segmentation fault.
0x7ff7bd8f7416 in memory_liste
On 2015/2/4 0:51, Laszlo Ersek wrote:
> On 02/03/15 17:19, Igor Mammedov wrote:
>> On Thu, 29 Jan 2015 16:37:11 +0800
>> Shannon Zhao wrote:
>>
>>> XDST points to other tables except FACS & DSDT.
>> Is there any reason to use XSDT instead of RSDT?
>> If ACPI tables are below 4Gb which probably wou
Hi,
I want to reproduce https://bugs.launchpad.net/qemu/+bug/495566
But I don't understand where do I get the Kernel and Initrd images. The
Test images do not include those. Is there any source for these image or do
I've to make those myself?
Thanks
Muhammad Azizul Hakim
From: Gonglei
qemu_boot_set() can't fail in restore_boot_order(),
then simply assert it doesn't fail, by passing
&error_abort.
Signed-off-by: Gonglei
---
bootdevice.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bootdevice.c b/bootdevice.c
index 52d3f9e..d3d4277 100644
-
From: Gonglei
The reset logic can be done by both machine reset and
boot handler. So we shouldn't return error when the boot
handler callback don't be set.
Signed-off-by: Gonglei
Reviewed-by: Alexander Graf
---
bootdevice.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
dif
From: Gonglei
The reset logic can be done by both machine reset and
boot handler. So we shouldn't return error when the boot
handler callback don't be set in patch 1.
Patch 2 check boot order argument validation
before vm running.
Patch 3 passing &error_abort instead of NULL.
Patch 4 update boo
From: Dinar Valeev
on sPAPR we need to update boot_order in MachineState in case it
got changed on reset.
Signed-off-by: Dinar Valeev
Reviewed-by: Alexey Kardashevskiy
Signed-off-by: Gonglei
---
bootdevice.c | 4
1 file changed, 4 insertions(+)
diff --git a/bootdevice.c b/bootdevice.c
From: Gonglei
Either 'once' option or 'order' option can take effect for -boot at
the same time, that is say initial startup processing can check only
one. And pc.c's set_boot_dev() fails when its boot order argument
is invalid. This patch provide a solution fix this problem:
1. If "once" is gi
201 - 208 of 208 matches
Mail list logo
