Howto provide an scsi changer (jukebox) to an VM?

udo

Distinguished Member
Apr 22, 2009
5,977
199
163
Ahrensburg; Germany
Hi,
I'm trying to change our backup-server from OpenVZ to kvm with an new SAS Jukebox (4 lto-6 drives plus changer device).

The drives can be provided, but the changer gives an error:
Code:
qm start 302
kvm: -device scsi-hd,bus=scsihw0.0,scsi-id=4,drive=drive-scsi4,id=scsi4: unwanted /dev/sg*
kvm: -device scsi-hd,bus=scsihw0.0,scsi-id=4,drive=drive-scsi4,id=scsi4: Device initialization failed.
kvm: -device scsi-hd,bus=scsihw0.0,scsi-id=4,drive=drive-scsi4,id=scsi4: Device 'scsi-hd' could not be initialized
start failed: command '/usr/bin/kvm -id 302 -chardev 'socket,id=qmp,path=/var/run/qemu-server/302.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/302.vnc,x509,password -pidfile /var/run/qemu-server/302.pid -daemonize -smbios 'type=1,uuid=0d60381a-1f1c-4480-879b-fbaf2dc5fd73' -name backup-srv-ng-kvm -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -m 4096 -k de -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:46383251a8db' -device 'lsi,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/sg1,if=none,id=drive-scsi1,cache=writethrough,aio=native,detect-zeroes=on' -device 'scsi-generic,bus=scsihw0.0,scsi-id=1,drive=drive-scsi1,id=scsi1' -drive 'file=/dev/sg3,if=none,id=drive-scsi3,cache=writethrough,aio=native,detect-zeroes=on' -device 'scsi-generic,bus=scsihw0.0,scsi-id=3,drive=drive-scsi3,id=scsi3' -drive 'file=/dev/sdb,if=none,id=drive-virtio1,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb' -drive 'file=/dev/sg0,if=none,id=drive-scsi0,cache=writethrough,aio=native,detect-zeroes=on' -device 'scsi-generic,bus=scsihw0.0,scsi-id=0,drive=drive-scsi0,id=scsi0' -drive 'file=/dev/sdc,if=none,id=drive-virtio2,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio2,id=virtio2,bus=pci.0,addr=0xc' -drive 'file=/dev/sg2,if=none,id=drive-scsi2,cache=writethrough,aio=native,detect-zeroes=on' -device 'scsi-generic,bus=scsihw0.0,scsi-id=2,drive=drive-scsi2,id=scsi2' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/302/vm-302-disk-1.raw,if=none,id=drive-virtio0,format=raw,cache=writethrough,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=106' -drive 'file=/dev/tape/by-id/scsi-1IBM_3573-TL_00L4U78W1613_LL0,if=none,id=drive-scsi4,cache=writethrough,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,scsi-id=4,drive=drive-scsi4,id=scsi4' -netdev 'type=tap,id=net0,ifname=tap302i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=9A:05:07:46:F6:1C,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
ipcc_send_rec failed: File too large
Looks that kvm think all scsi-devices must be an disk?!

The howto http://pve.proxmox.com/wiki/Tape_Drives looks much to old.

My VM-config:
Code:
bootdisk: virtio0
cores: 4
ide2: none,media=cdrom
memory: 4096
name: backup-srv-ng-kvm
net0: virtio=9A:05:07:46:F6:1C,bridge=vmbr0
ostype: l26
scsi0: /dev/sg0,cache=writethrough,backup=no
scsi1: /dev/sg1,cache=writethrough,backup=no
scsi2: /dev/sg2,cache=writethrough,backup=no
scsi3: /dev/sg3,cache=writethrough,backup=no
scsi4: /dev/tape/by-id/scsi-1IBM_3573-TL_00L4U78W1613_LL0,cache=writethrough,backup=no
smbios1: uuid=0d60381a-1f1c-4480-879b-fbaf2dc5fd73
sockets: 1
virtio0: local:302/vm-302-disk-1.raw,format=raw,cache=writethrough,size=8G
virtio1: /dev/sdb
virtio2: /dev/sdc
The last resort was the installation of bareos-sd (or bacula-sd) on the host, but I would avoid the traffic for 4 lto-6 drives (can be +500MB/s) through an additional network-bridge.

