Import ESXI image - Boot VM is not Working

B

BkBk

New Member
Aug 13, 2024
13
1
3
Hello,
I use import Esxi fonctionality proxmox to migrate server 2019 datacenter on proxmox.
Each time i do this import is working fine. No error message during the migration. Everything good but when i tryed to start the virtual server on the proxmox I get blue screen and the serveur windows 2019 never start.
I see on the forum that it could be necessary to select the correct controler but even i tryed to change I get error message the the virtual tryed to start. It's seem's not recognyse the boot during the migration.

Let me know if you know how to resolve this issue.

I tryed to migrate several esxi vm but each time, I get error error message when the server tried to started and boot.

Could you confirm that Import esxi to proxmox is working ?
Thank you for your help.

1739457533377.png

1739457919002.png
1739457964863.png

1739458029825.png
1739457558138.png

1739457579181.png

I tryed to change scsi controler, bios.. but it’s not working each time.

Have you any idea ?

1739457617935.png

I tryed to change controler.
1739457735313.png
 

Attachments

  • 1739457565577.png
    1739457565577.png
    25.1 KB · Views: 0
  • 1739457545632.png
    1739457545632.png
    51.7 KB · Views: 0
Hello!

To get your VM up and running, try detaching the disk and reattaching it as IDE or SATA. Be sure to check your "Boot Order" under options.
You may need to temporarily return your controller to the LSI until you install the VirtIO drivers.

After you get it up and running, you will need to install the VIrtIO drivers before you switch it back to SCSI
Check out the guide here: https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows
 
Last edited:
Set the controller to VMWare if you haven’t installed the VirtIO drivers before migrating, VMware removes all non-VMware drivers from operating systems, especially if you use ‘their’ deployment tools, to keep people locked in.
 
Weehooey-HSS said:
Hello!

To get your VM up and running, try detaching the disk and reattaching it as IDE or SATA. Be sure to check your "Boot Order" under options.
You may need to temporarily return your controller to the LSI until you install the VirtIO drivers.

After you get it up and running, you will need to install the VIrtIO drivers before you switch it back to SCSI
Check out the guide here: https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows
Click to expand...
Hello,
Even than I install Virtio on windows 2019 before the import, the drives was not recognyse. I need to unattach drive and put ide drive to work. neverless, i remark that the windows server 2019 datacenter doesn't work properly. I have install Hyper V on this server and I tryed to start one virtual machine on this this hyperv server but it's not workig.

For the moment Import esxi thrue proxmox is not working fine. I mean, copy on the proxmox is ok but when i Start the vm is not working without any change. When it's working after drive unattach and put ide drive, I don't have all functionnality for exemple Hyperv over proxmox...
Have you a guide or recommandation to do before import esxi vm to be sure is working fine after.
Thank you for your help
Boris
1739542720950.png
 
Have you set the drive to VMWare PV yet? Proxmox does support it. You need to load your drivers into the boot cache of Windows, if you do it from VMware, dism /image:c:\ /add-driver /driver:d:\viostor\…\viostor.inf . You can also do it from recovery in Windows, by adding the ISO over IDE, using drvload to load the driver, then your volume should show up, then dism… to insert the driver.
 
guruevi said:
Have you set the drive to VMWare PV yet? Proxmox does support it. You need to load your drivers into the boot cache of Windows, if you do it from VMware, dism /image:c:\ /add-driver /driver:d:\viostor\…\viostor.inf . You can also do it from recovery in Windows, by adding the ISO over IDE, using drvload to load the driver, then your volume should show up, then dism… to insert the driver.
Click to expand...
Hello,
I tryed to understand your explonation. Even I unstall drivers viostor on windows, hyper v under proxmox is not working.
the server that I want to migrate to proxmox is a windows server datacenter 2019 under wmware esxi 7.0 update3. On this server I have setup Hyper with some virtual machine. Concretly, I do vitual server (esxi 7) under virtual server (windows server Hyper). When I tryed to migrate this server on proxmox, Hyper v service and server is not working. Do I need to setup something on proxmox to accept virtual machine under virtual machine ?
I really appriciate if you have some idea for this issue.
Have a good day
Boris
 
Hello,
After to have import esxi virtual server on proxmox, windows server datacenter doesn't recognyse anymore my licence key. I suppose, due to this problèm, hyperv is not working also.
Have you any idea to keep initial licence wndows 2019 datacenter to avoid to buy another one ?
I would to migrate esxi server to proxmox and keep the licence windows 2019 datacenter.
For the moment I didn't found the solution for this issue.
Thank you very much for your help
 
BkBk said:
Hello,
After to have import esxi virtual server on proxmox, windows server datacenter doesn't recognyse anymore my licence key. I suppose, due to this problèm, hyperv is not working also.
Have you any idea to keep initial licence wndows 2019 datacenter to avoid to buy another one ?
I would to migrate esxi server to proxmox and keep the licence windows 2019 datacenter.
For the moment I didn't found the solution for this issue.
Thank you very much for your help
Click to expand...
Your License key is tied to the hardware ID that was generated under ESXi and needs to be rekeyed for Proxmox. If you are unlucky and have datacenter licensed by the CSP instead of a EA/VLK you are limited to 512 activations per license package before the key is burned out. You will have to contact MS (through partner if its a CSP key) to get the keys regenerated/licensing activations increased.

My advice is to get your VMs cut over and in the 90day trial period. Get Q35, VirtIO, and drivers going BEFORE working on the keys. Do not active under i440FX because you cannot mix and match activation between that and Q35 for these stupid keys now. KVM changes the hardware IDs for VMs on i440FX and Q35 causing activation issues.

MSFT support might try and push you down the AVMA activation path, which is only supported on HyperV and no other Hypervisor and you will probably need to them max out the available activation seats on your keys.
 
guruevi said:
Just re-enter your license key, you should be able to reactivate several times unless you don’t have a valid key.
Click to expand...
I tryed to re-enter my license but it's not accepted any more. My license was ok before to tryed to import esxi vm. Impossible to validate the liense by phone because key licence is not working and i don't have a possibility to activaye license by phone because id code is not appear. I'm sure that the license windows server 2019 datacenter was ok.
On the esxi this licence is activate and working fine, it's when import the virtual server thrue the share esxi proxmox that it's not working any more.
Thank you again for you help
Boris
 
BkBk said:
I tryed to re-enter my license but it's not accepted any more. My license was ok before to tryed to import esxi vm. Impossible to validate the liense by phone because key licence is not working and i don't have a possibility to activaye license by phone because id code is not appear. I'm sure that the license windows server 2019 datacenter was ok.
On the esxi this licence is activate and working fine, it's when import the virtual server thrue the share esxi proxmox that it's not working any more.
Thank you again for you help
Boris
Click to expand...
Do you know what kind of purchase your Windows Datacenter licensing is? If its EA you just need to contact MS through Email to request an activation reset. However if the keys are bought through CSP then your reseller must contact MS on your behalf. Please see this - https://www.reddit.com/r/Proxmox/comments/1ffeszy/psa_migrating_vmware_pve_csp_activated_windows/
 
You must log in or register to reply here.
Top Bottom