search for: virio

...work). So do I, and parsing the *.inf files is the last thing I'd like to do here; I'm not sure it can be made reliable (I mean, not the parsing, but making any sense out of the parsed data). However I'm now facing a more serious problem: when I actually went ahead and looked into the virio-win iso packaged in the rhel virtio-win rpm, I found out that its contents differed significantly from what was packaged in that very same rpm as a driver directory hierarchy. Namely, - there are no qxl drivers on the iso, but they are present in the rpm - there are no balloon, qemupciserial...

...path - virtio-net follows the behavior of an active backup bond/team - virtio-net acts as the interface to the VM - live migration initiates - link goes down on SR-IOV, or SR-IOV device is removed - failover to virtio-net as primary path - migration continues to new host - new host is started with virio-net as primary - if no SR-IOV, virtio-net stays primary - hypervisor can hot-add SR-IOV NIC, with same MAC addr as virtio - virtio-net notices new NIC and starts over at enslave step above Future ideas (brainstorming): - Optimize Fast east-west by having special rules to direct east-west traffic...

...path - virtio-net follows the behavior of an active backup bond/team - virtio-net acts as the interface to the VM - live migration initiates - link goes down on SR-IOV, or SR-IOV device is removed - failover to virtio-net as primary path - migration continues to new host - new host is started with virio-net as primary - if no SR-IOV, virtio-net stays primary - hypervisor can hot-add SR-IOV NIC, with same MAC addr as virtio - virtio-net notices new NIC and starts over at enslave step above Future ideas (brainstorming): - Optimize Fast east-west by having special rules to direct east-west traffic...

...uld be solvable without updating (plus the update might not > fix it for you. > Let me try and recap what is happening : On my custom embedded linux, using the same domain config xml, just changing the disk drivers and/or the iso Ubuntu.iso + ide disk drivers -> works Ubuntu.iso + virio disk drivers -> does not work; errors when reading from /dev/vda customLinuxOS.iso + virtio drivers -> does not seem to work; kernel panics and services stop working On Ubuntu10.04 host, using the same domain config xml as before, just changing the iso Ubuntu.iso + virtio disk driv...

...thought I responded, but I didn't do a very good job. > So here we have both a yes and a no :-) > > It would be nice to avoid those if () games all over and indeed just > use the DMA API, *however* we most certainly don't want to actually > create IOMMU mappings for the KVM virio case. This would be a massive > loss in performances on several platforms and generally doesn't make > much sense. > > However, we can still use the API without that on any architecture > where the dma mapping API ends up calling the generic dma_map_ops, > it becomes just a ma...

...thought I responded, but I didn't do a very good job. > So here we have both a yes and a no :-) > > It would be nice to avoid those if () games all over and indeed just > use the DMA API, *however* we most certainly don't want to actually > create IOMMU mappings for the KVM virio case. This would be a massive > loss in performances on several platforms and generally doesn't make > much sense. > > However, we can still use the API without that on any architecture > where the dma mapping API ends up calling the generic dma_map_ops, > it becomes just a ma...

...better to use "userspace" memory here since vhost-vDPA >> could be used by e.g dpdk application on the host in the future. >> > How about replaciing "guest's memory" with "address space". It is more > general and aligns with the with the fact that virio driver can run in > the guest's kernel. Probably but note that guest driver is not the only user for this. It could be either: 1) Guest virtio driver 2) Userspace virtio driver on the host 3) Kernel virtio driver on the host. Thanks >

...d but I have a few comments based on the above "it would be nice if ..." So here we have both a yes and a no :-) It would be nice to avoid those if () games all over and indeed just use the DMA API, *however* we most certainly don't want to actually create IOMMU mappings for the KVM virio case. This would be a massive loss in performances on several platforms and generally doesn't make much sense. However, we can still use the API without that on any architecture where the dma mapping API ends up calling the generic dma_map_ops, it becomes just a matter of virtio setting up som...

...bond/team > > - virtio-net acts as the interface to the VM > > - live migration initiates > > - link goes down on SR-IOV, or SR-IOV device is removed > > - failover to virtio-net as primary path > > - migration continues to new host > > - new host is started with virio-net as primary > > - if no SR-IOV, virtio-net stays primary > > - hypervisor can hot-add SR-IOV NIC, with same MAC addr as virtio > > - virtio-net notices new NIC and starts over at enslave step above > > > > Future ideas (brainstorming): > > - Optimize Fast east...

...bond/team > > - virtio-net acts as the interface to the VM > > - live migration initiates > > - link goes down on SR-IOV, or SR-IOV device is removed > > - failover to virtio-net as primary path > > - migration continues to new host > > - new host is started with virio-net as primary > > - if no SR-IOV, virtio-net stays primary > > - hypervisor can hot-add SR-IOV NIC, with same MAC addr as virtio > > - virtio-net notices new NIC and starts over at enslave step above > > > > Future ideas (brainstorming): > > - Optimize Fast east...

