Home > Hyper-V, Virtualization, Windows 2008 R2 > TroubleShooting Hyper-V R2 Server Core

TroubleShooting Hyper-V R2 Server Core

Christian Decker from MS had published a very interesting article about Trouble Shooting Hyper-V R2 Server Core. hereunder translated version from it

So fast you go from PowerPoint to command shell …

This morning I notice that my SBS is no longer at home – in itself a problem, Hyper-V Manager access from your PC – nil (not connect) – perhaps one should take into account the home, which you mitgibt the partners and not the only domain controller on a domain-integrated Hyper-V host can run.

Say I’m sitting in front of a black command-line and should now find out why the virtual machine will not start …

Below is a list of commands, websites, etc. that have helped me:

http://technet.microsoft.com/de-at/library/cc753802 (WS.10). aspx

I was a big help – is a collection of the most important command-line commands that you need on a core server Sun
Here you will find useful things like read EventLog, etc …

$ config

Not finding quite easily – so you start the command menu, which comes at the start of the Hyper-V cores
(Does anyone know anyway – I do such again and again)

CoreConfig

The Core should be missing on any server
http://coreconfig.codeplex.com/

Connect to the server with other credentials

After the authentication on the DC had not worked, I installed a local administrator.
On the PC you can with
cmdkey / add: server / user: servername \ username / pass: password
authentication for connections to this computer indicate
Hyper-V Manager is not working, computer management already

Which virtual machines are all on the server and run this?

In CoreConfig I see these (and can also stop start /), at the Command Line does the following:
Thanks to Christopher for their support Wilfing

Start with powershell PowerShell
get-WmiObject-Query “Select * from MSVM_ComputerSystem” namespace “root \ virtualization” | ft health state, element name, operationalstatus

However, this was for my server, even though he had the status of “Pause”

Virtual machine start / stop

again in the Power Shell
$ Vm = Get-WmiObject namespace “root \ virtualization”-Query “Select * from MSVM_Computersystem Where ElementName =” Virt. Machine Name ‘”

then

$ Vm.RequestStateChange (x) change the status, where x can be:

2 = Turn on VM
3 = Turn off VM
10 = Hard Reset
32768 = VM Pauses
32 769 = Suspend VM

more information navigate to http://msdn.microsoft.com/en-us/library/cc723874 (v = VS.85). aspx

Conclusion:

* Domain-integrated Hyper-V without DC is difficult to maintain
* If the backup VHD as described in the last post set up, should be enough room for it anyway – otherwise will not boot the SBS
* The emergency actions you should consider BEFORE watch, test – 6 hours of arrest is not even really allowed for a private server …

As always – Comments, other best practices, etc. are always welcome!

Christian

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: