Hyper-V guest NICs fail

So I got two new servers a Dell R620 and a R720 running Hyper-V on Windows 2012 R2 all clients on them are 2012 or 2012 R2.
All NICs are Broadcom NetXtreme, 2 quad port per server, I am currently running 15.6.0.10 drivers with 7.6.15 firmware on the R720 and 16.2.0.4 drivers and 7.8.16 firmware on the R620. No guest NICs are teamed.
In the last 2 weeks I had two guest NICs in hyper-v (with a few days between) on the R620 and 1 on the R720 fail to a point where the NIC cant communicate with the network, getting a 169.x.x.x IP address. I delete the NIC in the Virtual Switch Manager, re-add
it and everything is fine again. I don't allow the managing OS to share the network adapter, for the most part, I use 1 NIC per VM.
I recall this happening back with Hyper-V 2008 R2 as well, but generally at the time of a driver update or some sort of change. These Hyper-V hosts have no received any drivers, firmware or Microsoft updates anywhere around the time of these failures.
Any ideas?

Hi,
" In the last 2 weeks I had two guest NICs in hyper-v (with a few days between) on the R620 and 1 on the R720 fail to a point where the NIC cant communicate with the network, getting a 169.x.x.x IP address. "
It seems that there is a DHCP server in your LAN.
I would recommend you to do :
1. check if there is any new driver for your NICs
2. check whether mac address conflict exists .
3. disable the "save power " mode of your NIC
Best Regards
Elton Ji
If it is not the answer please unmark it to continue
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Server 2012 r2 Hyper-v guest network speed with 10 GB NIC's

Hi
Setting up a Server 2012 r2 Hyper-v host with an onboard 4 port 1 GB nic and a offboard dual port 10 GB nic. We are using the 1gb quad port for management. The 10 Gb we intend using for hyper-v guest use however we don't seem to be able to achieve very high
speeds though the 10 GB adapter when assigned to a virtual switch. Testing the 10 Gb nic from the host confirms that we can transfer/get 10 GB speeds. When assigned to a virtual switch however the speed drops to about 1-2 Gbps. Has anybody seen anything like
this ?. We've tried a variety of settings and i can confirm that the network traffic is using the 10 GB nic.

Hi,
I am almost certain what you see is by design. I don't want to go into to much detail because I'm in a bit of a hurry. But allow me to explain.
Suppose you have a 10Gb NIC interface and an multi-core CPU. When you have RSS (Receive-Side Scaling) disabled a single core can normally handing
around 2.5-4.3Gbps. When you enable RSS the data streams/traffic is spread across multiple cores.
But RSS is a network optimization feature for the Management OS, not for a vSwitch. Instead you should use VMQ (Virtual Machine Queuing). VMQ is
the equilavant of RSS, but then intended for VMs. But... there is a difference. VMQ does not spread single data streams/traffic across multiple cores. Instead is (dynamically) assigns each vmNIC its own core. So... you don't use multiple-cores at a time for
a single vmNIC. You can't use RSS and VMQ at the same time. Keep that in mind.
But... you can accomplish this by enabling vRSS as well. That's another story.
If you watch the following video, at the end you know all about VMQ.
Hyper-V dVMQ
http://www.hypervrockstar.com/tag/dvmq/
Boudewijn Plomp | BPMi Infrastructure & Security
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

Second drives on Hyper-V guests failing suddenly

In past 2 months or so, we have lost 3-4 Hyper-V guest systems that had a second drive attached via the virtual SCSI adapter. Up until this time, these servers have run flawlessly for 3 years+. The drives appear on the host, but if you try to access
them, they tell you that the disk cannot be found. However, the .vhd is full size and sitting in the SharedCluster storage folder where they belong.
Even if I create a new server or drive from scratch, in short order the second drive becomes unusable, even if I create it as an IDE device instead of SCSI.
I have 2 host servers running 2008 R2 Enterprise connected to a Equallogics SAN via iSCSI in a 2 node cluster.
Oddly, the boot drives seem to not have any issues, on old or new servers. It's only the second drive. Very odd, and scary. Any ideas out there?

Hi Kevin,
Please check the event log on each cluster node .
Have you restarted the cluster ?
Just one CSV ? I mean that the second drive and boot drive are not on the same LUN ?
Best Regards
Elton JI
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V Guest Cannot Find Host Domain Controller 2012 R2

Poweredge T320 server as a Domain Controller, file server and an EXCHANGE 2010 server. There are no other servers at the site.
DHCP is from the firewall.   The DC and the file server will be on the host.
The 2010 EXCHANGE server will be on the guest. The Hyper-V
2012 R2 server cannot see the Domain Controller on the host 2012 R2 server.
The Active Directory is requesting to be promoted to a Domain Controller.
I have a logical or physical error in the installation.
It is asking to promote the Hyper-V guest 2012 R2 to a Domain Controller.
I believe I should have only one Domain Controller in this application.
After the Hyper-V guest can see the host domain controller I will install EXCHANGE 2010.
This is a test environment, offsite.
NIC1 – Host IP:192.168.1.130, 255.255.255.0, Gateway:192.168.1.1, DNS:127.0.0.1
NIC2- Only Hyper-V switch checked
Virtual Switch: 192.168.1.140, 255.255.255.0, Gateway: Blank, DNS: Was 127.0.0.1 didn’t work so I pointed it to the host, 192.168.1.130, but that didn’t work either.
Host adapter: IP:192.168.1.150, 255.255.255.0, 192.168.1.1, DNS Pointing to HOST:162.168.1.130
Active Directory and DNS installed on the guest.
Removed IPv6 from both NICs without any change.
IPAM is not installed on the host or the guest.
Several articles in Internet search didn’t help.
Thanks for your help.

