Solved Windows and Linux VM's stopped booting

J

jardows

I have a Linux Mint VM and a Windows 10 VM on my system. I intially configured the VM's with vm-bhyve, and have the uefi graphics options enabled. Currently running 14.1-RELEASE-p5. I moved offices and had the desktop computer powered off for a few weeks, but when I got connected back up, the VM's won't load up. When I start them, they are stuck at the beginnin, not even bringing up the UEFI boot environment. Using VNC, they are stuck at
Code: 
[    0.036198] __common_interrupt: 1.55 No irq handler for vector
The number at the beginning changes.
Previous to this, the VM's would take a couple minutes at this screen before proceeding with boot, now it appears to hang indefinitely.
I created a new Linux Mint VM, and the graphical install booted and ran flawlessly, but after the installation, it too has failed to boot.
Interestingly, I created a 64 bit Haiku VM with EFI boot, and it is starting without issue.

Anyone see this issue? It isn't like the commonly reported issue where the system cannot boot, it isn't even getting to the bootable part of the UEFI. I am not seeing anything in the logs for the VM's that show any errors. Here is the log for my last startup:

Code: 
Oct 02 15:59:33: initialising
Oct 02 15:59:33:  [loader: uefi]
Oct 02 15:59:33:  [cpu: 2,sockets=1,cores=2]
Oct 02 15:59:33:  [memory: 4G]
Oct 02 15:59:33:  [hostbridge: standard]
Oct 02 15:59:33:  [com ports: com1]
Oct 02 15:59:33:  [uuid: 72ed1026-80b7-11ef-a7aa-54bf649a3c23]
Oct 02 15:59:33:  [debug mode: no]
Oct 02 15:59:33:  [primary disk: disk0.img]
Oct 02 15:59:33:  [primary disk dev: file]
Oct 02 15:59:33: initialising network device tap0
Oct 02 15:59:33: adding tap0 -> vm-public (public addm)
Oct 02 15:59:33: bring up tap0 -> vm-public (public addm)
Oct 02 15:59:33: dynamically allocated port 5900 for vnc connections
Oct 02 15:59:33: booting
Oct 02 15:59:33:  [bhyve options: -c 2,sockets=1,cores=2 -m 4G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U 72ed1026-80b7-11ef-a7aa-54bf649a3c23]
Oct 02 15:59:33:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,nvme,/zroot/bhyve/mint22/disk0.img -s 5:0,virtio-net,tap0,mac=58:9c:fc:05:81:71 -s 6:0,fbuf,tcp=0.0.0.0:5900 -s 7:0,xhci,tablet]
Oct 02 15:59:33:  [bhyve console: -l com1,/dev/nmdm-mint22.1A]
Oct 02 15:59:33: starting bhyve (run 1)
 
A bit of an update. I installed a fresh copy of FreeBSD on a different computer, and am having the same problem booting new Windows or Linux VM's. I can't think I'm the only one having this problem. Any thoughts?
 
rootbert said:
please provide some information on your CPU
Click to expand...
First system is Intel i7-8700
dmesg info:
Code: 
CPU: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (3200.00-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x906ea  Family=0x6  Model=0x9e  Stepping=10
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x121<LAHF,ABM,Prefetch>
  Structured Extended Features=0x29c6fbf<FSGSBASE,TSCADJ,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE>
  Structured Extended Features2=0x40000000<SGXLC>
  Structured Extended Features3=0xbc002e00<MCUOPT,MD_CLEAR,TSXFA,IBPB,STIBP,L1DFL,ARCH_CAP,SSBD>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  IA32_ARCH_CAPS=0x2000c04<RSBA>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
Second system is Intel i7-10700
dmesg info:
Code: 
CPU: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (2900.00-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0xa0655  Family=0x6  Model=0xa5  Stepping=5
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x121<LAHF,ABM,Prefetch>
  Structured Extended Features=0x29c67af<FSGSBASE,TSCADJ,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE>
  Structured Extended Features2=0x40000018<PKU,OSPKE,SGXLC>
  Structured Extended Features3=0xbc000600<MCUOPT,MD_CLEAR,IBPB,STIBP,L1DFL,ARCH_CAP,SSBD>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  IA32_ARCH_CAPS=0xa0a0c2b<RDCL_NO,IBRS_ALL,SKIP_L1DFL_VME,MDS_NO>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
 
I've been able to do some more work on this today. By getting rid of vm-bhyve and using just command line arguments, I was able to create a new Windows VM, and it is consistently working. I am OK with using the bhyve command line instead of vm-bhyve. The Linux Mint VM is still having the same issue though. I have installed it with the following command:


Code: 
bhyve \
      -c 4,sockets=1,cores=4 \
      -s 0,hostbridge \
      -s 3,nvme,/usr/local/vm/mint/mint.img \
      -s 4,ahci-cd,/usr/local/vm/.iso/mint22.iso \
      -s 10,virtio-net,tap0 \
      -s 31,lpc \
      -s 29,fbuf,tcp=0.0.0.0:5900,w=1600,h=900,wait \
      -s 30,xhci,tablet \
      -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/usr/local/vm/mint/BHYVE_UEFI_VARS.fd \
      -m 8G -H -w -A \
      mint

This is successful, where I get to the Mint GRUB menu, can run from the .iso and install Mint into the drive. For run, I remove the line for the mint22.iso file, and after the TianoCore logo loads, the system gets stuck just like it had before.
 
Found the solution to the Linux Mint VM. Apparently it is a Linux problem across all types of VM hypervisors. I encountered the same issue trying to setup a Hyper-V VM as well.

The fix was that after the install, to stay withing the live environment, access the drive (by default mounted at /target) then edit the /boot/grub/grub.cfg file and the /etc/default/grub file. Find any instance of "quiet splash" and replace with "nomodeset"

So final resolution - not sure why I initially had problems with the Windows VM, but that seems to have sorted itself out. The issue with the Linux VM ends up being a problem with the Linux boot graphics setup, resolved by changing the behavior of grub. I would like to know why it suddenly quit working, but at this point I need to get back to actually using the things.
 
You must log in or register to reply here.
Back
Top