search for: virtio1

VIRTIO_BLK_F_CONFIG_WCE is important in order to achieve good performance (up to 2x, though more realistically +30-40%) in latency-bound workloads. However, it was removed by mistake together with VIRTIO_BLK_F_FLUSH. It will be restored in the next revision of the virtio 1.0 standard, so do the same in Linux. Signed-off-by: Paolo Bonzini <pbonzini at redhat.com> ---

VIRTIO_BLK_F_CONFIG_WCE is important in order to achieve good performance (up to 2x, though more realistically +30-40%) in latency-bound workloads. However, it was removed by mistake together with VIRTIO_BLK_F_FLUSH. It will be restored in the next revision of the virtio 1.0 standard, so do the same in Linux. Signed-off-by: Paolo Bonzini <pbonzini at redhat.com> ---

..."-1" ATTRS{d3cold_allowed}=="0" looking at parent device '/devices/pci0000:00': KERNELS=="pci0000:00" SUBSYSTEMS=="" DRIVERS=="" # udevadm info -q all -a /dev/sdb looking at device '/devices/pci0000:00/0000:00:04.0/virtio1/host1/target1:0:1/1:0:1:0/block/sdb': KERNEL=="sdb" SUBSYSTEM=="block" DRIVER=="" ATTR{ro}=="0" ATTR{size}=="786432000" ATTR{stat}==" 219 0 12776 101 16 0 4096 63 0...

...not place kexec images on this memory), and it is exposed as "System RAM (virtio_mem)" in /proc/iomem, so esp. kexec-tools can properly handle it. Example /proc/iomem before this change: [...] 140000000-333ffffff : virtio0 140000000-147ffffff : System RAM 334000000-533ffffff : virtio1 338000000-33fffffff : System RAM 340000000-347ffffff : System RAM 348000000-34fffffff : System RAM [...] Example /proc/iomem after this change: [...] 140000000-333ffffff : virtio0 140000000-147ffffff : System RAM (virtio_mem) 334000000-533ffffff : virtio1 338000000-33ff...

...not place kexec images on this memory), and it is exposed as "System RAM (virtio_mem)" in /proc/iomem, so esp. kexec-tools can properly handle it. Example /proc/iomem before this change: [...] 140000000-333ffffff : virtio0 140000000-147ffffff : System RAM 334000000-533ffffff : virtio1 338000000-33fffffff : System RAM 340000000-347ffffff : System RAM 348000000-34fffffff : System RAM [...] Example /proc/iomem after this change: [...] 140000000-333ffffff : virtio0 140000000-147ffffff : System RAM (virtio_mem) 334000000-533ffffff : virtio1 338000000-33ff...

...ory), and it is exposed as "System RAM > (virtio_mem)" in /proc/iomem, so esp. kexec-tools can properly handle it. > > Example /proc/iomem before this change: > [...] > 140000000-333ffffff : virtio0 > 140000000-147ffffff : System RAM > 334000000-533ffffff : virtio1 > 338000000-33fffffff : System RAM > 340000000-347ffffff : System RAM > 348000000-34fffffff : System RAM > [...] > > Example /proc/iomem after this change: > [...] > 140000000-333ffffff : virtio0 > 140000000-147ffffff : System RAM (virtio_mem) >...

...resource instead, like dax/kmem to avoid the rename: :/# cat /proc/iomem 00000000-00000fff : Reserved [...] 100000000-13fffffff : System RAM 140000000-33fffffff : virtio0 140000000-147ffffff : System RAM 148000000-14fffffff : System RAM 150000000-157ffffff : System RAM 340000000-303fffffff : virtio1 340000000-347ffffff : System RAM 3280000000-32ffffffff : PCI Bus 0000:00 -- Thanks, David / dhildenb

...ase_pages_by_pfn virtio_balloon: do not change memory amount visible via /proc/meminfo Fam Zheng (1): virtio-blk: Allow extended partitions Graeme Gregory (1): virtio_mmio: add ACPI probing Paolo Bonzini (1): virtio-blk: use VIRTIO_BLK_F_WCE and VIRTIO_BLK_F_CONFIG_WCE in virtio1 drivers/block/virtio_blk.c | 6 +++--- drivers/virtio/virtio_balloon.c | 16 ++++++++++------ drivers/virtio/virtio_mmio.c | 10 ++++++++++ 3 files changed, 23 insertions(+), 9 deletions(-)

...ase_pages_by_pfn virtio_balloon: do not change memory amount visible via /proc/meminfo Fam Zheng (1): virtio-blk: Allow extended partitions Graeme Gregory (1): virtio_mmio: add ACPI probing Paolo Bonzini (1): virtio-blk: use VIRTIO_BLK_F_WCE and VIRTIO_BLK_F_CONFIG_WCE in virtio1 drivers/block/virtio_blk.c | 6 +++--- drivers/virtio/virtio_balloon.c | 16 ++++++++++------ drivers/virtio/virtio_mmio.c | 10 ++++++++++ 3 files changed, 23 insertions(+), 9 deletions(-)

...io disk to a CentOS 5.10 guest that runs on a CentOS 6.5 host. The Problem is that while the device shows up under /sys/ the corresponding device node does not: /sys/devices/virtio-pci/virtio0: bus device driver modalias net:eth0 power status subsystem uevent vendor /sys/devices/virtio-pci/virtio1: block:vda bus device driver modalias power serial status subsystem uevent vendor /sys/devices/virtio-pci/virtio2: bus device driver modalias power status subsystem uevent vendor So virtio0 is eth0 and virt1 is vda but virtio2 has no device associated with it. Any ideas why the sys...

