From: Dominik Csapak <d.csapak@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server v7 6/9] api: enable live migration for marked mapped pci devices
Date: Thu, 3 Apr 2025 15:07:06 +0200 [thread overview]
Message-ID: <1e85aa62-dd7d-4b33-b754-3e7207ee69a5@proxmox.com> (raw)
In-Reply-To: <72026c72-5ac0-4e76-8387-c95137529e46@proxmox.com>
On 4/3/25 15:00, Thomas Lamprecht wrote:
> Am 11.03.25 um 14:20 schrieb Dominik Csapak:
>> They have to be marked as 'live-migration-capable' in the mapping
>> config, and the driver and qemu must support it.
>>
>> For the gui checks, we now return the whole object of the mapped
>> resources, which includes info like the name and if it's marked as
>> live-migration capable. (while deprecating the old 'mapped-resource'
>> return value, since that returns strictly less information)
>>
>> Reviewed-by: Christoph Heiss <c.heiss@proxmox.com>
>> Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
>> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
>> ---
>> PVE/API2/Qemu.pm | 8 +++++++-
>> PVE/QemuMigrate.pm | 17 ++++++++++++-----
>> 2 files changed, 19 insertions(+), 6 deletions(-)
>>
>> diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
>> index 060bca8b..15bf7548 100644
>> --- a/PVE/API2/Qemu.pm
>> +++ b/PVE/API2/Qemu.pm
>> @@ -4665,13 +4665,18 @@ __PACKAGE__->register_method({
>> },
>> description => "List local resources (e.g. pci, usb) that block migration."
>> },
>> + # FIXME: remove with 9.0
>> 'mapped-resources' => {
>> type => 'array',
>> items => {
>> type => 'string',
>> description => "A mapped resource",
>> },
>> - description => "List of mapped resources e.g. pci, usb"
>> + description => "List of mapped resources e.g. pci, usb. Deprecated, use 'mapped-resource-info' instead."
>> + },
>> + 'mapped-resource-info' => {
>> + type => 'object',
>> + description => "Object of mapped resources with additional information such if they're live migratable.",
>
> Where is the schema/format for this? New stuff really should be documented
> here, I mean, have you not sent enough schema updates to unlock basic features
> in the rust based PVE api crate used in PDM? ;-)
Yes, you're right. I'll send a follow up for that if that's fine with you.
>
>> },
>> },
>> },
>> @@ -4737,6 +4742,7 @@ __PACKAGE__->register_method({
>>
>> $res->{local_resources} = $local_resources;
>> $res->{'mapped-resources'} = [ sort keys $mapped_resources->%* ];
>> + $res->{'mapped-resource-info'} = $mapped_resources;
>
> would be IMO nicer to add returning that info upfront and then combine this
> with patch with 4/9 to have two patches that each do one thing, and not a
> split/mix.
>
> But I probably will just apply this as is with trying to bend the commit
> message from implementation details to the effect of the patch, will not
> be ideal, but I want to finish this finally..
If you want I can try to rework this part of the series, since it does make
sense like you described, but I'm not sure I could finish that today.
>
> No offense to anybody, but IMO does not pain the best picture considering
> this has two R-b tags..
>
>>
>> return $res;
>>
>> diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
>> index 2153ac42..6909fc82 100644
>> --- a/PVE/QemuMigrate.pm
>> +++ b/PVE/QemuMigrate.pm
>> @@ -243,11 +243,18 @@ sub prepare {
>>
>> if (scalar(keys $mapped_res->%*)) {
>> my $missing_mappings = $missing_mappings_by_node->{$self->{node}};
>> - if ($running) {
>> - my $mapped_text = join(", ", sort keys $mapped_res->%*);
>> - die "can't migrate running VM which uses mapped devices: $mapped_text\n";
>> - } elsif (scalar($missing_mappings->@*)) {
>> - die "can't migrate to '$self->{node}': missing mapped devices " . join(", ", $missing_mappings->@*) . "\n";
>> + my $missing_live_mappings = [];
>> + for my $key (sort keys $mapped_res->%*) {
>> + my $res = $mapped_res->{$key};
>> + my $name = "$key:$res->{name}";
>> + push $missing_live_mappings->@*, $name if !$res->{'live-migration'};
>> + }
>> + if (scalar($missing_mappings->@*)) {
>> + my $missing = join(", ", $missing_mappings->@*);
>> + die "can't migrate to '$self->{node}': missing mapped devices $missing\n";
>> + } elsif ($running && scalar($missing_live_mappings->@*)) {
>> + my $missing = join(", ", $missing_live_mappings->@*);
>> + die "can't live migrate running VM which uses following mapped devices: $missing\n";
>> } else {
>> $self->log('info', "migrating VM which uses mapped local devices");
>> }
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-04-03 13:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 13:20 [pve-devel] [PATCH guest-common/qemu-server/manager/docs v7] implement experimental vgpu live migration Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH guest-common v7 1/2] mapping: pci: check the mdev configuration on the device too Dominik Csapak
2025-04-03 9:40 ` Thomas Lamprecht
2025-04-03 9:43 ` Dominik Csapak
2025-04-03 9:44 ` Thomas Lamprecht
2025-03-11 13:20 ` [pve-devel] [PATCH guest-common v7 2/2] mapping: pci: add 'live-migration-capable' flag to mappings Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH qemu-server v7 1/9] tests: cfg2cmd: fix mdev tests Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH qemu-server v7 2/9] pci: mapping: check mdev config against hardware Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH qemu-server v7 3/9] pci: set 'enable-migration' to on for live-migration marked mapped devices Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH qemu-server v7 4/9] check_local_resources: add more info per mapped device and return as hash Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH qemu-server v7 5/9] check_local_resources: allow mapped devices for offline migration Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH qemu-server v7 6/9] api: enable live migration for marked mapped pci devices Dominik Csapak
2025-04-03 13:00 ` Thomas Lamprecht
2025-04-03 13:07 ` Dominik Csapak [this message]
2025-04-03 14:19 ` [pve-devel] [PATCH follow-up qemu-server] api: migrate preconditions: add schema description for 'mapped-resource-info' Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH qemu-server v7 7/9] api: include not mapped resources for running vms in migrate preconditions Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH qemu-server v7 8/9] migrate: show vfio state transferred too Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH qemu-server v7 9/9] migrate: add transfer summary Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH manager v7 1/4] mapping: pci: include mdev in config checks Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH manager v7 2/4] bulk migrate: improve precondition checks Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH manager v7 3/4] ui: adapt migration window to precondition api change Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH manager v7 4/4] fix #5175: ui: allow configuring and live migration of mapped pci resources Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH docs v7 1/2] qm: resource mapping: add description for `mdev` option Dominik Csapak
2025-03-11 13:20 ` [pve-devel] [PATCH docs v7 2/2] qm: resource mapping: document `live-migration-capable` setting Dominik Csapak
2025-04-01 9:18 ` [pve-devel] [PATCH guest-common/qemu-server/manager/docs v7] implement experimental vgpu live migration Dominik Csapak
2025-04-01 13:17 ` Christoph Heiss
2025-04-03 16:33 ` [pve-devel] applied-series: " Thomas Lamprecht
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=1e85aa62-dd7d-4b33-b754-3e7207ee69a5@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal