Hi Folks,
sorry if this has been asked before but I couldn't find a solution as of today.
For a legacy app, based on slackware linux, I was able to produce a
custom kernel with kvm & virtio support, to be used in a guest-VM.
However the legacy Application to be run
requires the namespace for block devices to follow the scsi model (/dev/sdX).
I'd like to use the virtio block drivers instead of the scsi drivers.
Since I cannot change the application, I wonder if it is possible to change
the target naming for virtio devices from /dev(vdX into /dev/sdX in the guest.
my first thoughts:
- change udev rules in guest ?
- patch kvm / virtio modules in guest ?
- configure VM config on host ?
- wait until virtio_scsi in qemu has been made available/stable ?
- any other ideas ?
TIA,
p3x-749
sorry if this has been asked before but I couldn't find a solution as of today.
For a legacy app, based on slackware linux, I was able to produce a
custom kernel with kvm & virtio support, to be used in a guest-VM.
However the legacy Application to be run
requires the namespace for block devices to follow the scsi model (/dev/sdX).
I'd like to use the virtio block drivers instead of the scsi drivers.
Since I cannot change the application, I wonder if it is possible to change
the target naming for virtio devices from /dev(vdX into /dev/sdX in the guest.
my first thoughts:
- change udev rules in guest ?
- patch kvm / virtio modules in guest ?
- configure VM config on host ?
- wait until virtio_scsi in qemu has been made available/stable ?
- any other ideas ?
TIA,
p3x-749