blob: d4426021563cc85df87d6d45a5f3163793f70540 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
hypervisor: 0.948
kernel: 0.912
graphic: 0.912
architecture: 0.863
device: 0.853
performance: 0.821
peripherals: 0.812
ppc: 0.808
x86: 0.769
permissions: 0.766
files: 0.756
virtual: 0.751
user-level: 0.730
PID: 0.714
VMM: 0.700
socket: 0.695
vnc: 0.688
register: 0.643
network: 0.642
semantic: 0.621
mistranslation: 0.617
risc-v: 0.600
i386: 0.576
arm: 0.567
debug: 0.566
assembly: 0.520
boot: 0.509
KVM: 0.480
TCG: 0.476
VMware ESXi on QEmu Kernel Panic
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: https://communities.vmware.com/message/2297382
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:
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 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.
[Expired for QEMU because there has been no activity for 60 days.]
|