Hi all,
I have a really annoying problem with my home assistant virtual machine.
Im running this system on a Ubuntu 21.04 software together with VirtualBox VM.
The problem im facing is that recently my Home Assistant VM stops just minutes after booting but i can’t seem to find the reason why it’s doing this. I don’t know maybe there is somebody here that can take i look for, if you tell me what you need like log files or something, i can provide that.
Regards,
Jordy
You should probably start with the VirtualBox logs.
https://www.virtualbox.org/manual/UserManual.html#collect-debug-info
If I share my log files could you take a look because i really don’t have a clue where to look?
00:00:04.669730 GUI: 2D video acceleration is disabled
00:00:04.669919 GUI: HID LEDs sync is not supported on this platform
00:00:04.671239 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007f222b000000 w=1024 h=768 bpp=32 cbLine=0x1000 flags=0x0 origin=0,0
00:00:04.704242 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:04.816359 PS2K: Selected scan set 2
00:00:04.889585 ATA: LUN#2: EXECUTE DEVICE DIAGNOSTIC, status 00
00:00:04.943481 AHCI#0: Reset the HBA
00:00:04.943664 VD#0: Cancelling all active requests
00:00:05.479217 EFI: VBoxDbg> loadimage64 '.efi' 0x7dc85000 LB 0x71500
00:00:06.952281 EFI: VBoxDbg> loadimage64 '.efi' 0x1000000 LB 0x2628000
00:00:07.040511 EFI: debug point DXE_AP
00:00:07.178744 GIM: KVM: VCPU 0: Enabled system-time struct. at 0x000000007810b000 - u32TscScale=0xaaf0af98 i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x13a59e431 uVirtNanoTS=0xd1e73d6d TscKHz=1497599
00:00:07.179023 TM: Switching TSC mode from 'VirtTscEmulated' to 'RealTscOffset'
00:00:07.289918 GIM: KVM: Enabled wall-clock struct. at 0x000000007810a008 - u32Sec=1636830441 u32Nano=849939298 uVersion=2
00:00:07.290928 PIT: mode=2 count=0x4a9 (1193) - 1000.15 Hz (ch=0)
00:00:07.294885 EFI: relocate module to 0xfffffffefebc9000 from 0x7efc9000
00:00:07.295033 EFI: relocate module to 0xfffffffefebc8000 from 0x7efc8000
00:00:07.295159 EFI: relocate module to 0xfffffffefebc5000 from 0x7efc5000
00:00:07.295284 EFI: relocate module to 0xfffffffefebbc000 from 0x7efbc000
00:00:07.295431 EFI: relocate module to 0xfffffffefebbb000 from 0x7efbb000
00:00:07.295561 EFI: relocate module to 0xfffffffefebb8000 from 0x7efb8000
00:00:07.295690 EFI: relocate module to 0xfffffffefebb7000 from 0x7efb7000
00:00:07.295977 EFI: relocate module to 0xfffffffefebb6000 from 0x7efb6000
00:00:07.298200 IEM: rdmsr(0x140) -> #GP(0)
00:00:07.403713 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:07.405978 GIM: KVM: VCPU 1: Enabled system-time struct. at 0x000000007810b040 - u32TscScale=0xaaf0af98 i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x14ea39191 uVirtNanoTS=0xdf733d8c TscKHz=1497599
00:00:07.406682 IEM: rdmsr(0x140) -> #GP(0)
00:00:07.863901 OHCI: Software reset
00:00:07.865703 IEM: rdmsr(0x619) -> #GP(0)
00:00:07.865731 IEM: rdmsr(0x641) -> #GP(0)
00:00:07.934898 AHCI#0: Reset the HBA
00:00:07.934993 VD#0: Cancelling all active requests
00:00:07.961102 AHCI#0: Port 0 reset
00:00:07.999529 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:08.005599 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:08.300252 AHCI#0: Port 1 reset
00:00:08.302081 VD#0: Cancelling all active requests
00:00:08.762804 OHCI: USB Reset
00:00:08.938715 OHCI: Software reset
00:00:08.939215 OHCI: USB Operational
I have reinstalled the VBox machine running Hassio, hoping this would solve something
This didn’t help unfortunately
You really only have 8sec of logging?
Do you have other virtual machines working normally?
No i have more logging information, please follow this link to download it from my home synology NAS
I only have one virtual machine running and that is from HomeAssistant
is there somebody on the forum that could provide me some feedback, I struggle to find the reason why this keeps happening. I’m unable to use my home assistant for more then a couple hours and the suddenly the VM stops
I solved it by reinstalling Hassio, but this time removing Ubuntu from my Hassio PC and reinstalling Hassio with the Generic x86_64 image