how do you reboot your linux VMs in hyper-v?
-
@matteo-nunziati said in how do you reboot your linux VMs in hyper-v?:
@scottalanmiller said in how do you reboot your linux VMs in hyper-v?:
I've not heard of anyone having this issue. You might have something unique here.
yes. until it was ubuntu I was thinking about something strange in the vUEFI. but even win over win...
If the VM does not start at all, then what is in the container won't be the issue.
-
mmm... got this:
Restart-VM -Name zi-erp-as Confirm Are you sure you want to restart virtual machine "zi-erp-as"? [Y] Yes [A] Yes to All [H] Halt Command [?] Guida (il valore predefinito è "Y"): Restart-VM : 'zi-erp-as' failed to change state. + CategoryInfo : NotSpecified: (:) [Restart-VM], VirtualizationException + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.RestartVMAnd the machine just stops.
Now performed a sequence of start-restart with no idle, just waiting in VM Manager to see the CPU go down and then fire the restart. So far so good... really weird. Let's the VM stay idle for a while and retry!
Yep! if the machine stays idle for a few tens of seconds everything go nuts:
Restart-VM -Name zi-erp-as Confirm Are you sure you want to restart virtual machine "zi-erp-as"? [Y] Yes [A] Yes to All [N] No [L] No to All [?] Guida (il valore predefinito è "Y"): Restart-VM : 'zi-erp-as' failed to change state. + CategoryInfo : NotSpecified: (:) [Restart-VM], VirtualizationException + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.RestartVMNot this specific error but when people get this "change state" suggestions are to rebuild the machine
but those are all brand new.Apparently this is not the case with:
Stop-VM -Name zi-erp-as; Start-VM -Name zi-erp-asBut this is a no go for remote administration from within the VM. Need to sort this out
-
even tested a gen1 VM: not different.
-
ok, just got that Restart-VM does an hard restart (removes the plug). just forget it!
still missing an answer... -
So just the fact that you are running it as a VM makes all the difference?
If you run it on hardware, can you reboot normally?
Is it just with Hyper-V? Have you tried it on other hypervisors?
What happens if you install the latest actual LIS drivers from Microsoft?:
https://www.microsoft.com/en-us/download/details.aspx?id=51612 -
I never have any problems. I just did this.
Hyper-V Server 2012 R2 with a CentOS 7 guest in a Gen 2 VM.
Windows PowerShell Copyright (C) 2014 Microsoft Corporation. All rights reserved. PS C:\Users\user> Restart-VM -Name Zabbix Confirm Are you sure you want to restart virtual machine "Zabbix"? [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): y
-
Try following these instructions:
https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/supported-ubuntu-virtual-machines-on-hyper-v -
@Tim_G said in how do you reboot your linux VMs in hyper-v?:
So just the fact that you are running it as a VM makes all the difference?
If you run it on hardware, can you reboot normally?
you mean linux or windows? well yes never got issues on HW. but don't know on THIS HW!
Is it just with Hyper-V? Have you tried it on other hypervisors?
same linux machines on kvm run perfectly and autoreboot at every update
What happens if you install the latest actual LIS drivers from Microsoft?:
https://www.microsoft.com/en-us/download/details.aspx?id=51612ubuntu has them built in. windows vms don't need...
I was thinking about reboot my win10 machine with hyperv and test there...
-
Do you have the Linux Hyperv Agent updated?
https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/supported-ubuntu-virtual-machines-on-hyper-v -
@black3dynamite @Eltolargo @Tim_G latest kernel and tools are installed from the HWE stack. this doesn't help. just tried again from a VPN to my office. Also hell win2012r2 doesn't reboot in hyper-v 2016.
monday I'll reboot the server from within the server room, with a monitor attached. let see if something strange happens even at hw level... -
This post is deleted! -
@matteo-nunziati said in how do you reboot your linux VMs in hyper-v?:
nday I'll reboot the server from within the server room, with a monitor attached. let see if something strange happens even at hw level...
Looks as if there is more issues with that server than just VMs restarting. Are there any pending updates on it?
-
@Eltolargo no just a windows defender update pending. server has been restarted after last update batch.
looking now at ubuntu VM in the last reboot I see this:
reboot system boot 4.8.0-41-generic Sat Mar 25 18:21 still running reboot system boot 4.8.0-41-generic Sat Mar 25 18:48 still running reboot system boot 4.8.0-41-generic Sat Mar 25 15:15 still running reboot system boot 4.8.0-41-generic Sat Mar 25 15:11 - 15:14 (00:03) reboot system boot 4.8.0-41-generic Sat Mar 25 15:10 - 15:11 (00:00) reboot system boot 4.4.0-66-generic Sat Mar 25 15:00 - 15:11 (00:10)3 sessions still running! bah this is for sure something broken...
-
You have never shown your Hyper-V configuration.
-
@JaredBusch yes... Err... what conf? The vm conf (always the same) or the hypervisor itself?
-
Disabled hyperv time services and forced linux rtc to utc. Now monitoring drifts ( never say never). but win2012r2... Don't know..
-
@matteo-nunziati said in how do you reboot your linux VMs in hyper-v?:
ubuntu has them built in. windows vms don't need...
I know it's built in. But I would still try the latest from Microsoft as a troubleshooting step.
-
@Tim_G
The downloads from Microsoft is for Red Hat and CentOS. For Ubuntu, installing linux-virtual package is all that is needed. -
@black3dynamite said in how do you reboot your linux VMs in hyper-v?:
@Tim_G
The downloads from Microsoft is for Red Hat and CentOS. For Ubuntu, installing linux-virtual package is all that is needed.Ah that's right!
-
OK now I've eliminated some drifting in RCT <- yes RCT. I've monitored both gen1 and gen2 vm for something like 12 hours. no drift in 12 hours of VM idling.
this doesn't solve the thing: issued a reboot. got a shutdown! but at least without timing integration services now clocks seems logic in the VMs. I think even @JaredBusch got issues with timing and constant time reassignments...
I've also rebooted the server from the closet, nothing strange in the reboot sequence: all ok with the hypervisor. I've a new win update. let's apply this. also let's check the "latest" HPE service pack from october 2016, maybe some driver is apparently ok, but requires update...
bah. I'm going to think it's me. I'm cursed w/ hpe stuff.
A last thing remains: enter bios disable power savings and CPU c-states and let's see... then I'll STONITH my self
f#@*$%!
