similar to: [Qemu-devel] Headsup: windows virtio networking does not work on current git

I got a new USB ethernet adapter from ebay, the ad said RealTek chipset, so I thought I would chance it. Well, my 5.2 system does not recognize the USB device. At all. What do I need to do? I checked the driver CD and the XP driver directory's .inf file has the following: ; ASIX AX88172 USB2 to Fast Ethernet Adapter * ; * ; Copyright 2001-2003,

On Thu, Oct 29, 2015 at 10:33:57AM +0200, Yan Vugenfirer wrote: > > On 29 Oct 2015, at 10:28, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: > > > > Seems like looking at this field in the .inf file is better than our > > current approach of matching path names. > > You just need to

https://github.com/rwmjones/libguestfs/tree/rewrite-virtio-copy-drivers Instead of trying to split and parse elements from virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html

Hello guys, I was some years ago when I sent something to this list. NUT is a great tool but lacks SNMP management. It can access a device using SNMP but I found no way to read NUT values using SNMP. It would be very useful in order to integrate with network management software based on SNMP. As I did not find a solution, I wrote it myself. I wrote a MIB file and a SNMP agent for net-snmp

Hello guys, I was some years ago when I sent something to this list. NUT is a great tool but lacks SNMP management. It can access a device using SNMP but I found no way to read NUT values using SNMP. It would be very useful in order to integrate with network management software based on SNMP. As I did not find a solution, I wrote it myself. I wrote a MIB file and a SNMP agent for net-snmp

On Tue, Feb 09, 2016 at 12:20:35AM -0800, Joshua Pincus wrote: > Hi Rich, > > Thanks for the pointer. It looks like add_viostor_to_driver_database() is > the routine that I need to mimic. I'll try that out in the morning. I've > been staring at this problem for so long that my eyes are crossing. I should note that any doubled \\ that appear in the strings are really

Since v1: - Fix a bug in the calculation of lc_basename. By luck this doesn't affect anything given the contents of the current ISO. - Don't copy the WdfCoInstaller*.dll files. Rich.

v2 -> v3 - Don't make a special case for WdfCoInstaller* files. There is a difference of opinion about whether copying these is necessary, but it seems like it is not harmful. Rich.

> On 06 Nov 2015, at 08:51, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: > > On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: >> On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: >>> On Wed, 2015-10-28 at 14:53 +0300, Roman Kagan wrote: >>>> 1) tell which devices can be configured >>> Not sure that I fully understated

Windows QXL drivers include also qxldd.dll which used to get filtered out and not copied over into the guest. As a result QXL driver failed to install due to a missing file. Correct that, and update the tests accordingly. Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- v2v/fake-virtio-win/drivers/i386/Win7/qxldd.dll | 1 + v2v/test-v2v-in-place.sh | 1 +

This series makes several enhancements to tests for v2v conversion of Windows guests. Specifically, it - adds a number of files which imitate the stuff that is supposed to be present on the host when the actual conversion is performed, but may not be there when the tests are run. This includes certain tools and virtio drivers - fixes the test for windows conversion to actually

On Wed, Dec 05, 2018 at 01:18:49PM +0100, Fabien Dupont wrote: > On Wed, Dec 5, 2018 at 12:01 PM Richard W.M. Jones <rjones@redhat.com> > wrote: > > > On Wed, Dec 05, 2018 at 09:01:16AM +0000, Roman Kagan wrote: > > > On Tue, Dec 04, 2018 at 05:29:31PM +0000, Richard W.M. Jones wrote: > > > > This patch is just for discussion. There are still a couple of

On Mon, 2015-11-09 at 18:08 +0300, Roman Kagan wrote: > On Sun, Nov 08, 2015 at 10:15:31AM +0200, Yan Vugenfirer wrote: > > > > > On 06 Nov 2015, at 08:51, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: > > > > > > On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: > > >> On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld

On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: > > 1) tell which devices can be configured > Not sure that I fully understated your question. but if you are going to > create some sort of off-line automatic virtio-win drivers update > utility, then it shouldn't be too complicated. Roman is talking about what virt-v2v already does. This is good information:

On Wed, Dec 05, 2018 at 09:01:16AM +0000, Roman Kagan wrote: > On Tue, Dec 04, 2018 at 05:29:31PM +0000, Richard W.M. Jones wrote: > > This patch is just for discussion. There are still a couple of issues > > that I'm trying to fix. > > Sorry if I missed the original discussion on that, but why is copying > the static IP configuraition even considered to be a good

Some virtio-win drivers contain more files than just *.{cat,inf,sys}. They are filtered out currently, which prevents the drivers from being installed by PnP. Stop filtering driver files by extension, and copy all of them instead. Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- v1 -> v2: - update unit test to match the changed behavior v2v/v2v_unit_tests.ml | 202

Instead of trying to split and parse elements from virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html https://www.redhat.com/archives/libguestfs/2015-November/msg00065.html Currently the product variant (eg.

Patch 1 moves the v2v/fake-virtio-win and v2v/fake-virt-tools directories to the recently created test-data/ hierarchy. This is just refactoring with no functional change at all. Patches 2-4 then extend the available (fake) virtio-win drivers: - Patch 2 adds all of the drivers from the virtio-win RPM. - Patch 3 adds all of the drivers from the virtio-win ISO (which are different from the

On 3/13/23 11:28, Laszlo Ersek wrote: > On 3/9/23 14:48, Richard W.M. Jones wrote: >> On Thu, Mar 09, 2023 at 03:47:10PM +0200, Andrey Drobyshev wrote: >>> On 3/8/23 22:52, Richard W.M. Jones wrote: >>>> On Wed, Mar 08, 2023 at 08:05:35PM +0200, Andrey Drobyshev wrote: >>>>> During conversion we copy the necessary drivers to the directory

In order to test the copying of virtio-win drivers into the guest during v2v, create a set of fake virtio-win drivers and make use of them in the corresponding v2v tests. Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- tests/fake-virtio-win/drivers/i386/Win7/netkvm.cat | 1 + tests/fake-virtio-win/drivers/i386/Win7/netkvm.inf | 1 +