Win2008 R2 turns off no reason - Linux OS fine
- Thread starter Bwalker
- Start date
Also here are my Disk stats
Virtio - SYNC 550 read / 25 Write
Virtio - Writethrough 2837 / 12
Virtio - Writeback - 2800 / 2800
Virtio - No Cache 600 / 600
But your docs don't seem to make sense
When I use
Virtio - it installs "red hat virtio-scsi controller"
When I use SCSI it installs "red hat virtio-scsi PASSthrough controller"
But your documents say Virtio is an old block device which doesn't even seem to exist anymore at all.
Virtio - SYNC 550 read / 25 Write
Virtio - Writethrough 2837 / 12
Virtio - Writeback - 2800 / 2800
Virtio - No Cache 600 / 600
But your docs don't seem to make sense
When I use
Virtio - it installs "red hat virtio-scsi controller"
When I use SCSI it installs "red hat virtio-scsi PASSthrough controller"
But your documents say Virtio is an old block device which doesn't even seem to exist anymore at all.
- the SCSI controller, designed in 1985, is commonly found on server grade hardware, and can connect up to 14 storage devices. Proxmox VE emulates by default a LSI 53C895A controller.
A SCSI controller of type VirtIO SCSI is the recommended setting if you aim for performance and is automatically selected for newly created Linux VMs since Proxmox VE 4.3. Linux distributions have support for this controller since 2012, and FreeBSD since 2014. For Windows OSes, you need to provide an extra iso containing the drivers during the installation. If you aim at maximum performance, you can select a SCSI controller of type VirtIO SCSI single which will allow you to select the IO Thread option. When selecting VirtIO SCSI single Qemu will create a new controller for each disk, instead of adding all disks to the same controller.
- The Virtio controller, also called virtio-blk to distinguish from the VirtIO SCSI controller, is an older type of paravirtualized controller which has been superseded in features by the Virtio SCSI Controller.
