VMware Communities
freesco
Contributor
Contributor

Running Vmware in KVM or KVM in Vmware

😃before saying that running 2 hypervisor on the same machine is a big no no as they will fight over resources ... on new hardware nested virtualization is there already so I wonder if someone played around with this.

I have bunch of KVM vms what I would prefer NOT to convert to Vmware but create yet another KVM on the same server and install Vmware workstation inside it. Doable? Even if the performance would not be the best as long as it's going to work it's good enough for me.

 

Or if this is not possible I could theoretically create only Vmware machines on that box and dedicate one to be a host KVM server and run the kvms inside it.

Please share all your experiences if you did these setups.

0 Kudos
5 Replies
bluefirestorm
Champion
Champion

Haven't tried any of your scenarios, but just in case

There is a known bug in the Linux kernel that KVM running on AMD CPUs hosting a VMware hypervisor fail with "Invalid VMCB" error.
https://communities.vmware.com/t5/vSphere-Upgrade-Install/VMWare-ESXi-7-On-Top-KVM-VM-won-t-Start/m-...

As for Intel CPUs, for better nested virtualisation performance, the CPU should have VMCS shadowing feature. This feature ishould be available in Intel Haswell Xeon or newer but for desktop/mobile CPUs, it is indicated in the Intel ARK website as vPro availability as "Yes". This feature is indicated in the vmx flags of /proc/cpuinfo as shadow_vmcs.

Considering the AMD bug was reported, that means that there are people who have tried running either VMware Workstation or ESXi inside KVM.

0 Kudos
freesco
Contributor
Contributor

Another reason why I NEVER buy AMD nor for servers nor for workstations/laptops 🙂

Even if Intel is more expensive I staying with Intel only!

Intel 4 ever 😎

freesco
Contributor
Contributor

Finally I got a server where I can play around with this nested virtualization, running a latest Debian distro + 6.x kernel + KVM as the host and latest Kali Linux with Vmware 17 inside.

I using the host passthrough mode for the VM: https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-libvirt-config-virsh.html

Well it "works" you can really run some VM inside however that KVM machine craps itself together many times as well:

└─# virt-host-validate
QEMU: Checking for hardware virtualization : PASS
QEMU: Checking if device /dev/kvm exists : PASS
QEMU: Checking if device /dev/kvm is accessible : PASS
QEMU: Checking if device /dev/vhost-net exists : PASS
QEMU: Checking if device /dev/net/tun exists : PASS
QEMU: Checking for cgroup 'cpu' controller support : PASS
QEMU: Checking for cgroup 'cpuacct' controller support : PASS
QEMU: Checking for cgroup 'cpuset' controller support : PASS
QEMU: Checking for cgroup 'memory' controller support : PASS
QEMU: Checking for cgroup 'devices' controller support : PASS
QEMU: Checking for cgroup 'blkio' controller support : PASS
QEMU: Checking for device assignment IOMMU support : WARN (No ACPI DMAR table found, IOMMU either disabled in BIOS or not supported by this hardware platform)
QEMU: Checking for secure guest support : WARN (Unknown if this platform has Secure Guest support)
LXC: Checking for Linux >= 2.6.26 : PASS
LXC: Checking for namespace ipc : PASS
LXC: Checking for namespace mnt : PASS
LXC: Checking for namespace pid : PASS
LXC: Checking for namespace uts : PASS
LXC: Checking for namespace net : PASS
LXC: Checking for namespace user : PASS
LXC: Checking for cgroup 'cpu' controller support : PASS
LXC: Checking for cgroup 'cpuacct' controller support : PASS
LXC: Checking for cgroup 'cpuset' controller support : PASS
LXC: Checking for cgroup 'memory' controller support : PASS
LXC: Checking for cgroup 'devices' controller support : PASS
LXC: Checking for cgroup 'freezer' controller support : FAIL (Enable 'freezer' in kernel Kconfig file or mount/enable cgroup controller in your system)
LXC: Checking for cgroup 'blkio' controller support : PASS
LXC: Checking if device /sys/fs/fuse/connections exists : PASS

 

