I am not sure what I have done, but I now cannot create any VM's on my 6.2 build.

 

Keep getting the following error and have no idea where to start.

 

Search found some errors but they didn't seem to apply in my scenario.

 

VM creation error

 

Hook script execution failed: internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' prepare begin -) unexpected exit status 255

!

 

Not valid!

 

Edit: Looking through the log, it doesn't appear that anything was logged for this error. There is something in the libvert log?

 

2016-09-17 17:55:20.670+0000: 6785: error : virCommandWait:2553 : internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' release end -) unexpected exit status 255

2016-09-17 17:55:20.670+0000: 6785: error : virHookCall:304 : Hook script execution failed: internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' release end -) unexpected exit status 255

2016-09-17 17:56:09.227+0000: 6782: error : virCommandWait:2553 : internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' prepare begin -) unexpected exit status 255

2016-09-17 17:56:09.227+0000: 6782: error : virHookCall:304 : Hook script execution failed: internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' prepare begin -) unexpected exit status 255

2016-09-17 17:56:09.249+0000: 6782: error : virCommandWait:2553 : internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' stopped end -) unexpected exit status 255

2016-09-17 17:56:09.249+0000: 6782: error : virHookCall:304 : Hook script execution failed: internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' stopped end -) unexpected exit status 255

2016-09-17 17:56:09.270+0000: 6782: error : virCommandWait:2553 : internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' release end -) unexpected exit status 255

2016-09-17 17:56:09.270+0000: 6782: error : virHookCall:304 : Hook script execution failed: internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' release end -) unexpected exit status 255

2016-09-17 17:58:48.176+0000: 6784: error : virCommandWait:2553 : internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' prepare begin -) unexpected exit status 255

2016-09-17 17:58:48.176+0000: 6784: error : virHookCall:304 : Hook script execution failed: internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' prepare begin -) unexpected exit status 255

2016-09-17 17:58:48.199+0000: 6784: error : virCommandWait:2553 : internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' stopped end -) unexpected exit status 255

2016-09-17 17:58:48.199+0000: 6784: error : virHookCall:304 : Hook script execution failed: internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' stopped end -) unexpected exit status 255

2016-09-17 17:58:48.221+0000: 6784: error : virCommandWait:2553 : internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' release end -) unexpected exit status 255

2016-09-17 17:58:48.221+0000: 6784: error : virHookCall:304 : Hook script execution failed: internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'Windows 10' release end -) unexpected exit status 255

 

Link to diagnostics dump ->

 

Is there a way to reset KVM to its original state for a clean install, without affecting the rest of the config please?

I am having this exact issue with the latest unraid.

 

Did you manage to get this fixed? I noticed that you received zero support for it which is disappointing...

bump for someone else having this problem.