I'm talking about virtio-scsi. Our virtio-network device is working fine
Sent from BlueMail
Get BlueMail for Android
On Aug 14, 2024, 15:22, at 15:22, "DERUMIER, Alexandre"
wrote:
>>>Alexandre,
>>>
>>>the statement below is not true for our case. The OpenVMS guest OS is
>>>using a PCIE bus
Alexandre,
thank you for your information. On another KVM, the virtio-scsi device has the
hardware id of 0x10481AF4, whereas on Proxmox is has 0x10041AF4, which is a
legacy device.
But after more testing, I do not think that the issue is related to legacy vs
modern device, but rather interrupt
Alexandre,
the statement below is not true for our case. The OpenVMS guest OS is using a
PCIE bus, so the virtio-scsi device should be exposed as "modern", but is not.
Not sure why not at this point
/cmos
___
Christian Moser
Mobile:+358-4
Hello,
what I have been trying to tell is that both virtio-scsi and virtio-network
device on Proxmox are both getting configured on PCIE. I do not understand why
you claim that virtio-scsi is not configured on PCIE.
So both virtio-scsi and virtio-network devices on Proxmox are configured as
le
--- Begin Message ---
>>I'm talking about virtio-scsi. Our virtio-network device is working
>>fine
Yes, sorry, I wanted to said virtio-scsi.
All pci devices excluding passthrough devices (with pcie=on flag) are
actually plugged to pci bridge
sub get_pci_addr_map {
$pci_addr_map = {
--- Begin Message ---
>>Alexandre,
>>
>>the statement below is not true for our case. The OpenVMS guest OS is
>>using a PCIE bus, so the virtio-scsi device should be exposed as
>>"modern", but is not. Not sure why not at this point
See Fiona response,
the pci express bridge is present, but the vi
