public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 207099] New: VM fails to boot with invariant tsc enabled with kvm_amd
Date: Sat, 04 Apr 2020 11:38:31 +0000	[thread overview]
Message-ID: <bug-207099-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=207099

            Bug ID: 207099
           Summary: VM fails to boot with invariant tsc enabled with
                    kvm_amd
           Product: Virtualization
           Version: unspecified
    Kernel Version: 5.6.0 - 5.6.2
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: geggen54@gmail.com
        Regression: No

After the 5.6.0 release my windows 10 VM running on AMD 3950x fails to boot
when option "migratable=no,+invtsc" is enabled. The VM starts the boot process
but after a few seconds I get a bluescreen with the error "Kernel security
check failed". 

Neither the host or guest has any logs that I can find with any more details on
the issue, or even that it happens at all.

The issue is reproducible at least for me with a minimum set of options in QEMU
with no enlightenments:

"-M type=q35,accel=kvm,kernel_irqchip=on -cpu host, kvm=off,
migratable=no,+invtsc, topoext -smp 24,sockets=1, cores=12, threads=2
-enable-kvm"

I've tried changing the options kvm_amd.avic and nested to no avail.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2020-04-04 11:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-207099-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.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