All of lore.kernel.org
 help / color / mirror / Atom feed
* [Qemu-devel] [Bug 1487264] [NEW] Windows 8.1/10 Crashes during upgrade - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
@ 2015-08-21  2:22 ShawnStarr
  2018-08-14 16:05 ` [Qemu-devel] [Bug 1487264] " Thomas Huth
  2018-10-14  4:17 ` Launchpad Bug Tracker
  0 siblings, 2 replies; 3+ messages in thread
From: ShawnStarr @ 2015-08-21  2:22 UTC (permalink / raw)
  To: qemu-devel

Public bug reported:

Ever since Windows 8.x, 10 I cannot upgrade or upgrade to tech builds
within Windows 10 without hard shutting off the VM.

Physical hardware: Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz [Haswell]

QEMU 2.1-2.3.x seem all broken, I am using Q35 chipset w/ BIOS mode.

Launch command via virt-manager/libvirt launch:

QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name Windows_10 -S -machine
pc-q35-2.3,accel=kvm,usb=off -cpu Haswell-
noTSX,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -realtime
mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid ed7e372b-
ebf9-4feb-a305-869f82e6aaee -no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows_10.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard
-no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global
PIIX4_PM.disable_s4=1 -boot menu=off,strict=on -device
i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-
bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-
ehci1,id=usb,bus=pci.2,addr=0x3.0x7 -device ich9-usb-
uhci1,masterbus=usb.0,firstport=0,bus=pci.2,multifunction=on,addr=0x3
-device ich9-usb-
uhci2,masterbus=usb.0,firstport=2,bus=pci.2,addr=0x3.0x1 -device ich9
-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.2,addr=0x3.0x2 -device
virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x4 -drive
file=/var/lib/libvirt/images/Windows_10.qcow2,if=none,id=drive-
sata0-0-0,format=qcow2 -device ide-hd,bus=ide.0,drive=drive-
sata0-0-0,id=sata0-0-0,bootindex=1 -drive file=/usr/share/virtio-win
/virtio-win-0.1.109.iso,if=none,media=cdrom,id=drive-
sata0-0-1,readonly=on,format=raw -device ide-cd,bus=ide.1,drive=drive-
sata0-0-1,id=sata0-0-1 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23
-device virtio-net-
pci,netdev=hostnet0,id=net0,mac=52:54:00:54:14:20,bus=pci.2,addr=0x1
-chardev pty,id=charserial0 -device isa-
serial,chardev=charserial0,id=serial0 -chardev
spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-
serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
-device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-
ticketing,image-compression=off,seamless-migration=on -device qxl-
vga,id=video0,ram_size=268435456,vram_size=268435456,vgamem_mb=256,bus=pcie.0,addr=0x1
-device ich9-intel-hda,id=sound0,bus=pci.2,addr=0x2 -device hda-
duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device usb-
host,hostbus=1,hostaddr=2,id=hostdev0 -device virtio-balloon-
pci,id=balloon0,bus=pci.2,addr=0x5 -msg timestamp=on

The workaround I've been able to come up with is to set boot menu in
virt-manager, then put in a bootable CD so I have enough time to hard
power off the QEMU/KVM instance, when I power it back on, it continues
upgrade/install without issue, each time it needs to restart however I
go though same exercise.

Anything known about this issue? The workaround is a kludge, but it does
get it to upgrade/install Windows 8.1, and upgrade between Windows 10 X
builds.

Thanks,
Shawn

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1487264

Title:
  Windows 8.1/10 Crashes during upgrade -
  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Status in QEMU:
  New