29029.123411] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-...D 3-...D } 6687634 jiffies s: 605 root: 0x9/.
[29029.124573] rcu: blocking rcu_node structures (internal RCU debug):
[29029.124901] Sending NMI from CPU 1 to CPUs 0:
[29029.124917] NMI backtrace for cpu 0
[29029.124926] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W OE 6.6.9-amd64 #1 Kali 6.6.9-1kali1
[29029.124930] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[29029.124931] RIP: 0010:pv_native_safe_halt+0xf/0x20
[29029.124950] Code: 0b 90 66 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 0f 00 2d 65 94 41 00 fb f4 <c3> cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90 90 90 90
[29029.124952] RSP: 0018:ffffffff8f203e80 EFLAGS: 00000242
[29029.124956] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff970d075befa8
[29029.124957] RDX: 4000000000000000 RSI: 0000000000000000 RDI: 00000000397748b4
[29029.124958] RBP: ffffffff8f210900 R08: 0000000000000001 R09: 0000000000000000
[29029.124959] R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
[29029.124960] R13: 0000000000000000 R14: ffffffff8f210900 R15: 000000000008b000
[29029.124961] FS: 0000000000000000(0000) GS:ffff970e37c00000(0000) knlGS:0000000000000000
[29029.124963] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[29029.124964] CR2: 00007facbe57eb90 CR3: 000000010c42a006 CR4: 0000000000370ef0
[29029.124967] Call Trace:
[29029.124972] <NMI>
[29029.124983] ? nmi_cpu_backtrace+0x99/0x110
[29029.124987] ? nmi_cpu_backtrace_handler+0x11/0x20
[29029.124992] ? nmi_handle+0x61/0x150
[29029.124998] ? default_do_nmi+0x40/0x100
[29029.125000] ? exc_nmi+0x139/0x1c0
[29029.125001] ? end_repeat_nmi+0x16/0x67
[29029.125015] ? pv_native_safe_halt+0xf/0x20
[29029.125018] ? pv_native_safe_halt+0xf/0x20
[29029.125020] ? pv_native_safe_halt+0xf/0x20
[29029.125022] </NMI>
[29029.125023] <TASK>
[29029.125023] default_idle+0x9/0x20
[29029.125026] default_idle_call+0x2c/0xe0
[29029.125027] do_idle+0x226/0x270
[29029.125035] ? do_idle+0x7/0x270
[29029.125038] cpu_startup_entry+0x2a/0x30
[29029.125040] rest_init+0xd0/0xd0
[29029.125042] arch_call_rest_init+0xe/0x30
[29029.125054] start_kernel+0x4de/0x790
[29029.125057] x86_64_start_reservations+0x18/0x30
[29029.125062] x86_64_start_kernel+0x96/0xa0
[29029.125064] secondary_startup_64_no_verify+0x18f/0x19b
[29029.125085] </TASK>
[29029.125900] Sending NMI from CPU 1 to CPUs 3:
[29029.125915] NMI backtrace for cpu 3
[29029.125917] CPU: 3 PID: 3868 Comm: vmx-vcpu-0 Tainted: G W OE 6.6.9-amd64 #1 Kali 6.6.9-1kali1
[29029.125920] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[29029.125921] RIP: 0010:Task_Switch+0x2ee/0x1c20 [vmmon]
[29029.125954] Code: 0f 32 48 c1 e2 20 48 09 d0 48 89 44 24 08 48 89 c3 a8 01 74 0d 48 c1 eb 20 48 83 e0 fe 48 89 da 0f 30 0f 01 8c 24 a4 00 00 00 <41> 0f 01 9f 20 07 00 00 0f b6 35 3e b3 00 00 40 84 f6 74 32 b9 3a
[29029.125956] RSP: 0018:ffffae27856c7b20 EFLAGS: 00000046
[29029.125958] RAX: 000000000ed1e97c RBX: 0000000000000003 RCX: 0000000000015106
[29029.125959] RDX: 0000449e8108b6da RSI: 000009acaec30000 RDI: 000041238a78d093
[29029.125960] RBP: ffff970d01c49600 R08: 0000000000000001 R09: 0000000000000000
[29029.125962] R10: 000000000010c1a4 R11: 0000000000000003 R12: ffff970e37d8b000
[29029.125963] R13: 0000000000000206 R14: ffffae27809116f0 R15: ffffae2780911000
[29029.125964] FS: 00007fa3c13ee6c0(0000) GS:ffff970e37d80000(0000) knlGS:0000000000000000
[29029.125966] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[29029.125967] CR2: 00007f491834bb70 CR3: 000000010c42a006 CR4: 0000000000370ee0
[29029.125970] Call Trace:
[29029.125975] <NMI>
[29029.125977] ? nmi_cpu_backtrace+0x99/0x110
[29029.125980] ? nmi_cpu_backtrace_handler+0x11/0x20
[29029.125983] ? nmi_handle+0x61/0x150
[29029.125986] ? default_do_nmi+0x40/0x100
[29029.125988] ? exc_nmi+0x139/0x1c0
[29029.125990] ? end_repeat_nmi+0x16/0x67
[29029.125993] ? Task_Switch+0x2ee/0x1c20 [vmmon]
[29029.126004] ? Task_Switch+0x2ee/0x1c20 [vmmon]
[29029.126013] ? Task_Switch+0x2ee/0x1c20 [vmmon]
[29029.126024] </NMI>
[29029.126024] <TASK>
[29029.126026] Vmx86_RunVM+0xe1/0x700 [vmmon]
[29029.126039] ? LinuxDriver_Ioctl+0x52d/0x1310 [vmmon]
[29029.126047] LinuxDriver_Ioctl+0xabc/0x1310 [vmmon]
[29029.126057] ? __x64_sys_ioctl+0x97/0xd0
[29029.126060] ? exit_to_user_mode_prepare+0x40/0x1e0
[29029.126064] ? __x64_sys_ioctl+0x97/0xd0
[29029.126065] ? __pfx_LinuxDriver_Ioctl+0x10/0x10 [vmmon]
[29029.126072] __x64_sys_ioctl+0x97/0xd0
[29029.126074] do_syscall_64+0x60/0xc0
[29029.126078] ? __x64_sys_ioctl+0x97/0xd0
[29029.126079] ? exit_to_user_mode_prepare+0x40/0x1e0
[29029.126081] ? syscall_exit_to_user_mode+0x2b/0x40
[29029.126084] ? do_syscall_64+0x6c/0xc0
[29029.126086] ? syscall_exit_to_user_mode+0x2b/0x40
[29029.126089] ? do_syscall_64+0x6c/0xc0
[29029.126102] ? syscall_exit_to_user_mode+0x2b/0x40
[29029.126104] ? do_syscall_64+0x6c/0xc0
[29029.126107] ? do_syscall_64+0x6c/0xc0
[29029.126109] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[29029.126114] RIP: 0033:0x7fa3c511b51b
[29029.126119] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[29029.126121] RSP: 002b:00007fa3c13ea830 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[29029.126123] RAX: ffffffffffffffda RBX: 0000559c796f28b8 RCX: 00007fa3c511b51b
[29029.126124] RDX: 0000000000000000 RSI: 00000000000007d8 RDI: 000000000000000f
[29029.126126] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000004
[29029.126127] R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000014a
[29029.126128] R13: 00007fa3c4f12388 R14: 00007fa3c4f123a0 R15: 00007fa3c0bee000
[29029.126130] </TASK>

 

