On Tue, 2017-07-11 at 18:08 -0400, Sam Varshavchik wrote: > Patrick O'Callaghan writes: > > > On Tue, 2017-07-11 at 13:21 -0400, Sam Varshavchik wrote: > > > Upgraded F25 that had a Win10 guest VM to F26. > > > > > > When the VM got started, the initial logo and the spinning circle came up, > > > but then the display cleared to what appears to be the VGA 648x480 > > > resolution, with gray vertical lines and something else. > > > > > > After a few minutes of this I force-rebooted the VM. Windows 10 went into > > > "Automatic Repair", then gave up, reporting some corrupted file. It didn't > > > find any restore points either. > > > > > > So, I'm now reinstalling it from a recovery disk. I have no idea if the > > > restored image will come up… > > > > Anything further on this? I expect to update to F26 tomorrow and also > > have a Win10 VM under QEMU/KVM. I'll backup the VM (from Windows) and > > probably take a QCOW snapshot of the virtual disk just in case, but I'd > > be interested to know if: > > > > * You're running X11 or Wayland > > * Your virtual display is QXL, passthrough of a second GPU, or > > something else > > * You use VNC or Spice > > QXL, X11, Spice. > > I was able to reinstall Windows 10 on the same VM, and isolated one clue. A > VM-initiated reboot always fails, goes into "Preparing Automatic Repair", > then bluescreens and tells me that something is corrupted (I forget the > details), and there are no available restore points. > > But this is a bald-faced lie. But if I force off, and boot again, Windows 10 > comes up like there's nothing wrong. Normal boot. Just tried it and it worked perfectly. Did you shut down your Windows VM before the upgrade? > This continued to happen after a fresh Windows 10 install. If I initiate a > reboot from the Start menu, I don't even see the bios screen flash by. The > stupid thing immediately lands into "Preparing Automatic Repair". But a full > shutdown and a boot is fine. > > In hindsight, post-upgrade, my VM was probably ok, but it led me to believe > that it was bricked, leading me to wipe everything and reinstall. It was > very convincing. I am not amused. What you describe sounds very similar to something I saw a couple of months ago while playing with device configurations under libvirt- manager. I got the BSOD several times and resorted to a reinstall, but on reflection I think the problem was due to a lack of drivers in Windows (virtio-scsi or something, I forget) and the fact that I hadn't mounted a pseudo-ISO driver CD when trying to boot it. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