Hi Steve,
I suggest referring to the following links:
REMOTEFX, WINDOWS SERVER & HYPER-V SERVER
http://blogs.technet.com/b/puneetvig/archive/2011/04/21/remotefx-windows-server-amp-hyper-v-server.aspx
RemoteFX (with Hyper-V) is a serious business tool. For games.
http://blogs.technet.com/b/tristank/archive/2012/02/17/remotefx-with-hyper-v-is-a-serious-business-tool-for-games.aspx
Best Regards,
Vincent Wu
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

VSS timeouts on Hyper-V guest, Exchange Replication Service, CU5

I'm having a problem with a Hyper-V guest that is running Exchange 2013 CU5. I will say I have had issues with this VM since installing CU5.
Note: I am doing a backup from within the VM guest, not from the host.
The scheduled backup takes a long time to complete, an entire weekend to backup 150GB to an ISCSI disk. In addition the CPU time is very high (58%) while this is happening. Attempting to open the backup manager window consistently makes the CPU
time hit 99%. When this happens Outlook clients will fail. When backup manager opens it will continually say "Reading data; please wait..." If the backup manager happened to already been open, the backup job will say "Volume
1 0% of 4 volumes."
The processes taking up the CPU time are Microsoft Volume Shadow Copy Service (24%), Microsoft Block level backup service (62%) and virtual disk service (12%). Memory use always hovers around 65%. If I attempt to kill the processes with
task manager, there is no change. If I use the kill executable it will say the process is not running. I cannot stop the corresponding service either. I cannot stop the backup. I cannot query vss writer status. I cannot restart
the ISCSI service (device in use.) Restarting the NAS that contains the ISCSI target does nothing. The only recourse is to restart the server.
If I restart the server and start a backup fairly soon after, the backup completes normally, in about an hour. During a normal backup CPU usage is at about 30%. The Microsoft Volume Shadow Copy Service runs at 0% CPU time as well as the virtual
disk service. The Microsoft Block Level Backup Engine runs at 10% CPU time. The scheduled backup is set to start at 9:30pm. I have also tried changing backup times. If I restart the server at 4 am and do not run a manual backup, the
scheduled backup performs poorly.
After some digging I find these errors:
Log Name: Application
Source: MSExchangeRepl
Date: 10/14/2014 9:30:41 PM
Event ID: 2112
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User: N/A
Description:
The Microsoft Exchange Replication service VSS Writer instance 7a465f3f-25ba-45b2-952a-870a6ddc2f2b failed with error code 80070020 when preparing for a backup of database 'Mailbox Database 2123847568'.
Log Name: Application
Source: VSS
Date: 10/14/2014 9:30:41 PM
Event ID: 8229
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Description:
A VSS writer has rejected an event with error 0x00000000, The operation completed successfully.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
PrepareForBackup event
Context:
Execution Context: Writer
Writer Class Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
Writer Name: MSMQ Writer (MSMQ)
Writer Instance Name: MSMQ Writer (MSMQ)
Writer Instance ID: {b8ae6140-7fcb-427d-9493-e070221f752f}
Command Line: C:\Windows\system32\mqsvc.exe
Process ID: 1676
Log Name: Application
Source: MSExchangeRepl
Date: 10/14/2014 9:30:41 PM
Event ID: 2024
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User: N/A
Description:
The Microsoft Exchange Replication service VSS Writer (Instance 7a465f3f-25ba-45b2-952a-870a6ddc2f2b) failed with error 80070020 when preparing for a backup.
As you can see the errors happen almost immediately after the backup starts.
In addition the following VSSwriters show a last error "timed out"
Microsoft Exchange Writer
Com+ RegDB Writer
Shadow Copy Optimization Writer
Registry Writer
I will add also the following issues I have been experiencing ever since installing CU5:
1 Version buckets threshold easy reached. Had to modify threshold and set limits on email size. Sometimes still happens.
2 After a restart of the server, the server may have no, or limited connection to the network. It may or may not have an exclamation point on the network icon. If there is no exclamation point, it can ping other network resources, but inbound requests
and pings, will fail. The event log shows that the network should be available while booting, but it's not since it cannot communicate with active directory. The fix for this is to disable/enable the network adapter and then all is well.
I really need some help figuring this out. Again, never had an issue with this server prior to Exchange 2013 CU5 being installed.

Hi,
The reason I think it is Exchange related, is that from the error message it mentioned:
A VSS writer has rejected an event with error 0x00000000
And then it indicated it is "Microsoft Exchange Replication service VSS Writer".
The Microsoft Exchange Replication service VSS Writer (Instance 7a465f3f-25ba-45b2-952a-870a6ddc2f2b) failed with error 80070020 when preparing for a backup
Later I found this article:
How to turn on the Exchange writer for the Volume Shadow Copy service in Windows Small Business Server 2003
http://support2.microsoft.com/kb/838183/en-us
It mentioned that with turned on Exchange writer, we will fail to do system state backup and Exchange backup at a same time:
The Exchange writer may cause conflicts with the information store backup feature of the Backup utility. The information store backup feature uses online streaming to back up the Exchange databases. If the Exchange writer is registered, the Backup utility
may log errors if you try to back up the system state and the Exchange information store at the same time. (For example, the Backup utility may log Event ID 8019.)
In order to confirm if it is the cause, please test to:
1. Create a backup-once task to backup only a simple file - this is a quick test to confirm if Windows Server Backup is fine or not.
2. A second backup-once task to do a system state backup without any exchange related information.
3. If both failed, please test to disable Exchange Writer and redo test 1&2.
It will take us some time on doing these tests. The reason is to figure out if it is Exchange related or not. I'll continue discuss with you if any new clue is found.
If you have any feedback on our support, please send to [email protected]