Any ideas tricks how to tune this further? Would it be more efficient running ESX inside instead of Vmware Workstation? 🤔

0 Kudos
bluefirestorm
Champion
Champion

If I understand correctly, the host machine runs Debian OS with KVM hypervisor and running a Kali Linux VM where Workstation 17 is installed inside this Kali VM.

The crash trace shows NMI. NMI would indicate a hardware event, either a hardware failure or an important event/signal from the hardware telling the OS it cannot be ignored (so not necessarily a hardware failure). Is there any physical hardware that is on passthrough mode to the Kali VM? (such as USB WiFi adapter). 

[29029.124901] Sending NMI from CPU 1 to CPUs 0:
[29029.124917] NMI backtrace for cpu 0
[29029.124926] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W OE 6.6.9-amd64 #1 Kali 6.6.9-1kali1
[29029.124930] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014


Would it be more efficient running ESX inside instead of Vmware Workstation? 🤔

Not sure about efficiency but ESXi and Workstation are more likely to place nice with each other although officially nested virtualisation is not supported for a production environment. So if problems are encountered, VMware does not have any obligation to support/fix anything be it at Workstation or ESXi. 

0 Kudos
freesco
Contributor
Contributor

Hello,

 

The only thing which was passed through not used at all were the USB/CDRom I have removed them so the config now is:

 

