Hyper-v

The boot loader did not load an operating system.

My VM is installed and running but when I connect, I get the error that it didn’t load an OS. "No operating system was loaded. Your virtual machine may be configured incorrectly. Exit and re-configure your VM or click restart to retry the current boot
sequence again."

I downloaded a Win XP iso and used it during the initial creation of the VM. In the Firmware setting, the DVD Drive is pointed to the Win XP iso on my host PC’s C: drive.

I never got the Wizard I’ve seen described, so I don’t know what other configurations were possible.

How can I get up and running?

Side note: I tried 10-15 times to install a VM but always got out of memory messages (failure). Getting this one installed felt like a fluke.

Read full post . . . .

The boot loader did not load an operating system.

My VM is installed and running but when I connect, I get the error that it didn’t load an OS. "No operating system was loaded. Your virtual machine may be configured incorrectly. Exit and re-configure your VM or click restart to retry the current boot
sequence again."

I downloaded a Win XP iso and used it during the initial creation of the VM. In the Firmware setting, the DVD Drive is pointed to the Win XP iso on my host PC’s C: drive.

I never got the Wizard I’ve seen described, so I don’t know what other configurations were possible.

How can I get up and running?

Side note: I tried 10-15 times to install a VM but always got out of memory messages (failure). Getting this one installed felt like a fluke.

Read full post . . . .

Default Switch failing after windows update

Hi all,

I am running a VM on Hyper-V on my HP Z-Book and has been running fine until I did a Win 10 upgrade. Now when my Pc boots up the Hyper-V default switch continually drops in / out with "Attempting to Authenticate" which seemingly fails, then flicks
to a disabled state and dissapears and then just continues to do this.

I have tried all sorts of troubleshooting including uninstalling Hyper-V multiple times, reinstalling my laptop nic drivers multiple times, and performing Network resets. Nothing has fixed it. Sometimes it will also cause my laptop NIC to do the same thing,
but if I stop the Hyper-V service my laptop NIC stays connected and doing a network reset fixes it. I am real noob when it comes to network stuff, so any thoughts or help would be greatly appreciated.

thanks heaps

Read full post . . . .

Degraded performance with Core scheduler

Hi.

Since Core scheduler is now the default in WS2019/Hyper-V Server 2019, we’re now evaluating the impacts of this change.

I (think I) understand the implications of the Core scheduler, but from our testing, it’s severely degrading performance even in scenarios where it (in my opinion) shouldn’t.

Testing scenario: Dell PE R740xd with Xeon 6244 Gold (2 CPUs, 8 physical cores, HT enabled), Hyper-V Server 2019 installed with updates up to 2019-11 (since I couldn’t install 2019-12 CU on ANY Hyper-V Server 2019 host). Single testing VM running on the
host:

 - WS201 Standard, 4 vCPUs, 2-8GB vRAM (dynamic), VM config version 9, HWThreadCountPerCore=0 (ie. SMT enabled, default on 2019)

We’re seeing degraded CPU performance in the VM under Core scheduler. I thought that Core scheduler would be limiting VM density (and therefore performance), but only in situations where there are many VMs (vCPUs) running/assigned on the host.

We tested synthetic performance with Passmark PerformanceTest8 and Geekbench5.

Here’s a comparison (the only change is the scheduler used, nothing else is modified):

Passmark

Geekbench:

Is anyone else seeing similar behavior? Is this expected?

If this is expected even in a scenario like this (single/few VMs), then we’ll be forced to switch to classic scheduler for the time being.

Read full post . . . .

[New Admin Question] Remote into Server

I downloaded and installed the Core Hyper-V 2019 (where you only use PowerShell). I cannot for the life of me figure out how to "remote" into the VM after starting it. I’ve used the Virtual Manager in Windows 10 Pro before  where you can click
"CONNECT" and I’m sure there is another term that I don’t know but I’ve tried Googling my eyes out trying to figure this out.

