[Qemu-devel] APIC handling causing kernel panic with kernel-3.12.38 and qemu-1.2

2015-04-21 Thread Paulo Ricardo Paz Vital
loads. I'd like to know if someone already have had similar problem and/or have some tip/solution to give us. The latest call trace log is available at [1]. Best Regards, Paulo. [1] http://pastebin.com/g1VDYBKE -- Paulo Ricardo Paz Vital ProfitBricks GmbH

Re: [Qemu-devel] [PATCH] qmp: Give saner messages related to qmp_capabilities misuse

2015-04-15 Thread Paulo Ricardo Paz Vital
Reviewed-by: Paulo Vital On Wed, 2015-04-15 at 09:19 -0600, Eric Blake wrote: > Pretending that QMP doesn't understand a command merely because > we are not in the right mode doesn't help first-time users figure > out what to do to correct things. Although the documentation for > QMP calls out c

Re: [Qemu-devel] Getting VM state from outside QEMU?

2015-04-09 Thread Paulo Ricardo Paz Vital
;: {"class": "CommandNotFound", "desc": "The command query-status > > has not > > been found"}} > > it would be a LOT nicer if we reported 'still in negotiation phase; > "qmp_capabilities" expected' than a bland "CommandNotFound". Of course, > patches are welcome to improve the experience there! That's an interesting point to see. I'm going to take a look on this and submit a patch until next week, probably good to 2.4 release. > > Similarly, once you are NOT in capabilities negotiation, any subsequent > use of "qmp_capabilities" fails. That's also something where the error > message could be improved. > -- Paulo Ricardo Paz Vital ProfitBricks GmbH

Re: [Qemu-devel] [PATCH v6 0/8] QEMU memory hot unplug support

2015-04-08 Thread Paulo Ricardo Paz Vital
plug.c | 96 > > > --- > > > hw/acpi/piix4.c | 17 +-- > > > hw/core/qdev.c| 2 +- > > > hw/i386/acpi-build.c | 25 -- > > > hw/i386/acpi-dsdt-mem-hotplug.dsl | 13 +- > > > hw/i386/pc.c | 62 +++-- > > > include/hw/acpi/aml-build.h | 10 +++- > > > include/hw/acpi/memory_hotplug.h | 12 + > > > include/hw/acpi/pc-hotplug.h | 3 ++ > > > include/hw/qdev-core.h| 1 + > > > monitor.c | 1 + > > > qapi/event.json | 14 ++ > > > trace-events | 4 ++ > > > 18 files changed, 346 insertions(+), 35 deletions(-) > > > > -- Paulo Ricardo Paz Vital ProfitBricks GmbH

Re: [Qemu-devel] Getting VM state from outside QEMU?

2015-04-07 Thread Paulo Ricardo Paz Vital
ipt that sends the QMP command "query-status" an then parse the result. The syntax and output is: -> { "execute": "query-status" } <- { "return": { "running": true, "singlestep": false, "status": "running" } } > Thanks. > > Best regards, > > Erik > -- Paulo Ricardo Paz Vital ProfitBricks GmbH

Re: [Qemu-devel] [PATCH 2/2] docs: add memory-hotplug.txt

2015-03-04 Thread Paulo Ricardo Paz Vital
On Tue, 2015-03-03 at 09:47 -0500, Luiz Capitulino wrote: > This document describes how to use memory hotplug in QEMU. > > Signed-off-by: Luiz Capitulino > --- > docs/memory-hotplug.txt | 76 > + > 1 file changed, 76 insertions(+) > create mode 1

Re: [Qemu-devel] [PATCH 1/2] qemu-options.hx: improve -m description

2015-03-04 Thread Paulo Ricardo Paz Vital
On Tue, 2015-03-03 at 09:47 -0500, Luiz Capitulino wrote: > Add memory hotplug options to the command-line format. Also, > add a complete command-line example and improve description. > > Signed-off-by: Luiz Capitulino > --- > qemu-options.hx | 22 +- > 1 file changed, 17 ins

Re: [Qemu-devel] [PATCH 2/2] docs: add memory-hotplug.txt

2015-03-04 Thread Paulo Ricardo Paz Vital
On Tue, 2015-03-03 at 11:16 -0500, Luiz Capitulino wrote: > On Tue, 03 Mar 2015 16:12:58 +0100 > Paulo Ricardo Paz Vital wrote: > > > On Tue, 2015-03-03 at 09:47 -0500, Luiz Capitulino wrote: > > > This document describes how to use memory hotplug in QEMU. > >

Re: [Qemu-devel] [PATCH 2/2] docs: add memory-hotplug.txt

2015-03-03 Thread Paulo Ricardo Paz Vital
om regular RAM, 1GB is a 1GB hugepage page and 256MB is from > +2MB pages. Also, the guest has additional memory slots to hotplug more > +2GB if needed: > + > + qemu [...] -m 6GB,slots=4,maxmem=10G \ > + -object memory-backend-file,id=mem1,size=1G,mem-path=/mnt/hugepages-1G \ > + -device pc-dimm,id=dimm1,memdev=mem1 \ > + -object memory-backend-file,id=mem2,size=256M,mem-path=/mnt/hugepages-2MB > \ > + -device pc-dimm,id=dimm2,memdev=mem2 -- Paulo Ricardo Paz Vital ProfitBricks GmbH

Re: [Qemu-devel] [PATCH 1/2] qemu-options.hx: improve -m description

2015-03-03 Thread Paulo Ricardo Paz Vital
and @var{maxmem} are not specified, memory hotplug won't > > +be enabled and the guest startup RAM will never increase (although it can > > +be decreased with the use of ballooning). > Technically that's not true, startup RAM is not decreased it's just landed out > by balloon driver to host. Is you restart guest it will use ALL startup memory > until the balloon driver is loaded. > I'd suggest to drop "(...)" part here. > > > ETEXI > > > > DEF("mem-path", HAS_ARG, QEMU_OPTION_mempath, > -- Paulo Ricardo Paz Vital ProfitBricks GmbH

Re: [Qemu-devel] [PATCH 2/2] docs: add memory-hotplug.txt

2015-03-02 Thread Paulo Ricardo Paz Vital
t seem counterintuitive at first, > +but this allows for a lot of flexibility when using the file backend. > + > +In the following command-line example, a 8GB guest is created where 6GB > +comes from regular RAM, 1GB is a 1GB hugepage page and 256MB is from > +2MB pages. Also, t