...iommu on the command-line now inserts a virtual IOMMU in front of all virtio and vfio devices: $ lkvm run -k Image --console virtio -p console=hvc0 \ --viommu --vfio 0 --vfio 4 --irqchip gicv3-its ... [ 2.998949] virtio_iommu virtio0: probe successful [ 3.007739] virtio_iommu virtio1: probe successful ... [ 3.165023] iommu: Adding device 0000:00:00.0 to group 0 [ 3.536480] iommu: Adding device 10200.virtio to group 1 [ 3.553643] iommu: Adding device 10600.virtio to group 2 [ 3.570687] iommu: Adding device 10800.virtio to group 3 [ 3.627425] iommu: Adding de...

...read+0x150/0x170 > [<0000000000aeab3a>] kernel_thread_starter+0x6/0xc > [<0000000000aeab34>] kernel_thread_starter+0x0/0xc > > [..] > > virtio_ccw 0.0.0301: no vq > ---[ end trace d35815958c12cad3 ]--- > virtio_ccw 0.0.0300: no vq > virtio_blk: probe of virtio1 failed with error -12 > virtio_blk: probe of virtio3 failed with error -12 > > Means virtio devices broken. > > Should I > s/we have a problem if a virtio-ccw device/virtio-ccw devices do not work if the device/ > ? Much better :) (That is, this happens if we switch on the...

...ev.conf to this: udev_log="debug" and regenerate initramfs. Then, we can get more message about this issue. I select some useful messages from /run/initramfs/rdsosreport.txt: systemd-udevd[199] probe /dev/vdb raid offset=8 systemd-udevd[199] no db file to read /run/udev/data/+virtio:virtio1: No such systemd-udevd[199] handling device node '/dev/vdb', devnum=b253:16, mode=0660, systemd-udevd[199] set permissions /dev/vdb, 060660, uid=0, gid=6 systemd-udevd[199] creating symlink '/dev/block/253:16' to '../vdb' systemd-udevd[199] creating link '/dev/d...

...: "virtio0", "locked": false, "removable": false, "inserted": {"ro": false, "drv": "raw", "encrypted": false, "file": "/dev/null"}, "type": "hd"}, {"device": "virtio1", "locked": false, "removable": false, "inserted": {"ro": false, "drv": "qcow2", "backing_file": "/var/tmp/.guestfs-500/root.14807", "encrypted": false, "file": "/tmp/vl.Jv5iLK&quo...

...ts a virtual IOMMU in front > of all virtio and vfio devices: > > $ lkvm run -k Image --console virtio -p console=hvc0 \ > --viommu --vfio 0 --vfio 4 --irqchip gicv3-its > ... > [ 2.998949] virtio_iommu virtio0: probe successful > [ 3.007739] virtio_iommu virtio1: probe successful > ... > [ 3.165023] iommu: Adding device 0000:00:00.0 to group 0 > [ 3.536480] iommu: Adding device 10200.virtio to group 1 > [ 3.553643] iommu: Adding device 10600.virtio to group 2 > [ 3.570687] iommu: Adding device 10800.virtio to group 3 > [...

...ts a virtual IOMMU in front > of all virtio and vfio devices: > > $ lkvm run -k Image --console virtio -p console=hvc0 \ > --viommu --vfio 0 --vfio 4 --irqchip gicv3-its > ... > [ 2.998949] virtio_iommu virtio0: probe successful > [ 3.007739] virtio_iommu virtio1: probe successful > ... > [ 3.165023] iommu: Adding device 0000:00:00.0 to group 0 > [ 3.536480] iommu: Adding device 10200.virtio to group 1 > [ 3.553643] iommu: Adding device 10600.virtio to group 2 > [ 3.570687] iommu: Adding device 10800.virtio to group 3 > [...

...ay that > >> >> > works well for most setups: > >> >> > > >> >> > 1) Find the device name (e.g. vda) below /sys/block > >> >> > > >> >> > 2) Follow the 'device' link to e.g. /sys/devices/virtio-pci/virtio1 > >> >> > > >> >> > 3) Find the module need for this through either 'modalias' or the > >> >> > 'driver/module' symlink > >> >> > > >> >> > 4) Use modprobe to list any dependencies of...

...ay that > >> >> > works well for most setups: > >> >> > > >> >> > 1) Find the device name (e.g. vda) below /sys/block > >> >> > > >> >> > 2) Follow the 'device' link to e.g. /sys/devices/virtio-pci/virtio1 > >> >> > > >> >> > 3) Find the module need for this through either 'modalias' or the > >> >> > 'driver/module' symlink > >> >> > > >> >> > 4) Use modprobe to list any dependencies of...

...ISK_appliance -> ../../sdb lrwxrwxrwx 1 root root 9 Aug 23 06:15 scsi-0QEMU_QEMU_HARDDISK_hd0 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 23 06:15 scsi-0QEMU_QEMU_HARDDISK_hd0-part1 -> ../../sda1 /dev/disk/by-path: total 0 lrwxrwxrwx 1 root root 9 Aug 23 06:15 pci-0000:00:03.0-virtio-pci-virtio1-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 23 06:15 pci-0000:00:03.0-virtio-pci-virtio1-scsi-0:0:0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Aug 23 06:15 pci-0000:00:03.0-virtio-pci-virtio1-scsi-0:0:1:0 -> ../../sdb /dev/disk/by-uuid: total 0 lrwxrwxrwx 1 root root 9 A...

On 29.04.20 18:08, David Hildenbrand wrote: > Some paravirtualized devices that add memory via add_memory() and > friends (esp. virtio-mem) don't want to create entries in > /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware (e.g., e820), but > only