Backing up Hyper-V Guests on Windows 8/8.1 Hosts?

Hi,
is there any way to get DPM to backup Hyper-V Guests hosted on Win8 (or 8.1) machines? Requirement comes from developer workstations that have local VMs for sharepoint development.
Unfortunately, DPM doesn't seem to "see" the HV Component when trying to select a win8 machine as a server.
Thanks, Martin

DPM 2012 can protect ONLY files at Windows 8 (8.1).
Support Matrix for DPM Protection
Have a nice day !!!

Which version of Ubuntu server is supported as win2012R1 Hyper-V guest ?

I tried to install latest stable Ubuntu to win2012R1 Hyper-V but failed.
Which version of Ubuntu server is supported as win2012R1 Hyper-V guest ?

Ubuntu 12.04 and 12.10
Ubuntu 13.04 and 13.10
http://technet.microsoft.com/library/cc794868%28WS.10%29.aspx
If youre getting correct answer please mark this reply as answer
Darshana Jayathilake

2008 r2 hyper-v guest with static IP always looses network connectivity after every restart - no problem with DHCP

Hello,
We are running 2008 R2 domain with one physical DC and other running in VM on Hyper-V host (2008 R2 Standard). The host has 4 NICs and is configured to use one physical NIC for itself (management) and the hyper-v guest is configured to use another dedicated/physical
NIC (through microsoft virtual switch) just for itself.
I noticed that after setting the hyper-v guest with a static IP address all works fine only until guest restart. When the guest boots up the IP address is still configured correctly in IPv4 properties, but there is no network connectivity at all and in fact
the guest shows running APIPA config in ipconfig /all output. That situation continues until I remove the virtual NIC from hyper-v guest, remove the virtual switch from dedicated NIC on host and then reconfigure it (using same settings as they were). very
annoying.
For time being I switched the virtual DC (problematic hyper-v guest) to a DHCP IP and configured DHCP server (running on physical DC machine, not on hyper-v host) to store a reservation for the hyper-v guest so it always gets the same "static"
IP configuration.
Is there some kind of a problem/bug with using static IP on (2008 R2) hyper-v guests? is there a hotfix for static IP config in hyper-v guest environment?
both 2008 R2 OSes (host and guest) are up to date with all updates (synced with Microsoft, not WSUS).

