News

Go-Que offers news and technical knowledge articles from all IT visualization software brands. Go-que is sponsored by go-que.net & go-que.nl.

Abonnement IPTV France Pas Cher

Read full post . . . or http://www.go-que.com/abonnement-iptv-france-pas-cher

Read full post . . . or https://meilleurabonnementiptvavis.wordpress.com/2021/12/23/abonnement-iptv-france-pas-cher/

Comment configurer en WiFi mon formuler Z5G. Pour le moment il directement raccordé en direct sur mon modem. J’ai essayer aussi par une clé wifi mais cela ne fonctionne pas. Essayer de formater la clé usb avec Rufus. Lors de la lecture, le son est plutôt correct mais la vidéo se figé dès le départ.… Continue reading Abonnement IPTV France Pas Cher

Can I rename .mrt and .rct files?

I would like to rename the Virtual Disk file on some of our VMs … we are using Nakivo for backups, so the .rct and .mrt files are present for each .vhd(x) disk file on the VMs that we are backing up.

I know how to rename a .vhd(x) file … by shutting down the VM, physically renaming the file, reassigning the VM’s disk to the new filename, then restarting the VM.

My question is — what do I do about the .mrt and .rct file that accompany the .vhd(x) file?   Do I just manually rename those as well?  Or do I have to delete them somehow before renaming the disk file?  Or is there a utility that takes care
of all this?

I could not find documentation anywhere that talks about this. If there is doc I would appreciate a pointer to it … otherwise if there is a best practice for doing this then please explain 🙂

Thanks.  John

Read full post . . . .

What do you like most in your life?

What do you like most in your life? You will ask why this is to be a human

Read full post . . . .

Failure to Boot on Red Hat Enterprise Linux (RHEL) or CentOS 8 using Hyper-V 2016

When using RHEL 8 or CentOS 8 as the guest operating system on a virtual machine (VM) running on a Microsoft Hyper-V Server 2016 host, the VM in some cases fails to boot and returns to the GRUB boot menu. It sometimes takes up to 20 attempts before the vm starts
(VM therefore stays stopped after 5 retries to boot kernel with grub)

It seems that it’s this bug: https://access.redhat.com/solutions/4796261

The following error is logged in the Hyper-V event log:

The guest operating system reported that it failed with the following error code: 0x1E

We are increasingly seeing this problem occurring on sone clusters and on others not

Any Ideas, Workarrounds, Fixes? For example is it possible to increase the retries of 5 somewhere? Concerning Red Hat the Problem will be solved in Hyper-V 2019, but as we have 200+ physical nodes it takes a lot of time to upgrade and we need some workarrounds

Read full post . . . .

Cannot enable the Promiscuous mode at Virtual switch for spanning port

Hello,

How to enable Promiscuous mode at Virtual machines (Hyper-V) windows 2019 server

What the power shell command and version to run this command please?

Thanks,

Bilal

Read full post . . . .

Windows Admin Center cannot connect to hyper v core 2019

I need help connecting to Windows server core 2019, I currently have Hyper-v core 2019 installed on a dell server, then install the windows admin center tool on another computer, using Windows 10 , when running the windows admin center application to connect
to hyper-v core, the following error message

"WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default,
the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet.

Thanks for your support

Read full post . . . .

Windows 2012r2 Hyper-V Generation 2 firmware boot order No boot entries are configure

I have 2 host HyperV which configure in cluster. Inside the host there are multiple virtual machine. When I try to create new virtual machine usung Generation 2, its firmware boot order shows " No boot entries are configure". How to solve this
issues without break the failover cluster configuration? For your information, all virtual machine inside the host are production.


sha

Read full post . . . .

Windows 2019 Hyper-V Host Static or Dynamic ram allocation

We are setting up a Windows 2019 Hyper-V VM running on a Physical Windows 2019 Server with 64GB of Ram. The Physical server will be running a few lightweight apps and also the Hyper V roles. I have been reading up on Dynamic V’s Static memory allocation
for the Hyper-V server and cannot decide which option is better. As I see it I have 2 ways I could go -

1. Allot 32GB of static ram to the Windows 2019 Hyper-V VM

2. Enable Dymanic Ram Set 8GB of Ram as a minimum Value, Set the Max Ram to 32GB with a 20% Memory buffer

We are planning to use the Hyper V for lightweight Remote desktop use.

What I am wondering is, does having Dynamic Memory instead of static cause speed issues for the VM when the amount of RAM required has to be increased or is this so fast that it is not noticeable.

Any thoughts would be appreciated 

Read full post . . . .

Import VMs Exported from Hyper-V 2019 to Hyper-V 2012 R2

Hi,

We have a situation that we have to do the following:

  1. Move (Export/Import) VMs from Hyper-V 2012 R2 (Old Site) to new Hyper-V 2019 (new site)
  2. Add some VHDX to the moved VMs at Hyper-V 2019, and do some upgrade with the custom applications inside VMs
  3. Will keep Hyper-V 2012 R2 (old site) (that host other Apps/VMs) as a disaster recovery platform, so they will keep exporting VMs from Hyper-V 2019 (new site), and import it at Hyper-V 2012 R2 (old site)

Questions are:

  • Is it supported to move (Export/Import) VMs from Hyper-V 2019 to Hyper-V 2012 R2?
  • What  we need to consider when creating/attaching new Virtual Disks at Hyper-V 2019 (new site) to VMs that maybe later imported at Hyper-V 2012 (old site) in case of disaster?
  • Any other points that need to be considered in this scenario?

To share more thought related to this scenario:

  • We have to keep all VMs at Hyper-V 2019 (new site) as G1 including any new VM this to avoid any issue when move it back to Hyper-V 2012 R2 (old site).

Any other points related to disk type, whatever configuration, supportability….? knowing that this will be temp scenario till they build Hyper-V 2019 at old site.

Regards,

Maged

Read full post . . . .

Windows 1709 HyperV replication to Windows 2016 is getting failed

Hello Team,

Windows 1709 HyperV VM replication to Windows 2016 HyperV is getting failed. Giving below error

Please suggest…

Regards

Kedar

Read full post . . . .

Go Que Newsroom

Categories