Archives

New KB articles published for the week ending 25th May,2019

Read full post . . . or http://feedproxy.google.com/~r/VmwareKnowledgebaseBlog/~3/JHJ37WnEcP0/new-kb-articles-published-for-the-week-ending-25th-may2019.html

VMware Cloud Provider Pod “ReferenceError: vcsaSize is not defined.” error when deploying the resource infrastructure with Cloud Provider Pod 1.1 Date Published: 23-May-2019 VMware ESXi Across host vMotion fails for a specific hosts. Migration fails with error message “The Object or item referred to could not be found” Date Published: 23-May-2019 PSOD error: “VMKAPI-char-metadata heap

The post New KB articles published for the week ending 25th May,2019 appeared first on VMware Support Insider.

Multiple VLAN trunk, with one NIC, and one IPv4 network

I try to have one Hyper-V VM in two VLANs, with only one network card, trunked on the link going to the switch.

I’ve one switch CISCO. Here is it’s config:

interface FastEthernet0/1
 switchport mode trunk
!
interface FastEthernet0/8
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/9
 switchport access vlan 3
 switchport mode access
!
interface FastEthernet0/10
 switchport access vlan 240
 switchport mode access

I’ve a physical machine (named PC1) (Win 10 Pro) plugged in port fa0/1. This machine owns Hyper-V. In Hyper-V, I’ve a VM named "my_vm".

In Hyper-V, I’ve done:

Get-VMNetworkAdapter -VMName my_vm | Where-Object -Property MacAddress -eq "0000006CA095" | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "2-3" -NativeVlanId 240

MAC address seems to be good. I’ve verified and obtained:

PS C:> Get-VMNetworkAdapterVlan

VMName           VMNetworkAdapterName Mode     VlanList
——           ——————- —-     ——-
my_vm            Carte réseau         Trunk    240,2-3

I’ve an other physical machine (named PC2).

"my_vm" and PC2 are on the same IPv4 network (192.168.0.1/24 and 192.168.0.2/24).

"my_vm" is always plugged on port fa0/1 on the switch.

When I plug PC2 on port fa0/10 (mode access, VLAN 240): "my_vm" and PC2 are pinging themselves.

When I plug PC2 on port fa0/8 (mode access, VLAN 2), or on port fa0/9 (mode access, VLAN 3): "my_vm" and PC2 can’t ping themselves.

Hyper-V VM "my_vm" can be a Win 10 Pro or a Debian, the result is the same.

On physical machine PC1, I’ve two physical NIC (Intel I219V and TP-Link TG-3468 - Realtek in fact): the result is the same. "Priority and VLAN" is "Enabled" on this two NIC.

TAG seems to be good when arriving on VM: if I DON’T use

"Get-VMNetworkAdapter -VMName my_vm | Where-Object -Property MacAddress -eq "0000006CA095" | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "2-3" -NativeVlanId 240"

and, for VM "my_VM", for it’s network card (an external switch to NIC in fact), if I set "Activate virtual LAN identification" > VLAN 2, "my_vm" and PC2 plug on port fa0/8 (VLAN 2 - access) are pinging themselves.

If I set "Activate virtual LAN identification" > VLAN 3, "my_vm" and PC2 plug on port fa0/9 (VLAN 3 - access) are pinging themselves.

I don’t know how to moving forward.

Thanks for all.

Best regards.

Read full post . . . .

Add a new server host and using the same SAN storage currently used

Hello,

I have currently an Hyper-V cluster with 2 nodes Windows server 2012 Std.

Those node are attached to a SAN storage.

They both access to a CSVFS volume that contain all my VM.

I wanted to build a new architecture

- using a new host Windows server 2016 or 2019.

- Reinstall one of my old node in windows server 2016 and make a failover hyper-v cluster between this old node and my new server.

I wanted to know if it’s possible to attach the new server to my SAN storage and attach the CSVFS volume directly to this new host to get my VM on this new host ?

Benjamin

Read full post . . . .

KB4072650 not showing in Windows updates- not installed