Bug description:
  Ever since Windows 8.x, 10 I cannot upgrade or upgrade to tech builds
  within Windows 10 without hard shutting off the VM.

  Physical hardware: Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz [Haswell]

  QEMU 2.1-2.3.x seem all broken, I am using Q35 chipset w/ BIOS mode.

  Launch command via virt-manager/libvirt launch:

  QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name Windows_10 -S -machine
  pc-q35-2.3,accel=kvm,usb=off -cpu Haswell-
  noTSX,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096
  -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid ed7e372b-
  ebf9-4feb-a305-869f82e6aaee -no-user-config -nodefaults -chardev
  socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows_10.monitor,server,nowait
  -mon chardev=charmonitor,id=monitor,mode=control -rtc
  base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard
  -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global
  PIIX4_PM.disable_s4=1 -boot menu=off,strict=on -device
  i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-
  bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-
  ehci1,id=usb,bus=pci.2,addr=0x3.0x7 -device ich9-usb-
  uhci1,masterbus=usb.0,firstport=0,bus=pci.2,multifunction=on,addr=0x3
  -device ich9-usb-
  uhci2,masterbus=usb.0,firstport=2,bus=pci.2,addr=0x3.0x1 -device ich9
  -usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.2,addr=0x3.0x2 -device
  virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x4 -drive
  file=/var/lib/libvirt/images/Windows_10.qcow2,if=none,id=drive-
  sata0-0-0,format=qcow2 -device ide-hd,bus=ide.0,drive=drive-
  sata0-0-0,id=sata0-0-0,bootindex=1 -drive file=/usr/share/virtio-win
  /virtio-win-0.1.109.iso,if=none,media=cdrom,id=drive-
  sata0-0-1,readonly=on,format=raw -device ide-cd,bus=ide.1,drive=drive-
  sata0-0-1,id=sata0-0-1 -netdev
  tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=52:54:00:54:14:20,bus=pci.2,addr=0x1
  -chardev pty,id=charserial0 -device isa-
  serial,chardev=charserial0,id=serial0 -chardev
  spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus
  =virtio-
  serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
  -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-
  ticketing,image-compression=off,seamless-migration=on -device qxl-
  vga,id=video0,ram_size=268435456,vram_size=268435456,vgamem_mb=256,bus=pcie.0,addr=0x1
  -device ich9-intel-hda,id=sound0,bus=pci.2,addr=0x2 -device hda-
  duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device usb-
  host,hostbus=1,hostaddr=2,id=hostdev0 -device virtio-balloon-
  pci,id=balloon0,bus=pci.2,addr=0x5 -msg timestamp=on

  The workaround I've been able to come up with is to set boot menu in
  virt-manager, then put in a bootable CD so I have enough time to hard
  power off the QEMU/KVM instance, when I power it back on, it continues
  upgrade/install without issue, each time it needs to restart however I
  go though same exercise.

  Anything known about this issue? The workaround is a kludge, but it
  does get it to upgrade/install Windows 8.1, and upgrade between
  Windows 10 X builds.

  Thanks,
  Shawn

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1487264/+subscriptions

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Qemu-devel] [Bug 1487264] Re: Windows 8.1/10 Crashes during upgrade - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  2015-08-21  2:22 [Qemu-devel] [Bug 1487264] [NEW] Windows 8.1/10 Crashes during upgrade - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED ShawnStarr
@ 2018-08-14 16:05 ` Thomas Huth
  2018-10-14  4:17 ` Launchpad Bug Tracker
  1 sibling, 0 replies; 3+ messages in thread
From: Thomas Huth @ 2018-08-14 16:05 UTC (permalink / raw)
  To: qemu-devel

Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?

** Changed in: qemu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1487264

Title:
  Windows 8.1/10 Crashes during upgrade -
  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Status in QEMU:
  Incomplete

Bug description:
  Ever since Windows 8.x, 10 I cannot upgrade or upgrade to tech builds
  within Windows 10 without hard shutting off the VM.

  Physical hardware: Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz [Haswell]

  QEMU 2.1-2.3.x seem all broken, I am using Q35 chipset w/ BIOS mode.

  Launch command via virt-manager/libvirt launch:

  QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name Windows_10 -S -machine
  pc-q35-2.3,accel=kvm,usb=off -cpu Haswell-
  noTSX,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096
  -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid ed7e372b-
  ebf9-4feb-a305-869f82e6aaee -no-user-config -nodefaults -chardev
  socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows_10.monitor,server,nowait
  -mon chardev=charmonitor,id=monitor,mode=control -rtc
  base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard
  -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global
  PIIX4_PM.disable_s4=1 -boot menu=off,strict=on -device
  i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-
  bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-
  ehci1,id=usb,bus=pci.2,addr=0x3.0x7 -device ich9-usb-
  uhci1,masterbus=usb.0,firstport=0,bus=pci.2,multifunction=on,addr=0x3
  -device ich9-usb-
  uhci2,masterbus=usb.0,firstport=2,bus=pci.2,addr=0x3.0x1 -device ich9
  -usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.2,addr=0x3.0x2 -device
  virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x4 -drive
  file=/var/lib/libvirt/images/Windows_10.qcow2,if=none,id=drive-
  sata0-0-0,format=qcow2 -device ide-hd,bus=ide.0,drive=drive-
  sata0-0-0,id=sata0-0-0,bootindex=1 -drive file=/usr/share/virtio-win
  /virtio-win-0.1.109.iso,if=none,media=cdrom,id=drive-
  sata0-0-1,readonly=on,format=raw -device ide-cd,bus=ide.1,drive=drive-
  sata0-0-1,id=sata0-0-1 -netdev
  tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=52:54:00:54:14:20,bus=pci.2,addr=0x1
  -chardev pty,id=charserial0 -device isa-
  serial,chardev=charserial0,id=serial0 -chardev
  spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus
  =virtio-
  serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
  -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-
  ticketing,image-compression=off,seamless-migration=on -device qxl-
  vga,id=video0,ram_size=268435456,vram_size=268435456,vgamem_mb=256,bus=pcie.0,addr=0x1
  -device ich9-intel-hda,id=sound0,bus=pci.2,addr=0x2 -device hda-
  duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device usb-
  host,hostbus=1,hostaddr=2,id=hostdev0 -device virtio-balloon-
  pci,id=balloon0,bus=pci.2,addr=0x5 -msg timestamp=on

  The workaround I've been able to come up with is to set boot menu in
  virt-manager, then put in a bootable CD so I have enough time to hard
  power off the QEMU/KVM instance, when I power it back on, it continues
  upgrade/install without issue, each time it needs to restart however I
  go though same exercise.

  Anything known about this issue? The workaround is a kludge, but it
  does get it to upgrade/install Windows 8.1, and upgrade between
  Windows 10 X builds.

  Thanks,
  Shawn

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1487264/+subscriptions

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Qemu-devel] [Bug 1487264] Re: Windows 8.1/10 Crashes during upgrade - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  2015-08-21  2:22 [Qemu-devel] [Bug 1487264] [NEW] Windows 8.1/10 Crashes during upgrade - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED ShawnStarr
  2018-08-14 16:05 ` [Qemu-devel] [Bug 1487264] " Thomas Huth
@ 2018-10-14  4:17 ` Launchpad Bug Tracker
  1 sibling, 0 replies; 3+ messages in thread
