Discussion:
[PVE-User] Questions about virtio-scsi-pci
Marcus Mattern
2016-02-06 20:44:50 UTC
Permalink
Hi,

I tried to use virtio-scsi-pci and therefore created a VM with a VIRTIO
Controller and one SCSI HDD. If I start the VM no HDD is found so it
can't boot. If I create a VIRTIO HDD it is found, but virtio-blk-pci is
used. But with virtio-blk-pci TRIM is not supported.

I'm running Version:
proxmox-ve: 4.1-34 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-5 (running version: 4.1-5/f910ef5c)

So what can I do?

Thanks in advance.
Regards.
Alexandre DERUMIER
2016-02-07 11:13:19 UTC
Permalink
Hi
If I start the VM no HDD is found so it can't boot.
in the vm options,

are you sure to have select "scsiX" drive in boot order options ?


----- Mail original -----
De: "Marcus Mattern" <proxmox-***@mattern.org>
À: "proxmoxve" <pve-***@pve.proxmox.com>
Envoyé: Samedi 6 Février 2016 21:44:50
Objet: [PVE-User] Questions about virtio-scsi-pci

Hi,

I tried to use virtio-scsi-pci and therefore created a VM with a VIRTIO
Controller and one SCSI HDD. If I start the VM no HDD is found so it
can't boot. If I create a VIRTIO HDD it is found, but virtio-blk-pci is
used. But with virtio-blk-pci TRIM is not supported.

I'm running Version:
proxmox-ve: 4.1-34 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-5 (running version: 4.1-5/f910ef5c)

So what can I do?

Thanks in advance.
Regards.
_______________________________________________
pve-user mailing list
pve-***@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Marcus Mattern
2016-02-08 08:07:47 UTC
Permalink
Yes.
If I press F12 for the boot-menu there's also no HDD shown.
I found out that when I start the VM manually and change the -device
option from

-device
scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=2,drive=drive-scsi2,id=scsi2

to

-device scsi-hd,drive=drive-scsi2,id=scsi2

it works. But I don't think that's the correct way to start it.
I've tested on two diffrent 4.1-5 Systems.

Marcus
Post by Alexandre DERUMIER
Hi
If I start the VM no HDD is found so it can't boot.
in the vm options,
are you sure to have select "scsiX" drive in boot order options ?
----- Mail original -----
Envoyé: Samedi 6 Février 2016 21:44:50
Objet: [PVE-User] Questions about virtio-scsi-pci
Hi,
I tried to use virtio-scsi-pci and therefore created a VM with a VIRTIO
Controller and one SCSI HDD. If I start the VM no HDD is found so it
can't boot. If I create a VIRTIO HDD it is found, but virtio-blk-pci is
used. But with virtio-blk-pci TRIM is not supported.
proxmox-ve: 4.1-34 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-5 (running version: 4.1-5/f910ef5c)
So what can I do?
Thanks in advance.
Regards.
_______________________________________________
pve-user mailing list
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Alexandre DERUMIER
2016-02-08 13:00:54 UTC
Permalink
can you post your /etc/pve/qemu-server/vmid.conf ?



----- Mail original -----
De: "Marcus Mattern" <proxmox-***@mattern.org>
À: "proxmoxve" <pve-***@pve.proxmox.com>
Envoyé: Lundi 8 Février 2016 09:07:47
Objet: Re: [PVE-User] Questions about virtio-scsi-pci

Yes.
If I press F12 for the boot-menu there's also no HDD shown.
I found out that when I start the VM manually and change the -device
option from

-device
scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=2,drive=drive-scsi2,id=scsi2

to

-device scsi-hd,drive=drive-scsi2,id=scsi2

it works. But I don't think that's the correct way to start it.
I've tested on two diffrent 4.1-5 Systems.