OK, I'm not at the office now, but took my time to test out the restart scenarios on problematic virtual guest remotely.
No dice, same as it was, everything works fine after guest has IP configured in DHCP mode (IP reservation of 192.168.1.5 for specific MAC address) and it doesn't work after restart in static IP mode (same address, works before restart of guest).
I also took "arp -a" outputs at each step from host server and that was always saying there is only a single host (192.168.1.5 = VDC = problematic virtual guest) assigned to that IP address and always with same MAC, so that pretty much rules out
ARP/MAC troubles and no issues with switches/routers getting spoofed. Problem is most likely with the virtual guest (WS2008R2) or within the host running same OS.
Here are outputs:
A) VDC has IP configured in DHCP mode - always same, survives through restart (all works)
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : CD.lan
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
Physical Address. . . . . . . . . : 00-15-5D-01-D3-00
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b9af:6679:3142:8799%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, January 30, 2014 5:34:48 PM
Lease Expires . . . . . . . . . . : Friday, February 07, 2014 5:35:26 PM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.4.5
DHCPv6 IAID . . . . . . . . . . . : 268440925
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6F-5F-C2-00-15-5D-01-D3-00
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.4.5
NetBIOS over Tcpip. . . . . . . . : Enabled
ARP -a output from host server at that time:
Interface: 192.168.1.4 --- 0xc
Internet Address Physical Address Type
192.168.1.5 00-15-5d-01-d3-00 dynamic
B) VDC has IP configured in static mode - BEFORE RESTART (all works)
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
Physical Address. . . . . . . . . : 00-15-5D-01-D3-00
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b9af:6679:3142:8799%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 268440925
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6F-5F-C2-00-15-5D-01-D3-00
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.4.5
NetBIOS over Tcpip. . . . . . . . : Enabled
ARP -a output from host server at that time:
Interface: 192.168.1.4 --- 0xc
Internet Address Physical Address Type
192.168.1.5 00-15-5d-01-d3-00 dynamic
C) VDC has the same IP configured in static mode - AFTER RESTART (no more network connectivity at all, LAN in Public zone)
Windows IP Configuration
Host Name . . . . . . . . . . . . : VDC
Primary Dns Suffix . . . . . . . : CD.lan
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : CD.lan
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
Physical Address. . . . . . . . . : 00-15-5D-01-D3-00
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b9af:6679:3142:8799%13(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.135.153(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 268440925
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6F-5F-C2-00-15-5D-01-D3-00
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.4.5
NetBIOS over Tcpip. . . . . . . . : Enabled
ARP -a output from host server at that time:
Interface: 192.168.1.4 --- 0xc
Internet Address Physical Address Type
192.168.1.5 00-15-5d-01-d3-00 dynamic
Throughout the testing, the hyper-v host IP configuration and IPconfig output was always staying same.
The Network Connection #2 is the only one the host uses (not shared with hyper-v guests).
The Network Connection #4 is assigned to Microsoft Virtual Switch hence why it doesn't show up in results, like below:
Windows IP Configuration
Host Name . . . . . . . . . . . . : HYPER-V
Primary Dns Suffix . . . . . . . : CD.lan
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : CD.lan
Ethernet adapter Local Area Connection 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter #3
Physical Address. . . . . . . . . : 9C-8E-99-52-15-91
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter #2
Physical Address. . . . . . . . . : 9C-8E-99-52-15-90
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::dc78:8a3b:38a5:7af3%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 312250009
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-67-52-8F-9C-8E-99-52-15-93
DNS Servers . . . . . . . . . . . : 192.168.4.5
192.168.1.5
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter
Physical Address. . . . . . . . . : 9C-8E-99-52-15-93
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
On Monday I will install more test guests in Hyper-V host (WS2008R2), in variety of flavors like 7x64, 8.1x64, ws2012r2, and see if they show similar problems with static IP configuration when utilizing a dedicated NIC from host server.
Don't get me wrong, I can live with virtual DC running on DHCP IP reservation (which is based on MAC), because the virtual DC pretty much requires a physical PDC (hosting also DHCP in my network) to be present for safety reasons ... however I prefer a static
IP configuration on all servers, hence my question and surprise why it doesn't work.

PXE Boot a Hyper V Guest - Not receiving a DHCP IP Address

Hello Everyone,
I am trying to PXE boot a Hyper V guest, but am not getting a DHCP IP Address. Eventually the DHCP query times out and loads into the guest OS I have manually installed. See the PXE Boot Screen below. When in the installed guest OS, I do receive
a DHCP IP address as shown below. I am utilizing the Legacy Network Driver. I don't think it is related to VLAN identifier, but tried with/without and still no go. Any ideas what could be preventing this? Please let me know.
PXE Boot Screen:
CLIENT MAC ADDR: 00 15 5D F2 99 0C GUID: B366BBA1-D503-4D64-A77E-77474F3A2193
DHCP.........-
PXE-E51: No DHCP or proxyDHCP offers were received.
DHCP IPCONFIG in Guest OS:
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . : mywork.com
   IPv4 Address. . . . . . . . . . . : 10.242.242.251
   Subnet Mask . . . . . . . . . . . : 255.255.255.128
   Default Gateway . . . . . . . . . : 10.242.242.129
Thanks,
Ron

Hi Ron,
A solution is provided in this thread. You may need to have a look on the steps below:
• PXE-E51: No DHCP or proxyDHCP offers were received.
The client did not receive any valid DHCP, BOOTP or proxyDHCP offers. To resolve this issue, check each of the following network configuration items:
DHCP services are not available on the network to which the PXE-enabled NIC is connected.
A DHCP proxy or IP helper address is not configured for the subnet on which the PXE client is connected.
The switch port connected to the PXE NIC is running Spanning Tree Protocol, EtherChannel Protocol, or Port Aggregation Protocol and is thus not activated immediately when a link is detected. This forces the DHCP request from the PXE client to timeout.
DHCP is available on the network, but PXE is not.
The network cable is not attached to the PXE-enabled NIC on the target server.
See: http://social.technet.microsoft.com/Forums/en-US/d06413a4-af2b-4736-a510-c0a68eb880cf/cannot-get-certain-machines-to-pxe-boot
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

Router cannot see Hyper-V Guest MAC address

Greeting,
I have been trying to build a server on Hyper-V, on a host running Windows Server 2012 R2, and a wireless adapter is used.
A virtual switch was created as external, connected to the host's wireless adapter.
The guest OS is Debian 7, and the problem is it's unable to use DHCP to connect to the internet.
I have to manually specific an IP address and the subnet mask in order to access the internet in the Guest OS, say 192.168.0.50. And I set port forward to this IP for external connection to the guest, but then sometimes I cannot connect; without doing anything
it restores the connection after a while. At the same time I am keeping the MSRDP connection to tthe host so the host has not lost connecting to the internet.
When the server on Guest is not accessible from the web, I can still connect to the server within the host machine by typing the lan IP of the guest: 192.168.0.50
On checking the router, I found that two IP address 192.168.0.50 (Guest OS) and 192.168.0.15 (Host) are sharing the same MAC address (of the wireless card). It means the MAC address of the Guest OS is not seen by the router, and I suppose this is the root
for the instability.
Would you have any ideas about the situation, and suggested solution?
Thank you.

An update to my issue:
Just realized the possible cause: the (freaking) router is dropping inactive machine.
Basically the DHCP issue is not solved, but it doesn't seem to be a cause after all, as long as I manually assign the IP it works, even having the 2 IPs with the same MAC on the ARP table on router. (Host connection drop has to be further investigated).
As I found that the loss of connection actually happens after a while I don't touch the web server on VM, the longer I leave it idle the more likely I cannot connect to it again. The situation is like a prolonged loading when trying to access a website,
where sometimes you can connect after a while, or you never.
What's weird is, if I somehow manage to connect to the idle VM server by multiple attempts, and that after I have restored the connection, I can reconnect to the server from another computer very quickly without any significant loading time.
On some quick searches, I found someone using Linksys router is suffering from a similar situation as I do:
http://serverfault.com/questions/522448/application-request-routing-on-a-hyper-v-guest-intermittently-stops
So what I can try are basically 3 ways
-Change the router, not viable as I don't own it.
-Insert a wireless bridge in between
-Do something with Debian, making it periodically generate network request to the internet to keep the connection alive
Any ideas about my observation, and maybe possible solutions?
Thank you for reading.

Hyper-V guest OS, keyboard does not work from console

Brief background:
I'm doing some lab environment testing with Storagecraft Shadowprotect backup for a client. We are backing up Hyper-V guest operating systems. For busines continuity, the backups can be spun up to Oracle VirtualBox VMs in the event of disaster,
but the backups can also be restored via their Headstart Restore tool to a VHD or VHDX. Right now, I'm using a Windows 7 x64 VM for the test backup.
Here is my current problem (for the moment, forget about the Storagecraft part). Once the VM is restored, I've lost access to the keyboard via Hyper-V console (the mouse does work, this allowed me to run the
on-screen keyboard so I could see what was going on, and then test via RDP). I can RDP to the VM and use the keyboard and mouse. I have a few unknown devices in the Device Manager that weren't there before. The processor also has a
"splat" (yellow triangle, exclamation point).
At this point, I don't want to troubleshoot the "why" (that will be another step), but I do wish to find out how to reinstall the necessary drivers to get the system working. I tried reinstalling the Hyper-V Integration Services, but the
VM says they are already installed. These can't be uninstalled via Control Panel. I've tried mounting the Hyper-V Integration Services and doing a right-click "Repair" using the msi in the Support folder (both the x86 and the amd64);
when I do this, it reports that the action is only valid for products that are currently installed. The same happens for an uninstall.
Does anyone have any ideas how I can get keyboard support back?
Everyone gets everything he wants. Me, I wanted to be a sysadmin. And for my sins --they made me one.

Hi Sir,
>> I have a few unknown devices in the Device Manager that weren't there before. The processor
also has a "splat" (yellow triangle, exclamation point).
For troubleshooting , please try to use Windows server backup to backup/restore VM to narrow it down .
In addition please try to use installation media to perform "in-place upgrade" to "repair"
that VM .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Purpose of 2nd guest NIC (10.10.10.21)?

Why are both guest NICs connected to NAT/vmnet1 (192.168.203.0/24)?
Although the 2nd guest NIC (eth1) is set to 10.10.10.21, it is connected to NAT/vmnet1 (192.168.203.0/24), not host-only /vmnet8 (10.10.10.0/24).
This was from a clean and completely default installation of the 2/10/2005 disk set on a WinXP host.

In my original post, I should have written vmnet1 for vmnet8 and vice-versa; otherwise, it is correct, and is consistent with what I've written here.
I made a virginal install using the default install options of the 2/10/2005 disk set Oracle Installer version of VMware Workstation 4.5.2 w/SLES9 on a fresh WinXP Pro SP2.
The Oracle Installer installed VMWare as follows (from screenshot of "Virtual Network Editor", "Summary" tab):
VMnet0 (Bridged)
VMnet1 (Host-only) 10.10.10.0
VMnet8 (NAT) 192.168.203.0
There is no 2nd NAT configured.
The Oracle Installer installed the guest machine (SLES9) as follows:
NIC1 is connected to NAT
NIC2 is connected to NAT
Hence, both NICs are connected to the same vmnet (VMnet8).
Within the guest machine, "ifconfig -a" reveals that
eth0 (NIC1) has address 192.168.203.21
eth1 (NIC2) has address 10.10.10.21
(Also virtual interface eth0:1 has 192.168.203.121)
eth1, however, has an IP address consistent with VMnet1, although it is attached to VMnet8.
In a cmd window on the host, running 'ping 192.168.203.21', 'ping 192.168.203.121' receive responses, but 'ping 10.10.10.21' does not.
If I interpret Saar's comments correctly, the network is misconfigured as installed. NIC2 should be attached to VMnet1, and VMnet1 should be changed to NAT from Host-only.
After moving NIC2 to VMnet1 (Host-only), all three of
'ping 192.168.203.21', 'ping 192.168.203.121', 'ping 10.10.10.21' receive responses.

New Windows server 2003 Hyper-V guest fails to boot

Hello,
I'm currently doing some virtualization experiments on my new server hardware. The host hardware is:
IBM x3650 M4
x2 Xeon E5-2609
32GB RAM
x2 480 GB SSDs
Server OS: Windows server 2012
I'd like to test some legacy app virtualization. I've configured a VM and have installed Windows server 2003. The install is done via DVD. The issue at hand is that after the initial installation, the server fails to boot. The VM goes into a reboot loop
and so far the only error logging I'm able to find is in the hosts event log.
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 7/8/2014 2:14:48 PM
Event ID: 18560
Task Category: None
Level: Critical
Keywords:
User: NT VIRTUAL MACHINE\A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D
Computer: CCSTS1.cnet2k.cornerstonecredit.net
Description:
'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
<EventID>18560</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-07-08T21:14:48.544007000Z" />
<EventRecordID>159</EventRecordID>
<Correlation />
<Execution ProcessID="1512" ThreadID="3536" />
<Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
<Computer>CCSTS1.cnet2k.cornerstonecredit.net</Computer>
<Security UserID="S-1-5-83-1-2698121124-1264104059-3615998341-769460811" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>LegacyTS</VmName>
<VmId>A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D</VmId>
<Rax>0x0</Rax>
<Rbx>0x0</Rbx>
<Rcx>0x0</Rcx>
<Rdx>0x0</Rdx>
<Rsp>0x804de00c</Rsp>
<Rbp>0x0</Rbp>
<Rsi>0x0</Rsi>
<Rdi>0x0</Rdi>
<R8>0x0</R8>
<R9>0x0</R9>
<R10>0x0</R10>
<R11>0x0</R11>
<R12>0x0</R12>
<R13>0x0</R13>
<R14>0x0</R14>
<R15>0x0</R15>
<Rip>0x80547c7c</Rip>
<Rflags>0x10046</Rflags>
<FpControlStatus>7F030000000000000000000000000000</FpControlStatus>
<XmmControlStatus>0000000000000000801F0000FFFF0000</XmmControlStatus>
<Cr0>0x8001003d</Cr0>
<Cr2>0x804ddffc</Cr2>
<Cr3>0xa02000</Cr3>
<Cr4>0x20</Cr4>
<Cr8>0xf</Cr8>
<Xfem>0x1</Xfem>
<Dr0>0x0</Dr0>
<Dr1>0x0</Dr1>
<Dr2>0x0</Dr2>
<Dr3>0x0</Dr3>
<Dr6>0xffff0ff0</Dr6>
<Dr7>0x400</Dr7>
<Es>0000000000000000FFFFFFFF2300F3C0</Es>
<Cs>0000000000000000FFFFFFFF08009BC0</Cs>
<Ss>0000000000000000FFFFFFFF100093C0</Ss>
<Ds>0000000000000000FFFFFFFF2300F3C0</Ds>
<Fs>00F0DFFF00000000FF1F0000300093C0</Fs>
<Gs>0000000000000000FFFFFFFF00000000</Gs>
<Ldtr>00000000000000000000000000000000</Ldtr>
<Tr>90685580000000006800000050008B00</Tr>
<Idtr>000000000000FF0700F4038000000000</Idtr>
<Gdtr>000000000000FF0300F0038000000000</Gdtr>
<Tsc>0x148e4294</Tsc>
<ApicBase>0xfee00900</ApicBase>
<SysenterCs>0x0</SysenterCs>
<SysenterEip>0x0</SysenterEip>
<SysenterEsp>0x0</SysenterEsp>
</VmlEventLog>
</UserData>
</Event>
My VM config
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<configuration>
<_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
<ChannelInstanceGuid type="string">{E4E9CD0E-4BBF-4C1B-B655-715781690655}</ChannelInstanceGuid>
</_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
<_7d80d3db-61ee-4879-8879-5609f1100ad0_>
<address type="string">5353,00000000,00</address>
<version type="integer">1</version>
</_7d80d3db-61ee-4879-8879-5609f1100ad0_>
<_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
<controller0>
<drive0>
<pathname type="string">E:\Hyper-V\VHD\LegacyTS.vhdx</pathname>
<pool_id type="string"></pool_id>
<type type="string">VHD</type>
</drive0>
<drive1>
<pathname type="string"></pathname>
<type type="string">NONE</type>
</drive1>
</controller0>
<controller1>
<drive0>
<pathname type="string">SCSI\CDROM&VEN_IBM_SATA&PROD_DEVICE_81Y3681\4&1864BF9E&0&010000</pathname>
<pool_id type="string"></pool_id>
<type type="string">ISO</type>
</drive0>
<drive1>
<pathname type="string"></pathname>
<type type="string">NONE</type>
</drive1>
</controller1>
<version type="integer">5</version>
</_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
<_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
<port0>
<connection type="string"></connection>
</port0>
<port1>
<connection type="string"></connection>
</port1>
<version type="integer">2</version>
</_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
<_8f0d2762-0b00-4e04-af4f-19010527cb93_>
<controller0>
<drive0>
<pathname type="string"></pathname>
<type type="string">VFD</type>
</drive0>
</controller0>
<version type="integer">1</version>
</_8f0d2762-0b00-4e04-af4f-19010527cb93_>
<_a80e9c62-750a-4a6b-9548-d46677e806be_>
<ChannelInstanceGuid type="string">{23c9c636-93de-4aec-9bef-220766177a24}</ChannelInstanceGuid>
<Connection>
<AltPortName type="string">Dynamic Ethernet Switch Port</AltPortName>
<AltSwitchName type="string">Intel(R) I350 Gigabit Network Connection - Virtual Switch</AltSwitchName>
<AuthorizationScope type="string"></AuthorizationScope>
<ChimneyOffloadWeight type="integer">0</ChimneyOffloadWeight>
<Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
<DisplayName type="string"></DisplayName>
<Flags type="integer">0</Flags>
<Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
<Data type="bytes">AAIAAGQAAAAAAAAAAQAAAAAAAAA=
</Data>
<Version type="integer">256</Version>
</Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
<Settings>
<Id type="string">97274751-A1EC-4DC2-941D-B7F9A1AED814</Id>
</Settings>
</Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
<Features>
<Id type="string">C885BFD1-ABB7-418F-8163-9F379C9F7166</Id>
</Features>
<HostResources>
<HostResource type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</HostResource>
</HostResources>
<PoolId type="string"></PoolId>
<PreventIPSpoofing type="bool">False</PreventIPSpoofing>
<TestReplicaPoolId type="string"></TestReplicaPoolId>
<TestReplicaSwitchName type="string"></TestReplicaSwitchName>
</Connection>
<FriendlyName type="string">Network Adapter</FriendlyName>
<IsConnected type="bool">True</IsConnected>
<MacAddress type="string">00-15-5D-01-18-02</MacAddress>
<MacAddressIsStatic type="bool">False</MacAddressIsStatic>
<PortName type="string">E7F02418-A1EB-4FF9-84F8-BF461B2D00C6</PortName>
<SwitchName type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</SwitchName>
<VpciInstanceGuid type="string">{E9444985-111B-404A-82FE-48608A397676}</VpciInstanceGuid>
</_a80e9c62-750a-4a6b-9548-d46677e806be_>
<_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
<base_board>
<serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
</base_board>
<bios_guid type="string">{B54BE7B5-05A4-4C4A-A2BD-D63272C7CCCD}</bios_guid>
<bios_serial_number type="string">9595-3600-2199-6834-7686-3927-30</bios_serial_number>
<boot>
<device0 type="string">Optical</device0>
<device1 type="string">HardDrive</device1>
<device2 type="string">Network</device2>
<device3 type="string">Floppy</device3>
</boot>
<chassis>
<asset_tag type="string">8437-8592-0329-9603-9215-1886-12</asset_tag>
<serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
</chassis>
<num_lock type="bool">False</num_lock>
<version type="integer">2</version>
</_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
<_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
<version type="integer">0</version>
</_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
<global_settings>
<devices>
<allow_reduced_fc_redundancy type="bool">False</allow_reduced_fc_redundancy>
<generation_id type="string">883d11122d9b7b2c521be0c045ef3760</generation_id>
<storage_allow_full_scsi_command_set type="bool">False</storage_allow_full_scsi_command_set>
</devices>
<disk_merge_pending type="bool">False</disk_merge_pending>
<metrics>
<devicetype>
<deviceinstance>
<guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">B637F347-6A0E-4DEC-AF52-BD70CB80A21D</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">3F6F1051-C8FC-47EF-9821-C07240848748;0</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
</devicetype>
<devicetype>
<deviceinstance>
<guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">394DCE66-458F-4895-AE56-41D7C9602A49</typecode>
<value type="integer">0</value>
</metric>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">FF85EA46-9933-4436-BE5D-C96827399966</typecode>
<value type="integer">0</value>
</metric>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">04BDF59E-580D-4441-8828-FFFE44472D2D</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
</devicetype>
<devicetype>
<deviceinstance>
<guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">70BB60D2-A9D3-46AA-B654-3DE53004B4F8</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">AD29978B-AAB6-44AE-81CD-0609BF929F18;0\0\L</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
</devicetype>
</metrics>
<owner>
<sid type="string">S-1-5-21-1940488291-1951097212-1584025624-1392</sid>
</owner>
<power>
<host_shutdown>
<action type="integer">1</action>
</host_shutdown>
<host_startup>
<action type="integer">1</action>
</host_startup>
</power>
<snapshots>
<list>
<size type="integer">0</size>
</list>
</snapshots>
<unexpected_termination>
<action type="integer">1</action>
</unexpected_termination>
<vhd_path_acled type="bool">True</vhd_path_acled>
</global_settings>
<manifest>
<size type="integer">11</size>
<vdev001>
<device type="string">58f75a6d-d949-4320-99e1-a2a2576d581c</device>
<flags type="integer">1</flags>
<instance type="string">58F75A6D-D949-4320-99E1-A2A2576D581C</instance>
<name type="string">Microsoft Synthetic Mouse</name>
</vdev001>
<vdev002>
<device type="string">197f74e3-b84b-46de-8ae6-82f1cd181cdc</device>
<flags type="integer">1</flags>
<instance type="string">197F74E3-B84B-46DE-8AE6-82F1CD181CDC</instance>
<name type="string">Microsoft Synthetic Keyboard</name>
</vdev002>
<vdev003>
<device type="string">f3cf6965-e8d3-44a9-9b7d-a04245ea7525</device>
<flags type="integer">1</flags>
<instance type="string">F3CF6965-E8D3-44A9-9B7D-A04245EA7525</instance>
<name type="string">Microsoft Synthetic Video</name>
</vdev003>
<vdev004>
<device type="string">84eaae65-2f2e-45f5-9bb5-0e857dc8eb47</device>
<flags type="integer">1</flags>
<instance type="string">84EAAE65-2F2E-45F5-9BB5-0E857DC8EB47</instance>
<name type="string">Microsoft Heartbeat Component</name>
</vdev004>
<vdev005>
<device type="string">2a34b1c2-fd73-4043-8a5b-dd2159bc743f</device>
<flags type="integer">1</flags>
<instance type="string">2A34B1C2-FD73-4043-8A5B-DD2159BC743F</instance>
<name type="string">Microsoft Key-Value Pair Exchange Component</name>
</vdev005>
<vdev006>
<device type="string">9f8233ac-be49-4c79-8ee3-e7e1985b2077</device>
<flags type="integer">1</flags>
<instance type="string">9F8233AC-BE49-4C79-8EE3-E7E1985B2077</instance>
<name type="string">Microsoft Shutdown Component</name>
</vdev006>
<vdev007>
<device type="string">2497f4de-e9fa-4204-80e4-4b75c46419c0</device>
<flags type="integer">1</flags>
<instance type="string">2497F4DE-E9FA-4204-80E4-4B75C46419C0</instance>
<name type="string">Microsoft Time Synchronization Component</name>
</vdev007>
<vdev008>
<device type="string">5ced1297-4598-4915-a5fc-ad21bb4d02a4</device>
<flags type="integer">1</flags>
<instance type="string">5CED1297-4598-4915-A5FC-AD21BB4D02A4</instance>
<name type="string">Microsoft VSS Component</name>
</vdev008>
<vdev009>
<device type="string">6c5addb9-a11a-4e8e-84cb-e6208201db63</device>
<flags type="integer">1</flags>
<instance type="string">6C5ADDB9-A11A-4E8E-84CB-E6208201DB63</instance>
<name type="string">Microsoft RDV Component</name>
</vdev009>
<vdev010>
<device type="string">2fc216b0-d2e2-4967-9b6d-b8a5c9ca2778</device>
<flags type="integer">1</flags>
<instance type="string">A80E9C62-750A-4A6B-9548-D46677E806BE</instance>
<name type="string">Synthetic Ethernet Port</name>
</vdev010>
<vdev011>
<device type="string">d422512d-2bf2-4752-809d-7b82b5fcb1b4</device>
<flags type="integer">1</flags>
<instance type="string">24984ED0-BDAD-4B90-82B2-5D59F874E91E</instance>
<name type="string">Synthetic SCSI Controller</name>
</vdev011>
<version type="integer">260</version>
</manifest>
<properties>
<global_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</global_id>
<highly_available type="bool">False</highly_available>
<last_powered_off_time type="integer">130493284127496105</last_powered_off_time>
<last_powered_on_time type="integer">130493284065876653</last_powered_on_time>
<last_state_change_time type="integer">130493284127496105</last_state_change_time>
<name type="string">LegacyTS</name>
<notes type="string"></notes>
<type_id type="string">Virtual Machines</type_id>
<version type="integer">1024</version>
</properties>
<settings>
<global>
<logical_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</logical_id>
</global>
<memory>
<bank>
<dynamic_memory_enabled type="bool">True</dynamic_memory_enabled>
<limit type="integer">1048576</limit>
<priority type="integer">5000</priority>
<reservation type="integer">512</reservation>
<size type="integer">4096</size>
<target_memory_buffer type="integer">20</target_memory_buffer>
</bank>
<vnuma>
<max_size_per_node type="integer">14770</max_size_per_node>
</vnuma>
</memory>
<processors>
<count type="integer">1</count>
<features>
<limit type="bool">False</limit>
</features>
<limit type="integer">100000</limit>
<limit_cpuid type="bool">False</limit_cpuid>
<reservation type="integer">0</reservation>
<vnuma>
<count_per_node>
<max type="integer">4</max>
</count_per_node>
<node_per_socket>
<max type="integer">1</max>
</node_per_socket>
</vnuma>
<weight type="integer">100</weight>
</processors>
<stopped_at_host_shutdown type="bool">False</stopped_at_host_shutdown>
<vnuma>
<enabled type="bool">False</enabled>
</vnuma>
</settings>
</configuration>
If its relevant, the host is not yet activated license wise. I downloaded the demo version so I could test my idea before making a purchase to go ahead with full implementation.
As it stands right now I'm not sure how to troubleshoot this. Many searches on google have not turned up any helpful info. Does anyone have any ideas?
Thanks,
D

Hi ,
First , please refer to the supported guest OS of windows 2012 hyper-v :
http://technet.microsoft.com/library/hh831531.aspx
2003/R2 should be with sp2 and max 2 virtual processors .
"'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault."
If the issue is not due to the above items , you can try to check the "CPU compatibility " in that VM settings for troubleshooting:
Hope it helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Server 2008 R2 Hyper-V guests lose NIC after recent Windows Update

Hi Folks,
I have a Windows 2008R2 Hyper-V server with 20 guests. They have been using a standard network adapter for 2 years. Last night after running this months windows updates on a number of the guest VMs, each running Windows 2008R2 some of these
adapters disappeared. That is they are not visible in "network adapters" on the guest VM, the static IP configuration is gone and instead the VM had a dynamically assigned IP shown in IP config to a Microsoft VM bus network adapter #2.
The other machines that didn't have updates run on them and have adapters visible show a Microsoft VM bus network adapter.
I don't see anything obvious in event viewer.
I've done the basic "reinstall integration services" but it still doesn't show a configurable network adapter.
I've uninstalled the windows updates and "reinstalled integration services" no luck.
Does anyone have recommendations on next steps?
I'll update the post as I move forward.
Thanks,
Ivan
Ivan

Hi,
Could you try to show the hidden device in the device manager, you can refer the following article to show the hidden device:
How to Find a Lost, Missing, Hidden or Removed Network Card (NIC) or Other Device and Even Remove it
http://blogs.technet.com/b/danstolts/archive/2010/09/25/how-to-find-a-lost-missing-hidden-or-removed-network-card-nic-or-other-device-and-even-remove-it.aspx#sthash.z6jSu8tZ.dpuf
If you can see the lost NIC adapter then try to remove it uninstall it then rescan the device to see if there have the virtual NIC adapter found.
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V Guest Cluster Node Failing Regularly

Hi,
We currently have a 4-node Server 2012 R2 Cluster witch hosts among other things, a 3 node Guest Cluster running a single clustered file service.
Around once a week, the guest cluster node that is currently hosting the clustered file service will fail. It's as if the VM is blue screening. That in itself is fairly anoying and I'll be doing all the updates and checking event log for clues
as to the cause.
The problem then is that whichever physical cluster node that is hosting the VM when it fails, will not unlock some of the VM's files. The Virtual machine configuration lists as Online Pending. This means that the failed VM cannot be restarted
on any other cluster node. The only fix is to drain the physical host it failed on, and reboot.
Looking for suggestions on how to fix the following.
1. Crashing guest file cluster node
2. Failed VM with shared VHDX requiring Phyiscal host reboot.
Event messages for the physical host that was hosting the failed vm in order that they occured.
Hyper-V-Worker: Event ID 18590 - 'FS-03' has encountered a fatal error. The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x9E, ErrorCode1: 0x6C2A17C0, ErrorCode2: 0x3C, ErrorCode3: 0xA, ErrorCode4:
0x0. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID 36166B47-D003-4E51-AFB5-7B967A3EFD2D)
FailoverClustering: Event ID 1069 - Cluster resource 'Virtual Machine FS-03' of type 'Virtual Machine' in clustered role 'FS-03' failed.
Hyper-V-High-Availability: Event ID 21128 - 'Virtual Machine FS-03' failed to shutdown the virtual machine during the resource termination. The virtual machine will be forcefully stopped.
Hyper-V-High-Availability: Event ID 21110 - 'Virtual Machine FS-03' failed to terminate.
Hyper-V-VMMS: Event ID 20108 - The Virtual Machine Management Service failed to start the virtual machine '36166B47-D003-4E51-AFB5-7B967A3EFD2D': The group or resource is not in the correct state to perform the requested operation. (0x8007139F).
Hyper-V-High-Availability: Event ID 21107 - 'Virtual Machine FS-03' failed to start.
FailoverClustering: Event ID 1205 - The Cluster service failed to bring clustered role 'FS-03' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

Hi,
I don’t found the similar issue, Does your cluster can pass the cluster validation? Does all your Hyper-V host compatible with Server 2012r2? Have you try to disable all your
AV soft and firewall? Please rerun Storage validation on the Cluster in non-production hours, the cluster validation report will quickly locate the issue.
More information:
Cluster
http://technet.microsoft.com/en-us/library/dd581778(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V guest NICs fail

Similar Messages

Maybe you are looking for