From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
qemu-devel@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: Failing property setters + hardwired devices + -global = a bad day
Date: Wed, 29 Apr 2020 16:57:19 +0100 [thread overview]
Message-ID: <20200429155719.GL1495129@redhat.com> (raw)
In-Reply-To: <87mu6uia5i.fsf@dusky.pond.sub.org>
On Wed, Apr 29, 2020 at 05:28:25PM +0200, Markus Armbruster wrote:
> Is there any sane use for configuring backends via any of the default
> mechanisms?
>
> I'm aware of one, but it's outdated: -global isa-fdc.driveA=... Use
> -device floppy instead.
>
> I'd love to deprecate -global wholesale, but we can't as long as we
> don't have better means to configure onboard devices. Can we deprecate
> its use with backend properties at least?
Currently libvirt has code using the following
* Floppy
-global isa-fdc.driveA=ID
-global isa-fdc.driveB=ID
-global isa-fdc.bootindexA=NN
-global isa-fdc.bootindexB=NN
Only used when the machine type is pc-q35-2.4 or earlier
* NVRAM
-global spapr-nvram.reg=0xnnnn
* Video primary display adapter
-global qxl-vga.ram_size=NN
-global qxl-vga.vram_size=NN
-global qxl-vga.vram64_size=NN
-global qxl-vga.vgamem_mb=NN
-global qxl-vga.max_outputs=NN
-global VGA.vgamem_mb=MM
-global vmware-svga.vgamem_mb=MM
Only used for old qemu lacking -device support where we must use -vga
instead
* PIT policy
-global kvm-pit.lost_tick_policy=XXX
* S3/S4
-global PIIX4_PM.disable_s3=NNN
-global PIIX4_PM.disable_s4=NNN
-global ICH9-LPC.disable_s3=NNN
-global ICH9-LPC.disable_s4=NNN
* PCI hole
-global i440FX-pcihost.pci-hole64-size=NNN
-global q35-pcihost.pci-hole64-size=NNN
* SMM TSeg
-global mch.extended-tseg-mbytes=NNN
* pflash
-global driver=cfi.pflash01,property=secure,value=on
Used for EFI secure boot
I'm unclear which of these can be replaced with a different QEMU cli
option....
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-04-29 16:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 15:28 Failing property setters + hardwired devices + -global = a bad day Markus Armbruster
2020-04-29 15:39 ` Paolo Bonzini
2020-04-29 16:23 ` Eduardo Habkost
2020-04-29 15:57 ` Daniel P. Berrangé [this message]
2020-04-30 7:09 ` Markus Armbruster
2020-04-30 9:27 ` Peter Maydell
2020-04-30 10:03 ` Configuring onboard devices (was: Failing property setters + hardwired devices + -global = a bad day) Markus Armbruster
2020-04-30 10:29 ` Mark Cave-Ayland
2020-04-30 14:11 ` Configuring onboard devices Markus Armbruster
2020-04-30 14:32 ` Mark Cave-Ayland
2020-04-30 15:20 ` Markus Armbruster
2020-04-30 16:56 ` Mark Cave-Ayland
2020-05-02 5:47 ` Markus Armbruster
2020-05-03 22:13 ` Mark Cave-Ayland
2020-05-04 16:30 ` Eduardo Habkost
2020-04-30 10:34 ` Configuring onboard devices (was: Failing property setters + hardwired devices + -global = a bad day) Daniel P. Berrangé
2020-04-30 10:45 ` Peter Maydell
2020-04-30 10:53 ` Daniel P. Berrangé
2020-04-30 14:38 ` Configuring onboard devices Markus Armbruster
2020-04-30 10:54 ` Configuring onboard devices (was: Failing property setters + hardwired devices + -global = a bad day) Mark Cave-Ayland
2020-04-30 14:27 ` Configuring onboard devices Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200429155719.GL1495129@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).