From owner-freebsd-virtualization@freebsd.org Sat Nov 7 11:51:10 2020 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C31B22ED529 for ; Sat, 7 Nov 2020 11:51:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CSwZQ4vShz4kGL for ; Sat, 7 Nov 2020 11:51:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id A66182ED528; Sat, 7 Nov 2020 11:51:10 +0000 (UTC) Delivered-To: virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A623D2ED587 for ; Sat, 7 Nov 2020 11:51:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CSwZQ4FjLz4kNh for ; Sat, 7 Nov 2020 11:51:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8519C5F59 for ; Sat, 7 Nov 2020 11:51:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 0A7BpAKs094039 for ; Sat, 7 Nov 2020 11:51:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 0A7BpAYD094038 for virtualization@FreeBSD.org; Sat, 7 Nov 2020 11:51:10 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 250802] bhyve exited with status 134 when GPU PCI passthrough Date: Sat, 07 Nov 2020 11:51:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bhyve X-Bugzilla-Version: 12.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mr.xanto@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2020 11:51:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250802 --- Comment #20 from mr.xanto@gmail.com --- (In reply to Konstantin Belousov from comment #19) I mean, that when bhyve process is aborted, bhyvectl return "VM: is n= ot created. I've wrote stupid script for get bhyvectl message before start and after cl= ose vm: #!/bin/sh echo "=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D" >> /mnt/Data/vm/win10/get.log date +"%Y.%m.%d - %X" >> /mnt/Data/vm/win10/get.log bhyvectl --vm=3Dwin10 --get-all >> /mnt/Data/vm/win10/get.log echo "=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D" >> /mnt/Data/vm/win10/get.log vm start win10 sleep 1 while pgrep bhyve >/dev/null; do date +"%Y.%m.%d - %X" >> /mnt/Data/vm/win10/get.log bhyvectl --vm=3Dwin10 --get-all >> /mnt/Data/vm/win10/get.log echo "=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D" >> /mnt/Data/vm/win10/get.log sleep 0.1 done sleep 1 date +"%Y.%m.%d - %X" >> /mnt/Data/vm/win10/get.log bhyvectl --vm=3Dwin10 --get-all >> /mnt/Data/vm/win10/get.log echo "=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D" >> /mnt/Data/vm/win10/get.log Result of work this script I've placed at https://yadi.sk/d/Xn3AFSoW_wDdRA bhyve log: Unhandled ps2 keyboard command 0x02 Unhandled ps2 keyboard command 0x02 Assertion failed: (pi->pi_bar[baridx].type =3D=3D PCIBAR_IO), function passthru_write, file /usr/src/usr.sbin/bhyve/pci_passthru.c, line 916. bhyve options: Nov 07 14:32:42: booting Nov 07 14:32:42: [bhyve options: -c 1 -m 3G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U 00dad61d-0d2e-11eb-936d-70f3951447ea -S] Nov 07 14:32:42: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,ahci,hd:/mnt/Data/vm/win10/disk0.img -s 5:0,virtio-net,tap0,mac=3D58:9c:fc:01:00:a8 -s 6:0,passthru,1/0 /0 -s 6:1,passthru,1/0/1] Nov 07 14:32:42: [bhyve console: -l com1,stdio] Nov 07 14:32:42: [bhyve iso device: -s 3:0,ahci-cd,/mnt/Data/vm/.config/null.iso] Nov 07 14:32:42: starting bhyve (run 1) Nov 07 14:33:40: bhyve exited with status 0 Nov 07 14:33:40: restarting Nov 07 14:33:40: [bhyve options: -c 1 -m 3G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U 00dad61d-0d2e-11eb-936d-70f3951447ea -S] Nov 07 14:33:40: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,ahci,hd:/mnt/Data/vm/win10/disk0.img -s 5:0,virtio-net,tap0,mac=3D58:9c:fc:01:00:a8 -s 6:0,passthru,1/0 /0 -s 6:1,passthru,1/0/1] Nov 07 14:33:40: [bhyve console: -l com1,stdio] Nov 07 14:33:40: [bhyve iso device: -s 3:0,ahci-cd,/mnt/Data/vm/.config/null.iso] Nov 07 14:33:40: starting bhyve (run 2) Nov 07 14:34:15: bhyve exited with status 134 Some explanations: first start of Windows guest after crash will be in diagnostic mode, and because I don't have console access to VM (as I understand, GPU pass through not compatible with "fbuf" options), then I've reset VM and when VM load, bhyve exited. --=20 You are receiving this mail because: You are the assignee for the bug.=