惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
博客园 - 司徒正美
博客园 - 【当耐特】
爱范儿
爱范儿
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
IT之家
IT之家
人人都是产品经理
人人都是产品经理
雷峰网
雷峰网
酷 壳 – CoolShell
酷 壳 – CoolShell
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
大猫的无限游戏
大猫的无限游戏
月光博客
月光博客
宝玉的分享
宝玉的分享
V
V2EX
S
SegmentFault 最新的问题
V
Visual Studio Blog
阮一峰的网络日志
阮一峰的网络日志
Martin Fowler
Martin Fowler
Jina AI
Jina AI
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
博客园_首页
L
LangChain Blog
D
Docker
腾讯CDC

ktz.

Control a Mitsubishi mini-split with ESPHome and Home Assistant for $10 The Enshittification of Plex 💩 I read a book. Codex is changing how I think about computers Factorio: Controlling imports from Space Factorio: Controlling Space Ship collector filters via circuit logic Factorio: Recycler Belt Stacking Was Solar Worth It? AppArmor's Awkward Aftermath Atop Proxmox 9 Unprivileged LXCs are just a bit annoying My Terminal and Editor Theming Proxmox 9 broke my docker containers What if..? Self-Hosted 150. Fin. How to enable Intel Quicksync on NixOS with a Supermicro X13SAE-F and an Intel i5-13600k
Faking disks to look real with QEMU and Proxmox
Alex Kretzschmar · 2026-06-07 · via ktz.
Faking disks to look real with QEMU and Proxmox

Whilst prepping for Perfect Media Server Part 3, I needed to conduct some testing with a Proxmox VM and make fake QEMU disks attached via SCSI look real to inxi -xD.

The problem was that inxi kept showing generic QEMU HARDDISK. Fine, but not what I wanted when filming a video about how to identify physical disks and map them to your fstab file. I had hoped I could make it feel a bit more real in the video without having to drag a ton of old physical disks out of storage.

root@proxtest:~# inxi -xD
Drives:
  Local Storage: total: 240 GiB lvm-free: 16 GiB used: 5.71 GiB (2.4%)
  ID-1: /dev/sda vendor: QEMU model: HARDDISK size: 10 GiB
  ID-2: /dev/sdb vendor: QEMU model: HARDDISK size: 8 GiB
  ID-3: /dev/sdc vendor: QEMU model: HARDDISK size: 5 GiB
  ID-4: /dev/sdd vendor: QEMU model: HARDDISK size: 7 GiB
  ID-5: /dev/sde vendor: QEMU model: HARDDISK size: 10 GiB

Unfortunately, setting the serial= parameter had no effect. Which led me to do a deepdive on the fields that Proxmox SCSI disks support:

vendor
product
serial
wwn

The useful ones for inxi -xD are vendor and product.

Here is one example:

qm set 1000 \
  --scsi0 local-lvm:vm-1000-disk-2,discard=on,iothread=1,product=WD10EZEX-D10A,serial=SNAP1000D10A,size=10G,vendor=WDC,wwn=0x5000100001001000

I did that for each fake disk. Then after a full VM stop and start, inxi -xD showed me what I wanted. Pretty convincing at first glance, wouldn't you say? Perfect for my needs tonight.

ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-D10A size: 10 GiB
ID-2: /dev/sdb vendor: HGST (Hitachi) model: HDN7280D08 size: 8 GiB
ID-3: /dev/sdc vendor: Crucial model: CT500MX500D05 size: 5 GiB
ID-4: /dev/sdd vendor: Seagate model: ST7000VN-D07 size: 7 GiB
ID-5: /dev/sde vendor: Western Digital model: WD10PURX-P10 size: 10 GiB

A couple of small gotchas, you can only set the values to a max:

vendor  = max 8 bytes
product = max 16 bytes
serial  = max 20 bytes
wwn     = 0x plus 16 hex digits

Also, vendor=WDC shows up as Western Digital in inxi because it normalizes some short hardware vendor codes into friendly names. WDC is the common vendor string for Western Digital disks. Linux sees the SCSI vendor as WDC, but inxi maps that to Western Digital for display.

Hope you found this little tip useful.