Hi Experts
I am using HyperV 2016, i have requirement to extend C drive of the Virtual Machine, Can i extend C drive size on the Virtual Machine without shutdown.
↧
Extend HardDisk
↧
Hyper-v export and import logs
Hi,
I've had problems importing exported hyper-v virtual machines recently. I have also just exported and received no confirmation of the completion of the export.
In which of the hyper-v event logs is this information logged?
Thanks.
↧
↧
Run out of space in merge huge AVHDX file. any idea what to do?
I Hope you will help me with a huge problem..
The problem start in one of our VM in hyper V.
I had a 2TB unallocated space in that machine (win server 16) it and I wanted to move this space to the host (win server 16). so from the host I run a powershell to shrink space of this VM. BUT.. I had checkpoint on this VM (!!)..
So after the shrink process I couldn't power on that VM.
This VM had a 16TB hard disk.. (and no backup)..
In the end I had one VHD that was 30GB on AVHDX that have 500GB (this was the newest/latest checkpoint) and one more AVHDX with 15+TB..
After a lot of error message (mismatch etc) I decided to start merging the two AVHDX to the parent VHD. the first AVHDX (the 500GB) merged fine. now I need to merge the 16 TB to the parent.
before the second merge process I enter to the settings of that VM (in the host).. In the hard disk I saw that this VM is pointing to the first AVHDX (that is not exist because I did the first merge process with that file) so of course the VM didn't power on... I didn't wanted to point the hard disk to the second AVHDX (the 16 TB ) so because of that I started the second merge..
In that server (host) I had 5.5 TB free so I started the merging process. Now I have 400GB so I paused the merging process. the VHD is something about 6.5TB and the AVHDX is still 16TB.
How can I increase the C drive? If I add external 10TB USB drive. how can I increase C drive with that USB?
What will happens if i'll cancel the merge processes now and change the AVHDX in settings of this VM manually?
I so need to get to the files in that VM.. So Frustration...
↧
How to Install Guest OS from USB
I need to install an operating system onto a Hyper-V virtual machine via a bootable USB flash drive. I am not using an ISO file. It has to be from this bootable USB flash drive. I am using a product called SHB (Secure Host Baseline). The project I am working with at my company requires this setup to install this pre-configured version of Windows 10 (SHB) onto virtual machines.
So far I am not finding any info out there on how to accomplish this task. I could really use some guidance on this subject. Essentially, I want Hyper-V to boot from the USB flash drive at the initial startup. I have selected the option to "install OS later" so that I can install this specific version of Windows 10.
↧
Unable to add new 2019 HyperV node to 2012R2 HyperV Cluster
Hi all,
I could really use some help here. I evicted an failed HyperV node from our 2 node cluster, rebuilt it and am trying to re-inject it back to the cluster.
NOTE: The host was rebuilt using the same node name.
When i try to add the node i get the following error:
'Cluster service on node SERVER2 did not reach the running state. The error code is 0x5b4. For more information check the cluster log and the system event log from node SERVER2. This operation returned because the timeout period expired.'
In the FailoverClustering event log i see:
cxl::ConnectWorker::operator (): HrError(0x00000002)' because of '[SV] Schannel Authentication or Authorization Failed'
mscs_security::SchannelSecurityContext::AuthenticateAndAuthorize: (2)' because of 'Cluster certificate doesn't exist'
I did a search for the above errors however none of the below has worked:
- Confirmed i am am able to ping the hosts via the managment, production, clustercommunication and livemigration network interfaces.
- Confirmed iSCSI could connect to CSV volumes
- Ensured IPV6 is enabled
- Ensured the DCHP client service is running
- Ensured the system could access the QUORUM witness (able to write to the directory)
- Checked 'Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters' to check for 'DisabledComponents'
- Did a search in AD for a duplicate computer account hostname matching the the node to be added.
- Tried re-adding the node at least 12 times
I am lost of ideas apart from the fact that i am trying to add a 2019 node to a 2012R2 node cluster.
Any advice would be greatly appreciated.
↧
↧
When restarting Hyper-V server on Windows 2016 it shuts down.
Hi
We are unable to restart the Hyper-V Windows 2016 server: when restarting the Hyper V Server it shuts down instead, and we need to physically push the power button on the server in order to start it again.
The Virtual Windows 2016 server does not have this problem, and restarts fine.
In the event Viewer we have the following information:
The process C:\Windows\system32\shutdown.exe (HYPERV) has initiated the restart of computer HYPERV on behalf of user HYPERV\Administrator for the following reason: No title for this reason could be found
Reason Code: 0x800000ff
Shutdown Type: restart
Comment:
Event ID: 1074
*****
We had tryed to shutdown via command like shutdown /r .
And we have got following sugestion:
A
click start and type power plan and select 'choose a power plan' from the list
next to the power plan that is selected click 'change plan settings'
click 'change advanced power settings'
under power buttons and lid set power button and sleep button (and lid if its there) to do nothing.
should prevent events from power button.
B
Go to "Settings"
Select "System"
Select "Power and Sleep"
Select "Additional Power Settings"
Select "Choose what the power buttons do"
Select "Change settings currently available"
Ensure that "Turn on fast start up" is deselected (unticked)
Click on "Save Changes"
The sugestion did not help
A hint would be nice
Best Regards
John B
↧
P2V of SBE 2016 won't boot
Hi,
I have an SBE 2016 Server running on physical hardware. I am trying to P2V it so that it can be run as a VM
on a 2019 Hyper-V host. I have tried various ways to P2V the SBE 2016 Server using Disk2VHD doing it as a
VHD or VHDX, but when I build a new VM on the Hyper-V host and attach the imaged VHD/VHDX it refuses to boot.
All I get is black screen with a flashing cursor about 4 lines down the screen. If I mount the VHD's in Disk Manager
on a PC I can see the contents of the VHD's fine.
Anybody have any suggestions how to fix this?
Thanks
DB
↧
Move hyper-v manager profile to local account
We have a host server with multiple VMs that is on the domain, we want to remove it from the domain but keep the VM profiles that appear in hyper-v manager.
↧
Cannot perform shared-nothing live migration from a management VM
Hello.
I have several standalone Hyper-V Server 2016 hosts. All hosts are configured for live migration using constrained delegation and Kerberos (as detailed here https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/set-up-hosts-for-live-migration-without-failover-clustering).
The problem is despite these settings (LM enabled, LM network set, Kerberos protocol configured, constrained delegation configured), when I initiate the migration using Hyper-V manager or Powershell from a management computer, this fails with the dreaded error (below). However when I initiate migration directly from the source Hyper-V host (using Powershell as there's no GUI), the migration successfully proceeds.
The management server is in the same domain and I'm logged on as domain admin.
The error is:
There are events on the source hosts:
Event 20308, Hyper-V-VMMS: "Failed to authenticate the connection at the source host: no suitable credentials available."
Event 20306, Hyper-V-VMMS: "The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host '<destination_host_FQDN>': No credentials are available in the security package (0x8009030E)."
Event 21024, Hyper-V-VMMS: "Virtual machine migration operation for '<VM_name>' failed at migration source '<source_host_netbios_name>'. (Virtual machine ID 2CF6050E-A08A-4B0C-A321-648AF12517B4)"
Events on the destination host:
Event 22040, Hyper-V-VMMS: "Failed to receive data for a Virtual Machine migration: An existing connection was forcibly closed by the remote host. (0x80072746)."
Event 20402, Hyper-V-VMMS: "The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the destination host: An existing connection was forcibly closed by the remote host. (0x80072746)."
Event 20400, Hyper-V-VMMS: "The Virtual Machine Management Service blocked a connection request for a Virtual Machine migration from client address '192.168.30.7': An existing connection was forcibly closed by the remote host. (0x80072746)."
Here's a screenshot of constrained delegation configuration of one of the hosts, the configuration is identical on all hosts, ie. cifs and Microsoft Virtual System Migration Service allowed for all other Hyper-V hosts.
Any help is appreciated.
↧
↧
Windows 8.1 pro Remotefx USB redirection
We need local USB redirection from Windows Server 2019 host to Windows 8.1 Hyper-V guest.
On Windows 10 Pro guest, the redirection is working, meaning that all host settings and guest settings are correct.
In the connection bar, the little additional icon appears and devices connected to the host can be redirected to the guest.
However same setting with Windows 8.1 Pro does not work. RemoteFx USB devices can be selected from the enhanced session settings but they never appear in the guest nor is there the little additional icon.
From sources we learned that this is only possible with Windows 8.1 Enterprise? Really? Why is it working with Windows 10 Pro but not with Windows 8.1 Pro? This does not make sense.
Please add the missing drivers to Windows 8.1 Pro so that RemoteFx USB redirection can be used.
↧
Server 2019 VDI on Hyper-V cluster
Hi,
I'm not sure what to put this under but I am having an issue with creating a Microsoft VDI collection on to a Hyper-V cluster.
I have 3 Hyper-V hosts in a cluster and the Connection Broker is a VM on this cluster. I am trying to deploy to the same cluster.
From this connection broker I can create the collection fine if I select to store the VM on the virtualization host at a specific folder but if I choose to store on a cluster shared volume then the setup fails with the following (original VM names and ID replaced):
Failed to export virtual machine "VMTemplate". Can not merge Automatic VHD chain for 'C:\ClusterStorage\Volume1\VDI\VMTeplate_1833A97A-5803-480E-8659-E44C01D950DA.avhdx'
I did notice that the Connection Broker creates a folder "C:\ClusterStorage\Volume1\VDI\Win10" on itself (Win10 is the collection name I was giving it).
Any help would be greatly appreciated.
↧
Event ID 153 - The IO Operation at logical block address xxxx for Disk 3 was retried.
Hi,
I have my Exchange 2013 on Hyper V OS and Exchange installation is on one drive and mailbox database is on another HDD.
I am getting error on Exchange database HDD with warning
Event ID 153 Disk
Please help me to get rid of this warning, when warning occur my mailbox get disconnected.
The IO operation at logical block address 6c1a8 for Disk 3 was retried.
Please help me to get rid of this warning, when warning occur my mailbox get disconnected.
↧
Virtual switch has no TCP/IP bindings. How will VMs communicate outside?
OK so I am trying to understand this.
If it is recommended to have a separate NIC for management, how do VMs communicate with external networks (outside Hyper-V)?
I have built and managed many Hyper-V clusters over the years but always have used virtual switches which are shared with management partition....remember that option while creating a Hyper-V switch "Allow management operating system to share this network
adapter”?
Right
This time, I am trying to go with the "best practice".
- I have one dedicated NIC for host management.(I believe I do NOT need to create a virtual switch for this traffic)
- I have another NIC which I want to use for VM traffic going outside to the world.
For the second one, I should create a virtual switch and eventually my VMs would be able to communicate outside the host.
THAT is where I am stuck. I see no way to do that, yet. If I create a virtual switch with the checkbox checked for "Allow management operating system to share this network adapter” I do get a vNIC created and TCP/IP is there. (but isn't that what I am NOT supposed to do?). If I uncheck that, TCP/IP is removed from the switch. So no external network communication is possible by the VMs assigned to that switch.
What am I missing?
-Rajeev rajdude.com
↧
↧
2012 R2 - Checkpoint cleanup from failed VM backup
We recently had a network traffic / virtual switch issue crop up, due to VMQ being enabled and improperly configured on Broadcom 10GbE adapters. While that failure occurred, our backup appliances were taking backups of VMs. Because of lost network connectivity, the Hyper-V checkpoints used for those backups remain on some of our VMs.
These checkpoints do not have the usual "Delete Checkpoint" / "Delete Checkpoint Subtree" options available to them. How do I remove them so the virtual disks are merged and back to a single VHDX per virtual disk?
↧
Cluster node - Event 252 - cluster service crashed
We have a 4 node Windows Server 2016 Hyper-V Cluster. Over the weekend, one node of the cluster reported this in the System event log:
"Memory allocated for packets in a vRss queue (on CPU 14) on switch 620355C8-4D29-4D91-BE80-B840921EDC4A (Friendly Name: Team_Trunked) due to low resource on the physical NIC has increased to 256MB. Packets will be dropped once queue size reaches 512MB."
Seven seconds later it reported that it had increased to 512MB, then two seconds later the LiveMigration NIC reported it had begun resetting, then a few seconds later a reset was issued to \device\raidport1 (source: ql2300). After two minutes of this and a few other repeats, I started getting warnings of CSVs no longer being able to access this cluster node and then the Cluster service shut down on this node and all VMs are shut down and migrated to other nodes in the Cluster.
Our weekly DPM backups of the VMs had started about 1.5 hours before this occurred so there was some additional strain on the NICs at this time, though that should have gone through the NIC the OS is running on so I don't know why that would have affected the other NICs where the VMs general data was going through (Team_Trunked) and the LM NIC.
Does it make sense that the first warning about Event 252 would have caused all this or is there more to this?
↧
Problems with HyperV writers during VM backup (from host).
We are using Veritas Backup Exec and recently one of our VMs has stopped backing up and for the life of me I cannot get the blasted thing to work.
Lots of error in the event logs, on the host we have:
Log Name: Application
Source: VSS
Date: 12/08/2019 12:09:03
Event ID: 8229
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer:
Description:
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. 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:
PrepareForSnapshot Event
Context:
Execution Context: Writer
Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Name: Microsoft Hyper-V VSS Writer
Writer Instance ID: {80e6791b-1b9c-4064-a146-eb4a27a724b2}
Command Line: C:\Windows\system32\vmms.exe
Process ID: 2156
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="VSS" /><EventID Qualifiers="0">8229</EventID><Level>3</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2019-08-12T11:09:03.000000000Z" /><EventRecordID>88259</EventRecordID><Channel>Application</Channel><Security /></System><EventData><Data>0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.</Data><Data>
Operation:
PrepareForSnapshot Event
Context:
Execution Context: Writer
Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Name: Microsoft Hyper-V VSS Writer
Writer Instance ID: {80e6791b-1b9c-4064-a146-eb4a27a724b2}
Command Line: C:\Windows\system32\vmms.exe
Process ID: 2156</Data><Binary>2D20436F64653A20575254575254494330303030353334372D2043616C6C3A20575254575254494330303030323934392D205049443A202030303030323135362D205449443A202030303030363736382D20434D443A2020433A5C57696E646F77735C73797374656D33325C766D6D732E657865202020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary></EventData></Event>Have tried all maner of reset s and reboots and still struggling - can anyone help?
↧
Moving .VHDX and Retaining NTFS and Share permissions
Hi,
I have a server that has a .VHDX we will be moving to another server. This volume is 9TB so I want to avoid copying it if at all possible.
Does detaching it from one VM and re-attaching to another retain the NTFS and Share permissions of the volume? If not is there a way that I can do it that it would?
Thanks!
↧
↧
Disk management takes forever to open and it gives me a prompt to initialize the disks which were already initialized.
When trying to access Disk management, i am getting a prompt to initialize the disks which are already initialized, i am not able to access Diskpart as well via command prompt.
First, disk management takes forever to open and it gives me a prompt to initialize the disks which were already initialized.
First, disk management takes forever to open and it gives me a prompt to initialize the disks which were already initialized.
↧
External Ethernet adapter already bound error when no virtual switch exists
When I try to create a virtual switch it gives me the error "External
Ethernet Adapter is already bound to the Microsoft virtual switch protocol"but I don't have any virtual switches set up at all. Is there a way to clear this and start over?
↧
Error VHD when attached
Hi,
Need your advised on this error. Already removed security permission and use as local account user.
I'm using administrators privileged or even login to local administrator of my windows, but same error. Cannot attached .vhdx file but I tried other vhdx file which I can and no problem encountered.
This vhd is created in Windows server 2012 std Hyper-V Manager and trying to import or attached to my Windows 10 Hyper-V.
↧