how do you reboot your linux VMs in hyper-v?
-
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#@*$%!
-
latest news: my pc with hyper-v correctly reboots everything! everytime! vene without latest kernel/hyper-v stuff in VM!
definitively a platform issue. last resort: reinstall all.
-
@matteo-nunziati said in how do you reboot your linux VMs in hyper-v?:
latest news: my pc with hyper-v correctly reboots everything! everytime! vene without latest kernel/hyper-v stuff in VM!
definitively a platform issue. last resort: reinstall all.
Are you running Server 2016 on your PC?
-
@dafyre said in how do you reboot your linux VMs in hyper-v?:
@matteo-nunziati said in how do you reboot your linux VMs in hyper-v?:
latest news: my pc with hyper-v correctly reboots everything! everytime! vene without latest kernel/hyper-v stuff in VM!
definitively a platform issue. last resort: reinstall all.
Are you running Server 2016 on your PC?
It's windows 10, so yes, in theory, it is the same hyper-v stack.
Honestly the only thing I can think of is issues with ACPI with the cpu. I've even disabled any energy saving but nothing!
if I keep the VM idling too much it stops and not reboots... any VM. -
LATEST NEWS:
yesterday, after a number of tests VM did freeze at reboot command rather than shutdown. As a last resort I've chosen to format SD/rest bios and restart from scratch.
My installation procedure did not work anymore... hell 2 times was right the third has failed...
called HPE this morning, they have asked me to do some tests via Intelligent Provisioning. IP. chrashed with missing linux kernel file (IP is based on linux)
they will start mobo substitution procedures tomorrow morning.
F*#@ wasted 15 days.
15 D.A.Y.S.
ever seen a failing server MOBO? I've. And I've provisioned just 3 servers in my life!
-
@matteo-nunziati that sounds like a pain. Hopefully the issue is resolved after the changes.
-
@Eltolargo said in how do you reboot your linux VMs in hyper-v?:
@matteo-nunziati that sounds like a pain. Hopefully the issue is resolved after the changes.
Hope so :s
-
OK,
some news here after full rebuild of server.
MOBO failure was an extra, still VMs do not reboot.
well, not exactly...
we have installed some windows core, some ubuntu bare server, some windows full gui, some ubuntu server with full MATE desktop.
now the "barebone" VMs do not reboot, they just shutdown.
The full bloated VMs restart nicely!I think this is something to do with the speed of the reboot cycle... but even my reseller tech ignores what to do... HPE is finally thinking to pass me to L2 support.
project is delayed at least of 1 week wrt deadlines (and I've kept 1 extra week at the time, just in case)
-
BOTTOMLINE: NEVER NEVER NEVER BUY HPE STUFF EVERMORE!!!
ALSO CHECK FOR LOCAL XEN SHOP: THERE MUST BE ONE!
(yeah I know, we can have remote management, but company is not ready for this, they want sys admin cell phone and they what to touch sys admin like a sky-alighting divinity)
-
@matteo-nunziati said in how do you reboot your linux VMs in hyper-v?:
(yeah I know, we can have remote management, but company is not ready for this, they want sys admin cell phone and they what to touch sys admin like a sky-alighting divinity)
You can do that with a remote company too. But calling someone's cell phone isn't professional and introduces a single point of failure.
-
@scottalanmiller said in how do you reboot your linux VMs in hyper-v?:
@matteo-nunziati said in how do you reboot your linux VMs in hyper-v?:
(yeah I know, we can have remote management, but company is not ready for this, they want sys admin cell phone and they what to touch sys admin like a sky-alighting divinity)
You can do that with a remote company too. But calling someone's cell phone isn't professional and introduces a single point of failure.
not my decision. I was going to settle with dell stuff with another reseller, offering help desk with SLA + 24/7 dell onsite. but they (company) wanted the sysadmin to be physical and periodically "visible"
