Eu tenho um VPS hospedado (Windows Server 2012) e desligá-lo no hypervisor faz com que o seguinte evento crítico na exibição do sistema dos logs do Windows:
> Log Name: System Source: Microsoft-Windows-Kernel-Power Date:
> 4/13/2015 12:05:28 PM Event ID: 41 Task Category: (63) Level: Critical
> Keywords: (2) User: SYSTEM Computer: ********** Description: The
> system has rebooted without cleanly shutting down first. This error
> could be caused if the system stopped responding, crashed, or lost
> power unexpectedly. Event Xml: <Event
> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System> <Provider Name="Microsoft-Windows-Kernel-Power"
> Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID>
> <Version>3</Version> <Level>1</Level> <Task>63</Task>
> <Opcode>0</Opcode> <Keywords>0x8000000000000002</Keywords>
> <TimeCreated SystemTime="2015-04-13T10:05:28.557824700Z" />
> <EventRecordID>594549</EventRecordID> <Correlation /> <Execution
> ProcessID="4" ThreadID="8" /> <Channel>System</Channel>
> <Computer>**********</Computer> <Security UserID="S-1-5-18" />
> </System> <EventData> <Data Name="BugcheckCode">239</Data> <Data
> Name="BugcheckParameter1">0xfffffa8007110700</Data> <Data
> Name="BugcheckParameter2">0x0</Data> <Data
> Name="BugcheckParameter3">0x0</Data> <Data
> Name="BugcheckParameter4">0x0</Data> <Data
> Name="SleepInProgress">0</Data> <Data
> Name="PowerButtonTimestamp">0</Data> <Data
> Name="BootAppStatus">0</Data> </EventData> </Event>
Há informações sobre o evento (41) aqui:
link
E informações sobre a verificação de bugs aqui (239 = 0xEF):
link
Este evento foi acionado conectando meu VPS a uma segunda rede ethernet.
Eu relatei isso à festa de hospedagem e eles me garantiram que:
"this is a normal event when a VPS is shutdown in the hypervisor"
Eles são um provedor muito confiável, então estou inclinado a acreditar neles, mas não inteiramente certo também. Então, minha pergunta é: esse evento é preocupante ou normal nesse cenário?
--- UPDATE do hoster (transip.nl)
The message "The System Has rebooted without cleanly shutting down
first. This error Could be Caused if the system stopped responding,
crashed, or solves power unexpectedly." is logical.
For we have no access to the OS itself and therefore can not perform a
reboot from there, we do this by switching off the VPS in the
hypervisor what indeed will cause yields such a report.
Depois de insistir em elobarating:
Well, I really can not give you another answer. When you add VPS to a
private network or remove it, or when you restart it via the console
then this will never yield a "clean shutdown".
If we were to do so, then in case of a kernel panic or another critical
problem within the OS, then it could not re-start, because it would not
respond to this command.
UPDATE Depois de compartilhar a opção ACPI:
ACPI would indeed be a possibility, if it weren't for the fact that
this would require a daemon running within the OS and therefore
customers would always have the option to turn it off . In addition,
this would have no effect in case of a Kernel Panic / BSOD because the
daemon in the OS is also stalled.
It would not give us any guarantee that a shutdown / reboot is
actually executed and that would make the 'reset ' option rather
unreliable.