qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Christian Ehrhardt " <1915063@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1915063] Re: Windows 10 wil not install using qemu-system-x86_64
Date: Thu, 08 Apr 2021 14:30:07 -0000	[thread overview]
Message-ID: <161789220720.29516.5458396703430734934.malone@gac.canonical.com> (raw)
In-Reply-To: 161281335451.16853.7070328699645987751.malonedeb@wampee.canonical.com

David used "5.6.0-1042.46-oem", the closest I had was "5.6.0-1052-oem"
so I tried that one.

With that my win10 install immediately crashed into the reported issue.

So to summarize:
1. I can reproduce it
2. Chances are high that it is fixed by kernel commit 841c2be0 "kvm: x86: replace kvm_spec_ctrl_test_value with runtime test on the host"
3. there are some qemu changes which might be related, but we need Babu to reply about if/how those are related

I need to get myself updated on Ubuntu oem kernels.
If there is a 5.6 series that is supposed to work on that, then this patch needs to be backported.
But if OTOH it is a valid upgrade path that you'll get the 5.10.0-1020-oem that I had or later as part of your 20.04 OEM then that "is the fix" for you @David.



** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: linux-oem-5.6 (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: linux-oem-5.10 (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: linux-oem-5.10 (Ubuntu)
       Status: New => Fix Released

** Changed in: linux-oem-5.6 (Ubuntu)
       Status: New => Confirmed

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

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in QEMU:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-5.10 package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs and memory required
      Select customize configuration then select OVMF(UEFI) instead of seabios
      set first CDROM to the windows installation iso (enable in boot options)
      add a second CDROM and load with the virtio iso
  	change spice display to VNC

    Always get a security error from windows and it fails to launch the installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware                          1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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


  parent reply	other threads:[~2021-04-08 14:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <161281335451.16853.7070328699645987751.malonedeb@wampee.canonical.com>
2021-03-26  7:36 ` [Bug 1915063] Re: Windows 10 wil not install using qemu-system-x86_64 Christian Ehrhardt 
2021-04-01 11:51 ` David Ober
2021-04-03 16:52 ` Christian Ehrhardt 
2021-04-06 18:53   ` Igor Mammedov
2021-04-06 18:53     ` Igor
2021-04-06 12:48 ` David Ober
2021-04-06 14:07 ` Christian Ehrhardt 
2021-04-07 13:00 ` David Ober
2021-04-07 21:54   ` Igor Mammedov
2021-04-07 21:54     ` Igor
2021-04-07 23:04 ` Babu Moger
2021-04-08 12:35 ` Christian Ehrhardt 
2021-04-08 14:03 ` Christian Ehrhardt 
2021-04-08 14:11 ` Babu Moger
2021-04-08 14:30 ` Christian Ehrhardt  [this message]
2021-04-08 15:00 ` [Bug 1915063] Status changed to Confirmed Ubuntu Kernel Bot
2021-04-09  6:31 ` [Bug 1915063] Re: Windows 10 wil not install using qemu-system-x86_64 Christian Ehrhardt 
2021-04-12  8:27 ` Andy Whitcroft
2021-05-14 19:10 ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=161789220720.29516.5458396703430734934.malone@gac.canonical.com \
    --to=1915063@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).