Dear Peter Kieser, Thank you very much! Temporarily switching to core2duo did also help in my case. It was also useful to attach a recent windows iso as a virtual CD drive in order to avoid creating more space (otherwise not needed and thus only making backups more problematic) on the main virtual disk. There were no activation issues and no other issues I could find afterwards - except for the usual Microsoft related stuff in order to again reduce the involuntary donations of data as best as possible. Regards, Michael Schefczyk Von: Peter Kieser [mailto:peter@xxxxxxxxx] Gesendet: Sonntag, 14. August 2016 05:26 An: Prof. Dr. Michael Schefczyk <michael@xxxxxxxxxxxxx>; kvm@xxxxxxxxxxxxxxx Betreff: Re: KVM Guest Windows 10 Anniversary Update On 2016-08-13 7:42 PM, Peter Kieser wrote: On 2016-08-08 8:04 AM, Prof. Dr. Michael Schefczyk wrote: The error message shown is "0xC1900101 - 0x20017 The installation failed in the SAFE_OS phase with an error during BOOT operation." Searching for that, one ends up with BIOS issues and problems around wireless and Bluetooth drivers. This is either not applicable for a KVM guest (wireless, Bluetooth) or not really accessible (BIOS). Beyond that, I was not able to detect meaningful errors in the Windows eventviewer. I'm having the same problem. Linux 4.4.0 (Ubuntu xenial), qemu 2.5, the KVM guest is configured pc-q35, virtio-scsi, virtio-net, CPU is host-model (w/ libvirt) all Hyper-V enlightenments are enabled I got the Windows 10 Anniversary Update to apply by setting the CPU to core2duo. I can then switch it back after the update applies, and everything "seems" to work okay. Regards. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
