Hello
When we tried instant recovery for server agent, automatically created VM hardware version is latest. This example is VM version 14.
I'm experiencing some problems for VM 14 so when i create new VM i always use VM13.
Is there any registry key for that?
-
crackocain
- Service Provider
- Posts: 248
- Liked: 28 times
- Joined: Dec 14, 2015 8:20 pm
- Full Name: Mehmet Istanbullu
- Location: Türkiye
- Contact:
Instant Recovery VM Version
VMCA v12
-
HannesK
- Product Manager
- Posts: 14840
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Instant Recovery VM Version
Hello,
before I start researching a key, could you please help me out on two questions?
1) are you talking about the Windows or Linux agent?
2) what kind of problem do you have with VM hardware version 14?
Best regards,
Hannes
before I start researching a key, could you please help me out on two questions?
1) are you talking about the Windows or Linux agent?
2) what kind of problem do you have with VM hardware version 14?
Best regards,
Hannes
-
crackocain
- Service Provider
- Posts: 248
- Liked: 28 times
- Joined: Dec 14, 2015 8:20 pm
- Full Name: Mehmet Istanbullu
- Location: Türkiye
- Contact:
Re: Instant Recovery VM Version
Hello
Yes i tried Windows Agent. I couldn't use Vmware converter (gave error) so i tried to use P2V conversion via Veeam.
When i'm selected VM Hardware 14 with new installations after a while VM can not boot OS.
For example i'm upgraded linux kernel after the upgrade VM can not boot. I deployed 3 node ceph storage with VM hardware 14. All nodes can not boot after upgrade. Interesting part is this VM's not cloned. All VM's are clean install.
After that i installed ceph nodes and select VM13, all nodes are good after the upgrade. Worked stable.
Same situation i live in Windows 2016. After the Windows upgrade VeeamONE VM can not booted.
I think NVMe controller messed up boot squence (I tried manually hard drive boot, delete nvme controller etc) but i can't wait to Vmware Support so i delete all vm's and create new ones. So i'm in safe spot in VM hardware 13, very reliable.
Vsphere ESXi-6.7.0-20191204001-standard (Build 15160138)
Yes i tried Windows Agent. I couldn't use Vmware converter (gave error) so i tried to use P2V conversion via Veeam.
When i'm selected VM Hardware 14 with new installations after a while VM can not boot OS.
For example i'm upgraded linux kernel after the upgrade VM can not boot. I deployed 3 node ceph storage with VM hardware 14. All nodes can not boot after upgrade. Interesting part is this VM's not cloned. All VM's are clean install.
After that i installed ceph nodes and select VM13, all nodes are good after the upgrade. Worked stable.
Same situation i live in Windows 2016. After the Windows upgrade VeeamONE VM can not booted.
I think NVMe controller messed up boot squence (I tried manually hard drive boot, delete nvme controller etc) but i can't wait to Vmware Support so i delete all vm's and create new ones. So i'm in safe spot in VM hardware 13, very reliable.
Vsphere ESXi-6.7.0-20191204001-standard (Build 15160138)
VMCA v12
-
HannesK
- Product Manager
- Posts: 14840
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Instant Recovery VM Version
Hello,
although it seems to be a quite specific thing for your environment that should be fixed... what do you think about the recommended way by VMware KB and to create a new VM with hardware version 13 and attach the disks?
I just tried it out and it worked fine for me.
1) remove instant VM from inventory
2) create new VM with existing disk
Yes, NVMe controllers mess up boot sequence pretty often in my lab. But that's the same for hardware version 13 in my experience. I stopped using it because it only has downsides.
Best regards,
Hannes
although it seems to be a quite specific thing for your environment that should be fixed... what do you think about the recommended way by VMware KB and to create a new VM with hardware version 13 and attach the disks?
I just tried it out and it worked fine for me.
1) remove instant VM from inventory
2) create new VM with existing disk
Yes, NVMe controllers mess up boot sequence pretty often in my lab. But that's the same for hardware version 13 in my experience. I stopped using it because it only has downsides.
Best regards,
Hannes
Who is online
Users browsing this forum: No registered users and 10 guests