From: Launchpad Bug Tracker @ 2018-10-14  4:17 UTC (permalink / raw)
  To: qemu-devel

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1487264

Title:
  Windows 8.1/10 Crashes during upgrade -
  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Status in QEMU:
  Expired

Bug description:
  Ever since Windows 8.x, 10 I cannot upgrade or upgrade to tech builds
  within Windows 10 without hard shutting off the VM.

  Physical hardware: Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz [Haswell]

  QEMU 2.1-2.3.x seem all broken, I am using Q35 chipset w/ BIOS mode.

  Launch command via virt-manager/libvirt launch:

  QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name Windows_10 -S -machine
  pc-q35-2.3,accel=kvm,usb=off -cpu Haswell-
  noTSX,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096
  -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid ed7e372b-
  ebf9-4feb-a305-869f82e6aaee -no-user-config -nodefaults -chardev
  socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows_10.monitor,server,nowait
  -mon chardev=charmonitor,id=monitor,mode=control -rtc
  base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard
  -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global
  PIIX4_PM.disable_s4=1 -boot menu=off,strict=on -device
  i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-
  bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-
  ehci1,id=usb,bus=pci.2,addr=0x3.0x7 -device ich9-usb-
  uhci1,masterbus=usb.0,firstport=0,bus=pci.2,multifunction=on,addr=0x3
  -device ich9-usb-
  uhci2,masterbus=usb.0,firstport=2,bus=pci.2,addr=0x3.0x1 -device ich9
  -usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.2,addr=0x3.0x2 -device
  virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x4 -drive
  file=/var/lib/libvirt/images/Windows_10.qcow2,if=none,id=drive-
  sata0-0-0,format=qcow2 -device ide-hd,bus=ide.0,drive=drive-
  sata0-0-0,id=sata0-0-0,bootindex=1 -drive file=/usr/share/virtio-win
  /virtio-win-0.1.109.iso,if=none,media=cdrom,id=drive-
  sata0-0-1,readonly=on,format=raw -device ide-cd,bus=ide.1,drive=drive-
  sata0-0-1,id=sata0-0-1 -netdev
  tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=52:54:00:54:14:20,bus=pci.2,addr=0x1
  -chardev pty,id=charserial0 -device isa-
  serial,chardev=charserial0,id=serial0 -chardev
  spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus
  =virtio-
  serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
  -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-
  ticketing,image-compression=off,seamless-migration=on -device qxl-
  vga,id=video0,ram_size=268435456,vram_size=268435456,vgamem_mb=256,bus=pcie.0,addr=0x1
  -device ich9-intel-hda,id=sound0,bus=pci.2,addr=0x2 -device hda-
  duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device usb-
  host,hostbus=1,hostaddr=2,id=hostdev0 -device virtio-balloon-
  pci,id=balloon0,bus=pci.2,addr=0x5 -msg timestamp=on

  The workaround I've been able to come up with is to set boot menu in
  virt-manager, then put in a bootable CD so I have enough time to hard
  power off the QEMU/KVM instance, when I power it back on, it continues
  upgrade/install without issue, each time it needs to restart however I
  go though same exercise.

  Anything known about this issue? The workaround is a kludge, but it
  does get it to upgrade/install Windows 8.1, and upgrade between
  Windows 10 X builds.

  Thanks,
  Shawn

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1487264/+subscriptions

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2018-10-14  4:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-08-21  2:22 [Qemu-devel] [Bug 1487264] [NEW] Windows 8.1/10 Crashes during upgrade - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED ShawnStarr
2018-08-14 16:05 ` [Qemu-devel] [Bug 1487264] " Thomas Huth
2018-10-14  4:17 ` Launchpad Bug Tracker

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.