Comments

• Rebecca_Cran Member - All Emails Posts: 6

  February 2018

  On 2/13/2018 6:22 PM, [email protected] wrote:
  > Alternatively, if anyone has tips for using VMs that would help, but
  > my issue was I could never deploy properly - my host is Linux, and
  > nested KVM is broken on my hardware so I can not run VirtualBox inside
  > my development machine. I tried to deploy over network to the VM, but
  > was never able to get it working.
  
  What sort of driver are you developing? If it's for a PCIe device, you
  should be able to use KVM with PCIe passthrough given a machine from
  2012 onwards. If you can dedicate a machine to it, I'd suggest trying
  Proxmox VE (https://pve.proxmox.com/wiki/Main_Page) since it's already
  setup for running VMs. Alternatively, you should be able to boot pretty
  much any Linux system with the kernel parameter "intel_iommu=on", then
  configure passthrough for the IOMMU group that contains the device you
  want, via entries in /proc . Then, run qemu and you should have access
  to the device within Windows within the VM.
  
  --
  Rebecca

  0 · Share on Facebook
• Formerly_R0b0t1 Unsubscribed Member Posts: 131

  February 2018

  On Tue, Feb 13, 2018 at 11:15 PM, [email protected]
  <[email protected]> wrote:
  > On 2/13/2018 6:22 PM, [email protected] wrote:
  >>
  >> Alternatively, if anyone has tips for using VMs that would help, but
  >> my issue was I could never deploy properly - my host is Linux, and
  >> nested KVM is broken on my hardware so I can not run VirtualBox inside
  >> my development machine. I tried to deploy over network to the VM, but
  >> was never able to get it working.
  >
  >
  > What sort of driver are you developing? If it's for a PCIe device, you
  > should be able to use KVM with PCIe passthrough given a machine from 2012
  > onwards. If you can dedicate a machine to it, I'd suggest trying Proxmox VE
  > (https://pve.proxmox.com/wiki/Main_Page) since it's already setup for
  > running VMs. Alternatively, you should be able to boot pretty much any Linux
  > system with the kernel parameter "intel_iommu=on", then configure
  > passthrough for the IOMMU group that contains the device you want, via
  > entries in /proc . Then, run qemu and you should have access to the device
  > within Windows within the VM.
  >
  
  Currently a different keyboard transport protocol over USB (prototyped
  with libusb and userspace calls). PCIe is pretty far down on the list
  at the moment. I've gotten PCIe passthrough working, the problem is my
  hardware does not support nested KVM, so I am not able to follow the
  guides that use VirtualBox test targets.
  
  My question could also be interpreted as "does anyone have a known
  working test configuration?" Despite all my attempts, I can't get
  automated deployment with the WDK working, and have been doing things
  by hand. This is less than ideal.
  
  Thanks,
  R0b0t1

  0 · Share on Facebook
• Don_Burn Member - All Emails Posts: 1,760

  February 2018

  The deployment stuff in the WDK has never worked reliably. Most experienced driver developers would never use it, instead install the first time and use .kdfiles in Windbg to update the driver.
  
  
  Don Burn
  Windows Driver Consulting
  Website: http://www.windrvr.com
  
  
  
  -----Original Message-----
  From: [email protected] [mailto:[email protected]] On Behalf Of [email protected]
  Sent: Wednesday, February 14, 2018 1:56 AM
  To: Windows System Software Devs Interest List <[email protected]>
  Subject: Re: [ntdev] Driver Prototyping Hardware
  
  On Tue, Feb 13, 2018 at 11:15 PM, [email protected] <[email protected]> wrote:
  > On 2/13/2018 6:22 PM, [email protected]mail.com wrote:
  >>
  >> Alternatively, if anyone has tips for using VMs that would help, but
  >> my issue was I could never deploy properly - my host is Linux, and
  >> nested KVM is broken on my hardware so I can not run VirtualBox
  >> inside my development machine. I tried to deploy over network to the
  >> VM, but was never able to get it working.
  >
  >
  > What sort of driver are you developing? If it's for a PCIe device, you
  > should be able to use KVM with PCIe passthrough given a machine from
  > 2012 onwards. If you can dedicate a machine to it, I'd suggest trying
  > Proxmox VE
  > (https://pve.proxmox.com/wiki/Main_Page) since it's already setup for
  > running VMs. Alternatively, you should be able to boot pretty much any
  > Linux system with the kernel parameter "intel_iommu=on", then
  > configure passthrough for the IOMMU group that contains the device you
  > want, via entries in /proc . Then, run qemu and you should have access
  > to the device within Windows within the VM.
  >
  
  Currently a different keyboard transport protocol over USB (prototyped with libusb and userspace calls). PCIe is pretty far down on the list at the moment. I've gotten PCIe passthrough working, the problem is my hardware does not support nested KVM, so I am not able to follow the guides that use VirtualBox test targets.
  
  My question could also be interpreted as "does anyone have a known working test configuration?" Despite all my attempts, I can't get automated deployment with the WDK working, and have been doing things by hand. This is less than ideal.
  
  Thanks,
  R0b0t1
  
  ---
  NTDEV is sponsored by OSR
  
  Visit the list online at: <http://www.osronline.com/showlists.cfm?list=ntdev&gt;
  
  MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
  Details at <http://www.osr.com/seminars&gt;
  
  To unsubscribe, visit the List Server section of OSR Online at <http://www.osronline.com/page.cfm?name=ListServer&gt;

  0 · Share on Facebook
• Pavel_A Member Posts: 2,819

  February 2018

  > It may not be possible for me to dedicate a full x86_64 system to development.
  
  Just get a new hard drive or SSD, swap it in some real machine. Disks are cheap now.
  
  -- pa

  0 · Share on Facebook