[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-arm] Maintainers, please tell us how to boot your machines!

From: Anthony PERARD
Subject: Re: [Qemu-arm] Maintainers, please tell us how to boot your machines!
Date: Wed, 20 Mar 2019 12:21:08 +0000
User-agent: Mutt/1.11.3 (2019-02-01)

On Tue, Mar 19, 2019 at 07:34:45PM +0100, Markus Armbruster wrote:
>     = hw/xenpv/xen_machine_pv.c =
>     Stefano Stabellini <address@hidden> (supporter:X86)
>     Anthony Perard <address@hidden> (supporter:X86)
>     Paul Durrant <address@hidden> (supporter:X86)
>     address@hidden (open list:X86)

That machine requires Xen to be started and at least one service,

In dom0, when it's used to attach more disks to dom0:

$QEMU -M xenpv -xen-domid 0 -xen-attach \
        -name dom0 -nographic  -daemonize \
        -monitor /dev/null -serial /dev/null -parallel /dev/null \
        -nodefaults -no-user-config

Communication is then done via xenstore to attach disks, we would use
`xl block-attach` for that.

Another example, when we start a guest and want to attach qcow disk and
VNC. Our tool stack (xl / libxl) would first create the domain then
start QEMU:

$QEMU -machine xenpv -xen-domid 6 -xen-attach \
        -name pv-arch \
socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-6,server,nowait \
        -mon chardev=libxl-cmd,mode=control \
        -no-shutdown -nodefaults -no-user-config \
        -vnc,to=99 \
        -display none -m 1024

Is that enough information?

Also, we do automated tests of QEMU. It is done by `osstest' and the
results are sent to address@hidden
One example of a test result:


Anthony PERARD

reply via email to

[Prev in Thread] Current Thread [Next in Thread]