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.
-
@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.
-
@dustinb3403 said in What Are You Doing Right Now:
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.
If you have a cdrom already attached to your VM you can just mount it in KVM. I don't think you have to reboot for that.
-
St. Louis SpiceCorp tonight at Dave & Busters. Sponsored by HPE.
-
Fun times at the Peachtree Winds rehearsal.
-
@eddiejennings said in What Are You Doing Right Now:
Fun times at the Peachtree Winds rehearsal.
Do you see the Sage theme there?
-
Just back from the drive. Now I'm home alone for a week. But they took the Steam machine, so no video games here.
-
@scottalanmiller said in What Are You Doing Right Now:
Just back from the drive. Now I'm home alone for a week. But they took the Steam machine, so no video games here.
Play Steam on Deepin
it works well -
@scottalanmiller said in What Are You Doing Right Now:
Just back from the drive. Now I'm home alone for a week. But they took the Steam machine, so no video games here.
Time to purchase a ps4
-
@dustinb3403 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Just back from the drive. Now I'm home alone for a week. But they took the Steam machine, so no video games here.
Time to purchase a ps4
How about no.