...s://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788432 > > This normally does not cause problems, as these are usually infrequent > operations that happen in a well defined sequence and normally do not > fail. But occasionally sysfs attributes are directly dependent > on pieces of virio config and trigger a get on each read. This gives us > at least one method to trigger races. Yes, the idea behind ccw_io_helper() was to provide a simple way to use the inherently asynchronous channel I/O operations in a synchronous way, as that's what the virtio callbacks expect. I did no...

On (Thu) 11 Oct 2018 [18:15:41], Feng Li wrote: > Add Amit Shah. > > After some tests, we found: > - the virtio serial port number is inversely proportional to the iSCSI > virtio-blk-pci performance. > If we set the virio-serial ports to 2("<controller > type='virtio-serial' index='0' ports='2'/>), the performance downgrade > is minimal. If you use multiple virtio-net (or blk) devices -- just register, not necessarily use -- does that also bring the performance down? I susp...

...gt; wrote: > Currently we have a race on vcdev->config in virtio_ccw_get_config() and > in virtio_ccw_set_config(). > > This normally does not cause problems, as these are usually infrequent > operations. But occasionally sysfs attributes are directly dependent on > pieces of virio config and trigger a get on each read. This gives us at > least one trigger. So, the problem is that you might get unexpected/inconsistent config information? > > Signed-off-by: Halil Pasic <pasic at linux.ibm.com> > --- > drivers/s390/virtio/virtio_ccw.c | 10 ++++++++-- &g...

...s the update might not >> fix it for you. >> > > Let me try and recap what is happening : > On my custom embedded linux, using the same domain config xml, just > changing the disk drivers and/or the iso > Ubuntu.iso + ide disk drivers -> works > Ubuntu.iso + virio disk drivers -> does not work; errors when reading > from /dev/vda > customLinuxOS.iso + virtio drivers -> does not seem to work; kernel > panics and services stop working > > > On Ubuntu10.04 host, using the same domain config xml as before, just > changing the iso &...

...to do > > > here; I'm not sure it can be made reliable (I mean, not the parsing, but > > > making any sense out of the parsed data). > > > > > > However I'm now facing a more serious problem: when I actually went > > > ahead and looked into the virio-win iso packaged in the rhel virtio-win > > > rpm, I found out that its contents differed significantly from what was > > > packaged in that very same rpm as a driver directory hierarchy. > > > > > > Namely, > > > > > > - there are no qxl dr...

...dn't do a very good job. > > > So here we have both a yes and a no :-) > > > > It would be nice to avoid those if () games all over and indeed just > > use the DMA API, *however* we most certainly don't want to actually > > create IOMMU mappings for the KVM virio case. This would be a massive > > loss in performances on several platforms and generally doesn't make > > much sense. > > > > However, we can still use the API without that on any architecture > > where the dma mapping API ends up calling the generic dma_map_ops,...

...vcdev->config in virtio_ccw_get_config() and > >> in virtio_ccw_set_config(). > >> > >> This normally does not cause problems, as these are usually infrequent > >> operations. But occasionally sysfs attributes are directly dependent on > >> pieces of virio config and trigger a get on each read. This gives us at > >> least one trigger. > > > > So, the problem is that you might get unexpected/inconsistent config > > information? > > > >> > >> Signed-off-by: Halil Pasic <pasic at linux.ibm.com&...

...behavior of an active backup bond/team > - virtio-net acts as the interface to the VM > - live migration initiates > - link goes down on SR-IOV, or SR-IOV device is removed > - failover to virtio-net as primary path > - migration continues to new host > - new host is started with virio-net as primary > - if no SR-IOV, virtio-net stays primary > - hypervisor can hot-add SR-IOV NIC, with same MAC addr as virtio > - virtio-net notices new NIC and starts over at enslave step above > > Future ideas (brainstorming): > - Optimize Fast east-west by having special rules...

...face to the VM > > > > - live migration initiates > > > > - link goes down on SR-IOV, or SR-IOV device is removed > > > > - failover to virtio-net as primary path > > > > - migration continues to new host > > > > - new host is started with virio-net as primary > > > > - if no SR-IOV, virtio-net stays primary > > > > - hypervisor can hot-add SR-IOV NIC, with same MAC addr as virtio > > > > - virtio-net notices new NIC and starts over at enslave step above > > > > > > > > Future ide...

...face to the VM > > > > - live migration initiates > > > > - link goes down on SR-IOV, or SR-IOV device is removed > > > > - failover to virtio-net as primary path > > > > - migration continues to new host > > > > - new host is started with virio-net as primary > > > > - if no SR-IOV, virtio-net stays primary > > > > - hypervisor can hot-add SR-IOV NIC, with same MAC addr as virtio > > > > - virtio-net notices new NIC and starts over at enslave step above > > > > > > > > Future ide...