Hah! Yep! I was just coming here to say that last night I discovered I had a snapshot open on the VM.
Removed the snapshot and what had taken over 10 hours to migrate took only 52 minutes once the snapshot was removed.
New Import Wizard Available for Migrating VMware ESXi Based Virtual Machines
- Thread starter t.lamprecht
- Start date
Removed the snapshot and what had taken over 10 hours to migrate took only 52 minutes once the snapshot was removed.
I rebooted ESXi and I am still getting an error tying to import the VM..
TASK ERROR: unable to create VM 108 - cannot import from 'ESX1-1:ha-datacenter/VMFS-2TB-2/Print/Print.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/esxi/ESX1-1/mnt/ha-datacenter/VMFS-2TB-2/Print/Print.vmdk 'zeroinit:rbd
roxPool01/vm-108-disk-1:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/ProxPool01.keyring'' failed: exit code 1
TASK ERROR: unable to create VM 108 - cannot import from 'ESX1-1:ha-datacenter/VMFS-2TB-2/Print/Print.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/esxi/ESX1-1/mnt/ha-datacenter/VMFS-2TB-2/Print/Print.vmdk 'zeroinit:rbd
roxPool01/vm-108-disk-1:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/ProxPool01.keyring'' failed: exit code 1dammit..... 2e linux machine and this time troubles
----
transferred 15.1 GiB of 50.0 GiB (30.12%)
qemu-img: error while reading at byte 16542331392: Input/output error
Logical volume "vm-303-disk-0" successfully removed.
TASK ERROR: unable to create VM 303 - cannot import from 'ESXI:ha-datacenter/NAS/MAIL/MAIL.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/esxi/ESXI/mnt/ha-datacenter/NAS/MAIL/MAIL.vmdk zeroinit:/dev/pve/vm-303-disk-0' failed: exit code
---
anyone?
ow this is intresting now.. my web interface for the esxi machine is going crasy..
thinks dont responded anymore and now i want to login again and get a OBJECT message where normaly some image is suposed to be
i thing esxi does not always like the way things are being done by this proxmox import function yet
edit
warning i can no longer login to the esxi now.
i geuss only a reboot ( power off ) with running machines ;-( is the only option not that great
Last edited:
What version of ESX? Have you did any of the tuning settings such as Config.HostAgent.vmacore.soap.maxSessionCount?
nope i did not is there a list of all the configs?
beside that after a while it started to work again on it self no reboot needed
I set the import local storage instead of the ceph pool and it finally says vm disk created. I will then move it to ceph if it completes. Anyone else using Ceph Storage Pool?
i was able to transfer a powered off VM from an ESXi 7.0.3 23307199 to Proxmox with the following settings i set on the ESXi Host before i tried to import the VM
Set those, reboot the ESXi Host, and then try to import to Proxmox.
The web interface of the ESXi is unusable while the transfer is occuring, so dont try to use it
Code:
"Config.HostAgent.vmacore.soap.maxSessionCount" on the ESXi Host to "0"
"Config.HostAgent.vmacore.soap.sessionTimeout" on the ESXi Host to "0"Set those, reboot the ESXi Host, and then try to import to Proxmox.
The web interface of the ESXi is unusable while the transfer is occuring, so dont try to use it
Last edited:
Hi all;
I added Esxi as storage. There was a list of vm's to import. I provisioned one and proceeded to do the import and got an error. I removed the Esxi storage and when I tried to add it back I got the following error.
-----
when I checked later I saw that vmware had disabled the root account, I disabled user shutdown and repeated the above process, now it doesn't disable the user but I get the error again;
I added Esxi as storage. There was a list of vm's to import. I provisioned one and proceeded to do the import and got an error. I removed the Esxi storage and when I tried to add it back I got the following error.
Code:
create storage failed: (vim.fault.HostConnectFault) { dynamicType = <unset>, dynamicProperty = (vmodl.DynamicProperty) [], msg = '503 Service Unavailable', faultCause = <unset>, faultMessage = (vmodl.LocalizableMessage) [] } (500)-----
when I checked later I saw that vmware had disabled the root account, I disabled user shutdown and repeated the above process, now it doesn't disable the user but I get the error again;
Code:
create storage failed: (vim.fault.HostConnectFault) { dynamicType = <unset>, dynamicProperty = (vmodl.DynamicProperty) [], msg = '503 Service Unavailable', faultCause = <unset>, faultMessage = (vmodl.LocalizableMessage) [] } (500)While trying new settings before migration, you don't need to reboot ESXi every time. Just "Restart Management Agents" on your ESX-Host.
my version of esxi does not have those options to set
do you need version >7 plus to dho this?
Looks like earlier in this thread it was covered (have to edit xml files instead of gui):
https://forum.proxmox.com/threads/n...sxi-based-virtual-machines.144023/post-648272