Hello guys!
I'm really making a mess with PVLAN and Virtual Subnetting (VSID). I can't understand what is better or what is the most appropriated on an environment. I'm studing for the MCSE Private Cloud and I really would like to understand well that topic.
Thank you all!
Hi,
I tried booting Xen-kernel 4.3 in a Hyper-V virtual machine. The vm runs Debian7, which uses hv modules for Hyper-V. When I boot the normal kernel, it is fine, but booting Debian's xen-kernel doesn't work, because no virtual disk drives can be found. This looks like an issue with the hv modules, because without them, the xen-kernel boots fine. I tested this by using an older Debian6, where hv modules are not loaded by default.
Regards,
Sladi
Hi,
All vm's in hyper-v 2012 core cannot initialize.
there is ram and space in drive. Tried to run windows update and restarted hyper-V.
any suggestions?
Thanks
Hi,
we installed 2 Hyper-V Servers with a non-shared Storage Setup, that means every Hyper-V has his own storage.
On Both Hyper-Vs we installed several virtual machines, all Windows Server 2012.
After a while several servers created some avhdx file.
Now the strange part:
Lets say the config is like:
Server1 -> Server01.vhd -> Server01-823482384-randomnumber.avhdx
When i now shutdown the server for maintenance, it will do the following:
it will merge the avhdx to the parent .vhd ( So far so good and understandable )
BUT in the config it will change the server01.vhd which was associated to the Server01 with the now missing Server01-823482384-randomnumber.avhdx - which will result in the fact that the server wont come up again, until i change back the settings from Server01-823482384-randomnumber.avhdx to Server01.vhd which was configured before.
Is this a Bug or a misconfiguration ? How can we solve that ?
We have a server with 4 Intel Pro1000PT nic cards in it. Set up host (server 2012) and teamed nic cards. Then added Hyper-V and after reboot - moved Server 2012 virtual machine to server. VM would not connect or ping gateway. No network connection no matter what I did. Tried removing Hyper-V, team, rebooting, recreating etc. No luck.
Co-worker removes Hyper-V and team, reboot, teams nic, and put IP address on IP4 network, subnet, etc address on it. Then he installed Hyper-V which stripped address, but now virtual machine connects just fine.
Is this by design? Are Intel Pro1000PT dual-port cards compatible with 2012R2 Hyper-V? You do NOT put IP address on Virtual Switch do you???
Thanks for your help! This is to be a production server and need to get it right.
Theresa Greene
PS - we do not run DHCP on this network - all IP's are static.
Hi, I'm pretty new in the hyper-v world.
And I'm planning to migrate more servers to an hyper-v failover cluster with Fibre Channel SAN. I'm wondering about the CSV and the possibility to have less LUN with that. There is a lot of ressources about CSV since Windows Server 2008 R2, and all are speaking about the advantages!
But I'm asking if there is some requirement other than those described here: http://technet.microsoft.com/fr-fr/library/jj612868.aspx#BKMK_Reqs
1/ If I use only a dedicated 1Gbs network interface for CSV, will I slowdown the VMachines?
2/ Is the Hyper-v physical HardDrive heavily used?
3/ If a node loses the storage connectivity is it possible (with no human intervention) to switch the concerned VMachines to an other node to avoid the I/O Redirection?
.... Or other things to take care?
Regards,
L.H.
Hi
Bit of a wierd scenario this but I'm doing a bit of a lab experiment kind of thing. The setup is as follows:
VMWare Workstation 10 with Windows Server 2012 R2 running as a virtual machine. In VMW10 I have a NAT network interface and a Bridging interface set to load with the virtual machine. These seem to work fine (although the NAT doesn't seem to want to connect to the internet but that's why the bridging one is there in addition).
Server 2012 is configured with the following roles:
ADDS, DHCP, DNS, Hyper-V, Printer, WDS
I have correctly configured WDS to work on the same machine as DHCP and I can get PXE boot working with WDS on a Type1 Virtual Machine in Hyper-V using the Legacy Network adapter. My problem is when I try and PXE boot on a Type2 Virtual Machine (this type is new in R2 and should eliminate the need for a legacy network adapter) using the same network interface that I used for the Type1 machine, I get an IP address from DHCP but WDS doesn't seem to respond. Instead I get the "PXE-E16: No Offer Received" message. I have tried just about everything I can think of and spent the whole day trying to figure out why this is the case but came up with nothing. Has anyone else encountered this or can anyone shed any light on the matter?
Many thanks in advance
Can we set a hyper-v replica from Windows 2012 to Windows 2012 R2 server, and use extend replica to clone the image to another Windows 2012/Windows 2012 R2 server?
Thanks,
Tak
Hello
We are currently running two domain controllers with Server 2003 on them. We have a standard TCP/IP star topology networking including web servers, files servers, sql, iis etc.
We are upgrading 5 of our servers to 2012r2 and are using them as "host" servers for upgraded IIS (2012r2) and WebGrabber (2008r2) servers and these servers will be set up as virtual machines (the IIS and web grabbers) on the hosts.
My question is will using Windows Server 2003 domain controllers cause issues in the advanced settings in 2012r2 and Hyper-V? Should we upgrade our Domain Controllers and if so to what version? 2008r2 or 2012r2?
Thanks!
Theresa Greene
Theresa Greene
I have a 2012R2 Hyper-V cluster using SMB SOFS shares.
All Guests have the latest IC installed,
All the 2012R2/2012 guests backup fine and so do the 2008R2 guests, but when the online\ServerXYZ backup starts the network card disconnects for 20 to 60 seconds, and then reconnects, and the backup completes fine. as far as I can tell this is only happening on 2008R2 guests, and doesn't effect the 2012/R2 guests. although I see event ID 12 on all the 2012 and 2012R2 there is no network connection interruption
I have had to stop the jobs on these servers as it affecting various production applications that connect to SQL.
I am seeing event ID's 13 and 12 on the guest servers
need to find out what is causing this, I cannot find any other information.
thanks
Mark
I have a 2K12 hyperV machine with 2 NIcs (192..1.11 & 192..112)
I recently downloaded an appliance that creates a private switch with a network id 192.168.56.1, and the VM has 192.168.56.101. From IE or Chrome on the win 2012 box, when I typehttp://192.168.56.101 I reach the machine (web site inside it) but I can not do it from another machine (laptop or desktop they are on the same network as the hyper-V 192.168.1...) using IE or chrome. pinging the ip from the hyperv machine responds but not from others. I checked the route print and have this on the hyper-V
192.168.56.0 255.255.255.0 On-link 192.168.56.1 261
192.168.56.1 255.255.255.255 On-link 192.168.56.1 261
the question is why I can connect from the machine itself but not others? What is needed to be added in the routing table on the other machines in order to be able to join this appliance from another machine
Thanks in advance
Hi guys,
Anyone used QNAP NAS as iscsi with Hyper V? How is the performance? - Does it run smoothly in your enviroment ?
At the moment i am using a DAS storage- but i would like to purchase the QNAP . Please let me know if you have any experience with it .
Thanks
Regards, MassonTech
My hosts have 48GB RAM and two pCPUs giving me two NUMA nodes, and I have five VMs that need to run on each, four with 9100MB RAM and one with 7000MB. This should fit, and usually does. Prior to migrating to Hyper-V these hosts were running XenServer 5.5, which was not NUMA aware (and possibly had a lower memory overhead than Windows anyway), and I could always get all the VMs powered on, no problems. They were probably spanning all over the NUAM nodes, but performance was OK so I didn't care.
Then I moved a couple of hosts to 2012 (not R2) and ran the VMs in Hyper-V. Because Hyper-V is NUMA aware I thought it'd be nice to take advantage of this so I split the 7000MB VM into two smaller ones, and assigned one of those plus two of the larger VMs onto each NUMA node. I assigned the VMs to the NUMA nodes by using WMI http://rcmtech.wordpress.com/2013/08/12/set-hyper-v-2012-vm-numa-node/
2012 R2 seems to have changed/removed the ability to configure a VM to sit on a particular NUMA node though, as the above doesn't work anymore.
So now I'm experimenting with the various "allow to span NUMA" tickboxes that you get the for the host and the VMs, but with mixed success. I've gone back to five VMs, but can frequently only get four to power on, the fifth saying "not enough memory", yet on other hosts all five are running. Try the VM again later and it might power on, it might not. It seems pretty random, I've done a lot of testing with various combinations of the "allow numa spanning" setting for the VMs and it seems to not make much difference. Once I was only able to get three VMs to power on...!
What I would assume (hope) is that if the hostand VMs are all set to allow NUMA spanning, they should all power on, as the final VM will end up spanning across the two nodes even if the other four have been placed entirely within a node. but this doesn't seem to happen consistently.
The hosts that do have all five VMs running show about 2-3GB free RAM.
So can anyone offer any advice? Am I doing something daft? There must be something going on that I'm not aware of or not taking into account. I don't like inconsistent behaviour.
Thanks in advance!
Hello,
We've been having an interesting issue with our Windows Server 2012 Host. There are currently 10 VMs running on Hyper-V with guest OSes ranging from Windows XP to Windows Server 2008 R2. The currently running machines are working fine. I can connect to them, access them via RDP and Hyper-V, ping them, etc.
The issue arises when I attempt to start any of the remaining three VMs that are currently off. The VMs are running Windows XP, Windows Server 2003, and Windows Server 2008 R2 (all operating systems that are working fine on the other VMs). When I attempt to start the machine, I get the following error before any startup screen can be displayed:
The application encountered an error while attempting to change the state of 'WEBSERVER1'
'WEBSERVER1' failed to start worker process: Incorrect function. (0x80070001).
I even tried to create a new VM, but I received the exact same error message when I tried to start the machine. Anyone ever experienced this type of error? My first guess was some sort of logical VM limit, but I can't test that just yet as there are several users in our office who are utilizing the running VMs. I'm afraid that if I shut down any of the running VMs, I may not be able to start the machine up again.
Also, I went and checked the event viewer and found three entries for each attempt at starting a VM:
Event 17040, Hyper-V Worker: The authorization store could not be initialized from storage location 'msxml://C:\ProgramData\Microsoft\Virtual Machine Manager\VmmHyperVAuthstore.xml'. Error: The system cannot find the path specified. (0x80070003).
Event 15500, Hyper-V-VMMS: 'WEBSERVER1' failed to start worker process: Incorrect function. (0x80070001). (Virtual machine ID 4F14787D-58C6-4F30-92A8-E491828B2518)
Event 15130, Hyper-V-VMMS: 'WEBSERVER1' failed to start. (Virtual machine ID 4F14787D-58C6-4F30-92A8-E491828B2518)
Any help will be greatly appreciated!!
Experts !
What is the recommendation on Over committing CPUs specific to Windows Server 2012 R2? Is there any deviation from the previous recommendation like the aggregate vCPU on a Host should be less than or equal to the total cores available on the host.
I am happy with "Less is more" , however want to clarify this.
Thanks !
Optimism is the faith that leads to achievement. Nothing can be done without hope and confidence.
InsideVirtualization.com
Hi,
according to the official documentation of Microsoft, Hyper-V does not block Sleep and Hibernate on Windows Server 2012 and Windows Server 2012 R2.
From powercfg I get the following output:
The following sleep states are not available on this system: Standby (S1) The system firmware does not support this standby state. An internal system component has disabled this standby state. Hypervisor Standby (S2) The system firmware does not support this standby state. An internal system component has disabled this standby state. Hypervisor Standby (S3) An internal system component has disabled this standby state. Hypervisor Hibernate An internal system component has disabled hibernation. Hypervisor Standby (Connected) The hypervisor does not support this standby state. The system firmware does not support this standby state. Hybrid Sleep Standby (S3) is not available. Hibernation is not available. The hypervisor does not support this standby state. Fast Startup Hibernation is not available.
I already installed a graphics device driver to prevent the graphics device from blocking Sleep and Hyper-V. So this should not be an issue.
What can I do to enable Sleep and Hibernate?
Regards,
Daniel
Hi,
New two node Hyper-V cluster running Windows 2012R2.
Storage is delivered through a standalone Windows 2012R2 iSCSI Target server, with CSV.
We have about 14 VMs running on the cluster, so far no problem.
The problem comes when trying to backup the VMs using DPM 2012R2 and the Microsoft iSCSI VSS provider.
It creates the shadow copy fine on the iSCSI target server, but then my CSV volume goes offline for about a minute or so until it gets re-assigned to another node of the cluster, then comes back online.
Meanwhile of course, all the virtual machine crashes.
It sounds similar to problems I have seen in the past with Windows 2008R2 and 2012 clusters, but I can't find any of the hotfixes for 2012R2.
Any ideas?
Thank you,
Stephane
A couple of questions:
1. If we wanted to set up iSCSI connections for guests such as SQL servers, what is the best way to handle this? For example, if we had four 10-Gb NICs and wanted to use as few of them as possible, is it common to turn two of the NICs into Virtual Switches accessible by the OS, then use these to connect both the host and the SQL guests? Or would the best option be to use two 10-Gb NICs for the Hyper-V Host's iSCSI connections only, and use the other two 10-Gb NICs as virtual switches which are dedicated to the SQL server iSCSI connections?
2. I know MPIO should be used for storage connections instead of teaming; if two NICs are teamed as a virtual switch, however, does this change anything? For example, if a virtual switch is created from a NIC team of two 10-Gb NICs, is it acceptable to create an iSCSI connection on a network adapter created on that virtual switch?
Hello,
Since upgrading a host from 2012 to 2012 R2 I can no longer take "Online" backups of a Server 2008 R2 machine. It has the latest integration components, VSS is happy, the VM has a SCSI adapter. Everything worked OK under 2012 but not under R2 it seems the VM has to be suspended before backups.
Anyone know of a solution?
K
