KVM: VMs with a data volume already on a reserved device id still cannot start after the upgrade to the device id fix

Offen
  • Stimmt etwas nicht?
#14,514 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java
Bereich
backend, infrastructure

Rechercherichtung

Start by tracing the KVM VM start path that assigns device IDs to data volumes, CD-ROMs, and the config drive ISO; the issue does not name source files or tests. Compare how existing volumes with reserved IDs are handled during startup with the detach and reattach behavior described here. Done when affected q35 VMs start after upgrade without manual volume reattachment.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug component:kvm component:storage component:upgrade
Problem

The device id fixes on 4.22 and main reserve the device ids of the CD-ROMs and the config drive ISO for new data volumes. Volumes that already use one of these device ids (created on an earlier version) are not changed, as noted in both fixes. On q35 these VMs still fail to start with XML error: target '...' duplicated after the upgrade, until the volume is detached and attached again. These VMs could not start before the upgrade either (on 4.23.0.0 a config drive VM with a data volume on 5 also fails with vm.iso.max.count=2), so this is not a regression of the fixes.

Versions

The versions of ACS, hypervisors, storage, network etc..The VMs already fail on the old version (4.22.1.0, 4.23.0.0). They still fail after the upgrade to a build that includes the fix:

  • 4.22.1.0 upgraded to the 4.22 build with the device id fix (4.22.2.0-SNAPSHOT): q35 config drive VM with a data volume on deviceid 4 (target 'sde' duplicated).
  • 4.23.0.0 upgraded to main (24.0.0-SNAPSHOT): q35 VMs with a data volume on deviceid 4, with and without config drive (target 'sde' duplicated). A q35 config drive VM with a data volume on deviceid 5 starts with vm.iso.max.count=1 and fails with vm.iso.max.count=2 (target 'sdf' duplicated).

Environment:

KVM on Oracle Linux 9, qemu-kvm 7.2.0, libvirt 9.0.0, machine type pc-q35-rhel9.2.0 (template settings rootDiskController=scsi, kvm.guest.os.machine.type=pc-q35-rhel9.2.0, UEFI=LEGACY), host.cdrom.max.count 2. NFS primary storage.

The steps to reproduce the bug
  1. On the earlier version (4.22.1.0 or 4.23.0.0), create an L2 network with DefaultL2NetworkOfferingConfigDrive.
  2. Deploy a q35 scsi VM on it (stopped) and attach 3 data volumes. The 3rd gets deviceid 4.
  3. Upgrade the management server and the KVM agents to the version with the fix.
  4. Start the VM. It fails with 530 "Unable to orchestrate the start of VM instance", and the management server log has "Unable to start VM on Host ... XML error: target 'sde' duplicated" for each host.
  5. Detach the volume on deviceid 4 and attach it again: it gets 5 (4.22) or 6 (main), and the VM starts.
What to do about it?

Expected: after the upgrade, VMs with data volumes on the reserved device ids start without a manual detach and attach.

Vorherrschende Sprache
Java
Sterne
3.1k
Forks
1.4k
Ø Merge
7 T. 16 Std.
Gemergte PRs (30 T.)
15

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus apache/cloudstack

Alle Issues in apache/cloudstack

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.