Changes between Version 20 and Version 21 of TipAndDoc/VM/NestedVMM


Ignore:
Timestamp:
Dec 6, 2015 1:00:19 AM (4 years ago)
Author:
mitty
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TipAndDoc/VM/NestedVMM

    v20 v21  
    157157 * Core i5(物理マシン)上のVMwareゲスト(Fedora 16)上でKVMを動かし、その上でDebian Installerが仮想化支援有効で動作している[[br]][[Image(vmware-kvm-vmx-enabled.png,33%)]] 
    158158  * 一番内側のVMで使用したiso => http://ftp.tsukuba.wide.ad.jp/Linux/debian/dists/stable/main/installer-amd64/current/images/netboot/ mini.iso 
     159 
     160 == VMware on KVM == 
     161 * M/B ASUS H97M-PLUS 
     162 * Core i7-4790 3.60GHz 
     163 * Arch Linux 4.2.5-1-ARCH x86_64 
     164 * qemu 2.4.1-1 
     165 * seabios 1.8.2-1 
     166 * libvirt 1.2.21-1 
     167 * VMware Workstation 12.0.0 build-2985596 
     168 * vmware-patch 12.0.0-4 (AUR) 
     169 
     170 === Host (L0) === 
     171 * /etc/libvirt/qemu/GUEST.xml 
     172{{{ 
     173  <cpu mode='host-model'> 
     174    <model fallback='allow'/> 
     175  </cpu> 
     176}}} 
     177  * Host (L0), KVM Guest (L1 Guest)のcpuinfoについは[#proccpuinfo]と同じ 
     178 
     179 === L1 Guest === 
     180 * /etc/modprobe.d/vmware.conf 
     181{{{ 
     182blacklist kvm 
     183blacklist kvm-amd   # For AMD CPUs 
     184blacklist kvm-intel # For Intel CPUs 
     185}}} 
     186 
     187 * .vmx 
     188{{{ 
     189virtualHW.version = "12" 
     190guestOS = "other-64" 
     191ide1:0.fileName = "/var/lib/libvirt/images/archlinux-2015.12.01-dual.iso" 
     192virtualHW.productCompatibility = "hosted" 
     193vhv.enable = "FALSE" 
     194disable_acceleration = "FALSE" 
     195monitor.virtual_mmu = "automatic" 
     196monitor.virtual_exec = "automatic" 
     197vmx.allowNested = TRUE 
     198}}} 
     199  * {{{vmx.allowNested = TRUE}}}がないとこうなる[[br]][[Image(vmware-nested-incompatible-hypervisior.png,33%)]] 
     200 
     201 === MONITOR PANIC === 
     202 * エラーで起動不能 
     203 * vmware.log 
     204{{{ 
     2052015-12-06T00:35:35.029+09:00| vmx| I125: VTHREAD pthread_setschedparam failed: Invalid argument 
     2062015-12-06T00:35:35.029+09:00| vcpu-0| I125: VTHREAD start thread 4 "vcpu-0" tid 1081 
     2072015-12-06T00:35:35.029+09:00| vcpu-0| W115: MONITOR PANIC: vcpu-0:VMM fault 13: src=MONITOR rip=0xfffffffffc48c706 regs=0xfffffffffc607e60 
     2082015-12-06T00:35:35.029+09:00| vcpu-0| I125: Core dump with build build-2985596 
     2092015-12-06T00:35:35.029+09:00| vcpu-0| W115: Writing monitor corefile "/home/mitty/vmware/arch/vmmcores.gz" 
     2102015-12-06T00:35:35.029+09:00| vcpu-0| W115: Dumping core for vcpu-0 
     2112015-12-06T00:35:35.029+09:00| vcpu-0| I125: Beginning monitor coredump 
     2122015-12-06T00:35:35.436+09:00| vcpu-0| I125: End monitor coredump 
     2132015-12-06T00:35:35.452+09:00| vcpu-0| W115:  
     2142015-12-06T00:35:35.452+09:00| vcpu-0| W115+ The core dump limit is set to ZERO; no core dump should be expected 
     2152015-12-06T00:35:35.493+09:00| vcpu-0| W115: Core dumped. 
     2162015-12-06T00:35:35.493+09:00| vcpu-0| I125: Core dump pipes to process /usr/lib/systemd/systemd-coredump %P %u %g %s %t %e, core file unreliable 
     2172015-12-06T00:35:35.493+09:00| vcpu-0| W115: A core file is available in "/home/mitty/vmware/arch/core.1082" 
     2182015-12-06T00:35:35.493+09:00| vcpu-0| I125: Msg_Post: Error 
     2192015-12-06T00:35:35.493+09:00| vcpu-0| I125: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-0) 
     2202015-12-06T00:35:35.493+09:00| vcpu-0| I125+ vcpu-0:VMM fault 13: src=MONITOR rip=0xfffffffffc48c706 regs=0xfffffffffc607e60 
     2212015-12-06T00:35:35.493+09:00| vcpu-0| I125: [msg.panic.haveLog] A log file is available in "/home/mitty/vmware/arch/vmware.log".   
     2222015-12-06T00:35:35.493+09:00| vcpu-0| I125: [msg.panic.requestSupport.withoutLog] You can request support.   
     2232015-12-06T00:35:35.493+09:00| vcpu-0| I125: [msg.panic.requestSupport.vmSupport.windowsOrLinux]  
     2242015-12-06T00:35:35.493+09:00| vcpu-0| I125+ To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu. 
     2252015-12-06T00:35:35.493+09:00| vcpu-0| I125+ You can also run the "vm-support" script in the Workstation folder directly. 
     2262015-12-06T00:35:35.493+09:00| vcpu-0| I125: [msg.panic.response] We will respond on the basis of your support entitlement. 
     2272015-12-06T00:35:35.493+09:00| vcpu-0| I125: ---------------------------------------- 
     2282015-12-06T00:36:01.708+09:00| vcpu-0| W115: Writing monitor corefile "/home/mitty/vmware/arch/vmmcores.gz" 
     2292015-12-06T00:36:01.708+09:00| vcpu-0| W115: Dumping core for vcpu-0 
     2302015-12-06T00:36:01.709+09:00| vcpu-0| I125: Beginning monitor coredump 
     2312015-12-06T00:36:02.145+09:00| vcpu-0| I125: End monitor coredump 
     232}}} 
     233 * [[Image(vmware-nested-MONITOR_PANIC.png,33%)]] 
     234 
    159235 = KVM = 
    160236 * KVMはH/W仮想化支援が必須