Archives

VMs Have Gone Missing

I have been tasked with trying to discover how/why several VMs have gone missing from an on campus server.

The server runs Windows Server 2012 R2.

This server hosted/should be hosting several other VMs.

If I try to remote desktop onto any of the VMs then I get the message "Remote desktop cannot find the computer "VM name". This might mean that "VM name" does not belong to the specified network.

I can still remote onto the physical server without issue.

The folder  C:ProgamDataMicrosoftHyper-VVirtual Machines on the server is empty

If I look at the Hyper-V-Worker event logs (Log Viewer -> Microsoft -> Windows -> Hyper-V-Worker) then there are no logs for the last two years.

I.T. has run a hardware diagnostics on the server which came back healthy.

What else can i do to investigate this issue?

Please let me know of any additional details needed, my knowledge about servers is very limited.

Read full post . . . .

Cannot start Hyper-V Virtual Machine after install of KB4343887

Hi,

I wanted to report that I was unable to start any Virtual Machines in Hyper-V after an automated overnight update was installed last night: KB4343887 Cumulative Update for Windows Server 2016 for x_64-based systems.

After the update was installed, when trying to start any VM, it failed with an error message very similar to the following:

"Failed to start the virtual machine ‘test’ because one of the Hyper-V components is not running."

After removing the update, I was able to start the VMs. 

-Greg

Read full post . . . .

Unable to increase the vCPU in Virtual Machine

Hello Friends,

We have Hyper-V failover cluster on 2016 Datacenter O.S. 

When we are assigning vCPU in any Virtual Machine more than 8. Like 10 or 12 or 16. Live migration is not working and as soon as we reduce it with 8 vCPU than it started Live migrating.



Read full post . . . .

Unable to add iSCSI disk to VM as a physical drive

Hi, I am using Hyper-V Server Core build 17723 and I have an iSCSI target that I would like to add to my VM as a physical drive, but I can’t:

[hhvirt1]: PS J:etc> Get-Disk

Number Friendly Name Serial Number                    HealthStatus         OperationalStatus      Total Size Partition
                                                                                                             Style
------ ------------- -------------                    ------------         -----------------      ---------- ----------
0      HP LOGICAL... 5001438009BC7D80                 Healthy              Online                   136.7 GB MBR
1      IET VIRTUA...                              ... Healthy              Online                     512 GB GPT
2      IET VIRTUA...                              ... Healthy              Online                      48 GB GPT


[hhvirt1]: PS J:etc> Get-Disk 2 | Add-VMHardDiskDrive -VMName hhdc1
Add-VMHardDiskDrive : Unable to find a physical hard drive matching the given criteria.
    + CategoryInfo          : ObjectNotFound: (:) [Add-VMHardDiskDrive], VirtualizationException
    + FullyQualifiedErrorId : ObjectNotFound,Microsoft.HyperV.PowerShell.Commands.AddVMHardDiskDrive

[hhvirt1]: PS J:etc> Get-VMScsiController -VMName hhdc1