I moved 2 2012R2 VMs from a 2012 Hyper-V host over to a 2016 host.  During backups I received VSS errors that indicate I have an Integration services mismatch on these two VMs (I have Win2016/WIn10/Win2008 VMs that don’t have the issue on this same
host).  I have the latest VM integration package for 2012R2 EXCEPT for KB4072650 — it is not installed on either of this guest VMs.  I have ran Window update multiple times on both the HOST and both of these VMs and this KB never shows up and when
checking installed updates it has never been installed.  Only other reference I have found online is someone who had the same issue and ultimately gave up and re-installed the VMs.  Is there anyway I can access KB4072650 directly since Windows update
will not install it?

Thanks

 

Read full post . . . .

What is the point of checkpoint?

I get the idea of them but I keep reading that they are not to be used to replace back ups which I understand but was setting up a new virtual domain controller yesterday and I came across this MS article and it says:

  • Do not take or use a Snapshot of a virtual domain controller. It is technically supported with Windows Server 2012 and newer, it is not a replacement for a good backup strategy. There are few reasons for
    taking DC snapshots or restoring the snapshots

https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/get-started/virtual-dc/virtualized-domain-controllers-hyper-v

I thought a snapshot or checkpoint would be good to use before applying updates and rebooting the domain controller but after reading that they seem a bit useless on a DC

Read full post . . . .

Hyper-V 2019 – replica issues

We just moved from 2012R2 to 2019 for Hyper-V hosts.

Trying to enable Hyper-V replica for the guests, but it is failing when I deselect the paging drive (didn’t replicate them on 2012R2 to ease burden on network/WAN, etc).

If I include the paging drive, Hyper-V replica is established just fine.  But I can’t go back and deselect it since that is defined at the time of replication being enabled.

Errors seen on source host & destination host are below.

I’m assuming this is a bug, just wasn’t sure if known and on a roadmap to be fixed or if some other workaround exists.

Source Host:
Error 6/11/2019 11:14:40 PM Hyper-V-VMMS 32000 None
Hyper-V failed to enable replication for virtual machine ‘GuestVM’: Not found (0x80041002). (Virtual machine ID xxxx)

Destination Host:
Error 6/11/2019 11:14:40 PM Hyper-V-VMMS 33490 None
Hyper-V failed to remove virtual hard disk ‘E:Hyper-VGuestVMGuestVM-P.vhdx’ from the virtual machine ‘GuestVM’: Not found (0x80041002). (Virtual machine ID xxxx)
Error 6/11/2019 11:14:40 PM Hyper-V-VMMS 33684 None
Hyper-V failed to enable replication for Replica virtual machine ‘GuestVM’: Not found (0x80041002). (Virtual machine ID xxxx)

Thanks

Read full post . . . .

Server 2016 Hyper-V: VMs Not Booting After Previously Working

I’m running Hyper-V on Server 2016 Datacenter, at home. I’ve created a number of Windows 10 VMs, both Pro and Enterprise. While I was creating these VMs, I didn’t run into any problems. I was able to boot into the OS, log into the computer, and configure
it as normally. However, for each one of these VMs, at some point when I tried to start the VM, I would run into SEVERE slow down issues. Often times I couldn’t get to the log on screen again. It would simply sit at the black screen with the Hyper-V logo,
while the spinning dots would go on spinning endlessly. This is a recent issue. Within the past week. I didn’t previously have this problem, but I also haven’t been using Hyper-V heavily on this install until recently. My OS is fully updated (which hopefully
isn’t the problem…).

I have made no absolutely no hardware changes and no changes to the configuration of the VMs. Usually after, restarting my computer of the VMs a few times, this issue would show up and the VM s would become unusable. Again, these VMs initially worked just fine.
They started up quickly and were very responsive.

I’ve tried creating new VMs, using different ISOs, and even uninstalling and reinstalling the Hyper-V module and management tools. All with no luck. I would really like to avoid reinstalling my host OS if that could be helped, but right now that’s all I can
think of, though I have no idea if that would even work since I don’t have a clue where the problem lies. Below my hardware and VM configuration is listed below. Any help would be greatly appreciated.

———-

OS Name                       Microsoft Windows Server 2016 Datacenter
Version                       10.0.14393 Build 14393
System Type               x64-based PC
Processor                       Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date       American Megatrends Inc. 0301, 9/16/2011
SMBIOS Version               2.6
BIOS Mode               Legacy
BaseBoard Manufacturer   ASUSTeK Computer INC.
Platform Role               Workstation
Secure Boot State       Unsupported
Installed Physical             Memory (RAM)   16.0 GB DDR3
Total Virtual Memory       18.3 GB
Available Virtual Memory  12.5 GB
Page File Space               2.38 GB

