From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server 1/2] drive device: fix regression with missing '/dev/disk/by-id' paths
Date: Wed, 23 Jul 2025 15:35:23 +0200 [thread overview]
Message-ID: <175327772144.3593033.17903257035130840247.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250723111105.72422-1-f.ebner@proxmox.com>
On Wed, 23 Jul 2025 13:10:46 +0200, Fiona Ebner wrote:
> With the switch to '-blockdev', it is necessary to explicitly specify
> the device ID for SCSI drives, see also [0]. Otherwise, the device
> paths in '/dev/disk/by-id' would be missing. For IDE/SATA, the paths
> are still present with '-blockdev' without additional changes and
> VirtIO block did not have such paths even before. The relevant
> 'ide-{cd,hd}' and 'virtio-blk-pci' devices do not seem to have an
> option that would be equivalent to the 'scsi-{cd,hd}' 'device_id'
> option.
>
> [...]
Applied, thanks!
[1/2] drive device: fix regression with missing '/dev/disk/by-id' paths
commit: 46d1225ec112df0f5db781f2315ad5e4321bbea1
[2/2] fix #6556: vm status: fix querying block stats
commit: bcaf38e5d414e1777b06b9888e6522fa73ce9291
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-23 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 11:10 [pve-devel] " Fiona Ebner
2025-07-23 11:10 ` [pve-devel] [PATCH qemu-server 2/2] fix #6556: vm status: fix querying block stats Fiona Ebner
2025-07-23 12:51 ` [pve-devel] [PATCH qemu-server 1/2] drive device: fix regression with missing '/dev/disk/by-id' paths Hannes Duerr
2025-07-23 12:55 ` Hannes Duerr
2025-07-23 13:12 ` Thomas Lamprecht
2025-07-23 13:19 ` Fiona Ebner
2025-07-23 13:35 ` Thomas Lamprecht [this message]
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=175327772144.3593033.17903257035130840247.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.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