search for: 1af4

...work device 00:04.0 SCSI storage controller: Red Hat, Inc Virtio SCSI 00:05.0 Communication controller: Red Hat, Inc Virtio console 00:06.0 SCSI storage controller: Red Hat, Inc Virtio block device [root at ractorshe ~]# [root at ractorshe ~]# lspci -kn 00:00.0 0600: 8086:1237 (rev 02) Subsystem: 1af4:1100 00:01.0 0601: 8086:7000 Subsystem: 1af4:1100 00:01.1 0101: 8086:7010 Subsystem: 1af4:1100 Kernel driver in use: ata_piix Kernel modules: ata_piix, pata_acpi, ata_generic 00:01.2 0c03: 8086:7020 (rev 01) Subsystem: 1af4:1100 Kernel driver in use: uhci_hcd 00:01.3 0680: 8086:7113 (rev 03) Subsys...

...oller: Red Hat, Inc Virtio SCSI > 00:05.0 Communication controller: Red Hat, Inc Virtio console > 00:06.0 SCSI storage controller: Red Hat, Inc Virtio block device > [root at ractorshe ~]# > > > [root at ractorshe ~]# lspci -kn > 00:00.0 0600: 8086:1237 (rev 02) > Subsystem: 1af4:1100 > 00:01.0 0601: 8086:7000 > Subsystem: 1af4:1100 > 00:01.1 0101: 8086:7010 > Subsystem: 1af4:1100 > Kernel driver in use: ata_piix > Kernel modules: ata_piix, pata_acpi, ata_generic > 00:01.2 0c03: 8086:7020 (rev 01) > Subsystem: 1af4:1100 > Kernel driver in use: uhc...

On 5/5/2017 1:19 ??, Gianluca Cecchi wrote: > Could you verify, if /dev/sda is your boot disk, with the command > > fdisk -l /dev/sda > ? It's /dev/vda in my case: # fdisk -l /dev/vda Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512

Greetings, I have two vms, one is a router and the other one is a client, for some reason, the client vm is unable get ip via dhcp from the router vm. here are outputs: vm1.xml: <interface type='bridge'> <mac address='52:54:00:54:78:be'/> <source bridge='virbr0'/> <model type='virtio'/> <address

...t from 0x000f40a0 to 0x1bfbc6f0 (size 14464) malloc init init ivt init bda Add to e820 map: 0009fc00 00000400 2 init bios32 init PNPBIOS table init keyboard init mouse init pic math cp init PCI probe phys_alloc zone=0x1bfbff38 size=32 align=10 ret=1bfbc640 (detail=0x1bfbc610) PCI device 00:00.0 (vd=1af4:1000 c=0200) phys_alloc zone=0x1bfbff38 size=32 align=10 ret=1bfbc5f0 (detail=0x1bfbc5c0) PCI device 00:01.0 (vd=1af4:1001 c=0180) Found 2 PCI devices (max PCI bus is 00) tsc calibrate start=71959316 end=71968721 diff=9405 CPU Mhz=5 init timer init lpt Found 2 lpt ports init serial Found 4 serial p...

...static int vfio_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id) > return ret; > } > > + if (pdev->vendor == PCI_VENDOR_ID_REDHAT_QUMRANET && Virtio really owns this entire vendor ID block? Apparently nobody told ivshmem: http://pci-ids.ucw.cz/read/PC/1af4/1110 Even the comment by virtio_pci_id_table[] suggests virtio is only a subset even if the code doesn't appear to honor that comment. I don't know the history there, but that seems like really inefficient use of an entire, coveted vendor block. > + ((ret = vfio_pci_virtio_quirk(v...

...static int vfio_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id) > return ret; > } > > + if (pdev->vendor == PCI_VENDOR_ID_REDHAT_QUMRANET && Virtio really owns this entire vendor ID block? Apparently nobody told ivshmem: http://pci-ids.ucw.cz/read/PC/1af4/1110 Even the comment by virtio_pci_id_table[] suggests virtio is only a subset even if the code doesn't appear to honor that comment. I don't know the history there, but that seems like really inefficient use of an entire, coveted vendor block. > + ((ret = vfio_pci_virtio_quirk(v...

...o. If there are going to be implementations of virtio-mmio in future, then they will use whatever identifier we pick here. Either way, we get interoperability. I don't see any difference between our saying "the ID for virtio-mmio is QEMU0005" and saying "the ID for virtio-mmio is 1AF4103F". (The latter seems unnecessarily opaque to me, to be honest. At least an ID string QEMUxxxx gives you a clue where to look for who owns the thing.) Note also that strictly you don't mean "non-QEMU implementations of virtio-mmio", you mean "non-QEMU implementations of...

...o. If there are going to be implementations of virtio-mmio in future, then they will use whatever identifier we pick here. Either way, we get interoperability. I don't see any difference between our saying "the ID for virtio-mmio is QEMU0005" and saying "the ID for virtio-mmio is 1AF4103F". (The latter seems unnecessarily opaque to me, to be honest. At least an ID string QEMUxxxx gives you a clue where to look for who owns the thing.) Note also that strictly you don't mean "non-QEMU implementations of virtio-mmio", you mean "non-QEMU implementations of...

...00 > > [ 1.681068] pci 0000:00:02.0: reg 0x10: [mem 0xfc000000-0xfdffffff pref] > > [ 1.683771] pci 0000:00:02.0: reg 0x14: [mem 0xfebd0000-0xfebd0fff] > > [ 1.694209] pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref] > > [ 1.694644] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000 > > [ 1.696503] pci 0000:00:03.0: reg 0x10: [io 0xc060-0xc07f] > > [ 1.698431] pci 0000:00:03.0: reg 0x14: [mem 0xfebd1000-0xfebd1fff] > > [ 1.707348] pci 0000:00:03.0: reg 0x30: [mem 0xfeb80000-0xfebbffff pref] > > [ 1.707672] pci 0...

