On Tue, 22 Dec 2015, Wink Saville wrote:
> I've tried that, but it didn't work. I believe its because I don't have
> ACPI initialized and enabled as I haven't got that far yet. If my guess is
> possibly correct, would you happen to know the minimum necessary
> instructions to initialize and enable
I've tried that, but it didn't work. I believe its because I don't have
ACPI initialized and enabled as I haven't got that far yet. If my guess is
possibly correct, would you happen to know the minimum necessary
instructions to initialize and enable ACPI?
On Tue, Dec 22, 2015 at 4:29 AM Bodo Egger
On Mon, 21 Dec 2015, Jakob Bohm wrote:
> By "manually" I meant that your outer test-automating program or script
> would do it by simply sending the appropriate "kill" message/signal,
> not that you as a human would have to sit at the console ready to hit
> ctrl+C.
>
> For qemu-system-i386 (and q
Got it, txs, but hopefully someone will offer an internal mechanism.
On Mon, Dec 21, 2015 at 11:34 AM Jakob Bohm wrote:
> By "manually" I meant that your outer test-automating program or script
> would do it by simply sending the appropriate "kill" message/signal,
> not that you as a human would
By "manually" I meant that your outer test-automating program or script
would do it by simply sending the appropriate "kill" message/signal,
not that you as a human would have to sit at the console ready to hit
ctrl+C.
For qemu-system-i386 (and qemu-system-x86_64), you can use the same
PC BIOS re
Killing it "manually" is trivial usually just "ctrl-a", "x" but I want to
qemu to exit when my application completes. Following the lead from Peter
you start qemu with -no-reboot option and then "reset the cpu". So for ARM
the poweroff is:
void ac_poweroff(void) {
volatile ac_u32* pUnlockResetRe
I know that libvirt (which is huge) uses those. I am not up to date on
what the specific monitor and qmp commands are or where to find out.
So basically, I don't know either.
Hard killing the qemu process you launched yourself should be pretty
trivial using whatever tool/language you used to
Can you give me some pointers to implementations that use these techniques.
Txs.
On Mon, Dec 21, 2015, 4:02 AM Jakob Bohm wrote:
> There is a monitor and/or qmp command to simulate a "soft"
> press on the power button, which would trigger any OS
> provided clean shut down logic via ACPI/APM.
>
>
There is a monitor and/or qmp command to simulate a "soft"
press on the power button, which would trigger any OS
provided clean shut down logic via ACPI/APM.
There is a different monitor and/or qmp command to simulate
a hard power off while still keeping the virtualization
aspect of e.g. qcow2 fi
Peter,
I ended up using the first technique for VersatilePB and works just fine.
Now I want to be able "power off" a qemu-system-i386 and I was wondering
what you might suggest? I'm hoping there might be something "easy".
-- Wink
On Mon, Oct 19, 2015 at 1:49 PM Wink Saville wrote:
> THANKS, I
THANKS, I'll give those things a try!
On Mon, Oct 19, 2015, 1:46 PM Peter Maydell
wrote:
> On 19 October 2015 at 20:30, Wink Saville wrote:
> > I would like to use qemu in a test environment where I give a "kernel"
> image
> > to qmeu have it execute it and then when complete have qemu exit.
>
On 19 October 2015 at 20:30, Wink Saville wrote:
> I would like to use qemu in a test environment where I give a "kernel" image
> to qmeu have it execute it and then when complete have qemu exit. Currently
> when
> executing:
>
> $ qemu-system-arm -M versatilepb -m 128M -nographic -kernel test.b
12 matches
Mail list logo
