kvm: bad scsi device lun: 1

Apr 25, 2019
6
0
41
50
Frankfurt am Main / GER
Dear all,

hello, this is my first post. :)

I'm trying to import some Windows VMs from ESXi to a fully patched pve.
All these have pvscsi configured.

Import works well but as soon as adding a second disk to the vm the startup of these vms fails:

Code:
root@pve01:~# qm start 103
kvm: -device scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1: bad scsi device lun: 1

This only happens with pvscsi controller.

Maybe a bug?

Regards,
Rainer
 
Last edited:
can you post the vm config?
qm config ID
 
I was able to migrate ID 103 to virtio-scsi.

This is ID 105 which has the same problems:
Bash:
root@pve01:/dev/mapper# qm start 105
kvm: -device scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1: bad scsi device lun: 1
start failed: QEMU exited with code 1
root@pve01:/dev/mapper# qm config 105
boot: order=scsi0;net0
cores: 2
memory: 4096
name: xxx
net0: virtio=BE:BC:77:B3:E9:86,bridge=vmbr0
numa: 0
ostype: win7
scsi0: data-extern:vm-105-disk-0,size=50G
scsi1: data-extern:vm-105-disk-1,size=10G
scsihw: pvscsi
smbios1: uuid=23fbeafd-0ac7-4ade-9080-260971989135
sockets: 1
tablet: 0
vga: qxl
vmgenid: 9ca7425e-1152-4ec8-b6a6-0e2758980d5d
 
Last edited:
I have the same. My VM was working, but I installed (today) updates on PVE (wihout subscription). And stop all VMs.
After reboot only this VM didn't start.

Code:
root@vhs2:~# qm start 100
kvm: -device scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1: bad scsi device lun: 1
start failed: QEMU exited with code 1

root@vhs2:~# qm config 100
agent: 1
bios: seabios
boot: order=scsi0
cores: 4
hotplug: disk,network,usb
memory: 4096
name: UNIBACK
net0: virtio=22:CA:DF:21:F2:ED,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: vhs2ZFS:100/vm-100-disk-0.qcow2,size=100G
scsi1: vhs2ZFS:100/vm-100-disk-1.qcow2,size=512G
scsi2: vhs2ZFS:100/vm-100-disk-2.qcow2,size=512G
scsi3: vhs2ZFS:100/vm-100-disk-3.qcow2,size=32G
scsihw: pvscsi
smbios1: uuid=a3b816b3-f0f0-44fa-a6bd-bbc8b077b6d9
sockets: 1
vmgenid: 863cc277-e086-4e17-a7e5-dfe70944b5b3
vmstatestorage: vhs2ZFS
root@vhs2:~#
 
Hi,
this is currently an issue when scsihw: pvscsi is used with multiple disks. As a workaround until the problem is solved, use a different SCSI controller type. I've sent a preliminary fix for discussion to the developer mailing list.