What Are You Doing Right Now
-
@travisdh1 said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@rojoloco said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
Trying to focus on my work while it snowing (quite beautifully) outside and my complex tries to keep up with the snow with their snowplows, on top of the abnormal amount of dump truck traffic that is coming from the new building being built. It is next to impossible to focus -_-.
Silly northerners.... snow means "no more work, no more school, party time!!!" down here. But we still think snow is special... y'all are too jaded on the white stuff.
That's not till we see somewhere between 2' - 3' at least. I'm not even in the snow belt where 3' overnight is a normal thing.
For us it's usually around 6-9 inches before work ceases. Until that point we really don't tend to care too much. 2 winters ago I drove an hour and a half every day (one way) to buffalo in a foot of snow every day ish.
You're just as crazy as I am! So long as my bumper is not acting as a snow plow, I can probably make it to where I'm going.
Haha yep, that's pretty much the concept. I have the luxury this winter season of working from home so I can't complain too much. But previous winters were always fun
-
@quixoticjeremy said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@rojoloco said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
Trying to focus on my work while it snowing (quite beautifully) outside and my complex tries to keep up with the snow with their snowplows, on top of the abnormal amount of dump truck traffic that is coming from the new building being built. It is next to impossible to focus -_-.
Silly northerners.... snow means "no more work, no more school, party time!!!" down here. But we still think snow is special... y'all are too jaded on the white stuff.
That's not till we see somewhere between 2' - 3' at least. I'm not even in the snow belt where 3' overnight is a normal thing.
For us it's usually around 6-9 inches before work ceases. Until that point we really don't tend to care too much. 2 winters ago I drove an hour and a half every day (one way) to buffalo in a foot of snow every day ish.
The last time it really snowed well in Texas was 2010. It took me 3 hours to drive a 1 hour commute because of like 4" of snow on the ground.
Back then, I couldn't work from home. Now I can.
-
@nerdydad lol Texas will do that for you. I don't know why but I like the snow, I'm a weirdo. I just need snow for the Christmas season. Not to mention I spent a large portion of my youth snowboarding.
-
@quixoticjeremy My wife has always wanted a white Christmas. Hopefully, some day, I can try to deliver on that dream.
-
@nerdydad We're even hit or miss up here on that one. Christmas is just early enough in our snow season that sometimes it's white, sometimes not. Usually we end up getting dumped on right around January 1st. Prior to January 1st it's more often that we'll get a few days of snow and then nothing for a few days (just enough for it to completely melt) and then get some more.
-
Yeah... it might flurry here tomorrow, so I'm expecting mass panic, whole state will declare a state of emergency, stores will be bare, etc. @dafyre and @EddieJennings know what I'm talking about.
-
@rojoloco lol I've heard stories of down south how slight flurries result in mass panic and no one being able to drive. It cracks me up.
-
@rojoloco said in What Are You Doing Right Now:
Yeah... it might flurry here tomorrow, so I'm expecting mass panic, whole state will declare a state of emergency, stores will be bare, etc. @dafyre and @EddieJennings know what I'm talking about.
Thats the same here too.
-
@quixoticjeremy said in What Are You Doing Right Now:
@rojoloco lol I've heard stories of down south how slight flurries result in mass panic and no one being able to drive. It cracks me up.
probably not exaggerations. People here go totally batshit at the first flake.
-
@rojoloco said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
@rojoloco lol I've heard stories of down south how slight flurries result in mass panic and no one being able to drive. It cracks me up.
probably not exaggerations. People here go totally batshit at the first flake.
You got your bread & milk for tomorrow?
-
@rojoloco said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
@rojoloco lol I've heard stories of down south how slight flurries result in mass panic and no one being able to drive. It cracks me up.
probably not exaggerations. People here go totally batshit at the first flake.
-
@dafyre said in What Are You Doing Right Now:
@rojoloco said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
@rojoloco lol I've heard stories of down south how slight flurries result in mass panic and no one being able to drive. It cracks me up.
probably not exaggerations. People here go totally batshit at the first flake.
You got your bread & milk for tomorrow?
Got both. And beer and liquor. I'm ready!
-
@dustinb3403 said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
I've about had it with Hyper-V.
Now what?
Yes details please.
They always just stop working out of nowhere when you are "using" it. I'm so sick of it.
If you set up some VMs on Hyper-V, and never touch anything again, it'll go forever.
But as soon as you spend time importing/exporting, replication, VM settings, etc for a while, the hypervisor just completely loses it's stability for no real reason... causing you to need to restart the HV management service. And then eventually, you'll get crap like this below that requires a reboot:
Failed to register the service principal name 'Microsoft Virtual System Migration Service'. Failed to register the service principal name 'Hyper-V Replica'. Failed to register the service principal name 'Microsoft Virtual Console Service'.I verified in AD they are registered, so I don't know wtf it's talking about. Though, I'm sure a reboot will make it all well again.
-
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
I've about had it with Hyper-V.
Now what?
Yes details please.
They always just stop working out of nowhere when you are "using" it. I'm so sick of it.
If you set up some VMs on Hyper-V, and never touch anything again, it'll go forever.
But as soon as you spend time importing/exporting, replication, VM settings, etc for a while, the hypervisor just completely loses it's stability for no real reason... causing you to need to restart the HV management service. And then eventually, you'll get crap like this below that requires a reboot:
Failed to register the service principal name 'Microsoft Virtual System Migration Service'. Failed to register the service principal name 'Hyper-V Replica'. Failed to register the service principal name 'Microsoft Virtual Console Service'.I verified in AD they are registered, so I don't know wtf it's talking about. Though, I'm sure a reboot will make it all well again.
"They" as in Hyper-V "just stops working" as in shits the bed for no goddamn reason.
Good to know.
-
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
I've about had it with Hyper-V.
Now what?
Yes details please.
They always just stop working out of nowhere when you are "using" it. I'm so sick of it.
If you set up some VMs on Hyper-V, and never touch anything again, it'll go forever.
But as soon as you spend time importing/exporting, replication, VM settings, etc for a while, the hypervisor just completely loses it's stability for no real reason... causing you to need to restart the HV management service. And then eventually, you'll get crap like this below that requires a reboot:
Failed to register the service principal name 'Microsoft Virtual System Migration Service'. Failed to register the service principal name 'Hyper-V Replica'. Failed to register the service principal name 'Microsoft Virtual Console Service'.I verified in AD they are registered, so I don't know wtf it's talking about. Though, I'm sure a reboot will make it all well again.
"They" as in Hyper-V "just stops working" as in shits the bed for no goddamn reason.
Good to know.
Yeah, exactly.
I'm using Hyper-V Manager on a Win10 VM on my laptop, doing a ton of VM work... nothing relating to the hypervisor... you know, just doing thing in the way it's designed...
Oh, how about it just decides to stop working? Sure why not! How about again? Sure! Oh what's that... now your on another Hyper-V hypervisor, how about that stops working too!
-
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
I've about had it with Hyper-V.
Now what?
Yes details please.
They always just stop working out of nowhere when you are "using" it. I'm so sick of it.
If you set up some VMs on Hyper-V, and never touch anything again, it'll go forever.
But as soon as you spend time importing/exporting, replication, VM settings, etc for a while, the hypervisor just completely loses it's stability for no real reason... causing you to need to restart the HV management service. And then eventually, you'll get crap like this below that requires a reboot:
Failed to register the service principal name 'Microsoft Virtual System Migration Service'. Failed to register the service principal name 'Hyper-V Replica'. Failed to register the service principal name 'Microsoft Virtual Console Service'.I verified in AD they are registered, so I don't know wtf it's talking about. Though, I'm sure a reboot will make it all well again.
"They" as in Hyper-V "just stops working" as in shits the bed for no goddamn reason.
Good to know.
Yeah, exactly.
I'm using Hyper-V Manager on a Win10 VM on my laptop, doing a ton of VM work... nothing relating to the hypervisor... you know, just doing thing in the way it's designed...
Oh, how about it just decides to stop working? Sure why not! How about again? Sure! Oh what's that... now your on another Hyper-V hypervisor, how about that stops working too!
haha.... out of curiosity are you sure this isn't an issue caused from network connectivity issues?
-
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
I've about had it with Hyper-V.
Now what?
Yes details please.
They always just stop working out of nowhere when you are "using" it. I'm so sick of it.
If you set up some VMs on Hyper-V, and never touch anything again, it'll go forever.
But as soon as you spend time importing/exporting, replication, VM settings, etc for a while, the hypervisor just completely loses it's stability for no real reason... causing you to need to restart the HV management service. And then eventually, you'll get crap like this below that requires a reboot:
Failed to register the service principal name 'Microsoft Virtual System Migration Service'. Failed to register the service principal name 'Hyper-V Replica'. Failed to register the service principal name 'Microsoft Virtual Console Service'.I verified in AD they are registered, so I don't know wtf it's talking about. Though, I'm sure a reboot will make it all well again.
"They" as in Hyper-V "just stops working" as in shits the bed for no goddamn reason.
Good to know.
Yeah, exactly.
I'm using Hyper-V Manager on a Win10 VM on my laptop, doing a ton of VM work... nothing relating to the hypervisor... you know, just doing thing in the way it's designed...
Oh, how about it just decides to stop working? Sure why not! How about again? Sure! Oh what's that... now your on another Hyper-V hypervisor, how about that stops working too!
haha.... out of curiosity are you sure this isn't an issue caused from network connectivity issues?
Positive.
It happens every time there's heavy Hyper-V work. Even in test environments, off domain, on their own network, etc...
When I deal with the VMs directly, like Remote Desktop or Remote Powershell INTO the VM itself, all is fine. The guests are perfectly stable, always. It's the hypervisor's hyper-v management service that always screws up when you are doing a lot of work. It's like it can't handle the stress.
-
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
I've about had it with Hyper-V.
Now what?
Yes details please.
They always just stop working out of nowhere when you are "using" it. I'm so sick of it.
If you set up some VMs on Hyper-V, and never touch anything again, it'll go forever.
But as soon as you spend time importing/exporting, replication, VM settings, etc for a while, the hypervisor just completely loses it's stability for no real reason... causing you to need to restart the HV management service. And then eventually, you'll get crap like this below that requires a reboot:
Failed to register the service principal name 'Microsoft Virtual System Migration Service'. Failed to register the service principal name 'Hyper-V Replica'. Failed to register the service principal name 'Microsoft Virtual Console Service'.I verified in AD they are registered, so I don't know wtf it's talking about. Though, I'm sure a reboot will make it all well again.
"They" as in Hyper-V "just stops working" as in shits the bed for no goddamn reason.
Good to know.
Yeah, exactly.
I'm using Hyper-V Manager on a Win10 VM on my laptop, doing a ton of VM work... nothing relating to the hypervisor... you know, just doing thing in the way it's designed...
Oh, how about it just decides to stop working? Sure why not! How about again? Sure! Oh what's that... now your on another Hyper-V hypervisor, how about that stops working too!
haha.... out of curiosity are you sure this isn't an issue caused from network connectivity issues?
Positive.
It happens every time there's heavy Hyper-V work. Even in test environments, off domain, on their own network, etc...
When I deal with the VMs directly, like Remote Desktop or Remote Powershell INTO the VM itself, all is fine. The guests are perfectly stable, always. It's the hypervisor's hyper-v management service that always screws up when you are doing a lot of work. It's like it can't handle the stress.
I should clarify that I'm dealing with 40-50 VMs per hypervisor in Hyper-V Manager... doing some migrations/replication/failover changes across a handful of hyper-v hypervisors.
-
It just feels like this shouldn't happen, ever. I'm managing VMs the way they're supposed to be managed, doing nothing it shouldn't be able to handle.
I don't use KVM this heavily, but I assume it woudln't be an issue there.
-
Speaking of KVM, just playing in a lab at the moment and trying to mount an ISO from my management VM into the kvm server, and not seeing a simple way to do that.
If anyone has any pointers, let me know.
