• VM image stopped booting after system update


Please remember to read and follow the rules here.

Please Donate if you've found the website useful. Thanks.

 #24990  by bofe
 Sun Aug 13, 2017 9:16 am
I'm fairly sure my Sierra VM on Ryzen got updates and installed them last night, now it won't boot - is there an easy fix for this? Comparing a working log file from 2 days ago to now, it seems to fork off after the two svga lines:
Code: Select all
2017-08-13T12:56:04.378+10:00| vcpu-0| W115: E1000: E1000RegisterCommon: invalid port 0x1fffc and/or size 1
2017-08-13T12:56:04.378+10:00| vcpu-0| W115: E1000: E1000RegisterCommon: invalid port 0x1fffd and/or size 1
2017-08-13T12:56:04.378+10:00| vcpu-0| W115: E1000: E1000RegisterCommon: invalid port 0x1fffe and/or size 1
2017-08-13T12:56:04.378+10:00| vcpu-0| W115: E1000: E1000RegisterCommon: invalid port 0x1ffff and/or size 1
2017-08-13T12:56:06.616+10:00| svga| I125: SVGA enabling SVGA
2017-08-13T12:56:06.633+10:00| svga| I125: SVGA-ScreenMgr: Screen type changed to RegisterMode
2017-08-13T12:56:06.650+10:00| vcpu-0| I125: Vix: [7672 vmxCommands.c:7301]: VMAutomation_HandleCLIHLTEvent. Do nothing.
2017-08-13T12:56:06.651+10:00| vcpu-0| I125: MsgHint: msg.monitorevent.halt
2017-08-13T12:56:06.651+10:00| vcpu-0| I125+ The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.
2017-08-13T12:56:06.651+10:00| vcpu-0| I125+ ---------------------------------------
2017-08-13T12:58:36.033+10:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.
Any ideas?

Thanks
This topic has 7 replies
You must be a registered member and logged in to view the replies in this topic.

 Advertising