* [RFC] nvme errors on QEMU
@ 2021-06-08 5:03 Heinrich Schuchardt
0 siblings, 0 replies; only message in thread
From: Heinrich Schuchardt @ 2021-06-08 5:03 UTC (permalink / raw)
To: Bin Meng, Zhikang Zhang; +Cc: U-Boot Mailing List
I am calling qemu-x86_64_defconfig with
qemu-system-x86_64 -machine pc-i440fx-2.5 -m 1G -smp cores=2 \
-bios u-boot.rom -nographic -gdb tcp::1234 \
-drive file=../sandbox.img,if=none,format=raw,id=nvme1 \
-device nvme,drive=nvme1,serial="S3EWNX0J123456K" \
-netdev user,id=eth0,tftp=tftp -device e1000,netdev=eth0 \
-device virtio-rng-pci
nvme info displays a lot of errors:
=> nvme scan
=> nvme info
Device 0: Vendor: 0x8086 Rev: 1.0 Prod: S3EWNX0J123456K
Type: Hard Disk
Capacity: 128.9 MB = 0.1 GB (264190 x 512)
ERROR: status = 4002, phase = 1, head = 1
ERROR: status = 4002, phase = 0, head = 0
Device 1: Vendor: 0x8086 Rev: 1.0 Prod: S3EWNX0J123456K
Type: Hard Disk
Capacity: not available
ERROR: status = 4002, phase = 0, head = 1
ERROR: status = 4002, phase = 1, head = 0
Device 2: Vendor: 0x8086 Rev: 1.0 Prod: S3EWNX0J123456K
Type: Hard Disk
Capacity: not available
...
ERROR: status = 4002, phase = 1, head = 1
ERROR: status = 4002, phase = 0, head = 0
Device 255: Vendor: 0x8086 Rev: 1.0 Prod: S3EWNX0J123456K
Type: Hard Disk
Capacity: not available
Why does 'nvme scan' create 255 nvme-blk devices too many?
Best regards
Heinrich
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-06-08 5:03 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-08 5:03 [RFC] nvme errors on QEMU Heinrich Schuchardt
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.