From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 205243] CPU model name is not passed to Guest VM
Date: Fri, 24 Apr 2020 23:14:29 +0000 [thread overview]
Message-ID: <bug-205243-28872-hFIDCgUWj7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205243-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205243
Jordan (jorhand@linux.microsoft.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jorhand@linux.microsoft.com
--- Comment #1 from Jordan (jorhand@linux.microsoft.com) ---
This isn't really an issue with KVM, but instead just a matter of how the VM
was launched.
For example if you are launching the VM with qemu-kvm, passing "-cpu host" will
allow the guest full access to CPU details.
Similarly if you're using the virt-manager UI, in hardware details -> CPUs
there is a checkbox for "Copy host CPU configuration". This will pass full CPU
details through to the host.
--
You are receiving this mail because:
You are watching the assignee of the bug.
parent reply other threads:[~2020-04-24 23:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-205243-28872@https.bugzilla.kernel.org/>]
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-205243-28872-hFIDCgUWj7@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;
as well as URLs for NNTP newsgroup(s).