qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Bug 1850751] [NEW] kvm flag is not exposed by default
@ 2019-10-31  6:35 Leoyzen Liu
  2021-04-22  8:48 ` [Bug 1850751] " Thomas Huth
  2021-06-22  4:18 ` Launchpad Bug Tracker
  0 siblings, 2 replies; 3+ messages in thread
From: Leoyzen Liu @ 2019-10-31  6:35 UTC (permalink / raw)
  To: qemu-devel

Public bug reported:

Hi I found that the kvm flags is not exposed by default, but according
to the source code, it should be exposed by default when the CPU Model
is a X86CPU.

we have to specifically add "kvm=on" in QEMU custom cpu args like this to make VMWare Timing and KVM-Clock work:
<qemu:arg value='host,kvm=on,+invtsc,+hypervisor'/>

Also the libvirt can't expose kvm because of this (libvirt assumes the
kvm flag is exposed by default in QEMU, so only "kvm hidden = 'true'"
can be used to disable the kvm expose flag.

I'm using QEMU 4.1.0 and libvirt 20190803.

** Affects: qemu
     Importance: Undecided
         Status: New

** Description changed:

  Hi I found that the kvm flags is not exposed by default, but according
  to the source code, it should be exposed by default when the CPU Model
  is a X86CPU.
  
- we have to specifically add "kvm=on" in QEMU custom cpu args like this:
+ we have to specifically add "kvm=on" in QEMU custom cpu args like this to make VMWare Timing and KVM-Clock work:
  <qemu:arg value='host,kvm=on,+invtsc,+hypervisor'/>
  
  Also the libvirt can't expose kvm because this (libvirt assumes the kvm
  flag is exposed by default, only "kvm hidden = 'true'" can be used.
+ 
+ I'm using QEMU 4.1.0 and libvirt 20190803.

** Description changed:

  Hi I found that the kvm flags is not exposed by default, but according
  to the source code, it should be exposed by default when the CPU Model
  is a X86CPU.
  
  we have to specifically add "kvm=on" in QEMU custom cpu args like this to make VMWare Timing and KVM-Clock work:
  <qemu:arg value='host,kvm=on,+invtsc,+hypervisor'/>
  
- Also the libvirt can't expose kvm because this (libvirt assumes the kvm
- flag is exposed by default, only "kvm hidden = 'true'" can be used.
+ Also the libvirt can't expose kvm because of this (libvirt assumes the
+ kvm flag is exposed by default in QEMU, so only "kvm hidden = 'true'"
+ can be used to disable the kvm expose flag.
  
  I'm using QEMU 4.1.0 and libvirt 20190803.

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

Title:
  kvm flag is not exposed by default

Status in QEMU:
  New

Bug description:
  Hi I found that the kvm flags is not exposed by default, but according
  to the source code, it should be exposed by default when the CPU Model
  is a X86CPU.

  we have to specifically add "kvm=on" in QEMU custom cpu args like this to make VMWare Timing and KVM-Clock work:
  <qemu:arg value='host,kvm=on,+invtsc,+hypervisor'/>

  Also the libvirt can't expose kvm because of this (libvirt assumes the
  kvm flag is exposed by default in QEMU, so only "kvm hidden = 'true'"
  can be used to disable the kvm expose flag.

  I'm using QEMU 4.1.0 and libvirt 20190803.

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


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

* [Bug 1850751] Re: kvm flag is not exposed by default
  2019-10-31  6:35 [Bug 1850751] [NEW] kvm flag is not exposed by default Leoyzen Liu
@ 2021-04-22  8:48 ` Thomas Huth
  2021-06-22  4:18 ` Launchpad Bug Tracker
  1 sibling, 0 replies; 3+ messages in thread
From: Thomas Huth @ 2021-04-22  8:48 UTC (permalink / raw)
  To: qemu-devel

The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.

If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.

Thank you and sorry for the inconvenience.


** 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/1850751

Title:
  kvm flag is not exposed by default

Status in QEMU:
  Incomplete

Bug description:
  Hi I found that the kvm flags is not exposed by default, but according
  to the source code, it should be exposed by default when the CPU Model
  is a X86CPU.

  we have to specifically add "kvm=on" in QEMU custom cpu args like this to make VMWare Timing and KVM-Clock work:
  <qemu:arg value='host,kvm=on,+invtsc,+hypervisor'/>

  Also the libvirt can't expose kvm because of this (libvirt assumes the
  kvm flag is exposed by default in QEMU, so only "kvm hidden = 'true'"
  can be used to disable the kvm expose flag.

  I'm using QEMU 4.1.0 and libvirt 20190803.

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


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

* [Bug 1850751] Re: kvm flag is not exposed by default
  2019-10-31  6:35 [Bug 1850751] [NEW] kvm flag is not exposed by default Leoyzen Liu
  2021-04-22  8:48 ` [Bug 1850751] " Thomas Huth
@ 2021-06-22  4:18 ` Launchpad Bug Tracker
  1 sibling, 0 replies; 3+ messages in thread
From: Launchpad Bug Tracker @ 2021-06-22  4:18 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/1850751

Title:
  kvm flag is not exposed by default

Status in QEMU:
  Expired

Bug description:
  Hi I found that the kvm flags is not exposed by default, but according
  to the source code, it should be exposed by default when the CPU Model
  is a X86CPU.

  we have to specifically add "kvm=on" in QEMU custom cpu args like this to make VMWare Timing and KVM-Clock work:
  <qemu:arg value='host,kvm=on,+invtsc,+hypervisor'/>

  Also the libvirt can't expose kvm because of this (libvirt assumes the
  kvm flag is exposed by default in QEMU, so only "kvm hidden = 'true'"
  can be used to disable the kvm expose flag.

  I'm using QEMU 4.1.0 and libvirt 20190803.

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


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

end of thread, other threads:[~2021-06-22  5:25 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-31  6:35 [Bug 1850751] [NEW] kvm flag is not exposed by default Leoyzen Liu
2021-04-22  8:48 ` [Bug 1850751] " Thomas Huth
2021-06-22  4:18 ` Launchpad Bug Tracker

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).