<domain type='kvm' id='2'>
  <name>vmware</name>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <vcpu placement='static'>4</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-3.1'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'/>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/mnt/kvm/vmware.qcow' index='3'/>
      <backingStore/>
      <target dev='vda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    <controller type='ide' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='usb' index='0' model='piix3-uhci'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <source bridge='br0'/>
      <target dev='vnet20'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/15'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/15'>
      <source path='/dev/pts/15'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <input type='mouse' bus='ps2'>
      <alias name='input0'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input1'/>
    </input>
    <audio id='1' type='none'/>
    <video>
      <model type='cirrus' vram='16384' heads='1' primary='yes'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='none' model='apparmor'/>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+64055:+64055</label>
    <imagelabel>+64055:+64055</imagelabel>
  </seclabel>
</domain>

 

It's still keep doing it:

 

 

[Mon Feb 19 10:57:52 2024] Sending NMI from CPU 1 to CPUs 0:
[Mon Feb 19 10:57:52 2024] NMI backtrace for cpu 0
[Mon Feb 19 10:57:52 2024] CPU: 0 PID: 6823 Comm: vmware-clk Tainted: G W OE 6.6.9-amd64 #1 Kali 6.6.9-1kali1
[Mon Feb 19 10:57:52 2024] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[Mon Feb 19 10:57:52 2024] RIP: 0010:update_sd_lb_stats.constprop.0+0x123/0x990
[Mon Feb 19 10:57:52 2024] Code: 00 48 39 43 48 73 07 48 89 43 48 83 cd 01 41 8d 4c 24 01 8b 15 1e d4 d2 01 49 8b 77 38 48 63 c9 48 8b 7c 24 10 e8 fd 74 50 00 <3b> 05 07 d4 d2 01 49 89 c4 41 89 c5 0f 83 58 01 00 00 4d 63 dc 4c
[Mon Feb 19 10:57:52 2024] RSP: 0018:ffffb74246fefa38 EFLAGS: 00000002
[Mon Feb 19 10:57:52 2024] RAX: 0000000000000000 RBX: ffffb74246fefbb0 RCX: 0000000000000000
[Mon Feb 19 10:57:52 2024] RDX: 0000000000000000 RSI: ffff8b5d80072a38 RDI: 0000000000000000
[Mon Feb 19 10:57:52 2024] RBP: 0000000000000000 R08: ffff8b5d80389d28 R09: ffffffffffffffff
[Mon Feb 19 10:57:52 2024] R10: ffff8b5d80389d00 R11: ffff8b5d80389d00 R12: 0000000000000000
[Mon Feb 19 10:57:52 2024] R13: ffffb74246fefb28 R14: ffffb74246fefc98 R15: ffffb74246fefc98
[Mon Feb 19 10:57:52 2024] FS: 0000000000000000(0000) GS:ffff8b5eb7c00000(0000) knlGS:0000000000000000
[Mon Feb 19 10:57:52 2024] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Mon Feb 19 10:57:52 2024] CR2: 00007fa0cf487dc0 CR3: 00000001835da006 CR4: 0000000000370ef0
[Mon Feb 19 10:57:52 2024] Call Trace:
[Mon Feb 19 10:57:52 2024] <NMI>
[Mon Feb 19 10:57:52 2024] ? nmi_cpu_backtrace+0x99/0x110
[Mon Feb 19 10:57:52 2024] ? nmi_cpu_backtrace_handler+0x11/0x20
[Mon Feb 19 10:57:52 2024] ? nmi_handle+0x61/0x150
[Mon Feb 19 10:57:52 2024] ? default_do_nmi+0x40/0x100
[Mon Feb 19 10:57:52 2024] ? exc_nmi+0x139/0x1c0
[Mon Feb 19 10:57:52 2024] ? end_repeat_nmi+0x16/0x67
[Mon Feb 19 10:57:52 2024] ? update_sd_lb_stats.constprop.0+0x123/0x990
[Mon Feb 19 10:57:52 2024] ? update_sd_lb_stats.constprop.0+0x123/0x990
[Mon Feb 19 10:57:52 2024] ? update_sd_lb_stats.constprop.0+0x123/0x990
[Mon Feb 19 10:57:52 2024] </NMI>
[Mon Feb 19 10:57:52 2024] <TASK>
[Mon Feb 19 10:57:52 2024] find_busiest_group+0x42/0x4e0
[Mon Feb 19 10:57:52 2024] load_balance+0x162/0xf50
[Mon Feb 19 10:57:52 2024] ? update_load_avg+0x7e/0x780
[Mon Feb 19 10:57:52 2024] newidle_balance+0x1d3/0x430
[Mon Feb 19 10:57:52 2024] pick_next_task_fair+0x41/0x530
[Mon Feb 19 10:57:52 2024] __schedule+0x189/0xb20
[Mon Feb 19 10:57:52 2024] ? hrtimer_start_range_ns+0x246/0x350
[Mon Feb 19 10:57:52 2024] ? __pfx_HostIFFastClockThread+0x10/0x10 [vmmon]
[Mon Feb 19 10:57:52 2024] schedule+0x5e/0xd0
[Mon Feb 19 10:57:52 2024] schedule_hrtimeout_range_clock+0xbe/0x140
[Mon Feb 19 10:57:52 2024] ? __pfx_hrtimer_wakeup+0x10/0x10
[Mon Feb 19 10:57:52 2024] HostIFFastClockThread+0x81/0xd0 [vmmon]
[Mon Feb 19 10:57:52 2024] kthread+0xe8/0x120
[Mon Feb 19 10:57:52 2024] ? __pfx_kthread+0x10/0x10
[Mon Feb 19 10:57:52 2024] ret_from_fork+0x34/0x50
[Mon Feb 19 10:57:52 2024] ? __pfx_kthread+0x10/0x10
[Mon Feb 19 10:57:52 2024] ret_from_fork_asm+0x1b/0x30
[Mon Feb 19 10:57:52 2024] </TASK>
[Mon Feb 19 10:57:52 2024] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 2.771 msecs
[Mon Feb 19 10:57:52 2024] Sending NMI from CPU 1 to CPUs 3:
[Mon Feb 19 10:57:52 2024] NMI backtrace for cpu 3
[Mon Feb 19 10:57:52 2024] CPU: 3 PID: 6926 Comm: vmx-vcpu-0 Tainted: G W OE 6.6.9-amd64 #1 Kali 6.6.9-1kali1
[Mon Feb 19 10:57:52 2024] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[Mon Feb 19 10:57:52 2024] RIP: 0010:Task_Switch+0xa82/0x1c20 [vmmon]
[Mon Feb 19 10:57:52 2024] Code: ff be 35 00 00 00 48 89 df 25 ff ff fe ff 89 c2 e8 d3 af ff ff e9 20 fe ff ff 49 83 bf 30 04 00 00 02 0f 85 42 fd ff ff cd 02 <41> c6 87 18 07 00 00 00 e9 06 f7 ff ff f7 c3 00 00 02 00 0f 84 f6
[Mon Feb 19 10:57:52 2024] RSP: 0018:ffffb74247147b20 EFLAGS: 00000046
[Mon Feb 19 10:57:52 2024] RAX: 0000000000000065 RBX: 0000000000370ee0 RCX: 00000000c0000102
[Mon Feb 19 10:57:52 2024] RDX: 00000000ffffffff RSI: 0000000000000000 RDI: ffffb74241051000
[Mon Feb 19 10:57:52 2024] RBP: ffff8b5e23f11000 R08: 0000000080050033 R09: ffffffffffffffff
[Mon Feb 19 10:57:52 2024] R10: 00007fa1057f16c0 R11: 0000000000000040 R12: ffff8b5eb7d8b000
[Mon Feb 19 10:57:52 2024] R13: 0000000000000001 R14: ffffb742410516f0 R15: ffffb74241051000
[Mon Feb 19 10:57:52 2024] FS: 00007fa1057f16c0(0000) GS:ffff8b5eb7d80000(0000) knlGS:0000000000000000
[Mon Feb 19 10:57:52 2024] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Mon Feb 19 10:57:52 2024] CR2: 00007fa0ccdff350 CR3: 0000000183a24005 CR4: 0000000000370ee0
[Mon Feb 19 10:57:52 2024] Call Trace:
[Mon Feb 19 10:57:52 2024] <NMI>
[Mon Feb 19 10:57:52 2024] ? nmi_cpu_backtrace+0x99/0x110
[Mon Feb 19 10:57:52 2024] ? nmi_cpu_backtrace_handler+0x11/0x20
[Mon Feb 19 10:57:52 2024] ? nmi_handle+0x61/0x150
[Mon Feb 19 10:57:52 2024] ? default_do_nmi+0x40/0x100
[Mon Feb 19 10:57:52 2024] ? exc_nmi+0x139/0x1c0
[Mon Feb 19 10:57:52 2024] ? end_repeat_nmi+0x16/0x67
[Mon Feb 19 10:57:52 2024] ? Task_Switch+0xa82/0x1c20 [vmmon]
[Mon Feb 19 10:57:52 2024] ? Task_Switch+0xa82/0x1c20 [vmmon]
[Mon Feb 19 10:57:52 2024] ? Task_Switch+0xa82/0x1c20 [vmmon]
[Mon Feb 19 10:57:52 2024] </NMI>
[Mon Feb 19 10:57:52 2024] <TASK>
[Mon Feb 19 10:57:52 2024] Vmx86_RunVM+0xe1/0x700 [vmmon]
[Mon Feb 19 10:57:52 2024] LinuxDriver_Ioctl+0xabc/0x1310 [vmmon]
[Mon Feb 19 10:57:52 2024] ? __x64_sys_ioctl+0x97/0xd0
[Mon Feb 19 10:57:52 2024] __x64_sys_ioctl+0x97/0xd0
[Mon Feb 19 10:57:52 2024] do_syscall_64+0x60/0xc0
[Mon Feb 19 10:57:52 2024] ? __x64_sys_ioctl+0x97/0xd0
[Mon Feb 19 10:57:52 2024] ? __pfx_LinuxDriver_Ioctl+0x10/0x10 [vmmon]
[Mon Feb 19 10:57:52 2024] ? exit_to_user_mode_prepare+0x40/0x1e0
[Mon Feb 19 10:57:52 2024] ? syscall_exit_to_user_mode+0x2b/0x40
[Mon Feb 19 10:57:52 2024] ? do_syscall_64+0x6c/0xc0
[Mon Feb 19 10:57:52 2024] ? syscall_exit_to_user_mode+0x2b/0x40
[Mon Feb 19 10:57:52 2024] ? do_syscall_64+0x6c/0xc0
[Mon Feb 19 10:57:52 2024] ? do_syscall_64+0x6c/0xc0
[Mon Feb 19 10:57:52 2024] ? do_syscall_64+0x6c/0xc0
[Mon Feb 19 10:57:52 2024] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[Mon Feb 19 10:57:52 2024] RIP: 0033:0x7fa10903c51b
[Mon Feb 19 10:57:52 2024] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[Mon Feb 19 10:57:52 2024] RSP: 002b:00007fa1057ed830 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[Mon Feb 19 10:57:52 2024] RAX: ffffffffffffffda RBX: 000055dc939f48b8 RCX: 00007fa10903c51b
[Mon Feb 19 10:57:52 2024] RDX: 0000000000000000 RSI: 00000000000007d8 RDI: 000000000000000f
[Mon Feb 19 10:57:52 2024] RBP: 0000000000000000 R08: 0000000000000018 R09: 0000000000000000
[Mon Feb 19 10:57:52 2024] R10: 0000000000000031 R11: 0000000000000246 R12: 000000000000017c
[Mon Feb 19 10:57:52 2024] R13: 00007fa108e8a388 R14: 00007fa108e8a3a0 R15: 00007fa104ff1000
[Mon Feb 19 10:57:52 2024] </TASK>
[Mon Feb 19 10:58:56 2024] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-...D 3-...D } 290978 jiffies s: 1173 root: 0x9/.
[Mon Feb 19 10:58:56 2024] rcu: blocking rcu_node structures (internal RCU debug):
[Mon Feb 19 10:58:56 2024] Sending NMI from CPU 1 to CPUs 0:
[Mon Feb 19 10:58:56 2024] NMI backtrace for cpu 0
[Mon Feb 19 10:58:56 2024] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W OE 6.6.9-amd64 #1 Kali 6.6.9-1kali1
[Mon Feb 19 10:58:56 2024] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[Mon Feb 19 10:58:56 2024] RIP: 0010:pv_native_safe_halt+0xf/0x20
[Mon Feb 19 10:58:56 2024] Code: 0b 90 66 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 0f 00 2d 65 94 41 00 fb f4 <c3> cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90 90 90 90
[Mon Feb 19 10:58:56 2024] RSP: 0018:ffffffff9b603e80 EFLAGS: 00000246
[Mon Feb 19 10:58:56 2024] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[Mon Feb 19 10:58:56 2024] RDX: 4000000000000000 RSI: 0000000000000086 RDI: 00000000003bbd54
[Mon Feb 19 10:58:56 2024] RBP: ffffffff9b610900 R08: 0000000000000001 R09: 0000000000000000
[Mon Feb 19 10:58:56 2024] R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
[Mon Feb 19 10:58:56 2024] R13: 0000000000000000 R14: ffffffff9b610900 R15: 000000000008b000
[Mon Feb 19 10:58:56 2024] FS: 0000000000000000(0000) GS:ffff8b5eb7c00000(0000) knlGS:0000000000000000
[Mon Feb 19 10:58:56 2024] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Mon Feb 19 10:58:56 2024] CR2: 00007f5cfbc79698 CR3: 0000000183886002 CR4: 0000000000370ef0
[Mon Feb 19 10:58:56 2024] Call Trace:
[Mon Feb 19 10:58:56 2024] <NMI>
[Mon Feb 19 10:58:56 2024] ? nmi_cpu_backtrace+0x99/0x110
[Mon Feb 19 10:58:56 2024] ? nmi_cpu_backtrace_handler+0x11/0x20
[Mon Feb 19 10:58:56 2024] ? nmi_handle+0x61/0x150
[Mon Feb 19 10:58:56 2024] ? default_do_nmi+0x40/0x100
[Mon Feb 19 10:58:56 2024] ? exc_nmi+0x139/0x1c0
[Mon Feb 19 10:58:56 2024] ? end_repeat_nmi+0x16/0x67
[Mon Feb 19 10:58:56 2024] ? pv_native_safe_halt+0xf/0x20
[Mon Feb 19 10:58:56 2024] ? pv_native_safe_halt+0xf/0x20
[Mon Feb 19 10:58:56 2024] ? pv_native_safe_halt+0xf/0x20
[Mon Feb 19 10:58:56 2024] </NMI>
[Mon Feb 19 10:58:56 2024] <TASK>
[Mon Feb 19 10:58:56 2024] default_idle+0x9/0x20
[Mon Feb 19 10:58:56 2024] default_idle_call+0x2c/0xe0
[Mon Feb 19 10:58:56 2024] do_idle+0x226/0x270
[Mon Feb 19 10:58:56 2024] cpu_startup_entry+0x2a/0x30
[Mon Feb 19 10:58:56 2024] rest_init+0xd0/0xd0
[Mon Feb 19 10:58:56 2024] arch_call_rest_init+0xe/0x30
[Mon Feb 19 10:58:56 2024] start_kernel+0x4de/0x790
[Mon Feb 19 10:58:56 2024] x86_64_start_reservations+0x18/0x30
[Mon Feb 19 10:58:56 2024] x86_64_start_kernel+0x96/0xa0
[Mon Feb 19 10:58:56 2024] secondary_startup_64_no_verify+0x18f/0x19b
[Mon Feb 19 10:58:56 2024] </TASK>
[Mon Feb 19 10:58:56 2024] Sending NMI from CPU 1 to CPUs 3:
[Mon Feb 19 10:58:56 2024] NMI backtrace for cpu 3
[Mon Feb 19 10:58:56 2024] CPU: 3 PID: 6926 Comm: vmx-vcpu-0 Tainted: G W OE 6.6.9-amd64 #1 Kali 6.6.9-1kali1
[Mon Feb 19 10:58:56 2024] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[Mon Feb 19 10:58:56 2024] RIP: 0010:Task_Switch+0xa82/0x1c20 [vmmon]
[Mon Feb 19 10:58:56 2024] Code: ff be 35 00 00 00 48 89 df 25 ff ff fe ff 89 c2 e8 d3 af ff ff e9 20 fe ff ff 49 83 bf 30 04 00 00 02 0f 85 42 fd ff ff cd 02 <41> c6 87 18 07 00 00 00 e9 06 f7 ff ff f7 c3 00 00 02 00 0f 84 f6
[Mon Feb 19 10:58:56 2024] RSP: 0018:ffffb74247147ac0 EFLAGS: 00000046
[Mon Feb 19 10:58:56 2024] RAX: 0000000000000065 RBX: 0000000000370ee0 RCX: 00000000c0000102
[Mon Feb 19 10:58:56 2024] RDX: 00000000ffffffff RSI: 0000000000000000 RDI: ffffb74241051000
[Mon Feb 19 10:58:56 2024] RBP: ffff8b5e23f11000 R08: 0000000080050033 R09: ffffffffffffffff
[Mon Feb 19 10:58:56 2024] R10: 00007fa1057f16c0 R11: 0000000000000040 R12: ffff8b5eb7d8b000
[Mon Feb 19 10:58:56 2024] R13: 0000000000000001 R14: ffffb742410516f0 R15: ffffb74241051000
[Mon Feb 19 10:58:56 2024] FS: 00007fa1057f16c0(0000) GS:ffff8b5eb7d80000(0000) knlGS:0000000000000000
[Mon Feb 19 10:58:56 2024] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Mon Feb 19 10:58:56 2024] CR2: 00007fa0ccdff350 CR3: 0000000183a24006 CR4: 0000000000370ee0
[Mon Feb 19 10:58:56 2024] Call Trace:
[Mon Feb 19 10:58:56 2024] <NMI>
[Mon Feb 19 10:58:56 2024] ? nmi_cpu_backtrace+0x99/0x110
[Mon Feb 19 10:58:56 2024] ? nmi_cpu_backtrace_handler+0x11/0x20
[Mon Feb 19 10:58:56 2024] ? nmi_handle+0x61/0x150
[Mon Feb 19 10:58:56 2024] ? default_do_nmi+0x40/0x100
[Mon Feb 19 10:58:56 2024] ? exc_nmi+0x139/0x1c0
[Mon Feb 19 10:58:56 2024] ? end_repeat_nmi+0x16/0x67
[Mon Feb 19 10:58:56 2024] ? Task_Switch+0xa82/0x1c20 [vmmon]
[Mon Feb 19 10:58:56 2024] ? Task_Switch+0xa82/0x1c20 [vmmon]
[Mon Feb 19 10:58:56 2024] ? Task_Switch+0xa82/0x1c20 [vmmon]
[Mon Feb 19 10:58:56 2024] </NMI>
[Mon Feb 19 10:58:56 2024] <TASK>
[Mon Feb 19 10:58:56 2024] Vmx86_RunVM+0xe1/0x700 [vmmon]
[Mon Feb 19 10:58:56 2024] LinuxDriver_Ioctl+0xabc/0x1310 [vmmon]
[Mon Feb 19 10:58:56 2024] ? __x64_sys_ioctl+0x97/0xd0
[Mon Feb 19 10:58:56 2024] ? __pfx_LinuxDriver_Ioctl+0x10/0x10 [vmmon]
[Mon Feb 19 10:58:56 2024] __x64_sys_ioctl+0x97/0xd0
[Mon Feb 19 10:58:56 2024] do_syscall_64+0x60/0xc0
[Mon Feb 19 10:58:56 2024] ? __x64_sys_ioctl+0x97/0xd0
[Mon Feb 19 10:58:56 2024] ? exit_to_user_mode_prepare+0x40/0x1e0
[Mon Feb 19 10:58:56 2024] ? syscall_exit_to_user_mode+0x2b/0x40
[Mon Feb 19 10:58:56 2024] ? do_syscall_64+0x6c/0xc0
[Mon Feb 19 10:58:56 2024] ? __x64_sys_ioctl+0x97/0xd0
[Mon Feb 19 10:58:56 2024] ? exit_to_user_mode_prepare+0x40/0x1e0
[Mon Feb 19 10:58:56 2024] ? syscall_exit_to_user_mode+0x2b/0x40
[Mon Feb 19 10:58:56 2024] ? do_syscall_64+0x6c/0xc0
[Mon Feb 19 10:58:56 2024] ? do_syscall_64+0x6c/0xc0
[Mon Feb 19 10:58:56 2024] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[Mon Feb 19 10:58:56 2024] RIP: 0033:0x7fa10903c51b
[Mon Feb 19 10:58:56 2024] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[Mon Feb 19 10:58:56 2024] RSP: 002b:00007fa1057ed830 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[Mon Feb 19 10:58:56 2024] RAX: ffffffffffffffda RBX: 000055dc939f48b8 RCX: 00007fa10903c51b
[Mon Feb 19 10:58:56 2024] RDX: 0000000000000000 RSI: 00000000000007d8 RDI: 000000000000000f
[Mon Feb 19 10:58:56 2024] RBP: 0000000000000000 R08: 0000000000000018 R09: 0000000000000000
[Mon Feb 19 10:58:56 2024] R10: 0000000000000031 R11: 0000000000000246 R12: 000000000000017c
[Mon Feb 19 10:58:56 2024] R13: 00007fa108e8a388 R14: 00007fa108e8a3a0 R15: 00007fa104ff1000
[Mon Feb 19 10:58:56 2024] </TASK>

 

 

I don't have any preference for Kali Linux I just use it for testing the final one will be probably the same as the host OS Devuan 5 on Devuan 5 with same kernel and everything, I doubt it would make a hell of a lot difference. Maybe there is a better machine type to use than pc-i440fx-3.1 🤔

 

 

0 Kudos