New Question

nano server kvm build fails

asked 2016-07-21 11:45:22 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

I just followed your descriptions on: to set up a kvm based Nano Server image. The build failed with the error "dism /Add-Driver failed for path: $driverPath" with Driver path referring to "D:\Balloon\w10\amd64"

-> this path seems to be hardcoded somewhere, but I don't find where the "D:" comes from. the Ballon is part of a DriverExtension list. -> I don't know what would be the purpose of the Balloon folder and the others in the list. Is it expected to have further files prepared for the build - apart from providing a path to the WindowsServer2016 image? I am using the TP5 image.

Following the repo readme instructions with with the default options produces a valid HyperV image (vhdx): .\NewNanoServerImage.ps1 -IsoPath $isoPath -TargetPath $targetPath -AdministratorPassword $password)

As soon as I add the switch: -Platform "KVM" It fails. See:

The breaking point seems to be:

Installing 1 of 1 - G:\Balloon\w10\amd64\balloon.inf: Error - The driver package contains x64 boot-critical drivers, but the drivers are not properly signed.
Use the /forceunsigned option to install the drivers.

I assume I need to disable the signature check for drivers - It would be good if this would be documented somewhere.

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted

answered 2016-07-21 14:35:49 +0300

avladu gravatar image

updated 2016-07-21 18:47:19 +0300


Please follow the instructions from the repo readme, as those are updated for TP5. Make sure you have Internet connectivity, as the ISO with Fedora virtio drivers for Windows needs to be downloaded.

[edited] The fix has been merged to the main repository.

Thank you,

Adrian Vladu.

edit flag offensive delete link more


I followed the repo instructions. They work fine with the default options (.\NewNanoServerImage.ps1 -IsoPath $isoPath -TargetPath $targetPath -AdministratorPassword $password), but as soon as I add the switch: -Platform "KVM" It fails. See:

volviq gravatar imagevolviq ( 2016-07-21 17:11:10 +0300 )edit

Can you test this version of the code? Let me know if it works for you.

avladu gravatar imageavladu ( 2016-07-21 17:48:09 +0300 )edit

On a Windows 10 environment there were no such issues. From another perspective, did you make some changes to the code?

avladu gravatar imageavladu ( 2016-07-21 17:50:07 +0300 )edit

> Solves the problem! thank you. Please add this as the main answer, because that was the initial problem I assume.

volviq gravatar imagevolviq ( 2016-07-21 18:42:02 +0300 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2016-07-21 11:45:22 +0300

Seen: 139 times

Last updated: Jul 21 '16