In other news, I’ve tried to connect my Hyper-V Management Console from my Windows 10 Pro box to simply use the connect button, but I get an error: "The operation on computer "HyperServer" failed: The WinRM client cannot process the request.
A computer policy does not allow the delegation of the user credentials to the target computer because the computer is not trusted. The identity of the target computer can be verified if you configure the WSMAN service to use a valid certificate using the
following command: winrm set winrm/config/service @{CertificateThumbprint""} OR you can check the event viewer for an event that specifies that the following SPN could not be created: WSMAN/. If you find this
event, you can manually create the SPN using setspn.exe. if the SPN exists, but CredSSP cannot use Kerberos to validate the identity of the target computer and you still want to allow the delegation of the user credentials to the target computer, use gpedit.msc
and look at the following policy: Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow Fresh Credentials with NTLM-Only Server Authentication. Verify that it is enabled and configured with an SPN appropriate
for the target Computer. For example, for a target computer name "myserver.domain.com", the SPN can be one of the following: WSMAN/myserver.domain.com or WSMAN/*.doman.com. Try the request again after these changes.

Here is all the items I’ve accomplished via both Client and Server:

// Server
[X] Enable-PSRemoting -Force
[X] Enable-WSManCredSSP -Role Server
[X] Set-Item WSMan:localhostClientTrustedHosts -Value "PC-J86"
[X] Set-NetConnectionProfile -Name "Network" -NetworkCategory Private

// Client
[X] Enable-PSRemoting -Force
[X] Enable-WSManCredSSP -Role Client -DelegateComputer "HyperServer"

[X] Start-Service -Name winrm
[X] Set-Item WSMan:localhostClientTrustedHosts -Value "HyperServer"
[X] Stop-Service -Name winrm

[X] Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All -All

[X] gpedit.msc > Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow delegating fresh credentials with NTLM-Only server authentication
 > Enabled
 > Show > WSMAN/HyperServer

Thanks in advance and any help would be awesome.

Read full post . . . .

Ubuntu 18.04.3 LTS Not Working in Enhanced Mode

First, my hardware:  x64 Dell XPS 8930 with an i9-9900 (BIOS 1.1.10 (10/31/19)) with 32GB RAM, 4TB internal storage, 8GB nVidia 2770.  OS: Windows 10 Pro, build 18362

Ran Hyper-V Quick Create and Ubuntu 18.04.3 LTS shows in ‘Select an operating system’ so selected it.

Selected Enhanced Session (screen was aqua) - Session is Xorg (also tried X11rdp and sesman-any with same result)

Waited…

Received error - was able to connect sesman and login but when started connecting - failed ("some problem"). If I switch to Basic Session, no problems but cannot connect to Windows drives and that’s critical as all of my scripts, databases, configurations
are in a Windows folder.  I could blow away Hyper-V and run VirtualBox but would rather use Hyper-V if it works.  HELP!!!

In advance, thank you!

Nick.

Read full post . . . .

Problem with Enhanced Session Connection

I’m getting this error when I try to connect to Ubuntu through Hyper-V:

Read full post . . . .

Troubleshooting Hyper V

Hi quick query

Looking to troubleshoot a situation from a few weeks ago

Customer has a failover Hyper V setup, issue was connection to second HyperV went completely 

From the event log I am seeing a lot of 1254 failover cluster errors

I did a filter and these happen 3 days before this incident happened

Whats best way to troubleshoot this and do a RCA, is 1254 serious enough to make this happen what causes 1254 errors?

Thanks in advance

Read full post . . . .

Live migration error: Mirror operation failed. General access denied error. 0x80070005

I keep getting an error when performing a live migration from one host to another. There were 5 VMs on the source host. I moved 4 of them to the destination host without issue. For some reason, the last one keeps failing. It will perform the migration, and
once it gets to 100%, it errors out and fails. After the failure, the VM reboots on the source host and comes back up normally (hard reset). There is no VM on the destination host, but there is a vhdx file in the proper location that is the same size as the
source vhdx file.

The only difference that I can tell between the machines is that the one that is failing is 650GB (takes around 8 hours to migrate). The next highest is 350GB (no issues).

Both hosts on the same domain. Both hosts are running Hyper-V Server 2012 R2 (not Windows Server).

Both hosts are configured with the default options and locations (mostly).

Both hosts using local storage (no NAS/SAN/shared storage).

File permissions of source vhdx look identical to all other vhdx files on my other hosts.

I have 15 other hosts set up similarly on the same domain/network. I’ve done hundreds of live migrations between them, and never had an issue (up until this one).

Things I’ve tried:

1) Migrating to a different destination host. Same issue.

2) Shutting down the VM. Deleting the VM. Creating a new VM. Attaching the same vhdx file. Same issue.

3) Migrating a different VM from the destination host to the source host, then back again. Works just fine… The issue seems to be only with this VM and/or vhdx file.

Full error:
There was an error during move operation.

Virtual machine migration operation failed at migration source.

Mirror operation failed.

Virtual machine migration operation for ‘VM-NAME’ failed at migration source ‘SOURCE-HOST’.

Migration did not succeed. Mirror operation failed for the source VHD file ‘C:userspublicDocumentshyper-vVirtual hard disksVM-NAME.VHDX’ to the destination file ‘DESTINATION-HOSTSOURCE-HOST.1856233294$CuserspublicDo…Virtual hard disksVM-NAME.VHDX’:
‘General access denied error’ (‘0x80070005’).

Thoughts on possible issues:

1) Is it possible that the permissions/kerberos tickets expire due to the long migration time?

2) Is there an issue with this path: DESTINATION-HOSTSOURCE-HOST.1856233294$CuserspublicDo…Virtual hard disksVM-NAME.VHDX’ ?   The destination path should be DESTINATION-HOSTc$userspublicdocumentshyper-vvirtual hard disksVM-NAME.VHDX
. I am not sure if this is some temporary share created by hyper-v, or if this is where the error is occurring. The file seems to transfer to the correct location, but maybe the final commands after it reaches 100% are using the wrong path so it fails?

3) Some other issue? Any ideas would be appreciated. If you know of anywhere I can look to get more details (logs), please let me know. If you need what is in the logs, please be specific (as there are many logs and places to look).

I wish I could call Microsoft so they could help me with this bug, but unfortunately, there is noone to call.

Read full post . . . .

Hyperv is not in a state to accept replication on the Replica server when using existing VM to start initial replication

I tried to use "Use an existing virtual machine on the Replica server as an initial copy". I exported VM on primary and exported the same VM on replica keeping the same GUID. To make sure it has the same GUID I used powershell to confirm and that
part looks good.

When I wanted to enable replication using mentioned method, i got an error "Hyperv is not in a state to accept replication on the Replica server when using existing VM to start initial replication". 

I have replication working on primary and replica server using certificates for a long time that means replication is properly configured and it is working from primary to replica and vice versa. 

I tried to use the same method using another primary and replica server but got the same error.

We have 2012r2 server on both primary and replica.

Appreciate any help. 

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 40 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995