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

Aberta
  • Algo errado?
#14,514 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java
Domínio
backend, infrastructure

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Java
Estrelas
3.1k
Forks
1.4k
Merge médio
7d 16h
PRs com merge (30d)
15

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de apache/cloudstack

Todas as issues de apache/cloudstack

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.