Marcus
Post by Alexandre DERUMIER
Hi
If I start the VM no HDD is found so it can't boot.
in the vm options,
are you sure to have select "scsiX" drive in boot order options ?
----- Mail original -----
Envoyé: Samedi 6 Février 2016 21:44:50
Objet: [PVE-User] Questions about virtio-scsi-pci
Hi,
I tried to use virtio-scsi-pci and therefore created a VM with a VIRTIO
Controller and one SCSI HDD. If I start the VM no HDD is found so it
can't boot. If I create a VIRTIO HDD it is found, but virtio-blk-pci is
used. But with virtio-blk-pci TRIM is not supported.
proxmox-ve: 4.1-34 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-5 (running version: 4.1-5/f910ef5c)
So what can I do?
Thanks in advance.
Regards.
_______________________________________________
pve-user mailing list
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
pve-***@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Marcus Mattern
2016-02-08 14:14:17 UTC
Permalink
Shure,

---
# Test VM
balloon: 256
boot: c
bootdisk: scsi2
cores: 1
cpu: host
hotplug: usb,network,disk
ide2: none,media=cdrom
memory: 512
name: test1
net0: virtio=D6:44:29:57:80:7A,bridge=vmbr0,tag=10
numa: 0
ostype: l26
scsi2: nfs2:100/vm-100-disk-1.qcow2,cache=writeback,size=10G
scsihw: virtio-scsi-pci
smbios1: uuid=38cdd23a-12b2-4ced-ba34-8827e72d507c
sockets: 1
---

Now I discovered, that the numbering of the devices seems to be the
problem. If I rename scsi2 to scsi0 it works. scsi2 was the result of
adding/removing several devices.
More testing shows that if I connect two devices first with virtio0: and
the second with scsi1: the BIOS doesn't show the scsi device but the OS
can find the device. So maybe it's a problem of SeaBIOS. E.g. connecting
only one volume with virtio2: works fine.

Marcus
Post by Alexandre DERUMIER
can you post your /etc/pve/qemu-server/vmid.conf ?
----- Mail original -----
Envoyé: Lundi 8 Février 2016 09:07:47
Objet: Re: [PVE-User] Questions about virtio-scsi-pci
Alexandre DERUMIER
2016-02-08 14:45:45 UTC
Permalink
mmm, same here, it's working with scsi0 but not scsi2.


with virtio-scsi, 1 single controller is used for all scsiX disk.

I'm not sure if boot is working withh all drives.
maybe it's a qemu bug or seabios limitation,I'll try to check that.


(with classic virtio-blk, it's 1controller by disk, so no problem for booting)

----- Mail original -----
De: "Marcus Mattern" <proxmox-***@mattern.org>
À: "proxmoxve" <pve-***@pve.proxmox.com>
Envoyé: Lundi 8 Février 2016 15:14:17
Objet: Re: [PVE-User] Questions about virtio-scsi-pci

Shure,

---
# Test VM
balloon: 256
boot: c
bootdisk: scsi2
cores: 1
cpu: host
hotplug: usb,network,disk
ide2: none,media=cdrom
memory: 512
name: test1
net0: virtio=D6:44:29:57:80:7A,bridge=vmbr0,tag=10
numa: 0
ostype: l26
scsi2: nfs2:100/vm-100-disk-1.qcow2,cache=writeback,size=10G
scsihw: virtio-scsi-pci
smbios1: uuid=38cdd23a-12b2-4ced-ba34-8827e72d507c
sockets: 1
---

Now I discovered, that the numbering of the devices seems to be the
problem. If I rename scsi2 to scsi0 it works. scsi2 was the result of
adding/removing several devices.
More testing shows that if I connect two devices first with virtio0: and
the second with scsi1: the BIOS doesn't show the scsi device but the OS
can find the device. So maybe it's a problem of SeaBIOS. E.g. connecting
only one volume with virtio2: works fine.

Marcus
Post by Alexandre DERUMIER
can you post your /etc/pve/qemu-server/vmid.conf ?
----- Mail original -----
Envoyé: Lundi 8 Février 2016 09:07:47
Objet: Re: [PVE-User] Questions about virtio-scsi-pci
_______________________________________________
pve-user mailing list
pve-***@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Loading...