search for: virtio2

...he 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 system doesn't pick up the device all the way? Regards, Dennis

...10 19:42 affinity_hint -r--r--r-- 1 root root 0 Aug 10 19:42 node dr-xr-xr-x 2 root root 0 Aug 10 19:42 qxl -rw-r--r-- 1 root root 0 Aug 10 19:42 smp_affinity -rw-r--r-- 1 root root 0 Aug 10 19:42 smp_affinity_list -r--r--r-- 1 root root 0 Aug 10 19:42 spurious dr-xr-xr-x 2 root root 0 Aug 10 19:42 virtio2 $ ls -lA /proc/irq/21/qxl total 0 $ ls -lA /proc/irq/21/virtio2 total 0 ===== {{{ on host, everything else is on guest }}} virsh # managedsave <vmname> Domain servo state saved by libvirt virsh # start <vmname> Domain <vmname> started ===== [ 1117.083236] irq 21: nobody cared (t...

...TIF_F_GRO_HW feature bit as otherwise an attempt will be made to > program the virtio-net device using the ctrl queue which will fail. > > This resolves the following error when running on kvmtool: > > [ 1.865992] net eth0: Fail to set guest offload. > [ 1.872491] virtio_net virtio2 eth0: set_features() failed (-22); wanted 0x0000000000134829, left 0x0080000000134829 > > Signed-off-by: Rob Bradford <rbradford at rivosinc.com> > --- > Changes in v2: > - Use parentheses to group logical OR of features > - Link to v1: > https://lore.kernel.org/r/20230...

...#39;disk'> <driver name='qemu'/> <source dev='/dev/disk/by-path/ip-10.10.0.1:3260-iscsi-iqn.2001-05.com.equallogic:0-8a0906-4992c7f05-39c000000114b8fc-vglog-lun-0'/> <target dev='vdc' bus='virtio'/> <alias name='virtio2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> When I start VM, iscsi target is availaible. The snag is that when I reboot the host, the pool is not automatically started (making it imposs...

...F_F_GRO_HW feature bit as otherwise an attempt will be made to > program the virtio-net device using the ctrl queue which will fail. > > This resolves the following error when running on kvmtool: > > [ 1.865992] net eth0: Fail to set guest offload. > [ 1.872491] virtio_net virtio2 eth0: set_features() failed (-22); wanted 0x0000000000134829, left 0x0080000000134829 > > Signed-off-by: Rob Bradford <rbradford at rivosinc.com> > --- > Changes in v2: > - Use parentheses to group logical OR of features > - Link to v1: > https://lore.kernel.org/r/202...

...bcore: registered new device driver usb [ 0.829766] SCSI subsystem initialized [ 0.830240] input: VirtualPS/2 VMware VMMouse as /devices/platform/i8042/serio1/input/input3 [ 0.830430] input: VirtualPS/2 VMware VMMouse as /devices/platform/i8042/serio1/input/input2 [ 0.844882] virtio_blk virtio2: [vda] 41943040 512-byte logical blocks (21.5 GB/20.0 GiB) [ 0.854231] vda: vda1 vda2 [ 0.857633] xhci_hcd 0000:02:00.0: xHCI Host Controller [ 0.857638] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 1 [ 0.857900] xhci_hcd 0000:02:00.0: hcc params 0x00087001 hci ve...

...f24d153884439dad30484a0e3f02350692e4c > Author: Jason Wang <jasowang at redhat.com> > Date: Tue Aug 17 16:06:59 2021 +0800 > > virtio-net: use NETIF_F_GRO_HW instead of NETIF_F_LRO > > [ 1.865992] net eth0: Fail to set guest offload. > [ 1.872491] virtio_net virtio2 eth0: set_features() failed (-22); wanted 0x0000000000134829, left 0x0080000000134829 > > This is because during the probing the underlying netdev device has > identified that the netdev features on the device has changed and > attempts to update the virtio-net offloads through the vir...

