The problem has been resolved by the release of VMware Workstation 11.1.3: $ sudo /etc/init.d/vmware status GTK-Message: could not load module 'canberra-gtk-module': libcanberra-gtk - module.so: Nao e possible open objetos compartilhado land: land UO diretorio nao sown py: 5489): Gtk-WARNING *: Nao faith possible service a tool of temas no module_path: "murrine" GTK-Message: could not load module '-gtk-module unity ": libunity-gtk - module.so: Nao e possible open land of objetos compartilhado: land UO diretorio nao found I've upgraded to Ubuntu 15.10 x 64, and now my computer does not open.
I used Ubntu 15.04 x 64 as the host for VMware Workstation 11 Pro.
SWAP FREE 3145727 12 GB 100% of TOTAL SWAPĬOMMITTED 967960 3.VMware Workstation 11 Pro doesn't work on Ubuntu 15.10 x 64. #3 do_async_page_fault at ffffffffae38cf85īt: cannot transition from exception stack to current process stack:Įxception stack pointer: ffff8db551507ef8 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 PID: 3424 TASK: ffff8db3dd9a9070 CPU: 1 COMMAND: "calico-node" On some of the VM, I tried to add swap right away.īut just now, two of the VM hanged and they are consuming 200% CPU on the host. Why there is no problem logged in the host? Is there any mechanism that could prevent or alert user about the problem?Ģ) Should Qemu stop starting VM with KVM if it had detected another Hypervisor is already running?
This description was edit because I found out it's a problem with co-existing VMWARE Workstation and KVM.ġ) It is suspected that the processes for Qemu may have corruption when both hypervisor are running. Modules linked in: sunrpc dm_mirror dm_region_hash dm_log dm_mod i2c_i801 iTCO_wdt pcspkr iTCO_vendor_support crc32_pclmul ghash_clmulni_intel sg joydev lpc_ich aesni_intel lrw ppdev gf128mul glue_helper ablk_helper snd_hda_codec_generic cryptd snd_hda_intel snd_hda_codec snd_hda_core virtio_balloon snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore virtio_rng parport_pc parport binfmt_misc ip_tables xfs libcrc32c sr_mod cdrom qxl ahci virtio_console virtio_blk libahci drm_kms_helper crct10dif_pclmul crct10dif_common libata crc32c_intel serio_raw syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm virtio_net net_failover failover virtio_pci virtio_ring virtio drm_panel_orientation_quirks ptp_kvm ptp pps_core
BUG: unable to handle kernel paging request at ffffffffa9384750 For some cases, I haven't installed installed any Kubernetes packages.
The guest VMs are going to install Kubernetes, so there is no swap. Start some VM with both KVM and VMware workstation. Version-Release number of selected component (if applicable): If those processes are started, it would likely crash the KVM guest. For Qemu guests, they could run with KVM acceleration, but those guestsĬould not start docker or cri-o. But the speed for Qemu guests would be very slow.ģ) Vmware workstation is running. For Qemu guests, they need to run without KVM acceleration. Only run VM with KVM.Ģ) VMware workstation is running. These are some conditions would not crash KVM:ġ) VMware workstation is stopped. Then the guests in KVM would crash or freeze frequently. It is found that when VMware Workstation is running with their VM guests, A few days ago, I try to use some VM on Qemu (with KVM acceleration)īut many guest using KVM have hang or crash frequently. I am using VMware Workstation and Qemu on the host machine. On Fedora 32, using kernel from 5.6 to 5.8 on the host.