search for: yanvugenfirer

...scripts at > >https://github.com/crobinso/virtio-win-pkg-scripts > >and I should be submitting patches or pull requests to it? Yes, that's what I use to package the drivers for RHEL. >Or should the layout be determined only by the build machinery at > >https://github.com/YanVugenfirer/kvm-guest-drivers-windows > >and I should be direct my submissions that way? I don't know, but if you work strictly with virtio-win-pkg-scripts it shouldn't matter. >Or any combination of the above? > >Also does anybody know this is done in SUSE? No idea. >Any help wo...

...gt;> >>> and I should be submitting patches or pull requests to it? >> >> Yes, that's what I use to package the drivers for RHEL. >> >> >>> Or should the layout be determined only by the build machinery at >>> >>> https://github.com/YanVugenfirer/kvm-guest-drivers-windows >>> >>> and I should be direct my submissions that way? >> >> I don't know, but if you work strictly with virtio-win-pkg-scripts it >> shouldn't matter. > > Thanks a lot, I'll look into it early next week. > Sorry...

On Mon, Nov 23, 2015 at 08:26:10PM +0300, Roman Kagan wrote: > On Thu, Nov 19, 2015 at 09:45:36PM +0300, Roman Kagan wrote: > > On Wed, Nov 18, 2015 at 11:31:17PM -0500, Li Jin wrote: > > > > > > In any case the *.inf files don't seem to have any distinguishing > > > > > > feature which would allow us to check this. > > > > Catalog files

...so/virtio-win-pkg-scripts > > > >and I should be submitting patches or pull requests to it? > > Yes, that's what I use to package the drivers for RHEL. > > > >Or should the layout be determined only by the build machinery at > > > >https://github.com/YanVugenfirer/kvm-guest-drivers-windows > > > >and I should be direct my submissions that way? > > I don't know, but if you work strictly with virtio-win-pkg-scripts it > shouldn't matter. Thanks a lot, I'll look into it early next week. I guess there's no mailing list, so...

...stats: SWAP_IN 0 /* Amount of memory swapped in */ SWAP_OUT 1 /* Amount of memory swapped out */ MAJFLT 2 /* Number of major faults */ MINFLT 3 /* Number of minor faults */ MEMFREE 4 /* Total amount of free memory */ MEMTOT 5 /* Total amount of memory */ See https://github.com/YanVugenfirer/kvm-guest-drivers-windows/blob/9a5cb6749d68bad8c346d31b811c854ab078652e/Balloon/sys/public.h IFAIR, these should be queried by the virDomainMemoryStats function. Claudio -- BSc (Comp) Claudio Bley - Principal Software Engineer AV-TEST GmbH, Klewitzstr. 7, 39112 Magdeburg, Germany Phone: +49 391...

From: Anthony Liguori <aliguori at amazon.com> See https://issues.oasis-open.org/browse/VIRTIO-16 although it was prematurely closed. Red Hat has non-redistributable Windows drivers and Microsoft will not allow anyone else to WHQL certify drivers using that vendor ID. That makes it impossible to use virtio drivers with a Windows guest without changing the vendor ID. Cc: Matt Wilson

From: Anthony Liguori <aliguori at amazon.com> See https://issues.oasis-open.org/browse/VIRTIO-16 although it was prematurely closed. Red Hat has non-redistributable Windows drivers and Microsoft will not allow anyone else to WHQL certify drivers using that vendor ID. That makes it impossible to use virtio drivers with a Windows guest without changing the vendor ID. Cc: Matt Wilson

...o I get it right that the way virtio-win is packaged for Fedora and RHEL is driven by the scripts at https://github.com/crobinso/virtio-win-pkg-scripts and I should be submitting patches or pull requests to it? Or should the layout be determined only by the build machinery at https://github.com/YanVugenfirer/kvm-guest-drivers-windows and I should be direct my submissions that way? Or any combination of the above? Also does anybody know this is done in SUSE? Any help would be appreciated. Thanks, Roman.

...ote: " I think anyone can use a different subsystem vendor id and whql the driver. virtio-102 will make this even easier, by making the subsystem id flexible. Let's close this and re-open if someone tries to do this and runs into a problem. " Look here for example: https://github.com/YanVugenfirer/kvm-guest-drivers-windows/blob/master/NetKVM/NDIS5/wxp/netkvm.inf Replace SUBSYS_00011AF4 with SUBSYS_00011D0F, and you will get a virtio-net driver that (I think) you should be able to WHQL. On the host side, you will need a QEMU patch to allow libvirt control of the subsystem vendor ID. All thi...

...n use a different subsystem vendor id and whql the > driver. virtio-102 will make this even easier, by making the subsystem > id flexible. Let's close this and re-open if someone tries to do this > and runs into a problem. " > > Look here for example: > https://github.com/YanVugenfirer/kvm-guest-drivers-windows/blob/master/NetKVM/NDIS5/wxp/netkvm.inf > Replace SUBSYS_00011AF4 with SUBSYS_00011D0F, and you will get > a virtio-net driver that (I think) you should be able to WHQL. The string you are referencing is the device description which is part of what forms the device...

...n use a different subsystem vendor id and whql the > driver. virtio-102 will make this even easier, by making the subsystem > id flexible. Let's close this and re-open if someone tries to do this > and runs into a problem. " > > Look here for example: > https://github.com/YanVugenfirer/kvm-guest-drivers-windows/blob/master/NetKVM/NDIS5/wxp/netkvm.inf > Replace SUBSYS_00011AF4 with SUBSYS_00011D0F, and you will get > a virtio-net driver that (I think) you should be able to WHQL. The string you are referencing is the device description which is part of what forms the device...

Hello, I'm trying to get memory usage statistic inside a guest machine using virDomainMemoryStats function at libvirt. According to http://libvirt.org/html/libvirt-libvirt.html#virDomainMemoryStatTags the structure could have a lot of useful memory statistic but the amount of parameters depends on the hypervisor and the driver. However using KVM I'm able to get

...ndor id and whql the > > driver. virtio-102 will make this even easier, by making the subsystem > > id flexible. Let's close this and re-open if someone tries to do this > > and runs into a problem. " > > > > Look here for example: > > https://github.com/YanVugenfirer/kvm-guest-drivers-windows/blob/master/NetKVM/NDIS5/wxp/netkvm.inf > > Replace SUBSYS_00011AF4 with SUBSYS_00011D0F, and you will get > > a virtio-net driver that (I think) you should be able to WHQL. > > The string you are referencing is the device description which is part >...