[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 1243968] Re: VMware ESXi on QEmu Kernel Panic

From: Launchpad Bug Tracker
Subject: [Bug 1243968] Re: VMware ESXi on QEmu Kernel Panic
Date: Mon, 18 Jan 2021 04:17:14 -0000

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

  VMware ESXi on QEmu Kernel Panic

Status in QEMU:

Bug description:
  I attempted to install ESXi 5.5 (the free version) into a QEmu 1.6.1
  VM. The guest OS does have the svm capabilities, but it appears VMware
  is trying to do some kind of hypercall that crashes the guest.

  There is more information here:

  It seems to me that this stubbed feature should just be disabled if it
  is unusable. Or at the very least I should be able to disable it at
  run-time with a command-line argument.

  Is there some way to disable all the hypervisor features that makes it
  very obvious to a guest os that it is running inside a VM? It would be
  great if I could install a software and it would actually work (even
  if it's slow with those features disabled).

  FYI, my guest OS capabilities are:

  # cat /proc/cpuinfo
  processor       : 0
  vendor_id       : AuthenticAMD
  cpu family      : 6
  model           : 2
  model name      : QEMU Virtual CPU version 1.5.3
  stepping        : 3
  microcode       : 0x1000065
  cpu MHz         : 1999.999
  cache size      : 512 KB
  fpu             : yes
  fpu_exception   : yes
  cpuid level     : 4
  wp              : yes
  flags           : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 syscall nx lm nopl pni cx16 popcnt 
hypervisor lahf_lm svm abm sse4a
  bogomips        : 3999.99
  TLB size        : 1024 4K pages
  clflush size    : 64
  cache_alignment : 64
  address sizes   : 40 bits physical, 48 bits virtual
  power management:

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]