October 26, 20169 yr dear community I'm new to unRaid (i have latest version, 6.2) so please have patience with me. I have an old PC (dual core e8400 3GHz, asus x48 Rampage Formula with 8GB of ddr2) The CPU supports both vt-x and vt-d however the motherboard does not seem to support vt-d, but only vt-x (by enabling the vanderpool support option in bios). so far so good with unraid (enless options), and i was successfully able to create a VM machine with Ubuntu, access it via vnc, play a bit with the Ubuntu settings, but i haven't done yet something like a thorough testing to gain confidence that all is ok. But, when i'm trying to create a kali linux VM (v 2016.2), it fails to start with error: KVM internal error. Suberror: 1 emulation failure RAX=0000000000000016 RBX=0000000000000000 RCX=000000007e1ecff8 RDX=000000000000003f RSI=000000007e1ec838 RDI=000000007dfa9600 RBP=000000007dfa9600 RSP=000000007ff59af0 R8 =000000000001f800 R9 =000000007e1ec818 R10=00000000000000d4 R11=0000000000000200 R12=000000007dfa7180 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000 RIP=00000000000b0000 RFL=00010217 [----APC] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] CS =0038 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA] SS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] DS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] FS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] GS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT TR =0000 0000000000000000 0000ffff 00008b00 DPL=0 TSS64-busy GDT= 000000007fee67d8 00000047 IDT= 000000007f695018 00000fff CR0=80000033 CR2=0000000000000000 CR3=000000007fef8000 CR4=00000668 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000500 Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <ff> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff This is the startup command: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Kali Linux' -S -machine pc-q35-2.5,accel=kvm,usb=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/15f44a5e-5947-4fc8-230c-3fb70bfcd4b5_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 3072 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 15f44a5e-5947-4fc8-230c-3fb70bfcd4b5 -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Kali Linux/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 -device ich9-usb-uhci1,mastet,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0 -vnc 0.0.0.0:0,websocket=5700 -k en-gb -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x4 -msg timestamp=on Domain id=18 is tainted: high-privileges Domain id=18 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) I tried playing with params like type of machine (i440fx vs q35) and cpu mode (host passthrough e8400 vs qemu64) but it does not change a thing. Also, when creating the VM, i tried with different templates - Debian, Linux, and Ubuntu - but it did not help. What i am doing wrong? thank you
October 27, 20169 yr Author ok, i tried once again to create the VM, and this time i chose SeaBios. and... magic It worked without any issue... Problem with my previous troubleshooting attempts was that once the VM was created with default bios OVMF (and failed to start with the error in the original post) the option to change the bios was disabled. Now it's sorted out. hope this helps some other noobs
December 29, 20169 yr This was helpful, i couldnt understand why it wasnt booting which ISO did you download?
January 16, 20179 yr Author wow totally missed this one. i was using 2016.2, from the official site: https://www.kali.org/downloads/
Archived
This topic is now archived and is closed to further replies.