...-t logfs /dev/vda /sysroot/ [ 107.679255] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 [ 107.680173] IP: [<ffffffff81238127>] __list_add+0x16/0x83 [ 107.680173] PGD 0 [ 107.680173] Oops: 0000 [#1] SMP [ 107.680173] last sysfs file: /sys/devices/virtio-pci/virtio2/block/vdb/queue/rotational [ 107.680173] CPU 0 [ 107.680173] Modules linked in: nls_utf8 hfsplus hfs vfat fat logfs zlib_deflate i2c_piix4 i2c_core virtio_blk virtio_net virtio_console virtio_rng virtio_balloon virtio_pci sym53c8xx virtio_ring virtio scsi_transport_spi libcrc32c ext2 crc7 crc_it...

PCI, lguest and s390 can all only support 256-byte configuration space. So, this giant field broke just about everyone. Unfortunately, removing it is not so simple: we don't want to break old userspace, but we're going to want to re-use that part of the struct. So, modern users can #define VIRTIO_BLK_IDENTIFY_DEPRECATED to indicate that they know it's no longer in the config struct,

PCI, lguest and s390 can all only support 256-byte configuration space. So, this giant field broke just about everyone. Unfortunately, removing it is not so simple: we don't want to break old userspace, but we're going to want to re-use that part of the struct. So, modern users can #define VIRTIO_BLK_IDENTIFY_DEPRECATED to indicate that they know it's no longer in the config struct,

...r /dev/disk: total 0 drwxr-xr-x 2 root root 80 Nov 22 12:04 by-path drwxr-xr-x 2 root root 60 Nov 22 12:04 by-uuid /dev/disk/by-path: total 0 lrwxrwxrwx 1 root root 9 Nov 22 12:04 pci-0000:00:03.0-virtio-pci-virtio1 -> ../../vda lrwxrwxrwx 1 root root 9 Nov 22 12:04 pci-0000:00:04.0-virtio-pci-virtio2 -> ../../vdb /dev/disk/by-uuid: total 0 lrwxrwxrwx 1 root root 9 Nov 22 12:04 77215008-5380-4417-a972-7f7090ad4429 -> ../../vdb /dev/hugepages: total 0 /dev/input: total 0 drwxr-xr-x 2 root root 100 Nov 22 12:04 by-path crw-r----- 1 root root 13, 64 Nov 22 12:04 event0 crw-r----- 1 root...

Unfortunately, placing the link into the /boot does not work. libguestfs-test-tool failes with the same message: ************************************************************ * IMPORTANT NOTICE * * When reporting bugs, include the COMPLETE, UNEDITED * output below in your bug report. *

On Sun, Mar 23, 2014 at 12:26:28PM +0000, Richard W.M. Jones wrote: > Secondly, we should be able to inspect all Linux guests, including > Tiny Core Linux, but it looks like in this case it is failing. This > is a bug. I had a look at how the Tiny Core Linux ISO is arranged. It loads the main operating system root partition as a single large initramfs, with optional modules loaded

...ce 0000:00:06.0 with driver virtio-pci [ 266.858914] bus: 'pci': really_probe: probing driver virtio-pci with device 0000:00:06.0 [ 267.109167] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 [ 267.124508] virtio-pci 0000:00:06.0: setting latency timer to 64 [ 267.126302] device: 'virtio2': device_add [ 267.133174] bus: 'virtio': add device virtio2 [ 267.149833] driver: '0000:00:06.0': driver_bound: bound to device 'virtio-pci' [ 267.159363] bus: 'pci': really_probe: bound device 0000:00:06.0 to driver virtio-pci [ 267.178006] bus: 'pci...

...ce 0000:00:06.0 with driver virtio-pci [ 266.858914] bus: 'pci': really_probe: probing driver virtio-pci with device 0000:00:06.0 [ 267.109167] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 [ 267.124508] virtio-pci 0000:00:06.0: setting latency timer to 64 [ 267.126302] device: 'virtio2': device_add [ 267.133174] bus: 'virtio': add device virtio2 [ 267.149833] driver: '0000:00:06.0': driver_bound: bound to device 'virtio-pci' [ 267.159363] bus: 'pci': really_probe: bound device 0000:00:06.0 to driver virtio-pci [ 267.178006] bus: 'pci...