...type 00 class 0x030000 > [ 1.681068] pci 0000:00:02.0: reg 0x10: [mem 0xfc000000-0xfdffffff pref] > [ 1.683771] pci 0000:00:02.0: reg 0x14: [mem 0xfebd0000-0xfebd0fff] > [ 1.694209] pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref] > [ 1.694644] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000 > [ 1.696503] pci 0000:00:03.0: reg 0x10: [io 0xc060-0xc07f] > [ 1.698431] pci 0000:00:03.0: reg 0x14: [mem 0xfebd1000-0xfebd1fff] > [ 1.707348] pci 0000:00:03.0: reg 0x30: [mem 0xfeb80000-0xfebbffff pref] > [ 1.707672] pci 0000:00:04.0: [1af4:1...

...type 00 class 0x030000 > [ 1.681068] pci 0000:00:02.0: reg 0x10: [mem 0xfc000000-0xfdffffff pref] > [ 1.683771] pci 0000:00:02.0: reg 0x14: [mem 0xfebd0000-0xfebd0fff] > [ 1.694209] pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref] > [ 1.694644] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000 > [ 1.696503] pci 0000:00:03.0: reg 0x10: [io 0xc060-0xc07f] > [ 1.698431] pci 0000:00:03.0: reg 0x14: [mem 0xfebd1000-0xfebd1fff] > [ 1.707348] pci 0000:00:03.0: reg 0x30: [mem 0xfeb80000-0xfebbffff pref] > [ 1.707672] pci 0000:00:04.0: [1af4:1...

...0:02.0: [1013:00b8] type 00 class 0x030000 [ 6.484400] pci 0000:00:02.0: reg 0x10: [mem 0xfc000000-0xfdffffff pref] [ 6.490365] pci 0000:00:02.0: reg 0x14: [mem 0xfebe0000-0xfebe0fff] [ 6.514432] pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref] [ 6.538244] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000 [ 6.544317] pci 0000:00:03.0: reg 0x10: [io 0xc1c0-0xc1df] [ 6.550273] pci 0000:00:03.0: reg 0x14: [mem 0xfebe1000-0xfebe1fff] [ 6.574010] pci 0000:00:03.0: reg 0x30: [mem 0xfebd0000-0xfebdffff pref] [ 6.601099] pci 0000:00:04.0: [8086:100e] type 00 class 0...

...0:02.0: [1013:00b8] type 00 class 0x030000 [ 6.484400] pci 0000:00:02.0: reg 0x10: [mem 0xfc000000-0xfdffffff pref] [ 6.490365] pci 0000:00:02.0: reg 0x14: [mem 0xfebe0000-0xfebe0fff] [ 6.514432] pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref] [ 6.538244] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000 [ 6.544317] pci 0000:00:03.0: reg 0x10: [io 0xc1c0-0xc1df] [ 6.550273] pci 0000:00:03.0: reg 0x14: [mem 0xfebe1000-0xfebe1fff] [ 6.574010] pci 0000:00:03.0: reg 0x30: [mem 0xfebd0000-0xfebdffff pref] [ 6.601099] pci 0000:00:04.0: [8086:100e] type 00 class 0...