C Drive:                          Boot Drive
Model                       INTEL SSDSA2CW120G3 (SATA SSD)
Bytes/Sector               512
Size                               111.79 GB (120,031,511,040 bytes)
Free Space               44.94 GB (48,249,929,728 bytes)

D Drive:       Location of the VMs/VHDXs
Model       ST2000DL003-9VT166 (SATA HDD)
Bytes/Sector       512
Size       1.82 TB (2,000,396,321,280 bytes)
Free Space               746.33 GB (801,364,180,992 bytes)

Virtual Machines:
Type                               Hyper-V Version 2016 Generation 2
Storage                           VHDX Dynamic
Startup                           Memory 4GB (non-Dynamic)
Virtual Processors            1
OS                                 Windows 10 Pro or Enterprise

Read full post . . . .

CSV ran out of space during snapshot merge – now have too many AVHD files and a merge-pending state

While doing upgrade work on a VM running on a Windows Server 2016 cluster, multiple snapshots were created to provide a rollback if the upgrades had issues (they did, multiple times, so this was very helpful to have).  Once upgrade was completed and
working correctly, I deleted the newest snapshot.  Another tech had, in the meantime, created a new VM that used most of the remaining space on the CSV.  So, my VM moved to Paused-Critical state when the merge used up the remaining space.  I
immediately storage migrated other, still running VMs from the out-of-space CSV to another one.  I then resumed the VM that was in the Paused-Critical state.

The VM appears to be fine and operating correctly.  I can’t find any signs of data loss.  The snapshot I deleted no longer shows in Hyper-V manager.  Inspecting the disks show an intact differencing disk chain that has 3 links in it (Base
VHD, AVHD for the remaining snapshot, and AVHD for "Now").  This is what I would expect.

My concern is that there are 2 additional AVHD files on the CSV that are not chained into running configuration.  And an examination of the VM XML config file (version 2) shows that disk_merge_pending is true.

My suspicion is that there when I shut down the VM, it will try to finish the merge that was aborted when space ran out on the CSV.  I am not sure what affect this will have on the state of the data, since and inspection of the current chain no longer
includes these AVHD files.  Or, it may be that everything completed once space became available, and the flag simply didn’t get cleared or the AVHD files deleted.

Can anyone offer any insight into what I can expect when I shut this machine down?  Should my data remain intact?

Obviously I will take a backup immediately before shutting down, but I don’t want to have to do a restore if I don’t have to.

Thanks in advance for any help or insights.

Tim Reid

Read full post . . . .

How do I replicate to a server that already has a copy of the VM Guests?

Hello,

I have two servers at two different locations.   The internet speed would have taken forever to do an initial sync of all the VMS.   I have the VHDX files and VMs on both the production and the replica server.    I have no idea
how to do a sync if the data is already on the second server - just a day apart.

Read full post . . . .

hyper-v windows 2012 R2 – Move VM from one drive to another drive on the same Hyper-v server questions?

Dears,

I have two Hyper-V servers windows 2012 R2 (one is primary & other is Secondary)

- on primary hyperv- i have two virtual machines -a) DC server, b) SQL server

- Replication enabled for only one Virtual machine i.e."SQL server" between two hyperv server (primary & secondary)

- disk space becoming full on VM - SQL server, so we are adding more sas drives with new raid-5 configure

- After add disk i want to move this VM -SQL server to this new disk so will have more space.

- Need to know the correct procedure/steps for move this VM -"SQL server" & if need to take any precaution if it fails because     this SQL server is my business production server.

- Do I need to make any folder as share on new disk?, Do i need to have enough on the existing disk (my SQL server is around 400 GB but I have left space only 60GB free)?,

I want to take full precaution because as i said this is my production server.

- In my knowledge first I would need to pause replication, than stop virtual machine, detach any scsi drives from VM (i have external hdd attached for regular backup), then use MOVE command for Hyperv manager.

 

Read full post . . . .

Go Que Newsroom

Categories