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

[Markus Armbruster <armbru@xxxxxxxxxx>]

Anthony PERARD <anthony.perard@xxxxxxxxxx> writes:

> On Tue, Mar 19, 2019 at 07:34:45PM +0100, Markus Armbruster wrote:
>>     = hw/xenpv/xen_machine_pv.c =
>>     Stefano Stabellini <sstabellini@xxxxxxxxxx> (supporter:X86)
>>     Anthony Perard <anthony.perard@xxxxxxxxxx> (supporter:X86)
>>     Paul Durrant <paul.durrant@xxxxxxxxxx> (supporter:X86)
>>     xen-devel@xxxxxxxxxxxxxxxxxxxx (open list:X86)
>
> That machine requires Xen to be started and at least one service,
> xenstore.
>
> 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 \
>         -chardev 
> 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 0.0.0.0:0,to=99 \
>         -display none -m 1024
>
> Is that enough information?

At a glance, yes.  Thanks!

> Also, we do automated tests of QEMU. It is done by `osstest' and the
> results are sent to xen-devel@xxxxxxxxxxxxxxxxxxxx.
> One example of a test result:
>     https://lists.xenproject.org/archives/html/xen-devel/2019-03/msg01577.html
>
> Thanks,

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel