From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org,
libvir-list@redhat.com, Markus Armbruster <armbru@redhat.com>,
mreitz@redhat.com, jsnow@redhat.com
Subject: Re: [PATCH v2 1/3] fdc: Drop deprecated floppy configuration
Date: Thu, 4 Mar 2021 16:54:20 +0000 [thread overview]
Message-ID: <YEEQvHAJADUKd0Eb@redhat.com> (raw)
In-Reply-To: <20210304165250.GZ2875719@angien.pipo.sk>
On Thu, Mar 04, 2021 at 05:52:50PM +0100, Peter Krempa wrote:
> On Thu, Mar 04, 2021 at 17:23:05 +0100, Markus Armbruster wrote:
> > Daniel P. Berrangé <berrange@redhat.com> writes:
> >
> > > On Thu, Mar 04, 2021 at 03:26:55PM +0100, Markus Armbruster wrote:
> > >> Daniel P. Berrangé <berrange@redhat.com> writes:
> > >>
> > >> > On Thu, Mar 04, 2021 at 11:00:57AM +0100, Markus Armbruster wrote:
> > >> >> Drop the crap deprecated in commit 4a27a638e7 "fdc: Deprecate
> > >> >> configuring floppies with -global isa-fdc" (v5.1.0).
> > >> >>
> > >> >> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> > >> >> ---
> > >> >> docs/system/deprecated.rst | 26 --
> > >> >> docs/system/removed-features.rst | 26 ++
> > >> >> hw/block/fdc.c | 54 +--
> > >> >> tests/qemu-iotests/172 | 31 +-
> > >> >> tests/qemu-iotests/172.out | 562 +------------------------------
> > >> >> 5 files changed, 30 insertions(+), 669 deletions(-)
>
> [...]
>
> > >>
> > >> Correct.
> > >>
> > >> This was deprecated in commit 4a27a638e7 "fdc: Deprecate configuring
> > >> floppies with -global isa-fdc" (v5.1.0). Since then, its use triggers a
> > >> warning:
> > >>
> > >> $ qemu-system-x86_64 -nodefaults -M q35 -display none -drive if=none,id=drive-fdc0-0-0 -device isa-fdc,driveA=drive-fdc0-0-0,bootindexA=1
> > >> qemu-system-x86_64: -device isa-fdc,driveA=drive-fdc0-0-0,bootindexA=1: warning: warning: property isa-fdc.driveA is deprecated
> > >> Use -device floppy,unit=0,drive=... instead.
> > >>
> > >> Note the -M q35. Needed because the default machine type has an onboard
> > >> isa-fdc, which cannot be configured this way.
> > >>
> > >> Sadly, the commit's update of docs/system/deprecated.rst neglects to
> > >> cover this use. Looks the series overtaxed my capacity to juggle
> > >> details; my apologies.
> > >>
> > >> Is libvirt still using these properties?
> > >
> > > Unfortunately yes, but it seems like it ought to be fairly easy to
> > > change the syntax. Just need to figure out what the right way to
> > > detect the availability of the new syntax is. Presumably just look
> > > for existance of the 'floppy' device type ?
> >
> > Yes. The device type was added in merge commit fd209e4a7, v2.8.0.
> >
> > > Can you confirm that switching from -global to the new -device floppy
> > > does /not/ have any live migration impact ?
> >
> > Yes, it must not affect migration.
> >
> > When Kevin split the floppy device type off the floppy controller, he
> > had to add some moderately ugly hackery to keep the old qdev properties
> > working. Think propagate property values to floppy from controller,
> > which otherwise ignores them.
> >
> > The way you get the values into the floppy device cannot affect the
> > migration data. Only different values can.
> >
> > This patch removes a deprecated way.
>
> Note that when QEMU_CAPS_BLOCKDEV is asserted we format floppies as:
>
> -blockdev '{"driver":"file","filename":"/tmp/firmware.img",\
> "node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \
> -blockdev '{"node-name":"libvirt-2-format","read-only":false,"driver":"raw",\
> "file":"libvirt-2-storage"}' \
> -device floppy,unit=0,drive=libvirt-2-format,id=fdc0-0-0 \
> -blockdev '{"driver":"file","filename":"/tmp/data.img",\
> "node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \
> -blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2",\
> "file":"libvirt-1-storage"}' \
> -device floppy,unit=1,drive=libvirt-1-format,id=fdc0-0-1 \
>
> as visible in the test file:
>
> tests/qemuxml2argvdata/disk-floppy-q35-2_11.x86_64-latest.args
>
> So libvirt should be in the clear. isa-fdc with driveA/driveB is
> formatted only when the blockdev capability isn't present.
Ahh, excellant, I missed that detailed and worried that we still had
work todo.
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:[~2021-03-04 16:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 10:00 [PATCH v2 0/3] Drop deprecated floppy config & bogus -drive if=T Markus Armbruster
2021-03-04 10:00 ` [PATCH v2 1/3] fdc: Drop deprecated floppy configuration Markus Armbruster
2021-03-04 10:52 ` Daniel P. Berrangé
2021-03-04 14:26 ` Markus Armbruster
2021-03-04 14:34 ` Daniel P. Berrangé
2021-03-04 16:23 ` Markus Armbruster
2021-03-04 16:52 ` Peter Krempa
2021-03-04 16:54 ` Daniel P. Berrangé [this message]
2021-03-05 6:41 ` Markus Armbruster
2021-03-05 8:06 ` Markus Armbruster
2021-03-08 11:23 ` Daniel P. Berrangé
2021-03-04 10:00 ` [PATCH v2 2/3] fdc: Inline fdctrl_connect_drives() into fdctrl_realize_common() Markus Armbruster
2021-03-04 10:00 ` [PATCH v2 3/3] blockdev: Drop deprecated bogus -drive interface type 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=YEEQvHAJADUKd0Eb@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.