[Bug 271782] VM crashes with: bhyve exited with status 0
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 271782] VM crashes with: bhyve exited with status 0"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 271782] VM crashes with: bhyve exited with status 0"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 271782] VM crashes with: bhyve exited with status 0"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 271782] VM crashes with: bhyve exited with status 0"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 271782] VM crashes with: bhyve exited with status 0"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 271782] VM crashes with: bhyve exited with status 0"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 271782] VM crashes with: bhyve exited with status 0"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 02 Jun 2023 07:19:36 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271782 Bug ID: 271782 Summary: VM crashes with: bhyve exited with status 0 Product: Base System Version: 13.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bhyve Assignee: virtualization@FreeBSD.org Reporter: urtp5@yandex.by Good day! I have a machine AMD Ryzen 5 2600 Six-Core Processor + 32Gb RAM. OS: 13.2-RELEASE FreeBSD 13.2-RELEASE releng/13.2-525ecfdad In bhyve I have a Windows 2016 x64, and it has random crashes one time in 7-9 days. Please help me find reason of problem. Windows 2016 VM eventlog has only "critical problem possibly power fault" message /var/log/messages has no any related messages. In bhyve log I see such messages: -------------------------------------------------- Jun 02 10:12:10: bhyve exited with status 0 Jun 02 10:12:10: restarting Jun 02 10:12:10: [bhyve options: -c 4,sockets=1,cores=4 -m 12G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U 39387cd6-e074-11ed-9e3c-d8bbc11c8171] Jun 02 10:12:10: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,nvme,/mySSD/BHyVe/Win2016/disk0.img -s 5:0,virtio-net,tap1,mac=58:9c:fc:0c:3a:c7 -s 6:0,fbuf,tcp=0.0.0.0:5900 -s 7:0,xhci,tablet] Jun 02 10:12:10: [bhyve console: -l com1,/dev/nmdm-Win2016.1A] Jun 02 10:12:10: starting bhyve (run 9) There is config for that VM: ------------------------------------------------- loader="uefi" graphics="yes" xhci_mouse="yes" cpu=4 cpu_sockets=1 cpu_cores=4 memory=12G ahci_device_limit="8" network0_type="virtio-net" network0_switch="public" disk0_type="nvme" disk0_name="disk0.img" utctime="no" uuid="39387cd6-e074-11ed-9e3c-d8bbc11c8171" network0_mac="58:9c:fc:0c:3a:c7" there is bhyve-related packages: -------------------------------------------------- pkg info | grep -e "bhyve|vm" bhyve-firmware-1.0_1 Collection of Firmware for bhyve edk2-bhyve-g202202_10 EDK2 Firmware for bhyve grub2-bhyve-0.40_10 Grub-emu loader for bhyve uefi-edk2-bhyve-csm-0.2_4,1 UEFI EDK2 firmware for bhyve with CSM (16-bit BIOS) vm-bhyve-1.5.0 Management system for bhyve virtual machines And kldstat ------------------------------------------------- Id Refs Address Size Name 1 38 0xffffffff80200000 d5ca28 kernel 2 1 0xffffffff80f5d000 576280 vmm.ko 3 1 0xffffffff814d4000 582850 zfs.ko 4 2 0xffffffff81a57000 5c50 xdr.ko 5 1 0xffffffff81ee5000 3378 acpi_wmi.ko 6 1 0xffffffff81ee9000 3218 intpm.ko 7 1 0xffffffff81eed000 2180 smbus.ko 8 1 0xffffffff81ef0000 7638 if_bridge.ko 9 1 0xffffffff81ef8000 50d8 bridgestp.ko 10 1 0xffffffff81efe000 21db8 ipfw.ko 11 1 0xffffffff81f20000 21cc nmdm.ko 12 1 0xffffffff81f23000 4700 nullfs.ko 13 1 0xffffffff81f28000 3530 fdescfs.ko Thanks! -- You are receiving this mail because: You are the assignee for the bug.