After some trouble running VMware Player using VIX headless I get now this error:
~/VMware$ vmrun -T player start vmplayer.vmx nogui Message from syslogd@v22014041507617905 at Apr 17 09:43:12 ... kernel:[590498.736640] general protection fault: 0000 [#8] SMP Message from syslogd@v22014041507617905 at Apr 17 09:43:12 ... kernel:[590498.740029] Stack: Message from syslogd@v22014041507617905 at Apr 17 09:43:12 ... kernel:[590498.740029] Call Trace: Message from syslogd@v22014041507617905 at Apr 17 09:43:12 ... kernel:[590498.740029] Code: c5 e8 b8 15 cf e0 89 e8 48 3b 43 08 72 ec 48 89 df 5b 5b 5d e9 7f e9 d1 e0 41 5b 5b 5d c3 45 31 c0 89 f9 44 89 c0 44 89 c2 0f 32 <31> ff 41 89 c0 48 c1 e2 20 89 f8 4c 09 c2 48 89 16 c3 55 48 83 Error: Unknown error
/var/log/syslog contains following stacktrace:
Apr 17 09:43:12 v22014041507617905 kernel: [590498.736640] general protection fault: 0000 [#8] SMP Apr 17 09:43:12 v22014041507617905 kernel: [590498.737159] CPU 0 Apr 17 09:43:12 v22014041507617905 kernel: [590498.737262] Modules linked in: vmnet(O) parport_pc parport vsock(O) vmci(O) vmmon(O) fuse pci_stub ts_bm xt_string xt_length xt_dscp xt_comment xt_hl ip6t_rt xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_TCPMSS ip6t_LOG ipt_LOG ip6t_REJECT ipt_REJECT ip6table_mangle iptable_mangle xt_multiport xt_state xt_limit xt_conntrack nf_conntrack_ftp nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack ip6table_filter ip6_tables iptable_filter ip_tables x_tables nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop snd_pcm snd_page_alloc snd_timer snd psmouse processor i2c_piix4 i2c_core soundcore evdev serio_raw joydev pcspkr crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 aes_generic cryptd virtio_balloon thermal_sys button ext4 crc16 jbd2 mbcache usbhid hid sg sr_mod cdrom ata_generic virtio_blk virtio_net floppy uhci_hcd ehci_hcd ata_piix usbcore virtio_pci virtio_ring virtio usb_common libata scsi_mod [last unloaded: vmnet] Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] Pid: 5745, comm: vmware-vmx Tainted: G D O 3.2.0-4-amd64 #1 Debian 3.2.54-2 Bochs Bochs Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] RIP: 0010:[<ffffffffa03cd1ce>] [<ffffffffa03cd1ce>] HostIF_SafeRDMSR+0xd/0x1f [vmmon] Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] RSP: 0018:ffff8802b5d3bb30 EFLAGS: 00000246 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] RAX: 0000000000260d32 RBX: 0000000000000001 RCX: 0000000000000480 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] RDX: 0000000000000000 RSI: ffff88040ccf5dd0 RDI: 0000000000000480 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] RBP: ffff88040ccf5dc0 R08: 0000000000000000 R09: ffff88040bf6e958 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] R10: 0000000000003246 R11: 0000000000003246 R12: 0000000000000000 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] R13: ffff88040ccf5dc0 R14: 00000000fffffff4 R15: 00000000025964e0 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] FS: 00007f500a77e700(0000) GS:ffff88041fc00000(0000) knlGS:0000000000000000 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] CR2: 0000000001403970 CR3: 000000039a9cc000 CR4: 00000000001406f0 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] Process vmware-vmx (pid: 5745, threadinfo ffff8802b5d3a000, task ffff8801c0141810) Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] Stack: Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] ffffffffa03cf807 ffff88040bf6e958 ffffffffa03cf77b 0000000002596480 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] 00000000000007f2 ffff88040bc6c380 ffffffffa03ccb65 ffff88040bc6c380 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] ffff8802b5d3bb88 ffff88040ccf5dc0 ffffffffa03d0926 0000000000000001 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] Call Trace: Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffffa03cf807>] ? Vmx86GetMSR+0x8c/0xa4 [vmmon] Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffffa03cf77b>] ? Vmx86EnableHVOnCPU+0xa9/0xa9 [vmmon] Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffffa03ccb65>] ? HostIF_CallOnEachCPU+0x12/0x2a [vmmon] Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffffa03d0926>] ? Vmx86_GetAllMSRs+0x23/0x3b [vmmon] Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffffa03cb143>] ? LinuxDriver_Ioctl+0x6c7/0xaec [vmmon] Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff810b60d4>] ? __generic_file_aio_write+0x248/0x278 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff810b4cd7>] ? find_get_page+0x40/0x62 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff811aacc9>] ? cpumask_any_but+0x24/0x37 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff81031a61>] ? flush_tlb_page+0x54/0x6f Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff810c2c15>] ? page_evictable+0xf/0x7b Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff810be88e>] ? __lru_cache_add+0x2b/0x51 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff810ce7cd>] ? set_pte_at+0x5/0x8 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff810cfefb>] ? do_wp_page+0x4a7/0x563 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff810d1768>] ? handle_pte_fault+0x739/0x79f Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff810de467>] ? free_pages_and_swap_cache+0x48/0x60 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff810ce865>] ? pte_offset_kernel+0x16/0x35 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff81352d18>] ? do_page_fault+0x30a/0x345 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffffa03cb579>] ? LinuxDriver_UnlockedIoctl+0x11/0x18 [vmmon] Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff81107e35>] ? do_vfs_ioctl+0x459/0x49a Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff81107ec1>] ? sys_ioctl+0x4b/0x72 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] [<ffffffff81354d92>] ? system_call_fastpath+0x16/0x1b Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] Code: c5 e8 b8 15 cf e0 89 e8 48 3b 43 08 72 ec 48 89 df 5b 5b 5d e9 7f e9 d1 e0 41 5b 5b 5d c3 45 31 c0 89 f9 44 89 c0 44 89 c2 0f 32 <31> ff 41 89 c0 48 c1 e2 20 89 f8 4c 09 c2 48 89 16 c3 55 48 83 Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] RIP [<ffffffffa03cd1ce>] HostIF_SafeRDMSR+0xd/0x1f [vmmon] Apr 17 09:43:12 v22014041507617905 kernel: [590498.740029] RSP <ffff8802b5d3bb30> Apr 17 09:43:12 v22014041507617905 kernel: [590498.783907] ---[ end trace 07511f52bf2ac3bf ]---
Note: same error trying to run as root.
I am using the following config file:
.encoding = "UTF-8" config.version = "8" virtualHW.version = "10" ide0:0.present = "TRUE" ide0:0.filename = "~/discs/VMware-Titan.vmdk" memsize = "3072" MemAllowAutoScaleDown = "FALSE" ide1:0.present = "TRUE" ide1:0.fileName = "~/X17-59886.iso" ide1:0.deviceType = "cdrom-image" ide1:0.autodetect = "TRUE" floppy0.present = "FALSE" ethernet0.present = "TRUE" usb.present = "FALSE" sound.present = "FALSE" displayName = "Titan" guestOS = "windows7" nvram = "someos.nvram" MemTrimRate = "-1" ide0:0.redo = "" ethernet0.addressType = "generated" ethernet0.connectionType = "nat" uuid.location = "56 4d 0d 92 c9 cd 3c 25-c5 bf 91 91 43 5d bf 33" uuid.bios = "56 4d 0d 92 c9 cd 3c 25-c5 bf 91 91 43 5d bf 33" ethernet0.generatedAddress = "00:0c:29:5d:bf:33" ethernet0.generatedAddressOffset = "0" tools.syncTime = "TRUE" ide1:0.startConnected = "TRUE" uuid.action = "create" checkpoint.vmState = "" tools.remindInstall = "TRUE" extendedConfigFile = "vmplayer.vmxf" numvcpus = "1" virtualHW.productCompatibility = "hosted" ;vhv.enable = "TRUE"
Starting row 33 is new stuff I tried from various google results, no changes. ~ is actually a full path of the home dir, just censored for the dump.
The server is running:
Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
Since this is a virtualized server via KVM not all CPU feature are avaible, this is what /proc/cpuinfo says:
| flags | : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c rdrand hypervisor lahf_lm xsaveopt fsgsbase smep erms |
So essencially VT-x is missing on this "Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz". I tried to ensure it doesn't try to run a 64bit guest, I just can't find any reasonable complete documentary on the config file to ensure it doesn't try it, just because it detects a 64bit CPU and assumes it supports VT-x even though it doesn't. I also know you should try to start 2 diffrent virtualizations within the same host, but could a parallel running QEMU (which is working, but pretty slow, I had hoped VMware would run faster) doesn't block something on the kernel, but I thought since QEMU without KVM is just a emulation, it shouldn't make any troubles, but I can't confirm that for a few more hours and I'd really like to see if VMware was running much better. VirtualBox was also running stable on this condition, however it had like 10% of the performance of a bare QEMU emulation, so it was totally useless for our case (which is running a Team Foundation Server 2010 that requires an IIS and MSSQL service on Win Vista or above).
Can you give us any hints on the error or the configuration?
Update: QEMU is unrelated to that error, I just had the opportunity to verify that.