Any hints?

Udo
 
Hi,
I'm trying to change our backup-server from OpenVZ to kvm with an new SAS Jukebox (4 lto-6 drives plus changer device).

The drives can be provided, but the changer gives an error:
Code:
qm start 302
kvm: -device scsi-hd,bus=scsihw0.0,scsi-id=4,drive=drive-scsi4,id=scsi4: unwanted /dev/sg*
kvm: -device scsi-hd,bus=scsihw0.0,scsi-id=4,drive=drive-scsi4,id=scsi4: Device initialization failed.
kvm: -device scsi-hd,bus=scsihw0.0,scsi-id=4,drive=drive-scsi4,id=scsi4: Device 'scsi-hd' could not be initialized
start failed: command '/usr/bin/kvm -id 302 -chardev 'socket,id=qmp,path=/var/run/qemu-server/302.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/302.vnc,x509,password -pidfile /var/run/qemu-server/302.pid -daemonize -smbios 'type=1,uuid=0d60381a-1f1c-4480-879b-fbaf2dc5fd73' -name backup-srv-ng-kvm -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -m 4096 -k de -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:46383251a8db' -device 'lsi,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/sg1,if=none,id=drive-scsi1,cache=writethrough,aio=native,detect-zeroes=on' -device 'scsi-generic,bus=scsihw0.0,scsi-id=1,drive=drive-scsi1,id=scsi1' -drive 'file=/dev/sg3,if=none,id=drive-scsi3,cache=writethrough,aio=native,detect-zeroes=on' -device 'scsi-generic,bus=scsihw0.0,scsi-id=3,drive=drive-scsi3,id=scsi3' -drive 'file=/dev/sdb,if=none,id=drive-virtio1,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb' -drive 'file=/dev/sg0,if=none,id=drive-scsi0,cache=writethrough,aio=native,detect-zeroes=on' -device 'scsi-generic,bus=scsihw0.0,scsi-id=0,drive=drive-scsi0,id=scsi0' -drive 'file=/dev/sdc,if=none,id=drive-virtio2,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio2,id=virtio2,bus=pci.0,addr=0xc' -drive 'file=/dev/sg2,if=none,id=drive-scsi2,cache=writethrough,aio=native,detect-zeroes=on' -device 'scsi-generic,bus=scsihw0.0,scsi-id=2,drive=drive-scsi2,id=scsi2' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/302/vm-302-disk-1.raw,if=none,id=drive-virtio0,format=raw,cache=writethrough,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=106' -drive 'file=/dev/tape/by-id/scsi-1IBM_3573-TL_00L4U78W1613_LL0,if=none,id=drive-scsi4,cache=writethrough,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,scsi-id=4,drive=drive-scsi4,id=scsi4' -netdev 'type=tap,id=net0,ifname=tap302i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=9A:05:07:46:F6:1C,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
ipcc_send_rec failed: File too large
Looks that kvm think all scsi-devices must be an disk?!

The howto http://pve.proxmox.com/wiki/Tape_Drives looks much to old.

My VM-config:
Code:
bootdisk: virtio0
cores: 4
ide2: none,media=cdrom
memory: 4096
name: backup-srv-ng-kvm
net0: virtio=9A:05:07:46:F6:1C,bridge=vmbr0
ostype: l26
scsi0: /dev/sg0,cache=writethrough,backup=no
scsi1: /dev/sg1,cache=writethrough,backup=no
scsi2: /dev/sg2,cache=writethrough,backup=no
scsi3: /dev/sg3,cache=writethrough,backup=no
scsi4: /dev/tape/by-id/scsi-1IBM_3573-TL_00L4U78W1613_LL0,cache=writethrough,backup=no
smbios1: uuid=0d60381a-1f1c-4480-879b-fbaf2dc5fd73
sockets: 1
virtio0: local:302/vm-302-disk-1.raw,format=raw,cache=writethrough,size=8G
virtio1: /dev/sdb
virtio2: /dev/sdc
The last resort was the installation of bareos-sd (or bacula-sd) on the host, but I would avoid the traffic for 4 lto-6 drives (can be +500MB/s) through an additional network-bridge.

Any hints?

Udo

Hi, I have the same problem with the scsi type=8 devices.

Did you find a solution?

Regards.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!