언어 설정

Menu
Sites
Language
Tizen studio 2.0, HAXM error after upgrading macOS high siera

I installed tizen studio 2.0 at macos siera and some days ago upgrading macOS High Siera.
And after upgrading macos high siera, emulator is not work well.

Then i re-install tizen studio 2.0, re-create vms... but now every time show the below capture shot.




This is vm's log
----------------------- log start --------------------------

13:41:30.407| 4266|I| main| 345|Start emulator...
qemu args: =========================================
"/Users/thinkbee/tizen-studio/platforms/tizen-4.0/tv-samsung/emulator/bin/emulator-x86_64" "-drive" "file=/Users/thinkbee/tizen-studio-data/emulator/vms/t-1121-1/emulimg-t-1121-1.x86,if=none,index=0,cache.no-flush=on,id=drive" "-device" "virtio-blk-pci,drive=drive" "-drive" "file=/Users/thinkbee/tizen-studio-data/emulator/vms/t-1121-1/swap-t-1121-1.img,if=none,index=1,id=swap" "-device" "virtio-blk-pci,drive=swap" "-enable-hax" "-device" "vigs,backend=gl,wsi=vigs_wsi,gl_version=2" "-device" "yagl,wsi=vigs_wsi,gl_version=2" "-smp" "4" "-m" "1024" "-device" "maru-virtual-tuner,system=ATSC,country=USA,table=/Users/thinkbee/tizen-studio-data/emulator/vms/t-1121-1/tuner_default.cfg,stillimg=/Users/thinkbee/tizen-studio/platforms/tizen-4.0/tv-samsung/emulator-resources/images,wsi=vigs_wsi" "-display" "maru_qt,forcelegacy,rendering=onscreen,resolution=1920x1080,dpi=72" "-net" "nic,model=virtio" "-net" "user" "-chardev" "file,path=/Users/thinkbee/tizen-studio-data/emulator/vms/t-1121-1/logs/emulator.klog,id=con0" "-device" "isa-serial,chardev=con0" "-device" "virtio-serial" "-L" "/Users/thinkbee/tizen-studio/platforms/tizen-4.0/tv-samsung/emulator/data/bios" "-kernel" "/Users/thinkbee/tizen-studio/platforms/tizen-4.0/tv-samsung/emulator/data/kernel/bzImage.x86" "-append" "vm_name=t-1121-1 video=LVDS-1:1920x1080-32@60 dpi=72 http_proxy= https_proxy= ftp_proxy= socks_proxy= host_ip=10.0.2.2 console=ttyS0 yagl=1 force_pat" "-device" "virtio-maru-tablet-pci" "-device" "virtio-maru-esm-pci" "-device" "virtio-maru-hwkey-pci" "-device" "virtio-maru-evdi-pci" "-device" "virtio-maru-keyboard-pci" "-rtc" "base=utc" "-M" "maru-x86-machine" "-soundhw" "all" "-usb" "-vga" "none" "-device" "maru-external-input-pci,stillimg=/Users/thinkbee/tizen-studio/platforms/tizen-4.0/tv-samsung/emulator-resources/images,wsi=vigs_wsi" 
====================================================
13:41:30.409| 4266|I| main| 348|qemu main start...
13:41:30.417| 4266|I|emul_state| 690|initial display resolution: 1920x1080
13:41:30.417| 4266|I|qt5_consol| 171|display density: 72
13:41:30.600| 4266|I|qt5_supple| 515|* Qt version (compile time): 5.6.0
13:41:30.601| 4266|I|qt5_supple| 516|* Qt version (runtime): 5.6.0
13:41:30.601| 4266|I|qt5_supple| 517|* working path: "/Users/thinkbee/tizen-studio/platforms/tizen-4.0/tv-samsung/emulator/bin"
13:41:30.601| 4266|I|qt5_supple| 518|* binary path: "/Users/thinkbee/tizen-studio/platforms/tizen-4.0/tv-samsung/emulator/bin"
13:41:30.601| 4266|I|qt5_supple| 519|* Qt plugin library path: ("/Users/thinkbee/tizen-studio/platforms/tizen-4.0/tv-samsung/emulator/bin")
13:41:30.609| 4266|I|qt5_consol| 153|Display Type: QT5 Onscreen
ram_size 0x40000000
Open the vm devcie error:(null)
Failed to create HAX VM
emulator-x86_64: Cannot initialize HAX.
Failed to create HAX VM.
See the emulator.log file for details.
13:41:30.616| 4266|I|qt5_msgbox| 69|qt5_msgbox starts... 
13:41:30.616| 4266|I|qt5_msgbox| 63|qt5_msgbox path : /Users/thinkbee/tizen-studio/platforms/tizen-4.0/tv-samsung/emulator/bin/qt5_msgbox
failed to initialize HAX: Invalid argument
13:41:30.618| 4266|I| main| 91|Exit emulator...
----------------------- end of log -----------------------

Responses

1 댓글
Yasin Ali

Hi,

You may try with re-installing standalone Intel® HAXM on macOS.
Check this site for guidance.
https://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-mac-os-x
Also check https://developer.tizen.org/development/tizen-studio/download/installing-tizen-studio/prerequisites
Section: Emulator Requirements
for details.

Hope your problem will be solved.