[Bug 256159] Windows10 with bhyve on i5-5200U can not boot

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256159

--- Comment #7 from Aleks Michajlow <alex at alexmihajlov.ru> ---
I download ISO from 
https://www.microsoft.com/de-de/software-download/windows10ISO
und start Virtual Machine with configuration

$ cat windows10.conf 
loader="uefi"
graphics="yes"
xhci_mouse="yes"
cpu=2
memory=4G
graphics_port="5900"
graphics_res="1024x768"
xhci_mouse="yes"
virt_random="yes"
debug="yes"
ahci_device_limit="8"
network0_type="e1000"
network0_switch="public"
disk0_type="ahci-hd"
disk0_name="disk0.img"
disk0_dev="image"
utctime="no"
uuid="3090c18f-02a8-4083-b857-6364eceb7eb6"
network0_mac="58:9c:fc:04:61:cb"

VM crached after run on step  "Press any key to boot from CD..." 

logs vm:
$ cat vm-bhyve.log 
May 28 16:57:44: generated static mac 58:9c:fc:04:61:cb (based on
'windows10:0:1622210264:0')
May 28 17:02:00: initialising
May 28 17:02:00:  [loader: uefi]
May 28 17:02:00:  [cpu: 2]
May 28 17:02:00:  [memory: 4G]
May 28 17:02:00:  [hostbridge: standard]
May 28 17:02:00:  [com ports: com1]
May 28 17:02:00:  [uuid: 3090c18f-02a8-4083-b857-6364eceb7eb6]
May 28 17:02:00:  [utctime: no]
May 28 17:02:00:  [debug mode: yes]
May 28 17:02:00:  [primary disk: disk0.img]
May 28 17:02:00:  [primary disk dev: image]
May 28 17:02:00: initialising network device tap2
May 28 17:02:00: adding tap2 -> vm-public (public addm)
May 28 17:02:00: bring up tap2 -> vm-public (public addm)
May 28 17:02:00: booting
May 28 17:02:00:  [bhyve options: -c 2 -m 4G -Hwl
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U
3090c18f-02a8-4083-b857-6364eceb7eb6]
May 28 17:02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s
4:0,ahci,hd:/vm/windows10/disk0.img -s 5:0,e1000,tap2,mac=58:9c:fc:04:61:cb -s
6:0,virtio-rnd -s 7:0,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s
8:0,xhci,tablet]
May 28 17:02:00:  [bhyve console: -l com1,/dev/nmdm-windows10.1A]
May 28 17:02:00:  [bhyve iso device: -s
3:0,ahci-cd,/vm/.iso/Win10_21H1_German_x64.iso,ro]
May 28 17:02:00: starting bhyve (run 1)
May 28 17:02:15: bhyve exited with status 134
May 28 17:02:15: destroying network device tap2
May 28 17:02:15: stopped

$ cat bhyve.log 
vm exit[0]
        reason          VMX
        rip             0x0000000001e50a67
        inst_length     2
        status          0
        exit_reason     2 (Triple fault)
        qualification   0x0000000000000000
        inst_type               0
        inst_error              0

-- 
You are receiving this mail because:
You are the assignee for the bug.