search for: miniport

What is the state of GPLPV and Windows 8? I am currently running tests with Windows 8 and GPLPV rev956 and operations (disk IO, net IO) look good. There seems to be a problem with shutdown/reboot where Windows hangs somewhat and displays a warning about improper shutdown on next reboot. Regards Andreas

''cat /proc/interrupts'' in a Linux PV domain shows interrupts starting at 256 and labelled as ''Dynamic-irq''. Are these available in a HVM domain, eg under Windows? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...verVer which looks like this one: > DriverVer=XX/YY/ZZZZ,62.AA.BBB.CCCCC > > Still no luck - decrease the target OS version to 61 and repeat. > > For WDF drivers like balloon, vioserial, and rng you can go as far as > you can trying to find an appropriate driver. > > For miniport drivers like netkvm ( Yan, please confirm ), viostor and > vioscsi I wouldn't go too far. For example drivers designed to fork in > specific stacks at kernel version 5.1 (WinXP) can refuse working with > kernel 6.2 (Win8). While NDIS miniport designed for NDIS 5.1 (XP) still can run o...

Does anyone know if the ABIOSDSK service in XP would "find" and a HDD image pushed to ram by MEMDISK?? ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

...e rx buffer and multiqueue, etc. > Second, it can reduce many duplicate codes and make it easy to be > maintained. I would like to add that from Windows guest support perspective it makes more sense. To support vsock we most probably need NDIS protocol driver and if it will be binded to NDIS miniport driver (the driver that currently handles virtio-net in Windows) it will make our life much easier. Otherwise we need to ?plug? into NIDS on one hand, and handle transport outside of NDIS on other hand or in some strange way by creating mini port driver that is not really NIC miniport driver. Best...

...CCCCC > > > > > > Still no luck - decrease the target OS version to 61 and repeat. > > > > > > For WDF drivers like balloon, vioserial, and rng you can go as far as > > > you can trying to find an appropriate driver. > > > > > > For miniport drivers like netkvm ( Yan, please confirm ), viostor and > > > vioscsi I wouldn't go too far. For example drivers designed to fork in > > > specific stacks at kernel version 5.1 (WinXP) can refuse working with > > > kernel 6.2 (Win8). > > > > While NDIS m...

...gt; DriverVer=XX/YY/ZZZZ,62.AA.BBB.CCCCC > > > > Still no luck - decrease the target OS version to 61 and repeat. > > > > For WDF drivers like balloon, vioserial, and rng you can go as far as > > you can trying to find an appropriate driver. > > > > For miniport drivers like netkvm ( Yan, please confirm ), viostor and > > vioscsi I wouldn't go too far. For example drivers designed to fork in > > specific stacks at kernel version 5.1 (WinXP) can refuse working with > > kernel 6.2 (Win8). > > While NDIS miniport designed for NDIS...

...-E325-11CE-BFC1-08002BE10318}" ]; - [ current_cs; "Services"; "viostor" ], + [ current_cs; "Services"; driver_name ], [ "Type", REG_DWORD 0x1_l; "Start", REG_DWORD 0x0_l; "Group", REG_SZ "SCSI miniport"; "ErrorControl", REG_DWORD 0x1_l; - "ImagePath", REG_EXPAND_SZ "system32\\drivers\\viostor.sys"; + "ImagePath", REG_EXPAND_SZ ("system32\\drivers\\" ^ driver); "Tag", REG_DWORD 0x21_l ]; - [ cur...

Hi Stefan, Michael, Jason and everyone, Several days ago, I discussed with jason about "Vsock over Virtio-net". This idea has two advantages: First, it can use many great features of virtio-net, like batching, mergeable rx buffer and multiqueue, etc. Second, it can reduce many duplicate codes and make it easy to be maintained. Before the implement, I want to discuss with everyone

Hi Stefan, Michael, Jason and everyone, Several days ago, I discussed with jason about "Vsock over Virtio-net". This idea has two advantages: First, it can use many great features of virtio-net, like batching, mergeable rx buffer and multiqueue, etc. Second, it can reduce many duplicate codes and make it easy to be maintained. Before the implement, I want to discuss with everyone