...0:02.0: [1013:00b8] type 00 class 0x030000 [ 0.581088] pci 0000:00:02.0: reg 0x10: [mem 0xfc000000-0xfdffffff pref] [ 0.584014] pci 0000:00:02.0: reg 0x14: [mem 0xfebe4000-0xfebe4fff] [ 0.589993] pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref] [ 0.592041] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000 [ 0.594196] pci 0000:00:03.0: reg 0x10: [io 0xc1c0-0xc1df] [ 0.596005] pci 0000:00:03.0: reg 0x14: [mem 0xfebe5000-0xfebe5fff] [ 0.601724] pci 0000:00:03.0: reg 0x30: [mem 0xfebd0000-0xfebdffff pref] [ 0.603536] pci 0000:00:04.0: [8086:100e] type 00 class 0...

...0:02.0: [1013:00b8] type 00 class 0x030000 [ 0.581088] pci 0000:00:02.0: reg 0x10: [mem 0xfc000000-0xfdffffff pref] [ 0.584014] pci 0000:00:02.0: reg 0x14: [mem 0xfebe4000-0xfebe4fff] [ 0.589993] pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref] [ 0.592041] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000 [ 0.594196] pci 0000:00:03.0: reg 0x10: [io 0xc1c0-0xc1df] [ 0.596005] pci 0000:00:03.0: reg 0x14: [mem 0xfebe5000-0xfebe5fff] [ 0.601724] pci 0000:00:03.0: reg 0x30: [mem 0xfebd0000-0xfebdffff pref] [ 0.603536] pci 0000:00:04.0: [8086:100e] type 00 class 0...

...memory in qemu monitor: > object_add memory-backend-ram,id=mem1,size=256m > device_add virtio-mem-pci,id=vm0,memdev=mem1 > qom-set vm0 requested-size 256M > > // Go back to the terminal and access file system will got following kernel warning. > [ 19.515549] pci 0000:00:04.0: [1af4:1015] type 00 class 0x00ff00 > [ 19.516227] pci 0000:00:04.0: reg 0x10: [io 0x0000-0x007f] > [ 19.517196] pci 0000:00:04.0: BAR 0: assigned [io 0x1000-0x107f] > [ 19.517843] virtio-pci 0000:00:04.0: enabling device (0000 -> 0001) > [ 19.535957] PCI Interrupt Link [LNKD] ena...

...pref] [ 10.497181] pci 0000:00:02.0: reg 14: [mem 0xfebe0000-0xfebe0fff] [ 10.521399] pci 0000:00:02.0: reg 30: [mem 0xfebc0000-0xfebcffff pref] [ 10.524259] device: '0000:00:02.0': device_add [ 10.530638] bus: 'pci': add device 0000:00:02.0 [ 10.542025] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000 [ 10.550293] pci 0000:00:03.0: reg 10: [io 0xc1c0-0xc1df] [ 10.553873] pci 0000:00:03.0: reg 14: [mem 0xfebe1000-0xfebe1fff] [ 10.577069] pci 0000:00:03.0: reg 30: [mem 0xfebd0000-0xfebdffff pref] [ 10.580981] device: '0000:00:03.0': device_add [ 10.5...

...pref] [ 10.497181] pci 0000:00:02.0: reg 14: [mem 0xfebe0000-0xfebe0fff] [ 10.521399] pci 0000:00:02.0: reg 30: [mem 0xfebc0000-0xfebcffff pref] [ 10.524259] device: '0000:00:02.0': device_add [ 10.530638] bus: 'pci': add device 0000:00:02.0 [ 10.542025] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000 [ 10.550293] pci 0000:00:03.0: reg 10: [io 0xc1c0-0xc1df] [ 10.553873] pci 0000:00:03.0: reg 14: [mem 0xfebe1000-0xfebe1fff] [ 10.577069] pci 0000:00:03.0: reg 30: [mem 0xfebd0000-0xfebdffff pref] [ 10.580981] device: '0000:00:03.0': device_add [ 10.5...

...0000:00:02.0: [1013:00b8] type 00 class 0x030000 [ 0.141248] pci 0000:00:02.0: reg 10: [mem 0xfc000000-0xfdffffff pref] [ 0.143352] pci 0000:00:02.0: reg 14: [mem 0xfebf2000-0xfebf2fff] [ 0.155789] pci 0000:00:02.0: reg 30: [mem 0xfebe0000-0xfebeffff pref] [ 0.155975] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000 [ 0.157849] pci 0000:00:03.0: reg 10: [io 0xc160-0xc17f] [ 0.160004] pci 0000:00:03.0: reg 14: [mem 0xfebf3000-0xfebf3fff] [ 0.172317] pci 0000:00:03.0: reg 30: [mem 0xfebc0000-0xfebdffff pref] [ 0.172570] pci 0000:00:04.0: [8086:2922] type 00 class 0x01060...