HI Hyper-V Experts, How to Move the Virtual Machines from Hyper-V to Hyper-V without interruption.
B@l@.N
HI Hyper-V Experts, How to Move the Virtual Machines from Hyper-V to Hyper-V without interruption.
B@l@.N
I have a large collection of Hyper-V hosts for which I would like to retrieve the target WNN and LUN ID for the LUNs visible on each host. By target WWN I mean the storage array's WWN.
I have tried using the root\wmi namespace to retrieve MS_SMHBA_PORT_LUN instances, but I get 0 instances back.
I get instances of MSFC_FibrePortHBAAttributes back, but those only tell me the local host's HBA WWN, not the target information.
This information must be stored somewhere, because you can't access the LUN without it, I hope there is a way to retrieve it. Is there? Or is it write only during LUN setup?
Hi,
So i set up a storage server. Created a disk pool, a VD and an iSCSI VD. Created a target and chose initiator IPs of my test host. Disk shows as ok, everything is fine.
I go to my Hyper-V host and run commands as shown below. As you can see it gets connected just fine and storage server says initiator is connected ok, but i can se no disks... Why?
Enter-PSSession hpv0 Get-NetFirewallServiceFilter -Service msiscsi | Get-NetFirewallRule | Select DisplayGroup,DisplayName,Enabled DisplayGroup DisplayName Enabled ------------ ----------- ------- iSCSI Service iSCSI Service (TCP-In) False iSCSI Service iSCSI Service (TCP-Out) False Get-NetFirewallServiceFilter -Service msiscsi | Get-NetFirewallRule | Set-NetFirewallRule -Enabled True Get-NetFirewallServiceFilter -Service msiscsi | Get-NetFirewallRule | Select DisplayGroup,DisplayName,Enabled DisplayGroup DisplayName Enabled ------------ ----------- ------- iSCSI Service iSCSI Service (TCP-Out) True iSCSI Service iSCSI Service (TCP-In) True Set-Service -Name MSiSCSI -StartupType Automatic Start-Service MSiSCSI WARNING: Waiting for service 'Microsoft iSCSI Initiator Service (MSiSCSI)' to start... Get-Service -Name MSiSCSI Status Name DisplayName ------ ---- ----------- Running MSiSCSI Microsoft iSCSI Initiator Service New-IscsiTargetPortal -TargetPortalAddress 10.10.10.1 InitiatorInstanceName : InitiatorPortalAddress : IsDataDigest : False IsHeaderDigest : False TargetPortalAddress : 10.10.10.1 TargetPortalPortNumber : 3260 PSComputerName : $target = Get-IscsiTarget Connect-IscsiTarget -NodeAddress $target.NodeAddress AuthenticationType : NONE InitiatorInstanceName : ROOT\ISCSIPRT\0000_0 InitiatorNodeAddress : iqn.1991-05.com.microsoft:hpv0.sub.domain.com InitiatorPortalAddress : 0.0.0.0 InitiatorSideIdentifier : 400001370000 IsConnected : True IsDataDigest : False IsDiscovered : True IsHeaderDigest : False IsPersistent : False NumberOfConnections : 1 SessionIdentifier : ffffe0001ef44430-4000013700000003 TargetNodeAddress : iqn.1991-05.com.microsoft:blue-hpv0-target TargetSideIdentifier : 0100 PSComputerName : Get-IscsiConnection ConnectionIdentifier : ffffe0001ef44430-2 InitiatorAddress : 0.0.0.0 InitiatorPortNumber : 46539 TargetAddress : 10.10.10.1 TargetPortNumber : 3260 PSComputerName : Get-IscsiSession | Register-IscsiSession Get-IscsiSession AuthenticationType : NONE InitiatorInstanceName : ROOT\ISCSIPRT\0000_0 InitiatorNodeAddress : iqn.1991-05.com.microsoft:hpv0.sub.domain.com InitiatorPortalAddress : 0.0.0.0 InitiatorSideIdentifier : 400001370000 IsConnected : True IsDataDigest : False IsDiscovered : True IsHeaderDigest : False IsPersistent : True NumberOfConnections : 1 SessionIdentifier : ffffe0001ef44430-4000013700000003 TargetNodeAddress : iqn.1991-05.com.microsoft:blue-hpv0-target TargetSideIdentifier : 0100 PSComputerName : Get-Disk Number Friendly Name OperationalStatus Total Size Partition Style ------ ------------- ----------------- ---------- --------------- 0 DELL PERC 6/i Adapter SCSI Disk Device Online 232.25 GB MBR
This posting is provided "AS IS" with no warranties or guarantees and confers no rights
We have an existing VMware 3.5 environment where the vlans are all set up for Management, VMotion etc.
my client is moving away from VMware and switching to Hyper v long term.
There is an immediate requirement to deploy 2012 servers. ESX 3.5 environment does not support.
Two DL385 G6 servers that are certified for 2012 have been found and I was wondering if there would be any problem in using the existing VLANs for the similar services Management, Live migration etc for the creation of a temporary Hyper V failover cluster until we have designed the new Hyper V clusters to replace ESX 3.5.
I have a 500GB R1
Someone took a snapshot and deleted it a long time ago - I think back in January.
There are two VMs on the Win Hyperv 2008R2 server
1 with the snapshot has a 40GB C: and a 200GB D:
The other was a 40GB C:
I shut down the one with the snapshoot and expected the merge to just work.... however, the second server paused due to disk space issues. I am monitoring the merge process using powershell get-wmiobject (widely documented online).
What has me puzzled is the server has basically run out of drive space. When I run the get-wmi I see the precentage complete rising and the Instance IDs changing. It has been running since Friday evening.
What do the InstanceIDs mean (they dont match the UID of any of the avhds)?
As things are progressing through to different instanceids - how come the .avhs aren't shrinking or being deleted?
Will this thing ever finish? I can't start the other VM because there is no drive space available.
I ordered 2 more drives to plug into my server that has 2 slots available. My plan is to put the new drives in and move the 2 server VM to it and start it up.
We have an existing VMware 3.5 environment where the vlans are all set up for Management, VMotion etc.
my client is moving away from VMware and switching to Hyper v long term.
There is an immediate requirement to deploy 2012 servers. ESX 3.5 environment does not support.
Two DL385 G6 servers that are certified for 2012 have been found and I was wondering if there would be any problem in using the existing VLANs for the similar services Management, Live migration etc for the creation of a temporary Hyper V failover cluster until we have designed the new Hyper V clusters to replace ESX 3.5.
Here is the error what i am suffering from, it fails and i dont know what this error is all about
Saved State Errors
The following saved state errors were reported... the processor settings for virtual machine....
can some one help
Hello,
I scheduled the backup of all my physical and virtual servers in a networkshare.
Now I'm doing some disaster recovery test restoring a physical server in a Hyper V virtual machine but after restore prosess the system doesn't boot. I saw that there are some unusually situations: The partition drive letters are messed up. The "System reserved" patition has C: drive letter and Windows partition has D: drive letter.
So I tried to fix like before using DISKPART but it seems that the changes are not saved, when I reboot the system doesn't work and giving list vol the letter assignment doesn't change.
How can I fix it?
Thank you
Hi All,
I have hyperv 2012 hypervisor and i have created some vms on it. I need one of my win7 vm to boot over network. It is created with generation 1. As generation 1 has some problem to boot vms over network, i thought of creating a generation 2 vm. I have downloaded valid win8 evaluation edition iso from microsoft site. That iso is working fine for me, but when I use the same iso for my vm, it stucks at 22%. i tried almost 40-50 times. Everytime it stucks at 22% only. I am also sure that I have put it in generation 2. I also thought to create a vm with generation 1 and convert it to generation 2 (OS is win 8). But unfortunately, when i use generation 1, vm stops at 10%. getting files ready for installation (10%). In none of the generations, with none of my ISO files, it crossed 23%. Am I missing something? Please guide.
Chaitanya.
Hi,
I was recently restarting a virtual machine due to applying updates and the virtual machine froze. This vm is located on one of our clusters which are running the Hyper-V role. The vm worked just fine until the restart. I was unable to stop the vm at first so I ended the process via Task Manager. Now I am unable to start the virtual machine.
The following error comes up when I try to start it:
The operation has failed. Failed to start virtual machine 'vmname'.
The details for this error are as follows:
Failed to bring the resource 'vmname" online. Error Code: 0x8007139f. The group or resource is not in the correct state to perform the requested operation.
Can you please tell me what I should do. I am thinking of deleting the virtual machine and re-creating it but would that erase the data from the virtual drive as well? Also, if this is a good idea, how would I go about giving the vm the smae IP address? Our environment only uses DHCP and does not allow static IP assignments.
Is there a way to go about this without having to delete the virtual machine? And without having to restart the entire Hyper-V node on which the vm is located on?
Thanks in advance,
Hello,
Windows server 2012 STD run to virtual machine on Hyper-V. one is AD 2012 and second is Exchange server 2013. But exchange server Hyper-v machine restart once a day. windows server shown blue screen and automatically restart.
Error: 'ADCD01' has encountered a fatal error. The guest operating system reported that it failed with the following error codes: ErrorCode0: 0xEF, ErrorCode1: 0x4135980, ErrorCode2: 0x0, ErrorCode3: 0x0, ErrorCode4: 0x0. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID 6E69337A-AB09-485A-A326-ECB4C12D37DB)
Please suggest.
Thanks
HI FRIENDS,
i have one firewall model number sg300 i configured each and everything
but after configuration internet working very slow.if i want to open any website it is taking 5 min .i connected
my lease ling directly in this device.
please help me....
Thanks,
Madhukar
Hi,
We're having a very odd and elusive networking problem with a Hyper-V 2012 R2 server.
Shortly are upgrading all our servers to Server 2012 R2 and migrating to Hyper-V 2012 R2 users started to notice that Outlook would disconnect and redirected documents would become inaccessible randomly at varying times throughout the day.
After some troubleshooting we managed to isolate the following behaviour.
Pings to the VM's drop off first followed shortly by pings to the Hyper-V host.
The packets are dropped for a period of around 2 minutes intermittently around 1-2 times per day.
The timing seems completely random.
Neither the VM's nor Hyper-V host register any loss of network connection.
VM's can not talk to each other over the vSwitch whilst the problem is occurring.
Normal service resumes after usually around 2 minutes or so.
Nothing seems to be logged in the event log on any of the machines to do with network issues. The only trace we can find is EventID 2070 been logged on the exchange servers application log to say that the DC is unavailable. And on the domain controller/file server we can see LDAP session time outs and SMB handles been scavenged.
The server is running on a ML350P Gen8 (Broadcom NIC) - All firmware and drivers have been updated.
All servers are up to date with all the latest updates.
We have also tried a second Intel based NIC but this has made no difference as did swapping all network cables and the switch.
There are currently 4 VM's connected to a single vSwitch which is linked to a dedicated port on the Intel NIC - management is not allowed through this interface but is done through the second interface on the Intel NIC.
Has anyone come across this before? It is causing a lot of problems with the client and we are very close to rebuilding the Hyper-V host with an earlier version of Windows server.
Thanks,
Richard.
.