qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Randrianasulu <randrianasulu@gmail.com>
To: liebrecht@grossmann-venter.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu the right way -[Subthread Cores]
Date: Thu, 27 Dec 2018 14:21:34 +0300	[thread overview]
Message-ID: <201812271421.34926.randrianasulu@gmail.com> (raw)

> Since I do not have networking sorted out yet I cannot update win7 pro, and it 
might be the updates which are needed for allowing more than two cpus.

hm, brief search on my side resulted in this tip:

https://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/windows-7-professional-x64-only-showing-2-of-8/0155f525-df73-4642-a828-21b80d1564b0

----------
Some recommendations (in Windows, make sure you are running as Administrator):
 
- Run MSConfig -> Change to Boot tab -> Advanced Options -> "Number of 
Processors", make sure there is no check mark.
- Delete processor entries listed in Device Manager, then reboot.

-------------

(I don't think BIOS options from this answer really apply directly to qemu case)

also, if win (or some applications inside it) keep crashing with -cpu host, you 
can try to reload host (Linux) kvm module with additional option:

"options kvm ignore_msrs=1" line (without quotes) should be added to
 /etc/modprobe.d/kvm.conf

from 
https://www.passmark.com/forum/performancetest/4748-startup-error-number-4-on-qemu-bsod

             reply	other threads:[~2018-12-27 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27 11:21 Andrew Randrianasulu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-27 22:14 [Qemu-devel] Qemu the right way -[Subthread Cores] liebrecht
     [not found] <201812270548.42446.randrianasulu@gmail.com>
2018-12-27  3:31 ` liebrecht

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=201812271421.34926.randrianasulu@gmail.com \
    --to=randrianasulu@gmail.com \
    --cc=liebrecht@grossmann-venter.com \
    --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).