...table: =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x2 ...00 ff d3 00 a9 49 ...... TAP-Win32 Adapter V9 0x3 ...00 13 20 ab 73 df ...... Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.2.54.1...

The way we patch the Windows registry in order to allow it to boot off a virtio-blk drive was initially conceived by comparing the state with virtio-blk driver properly installed, to that without. However, we don't want to replicate the Windows PnP system; rather we need to apply just enough edits to make the system boot, and then let the Windows PnP manager figure out the rest. This series

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 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. Firs of all you will

...a driver, but the app failed with following information. Would you please tell me the meaning of "..failed. Error code: 0x80070002". Thank you very much! Following is the end part of the error messages. ... CertMgr Succeeded Current full path - C:\windows\temp\~ndtmp~\ndisrd.inf Current miniport full path - C:\windows\temp\~ndtmp~\ndisrd_m.inf Trying to install 'nt_ndisrd'... ...C:\windows\temp\~ndtmp~\ndisrd.inf was copied to C:\windows\inf\oem0.inf ...C:\windows\temp\~ndtmp~\ndisrd_m.inf was copied to C:\windows\inf\oem1.inf fixme:advapi:CheckTokenMembership ((nil) 0x1220c8 0x33f...

...hat windows doesn''t detect that (two access methods to the same block device can''t be a good idea!)... how might I get xen/qemu to turn that off at a given point... by writing something into xenstore? 2. I''m presently planning on writing the vbd driver as a Windows SCSI miniport driver, which means windows would see the vbd driver as a scsi disk. It appears that Xen has a fairly simple idea of single block devices, without the concept of buses and controllers. Windows, however, likes controller buses with devices hanging off them. So I can create one virtual scsi HBA, and...

...ht directory. > > 2) offline-"install" the storage driver and thus enable the guest too > boot > This is not so easy. You can do the same thing that Rich does for v2v an it should work fine. But in some cases, when a guest already has at least one third party storport miniport device driver intalled, the boot can fail > 3) copy over the matching drivers into the guest and allow it to pick > them up on the first boot. It should be pretty the same what v2v does. Some sort of emulation of what "software first" installation procedure does. Cheers, V...

...uot; "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" -[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\viostor] +[HKEY_LOCAL_MACHINE\\SYSTEM\\$current_cs\\Services\\viostor] "Type"=dword:00000001 "Start"=dword:00000000 "Group"="SCSI miniport" @@ -242,27 +247,27 @@ sub _add_viostor_to_registry "ImagePath"="system32\\\\drivers\\\\viostor.sys" "Tag"=dword:00000021 -[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\viostor\Parameters] +[HKEY_LOCAL_MACHINE\\SYSTEM\\$current_cs\\Services\\viostor\\Param...

..._7010 { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): intelide } pci#ven_8086&dev_7111 { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): intelide } [2]: atapi { ErrorControl(REG_DWORD): 00000001 Group(REG_SZ): SCSI miniport Start(REG_DWORD): 00000000 Tag(REG_DWORD): 00000019 Type(REG_DWORD): 00000001 DisplayName(REG_SZ): Standard IDE/ESDI Hard Disk Controller ImagePath(REG_SZ): system32\drivers\atapi.sys } intelide { ErrorControl(REG_DWORD): 00000001 Group(REG_SZ): System Bus Extender...

...710:67d3%12(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.222.0(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : Ethernet adapter Network Bridge: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : MAC Bridge Miniport Physical Address. . . . . . . . . : 02-11-43-AC-52-ED DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::3172:6147:f1fa:f349%15(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.222.12(Preferred) Subnet Mas...

...le with 6.3). So, we are looking for DriverVer which looks like this one: DriverVer=XX/YY/ZZZZ,62.AA.BBB.CCCCC Still no luck - decrease the target OS version to 61 and repeat. For WDF drivers like balloon, vioserial, and rng you can go as far as you can trying to find an appropriate driver. For miniport drivers like netkvm ( Yan, please confirm ), viostor and vioscsi I wouldn't go too far. For example drivers designed to fork in specific stacks at kernel version 5.1 (WinXP) can refuse working with kernel 6.2 (Win8). However, Win10 will be a problem. At least as long as we do not release virti...