Backtrack:  
 
showing posts tagged with 'hyperv'
 
by lunarg on September 18th 2019, at 12:02
When adding a new disk to a live system (e.g. a linux VM), the new disk may not always show up. Additionally, when resizing a disk through the hypervisor, the VM may not always immediately have the new size available for use. Luckily, you can trigger a rescan of the SCSI bus through the sysfs system.

For this to work, you'll need to have shell and root access to the server/VM.

Modern linux kernels automatically detect the addition of a disk, but in case it doesn't, you can trigger a rescan of a specific (virtual) SCSI controller:

echo "- - -" > /sys/class/scsi_host/hostX/scan

Replace hostX with the number of the SCSI controller, where host0 is the first, host1 is the second, et  ...
by lunarg on August 23rd 2017, at 14:11

Hyper-V does not allow to be installed on a machine that's already virtual (such as on another Hyper-V or VMWare). For VMWare, you can circumvent this by adding custom configuration parameters to the VM's configuration.

Add these to the VM's configuration, either through the vSphere (web)client, or by directly editing the VMX-file:

hvh.enable = TRUE
hypervisor.cpuid.v0 = FALSE 

If you're editing the VMX-file, you need to enclose the values (behind the =) in double quotes (").

by lunarg on January 27th 2015, at 12:56
You may get an error during the upgrade of Veeam Backup & Recovery to version 8, stating that the vPower NFS service is unable to start. Alternatively, when updating the individual components, you may also get a similar error (such as: "Error 1920.Service Veeam vPower NFS Service (VeeamNFSSvc) failed to start. Verify that you have sufficient privileges to start system services.").

There are several reasons possible for this, but the most likely one is a wrong NFS Datastore path specified in the registry, usually because the drive that the datastore is pointing to, is no longer present.
Another reason could be that your server has the "NFS sharing" feature installed,   ...
by lunarg on September 9th 2014, at 12:04

Shutdown the VM.

Open .vmx file with Notepad or another plain text editor.
Add these lines:

hypervisor.cpuid.v0 = "FALSE" 
mce.enable = "TRUE"
vhv.enable = "TRUE"
vpmc.enable = "TRUE"

Save and start the VM. Now you can install the Hyper-V role.

 
showing posts tagged with 'hyperv'