Ask Your Question

SilentM's profile - activity

2016-12-07 15:52:08 -0600 received badge  Famous Question (source)
2016-03-15 10:03:52 -0600 received badge  Popular Question (source)
2016-03-15 10:03:52 -0600 received badge  Notable Question (source)
2015-12-16 10:02:45 -0600 received badge  Enthusiast
2015-12-04 14:37:54 -0600 asked a question How to reboot a Windows instance stuck in BSOD when not responding to Soft/Hard reboot command

Hello, I am working as an IT Support agent and my client is using OpenStack Grizzly Bear I believe. We encounter a problem fairly often where a Windows 7 instance will get stuck in a BSOD screen. Clicking Soft Reboot or Hard Reboot from the administrative webpage will not reboot the instance. Unfortunately I do not have direct access to the RedHat server in which to run commands locally but I do have access to run openstack commands from windows powershell remotely. Are there any hidden commands in the OpenStack command line tool which can get these VMs unstuck and rebooted?

The BSODs are happening because the host is overloaded with more VMs than it should have which causes a CPU watchdog BSOD because the CPU on the client is not responding in time. Unfortunately the client refuses to add hosts or resources.

2015-12-04 14:37:54 -0600 asked a question How to reboot an instance in BSOD when it does not respond to hard reboot

Hello, I am working as an IT Support agent and my client is using OpenStack Grizzly Bear I believe. We encounter a problem fairly often where a Windows 7 instance will get stuck in a BSOD screen. Clicking Soft Reboot or Hard Reboot from the administrative webpage will not reboot the instance. Unfortunately I do not have direct access to the RedHat server in which to run commands locally but I do have access to run openstack commands from windows powershell remotely. Are there any hidden commands in the OpenStack command line tool which can get these VMs unstuck and rebooted?

The BSODs are happening because the host is overloaded with more VMs than it should have which causes a CPU watchdog BSOD because the CPU on the client is not responding in time. Unfortunately the client refuses to add hosts or resources.