VMName ControllerNumber Drives
------ ---------------- ------
hhdc1  0                {Hard Drive on SCSI controller number 0 at location 0, DVD Drive on SCSI controller number 0...


[hhvirt1]: PS J:etc> Get-VMScsiController -VMName hhdc1 -ControllerNumber 0 | Add-VMHardDiskDrive -DiskNumber 2
Add-VMHardDiskDrive : Unable to find a physical hard drive matching the given criteria.
    + CategoryInfo          : ObjectNotFound: (:) [Add-VMHardDiskDrive], VirtualizationException
    + FullyQualifiedErrorId : ObjectNotFound,Microsoft.HyperV.PowerShell.Commands.AddVMHardDiskDrive

In Hyper-V Manager, the option to add a physical disk is greyed out. I’m not sure what other information to give… it’s a standard iSCSI target and initiator. I have another iSCSI drive mounted as a disk with VHDs stored on it that works perfectly fine.

I’ve read online that this is supported and works fine for others. I found another thread in Japanese from someone with the same problem (Google "Unable to find a physical hard drive matching the given criteria", I can’t post a link yet), and they
are using an older build of Server Core, so I don’t think it’s my build.

What could I try next?

Thank you!

Read full post . . . .

How do I add the expanded physical disk-space to Hyper-V Host C-Drive partition

Hi,

I have a problem here. We’re running Hyper-V core on HP DL380p G8 machine, Smart Array 430 RAID-6. 

Added 2 more disks to the RAID, expanded the array and see the additional available space in storage manager.

On VMware the host immediately sees the added HD space after a rescan, I can expand the Volume and it’s ready for use.

The Hyper-V doesn’t see the additional space in DISKPART, even after a RESCAN.

Is there any possibility to add this disk space to an existing host partition or add a second partition to use the additional space?

Regards

Walter

Read full post . . . .

How do I add the expanded physical disk-space to Hyper-V Host C-Drive partition

Hi,

I have a problem here. We’re running Hyper-V core on HP DL380p G8 machine, Smart Array 430 RAID-6. 

Added 2 more disks to the RAID, expanded the array and see the additional available space in storage manager.

On VMware the host immediately sees the added HD space after a rescan, I can expand the Volume and it’s ready for use.

The Hyper-V doesn’t see the additional space in DISKPART, even after a RESCAN.

Is there any possibility to add this disk space to an existing host partition or add a second partition to use the additional space?

Regards

Walter

Read full post . . . .

Install Hyper V 2016 on an SD card

Hello, Im trying to install an Hyper-V 2016 on an sd card (HP ML380 gen10) but the sd is not appearing on OS installation.

I read a lot of forums and trying to do it by cmd but whitout success.

Any ideas?

Thanks in advance

Regards

Read full post . . . .

Migrating Hyper-V VDI machines

Hello! VDI/Hyper-V noob here. I have a VDI deployment with a bunch of Hyper-V VMs spread across 2 physical servers and I need to combine this all onto one server. What is the process to safely take all my VMs on server 2 and migrate them to server 1?

OS is windows server 2016, VMs are running Win10 Enterprise. VDI is a persistent pooled desktop collection.

Thank you for any help you can offer! I know this may be basic stuff but I’m trying to learn a ton as I go.

Read full post . . . .

vSAN Proactive Support with VMware Skyline

Read full post . . . or http://feedproxy.google.com/~r/VmwareKnowledgebaseBlog/~3/oE65P78aiL8/vsan-proactive-support-with-vmware-skyline.html

');})

We are excited to announce the introduction of vSAN proactive support in VMware Skyline. Customers utilizing vSAN will receive proactive findings that identify potential issues for vSAN. In order to enable vSAN proactive support in Skyline, customers must upgrade to Skyline Collector 1.4. The Release Notes for Skyline Collector 1.4 can be found here.

To upgrade to Skyline Collector 1.4, either enable Auto-Upgrade within Skyline Collector 1.3, or login to the Skyline Collector VAMI and check for and install updates.

VMware Skyline documentation is now available on VMware Docs. Visit VMware Docs for instructions to enable Auto-Upgrade or manually upgrade your Skyline Collector.

vSAN Proactive Findings

The following are two of the vSAN proactive findings being delivering in Skyline.

Proactive Finding: Internal vSAN Memory (LSOM) or SSD Device Congestion

For this finding, Skyline utilizes the VC_EVENT endpoint to check for the vSAN LSOM congestion state exceeded message. If the congestion state exceeded message is observed by Skyline, this proactive finding will appear within your next Operational Summary Report (OSR).

If a virtual machine, or virtual machines, perform a high number of write operations, write buffers could fill up on flash cache devices. These buffers must be de-staged to magnetic disks in hybrid configurations. De-staging can only be performed at a rate at which the magnetic disks in a hybrid configuration can handle.

vSAN Proactive Finding: vSAN memory or SSD congestion reached threshold limit

VMware Knowledge Base article 2071384 provides you with information to remediate this issue.

Proactive Finding: H730 Mini-Controller running 25.5.3.0005 Firmware may cause vSAN Host Instability

This finding determines if the H730 RAID Controller is being utilized for vSAN. If the H730 RAID Controller is being utilized, Skyline then checks the version of firmware. If the firmware version is 25.5.3.0005, this proactive finding is added to the customer’s Operational Summary Report (OSR).

VMware Knowledge Base (KB) article 52783 is provided within the proactive finding. This KB article provides additional symptoms related to this potential issue, such as specific entries in log files. This issue is resolved in firmware version 25.5.3.0006. Additionally, the link to the PowerEdge RAID Controller H730 support page is provided within the KB article.

If your vSAN environment matches the characteristics detailed in either of these proactive findings, you can expect to see these vSAN proactive findings in your OSR. These are just two examples of the vSAN proactive findings now available within Skyline. There are more vSAN proactive findings available today, and we will continue to add new vSAN proactive findings in the future.

vSAN proactive support with Skyline does not replace vSAN Support Insight. We are continuing to evaluate how to utilize the information available within both Skyline and Support Insight to deliver a single, holistic support experience for our customers.

Additional vSphere Proactive Findings

While we’re on the topic of new proactive findings added to Skyline, I wanted to highlight two vSphere proactive findings added a short-time ago.

Proactive Finding: Network becomes Unavailable with ntg3 Driver on ESXi 6.5

This finding determines if the native ntg3 driver is being used on a passthrough Broadcom Gigabit Ethernet Adapter in your vSphere environment. If it is, it is possible that the network on the ESXi 6.5 host becomes unavailable. To resolve this potential issue, the recommendation is to run the ntg3 driver in legacy mode. As with all of the proactive findings delivered within the Operational Summary Report (OSR), a Knowledge Base (KB) article is provided for your reference. For this particular finding, KB article 2150889 is provided.

Proactive Finding: ESXi 6.5 host fails with PSOD when IPv6 disabled

This finding is interesting because there is no resolution at this time. If you disable IPv6 within ESXi 6.5, the ESXi host could fail with a purple screen of death (PSOD). To workaround this issue, enable IPv6. Additional information, including log excerpts, are provided within KB 2150794.

You’re probably thinking, why would Skyline alert me of a potential issue that does not have a resolution. First, one goal of Skyline is to notify customers of potential issues. In most instances, a resolution is provided for the potential issue. For this finding, a workaround is provided. However, once a resolution is available, customers will be notified that the KB article has been updated, and that a resolution is now available for this potential issue. By better understanding how our customer’s are utilizing our products and services, we can better provide relevant, personalized information and recommendations.

From VMware Docs, how to enable or disable IPv6 on an ESXi host.

Conclusion

We continue to expand the features and functionality available within Skyline. vSAN is the latest product to be added, joining VMware vSphere and VMware NSX. We will be announcing additional features and functionality for Skyline in less than two weeks at VMworld US. If you’re attending VMworld US and want to learn more about proactive support with Skyline, keep an eye out for our upcoming blog post that will provide details for where to find Skyline content at VMworld.

Additionally, follow @VMwareCSE (VMware Customer Support Experience) on Twitter for additional information related to proactive support with Skyline, along with Communities, Intelligent Search, My VMware and other VMware customer support programs.

The post vSAN Proactive Support with VMware Skyline appeared first on Support Insider.

vSAN Proactive Support with VMware Skyline

Read full post . . . or http://feedproxy.google.com/~r/VmwareKnowledgebaseBlog/~3/oE65P78aiL8/vsan-proactive-support-with-vmware-skyline.html

');})

We are excited to announce the introduction of vSAN proactive support in VMware Skyline. Customers utilizing vSAN will receive proactive findings that identify potential issues for vSAN. In order to enable vSAN proactive support in Skyline, customers must upgrade to Skyline Collector 1.4. The Release Notes for Skyline Collector 1.4 can be found here.

To upgrade to Skyline Collector 1.4, either enable Auto-Upgrade within Skyline Collector 1.3, or login to the Skyline Collector VAMI and check for and install updates.

VMware Skyline documentation is now available on VMware Docs. Visit VMware Docs for instructions to enable Auto-Upgrade or manually upgrade your Skyline Collector.

vSAN Proactive Findings

The following are two of the vSAN proactive findings being delivering in Skyline.

Proactive Finding: Internal vSAN Memory (LSOM) or SSD Device Congestion

For this finding, Skyline utilizes the VC_EVENT endpoint to check for the vSAN LSOM congestion state exceeded message. If the congestion state exceeded message is observed by Skyline, this proactive finding will appear within your next Operational Summary Report (OSR).

If a virtual machine, or virtual machines, perform a high number of write operations, write buffers could fill up on flash cache devices. These buffers must be de-staged to magnetic disks in hybrid configurations. De-staging can only be performed at a rate at which the magnetic disks in a hybrid configuration can handle.

vSAN Proactive Finding: vSAN memory or SSD congestion reached threshold limit

VMware Knowledge Base article 2071384 provides you with information to remediate this issue.

Proactive Finding: H730 Mini-Controller running 25.5.3.0005 Firmware may cause vSAN Host Instability

This finding determines if the H730 RAID Controller is being utilized for vSAN. If the H730 RAID Controller is being utilized, Skyline then checks the version of firmware. If the firmware version is 25.5.3.0005, this proactive finding is added to the customer’s Operational Summary Report (OSR).

VMware Knowledge Base (KB) article 52783 is provided within the proactive finding. This KB article provides additional symptoms related to this potential issue, such as specific entries in log files. This issue is resolved in firmware version 25.5.3.0006. Additionally, the link to the PowerEdge RAID Controller H730 support page is provided within the KB article.

If your vSAN environment matches the characteristics detailed in either of these proactive findings, you can expect to see these vSAN proactive findings in your OSR. These are just two examples of the vSAN proactive findings now available within Skyline. There are more vSAN proactive findings available today, and we will continue to add new vSAN proactive findings in the future.

vSAN proactive support with Skyline does not replace vSAN Support Insight. We are continuing to evaluate how to utilize the information available within both Skyline and Support Insight to deliver a single, holistic support experience for our customers.

Additional vSphere Proactive Findings

While we’re on the topic of new proactive findings added to Skyline, I wanted to highlight two vSphere proactive findings added a short-time ago.

Proactive Finding: Network becomes Unavailable with ntg3 Driver on ESXi 6.5

This finding determines if the native ntg3 driver is being used on a passthrough Broadcom Gigabit Ethernet Adapter in your vSphere environment. If it is, it is possible that the network on the ESXi 6.5 host becomes unavailable. To resolve this potential issue, the recommendation is to run the ntg3 driver in legacy mode. As with all of the proactive findings delivered within the Operational Summary Report (OSR), a Knowledge Base (KB) article is provided for your reference. For this particular finding, KB article 2150889 is provided.

Proactive Finding: ESXi 6.5 host fails with PSOD when IPv6 disabled

This finding is interesting because there is no resolution at this time. If you disable IPv6 within ESXi 6.5, the ESXi host could fail with a purple screen of death (PSOD). To workaround this issue, enable IPv6. Additional information, including log excerpts, are provided within KB 2150794.

You’re probably thinking, why would Skyline alert me of a potential issue that does not have a resolution. First, one goal of Skyline is to notify customers of potential issues. In most instances, a resolution is provided for the potential issue. For this finding, a workaround is provided. However, once a resolution is available, customers will be notified that the KB article has been updated, and that a resolution is now available for this potential issue. By better understanding how our customer’s are utilizing our products and services, we can better provide relevant, personalized information and recommendations.

From VMware Docs, how to enable or disable IPv6 on an ESXi host.

Conclusion

We continue to expand the features and functionality available within Skyline. vSAN is the latest product to be added, joining VMware vSphere and VMware NSX. We will be announcing additional features and functionality for Skyline in less than two weeks at VMworld US. If you’re attending VMworld US and want to learn more about proactive support with Skyline, keep an eye out for our upcoming blog post that will provide details for where to find Skyline content at VMworld.

Additionally, follow @VMwareCSE (VMware Customer Support Experience) on Twitter for additional information related to proactive support with Skyline, along with Communities, Intelligent Search, My VMware and other VMware customer support programs.

The post vSAN Proactive Support with VMware Skyline appeared first on Support Insider.

Go Que Newsroom

Categories