plamen_d's Posts

Hello Bill, This is really weird, I have never heard of such an issue before. From Converter PoV this is P2V (It treats powered on machines as if physical. The fact that they are Hyper-V VMs shouldn... See more...
Hello Bill, This is really weird, I have never heard of such an issue before. From Converter PoV this is P2V (It treats powered on machines as if physical. The fact that they are Hyper-V VMs shouldn't make a difference). In this case Windows event viewer might give more interesting information. Converter's agent log might still be interesting, but it might as well end abruptly. An interesting question is whether these were incremental conversions. There are differences between incremental and one shot.In the first case a change tracking driver runs on the source; also VSS snapshots are performed at different times. It may be an interesting experiment to try the other way and see what happens. Regards, Plamen
Hello, I have not heard of any similar issue before. Any chance the source machine uses TPM (or any other encryption that is outside the OS)? Posting the log bundle for this conversion might be hel... See more...
Hello, I have not heard of any similar issue before. Any chance the source machine uses TPM (or any other encryption that is outside the OS)? Posting the log bundle for this conversion might be helpful for diagnosing the issue. Regards, Plamen
Hello, I am not sure I understand what exactly is going on. Usually BSODs appear after the conversion has finished successfully but the destination VM won't boot. Is that the case? OTOH you mention... See more...
Hello, I am not sure I understand what exactly is going on. Usually BSODs appear after the conversion has finished successfully but the destination VM won't boot. Is that the case? OTOH you mention 84 and 90%. Does it mean the conversion has failed at that percentage? Is so, download the log bundle and look at the agent log (I suppose this source is remote powered on machine; if not - the worker log). If you can afford, upload the logs for examination. Regards, Plamen
The issue is the source machine OS version, not Converter's. Converter doesn't work (yet) with RHEL 8.* (or CentOS 8.*, or ORL 8.*, or any other derivative). That is, if I am not mistaken that ORL s... See more...
The issue is the source machine OS version, not Converter's. Converter doesn't work (yet) with RHEL 8.* (or CentOS 8.*, or ORL 8.*, or any other derivative). That is, if I am not mistaken that ORL stands for Oracle Linux? (it is kind of ungoogleable)
Hello,   If the issue is still relevant, could you please examine or post the installation log file? It's full path is "%TEMP%\vminst.log". Since it is in temp folder, you may need to retry the ins... See more...
Hello,   If the issue is still relevant, could you please examine or post the installation log file? It's full path is "%TEMP%\vminst.log". Since it is in temp folder, you may need to retry the installation and then look the log up. Regards, Plamen
Hello,   If ORL stands for Oracle Linux, then the issue is the version. Converter currently does not convert RHEL 8 (and Oracle Linux is a clone of RHEL, right?). However, since this is a Hyper-V ... See more...
Hello,   If ORL stands for Oracle Linux, then the issue is the version. Converter currently does not convert RHEL 8 (and Oracle Linux is a clone of RHEL, right?). However, since this is a Hyper-V VM, you may try V2V, i.e. converting it as a powered off VM.   HTH, Plamen
Good to see that it works The old cold clone was for Windows only and it is very old. I'd say - don't bother to look for it. As for the ASM disks, I am not familiar with these. I guess their blo... See more...
Good to see that it works The old cold clone was for Windows only and it is very old. I'd say - don't bother to look for it. As for the ASM disks, I am not familiar with these. I guess their block devices may look different and Converter doesn't recognize them. The usual workaround in such cases is to copy the volumes manually, i.e. create new disks in the VM, setup logical volumes if needed, format the volumes, and then use scp, rsync, or whatever your favorite way is. Converter itself uses tar during cloning. HTH, Plamen
Hello, This is correct, Converter 6.3 cannot convert RHEL versions prior to 6. Converter 6.2 can, though. It is not available for download, for security reasons as well (including the one that you ... See more...
Hello, This is correct, Converter 6.3 cannot convert RHEL versions prior to 6. Converter 6.2 can, though. It is not available for download, for security reasons as well (including the one that you hit here), but if have a copy left somewhere, or if someone can hand it to you, it is expected to do the job. HTH and regards, Plamen
Hola, It is not so much about ports as about IP addresses. If you use NAT, then in theory you could configure a specific port as representative of your destination machine's address. But then you mi... See more...
Hola, It is not so much about ports as about IP addresses. If you use NAT, then in theory you could configure a specific port as representative of your destination machine's address. But then you might have other issues. Probably the best option is to use proxy mode. HTH, Plamen  
In case the thumbprint is empty because it has been previously saved by Converter, this is the location where these thumbprints are saved - [HKEY_CURRENT_USER\Software\VMware\Virtual Infrastructure C... See more...
In case the thumbprint is empty because it has been previously saved by Converter, this is the location where these thumbprints are saved - [HKEY_CURRENT_USER\Software\VMware\Virtual Infrastructure Client\Preferences\UI\SSLIgnore] If that's the issue, removing it from there could be a workaround.
Hello, You need to have connectivity from the source machine (the agent) to the network share where it will clone the data. You can verify that e.g. by pinging the destination address from the sourc... See more...
Hello, You need to have connectivity from the source machine (the agent) to the network share where it will clone the data. You can verify that e.g. by pinging the destination address from the source machine. If, perchance, the desired destination is your local machine, you need to provide a public IP. 198.168.*.* is a private network space that is not routable. Regards
Upon more careful look, there is a workaround I have managed to reproduce the issue. The reason is that in ESXi 8.0 the usage of VirtualMachineTicketType.device and VirtualMachineTicketType.mks is d... See more...
Upon more careful look, there is a workaround I have managed to reproduce the issue. The reason is that in ESXi 8.0 the usage of VirtualMachineTicketType.device and VirtualMachineTicketType.mks is disabled. Instead VirtualMachineTicketType.webDevice and VirtualMachineTicketType.webMks should be used respectively. Fortunately there is an option to allow the old behaviour. You need to set "allow_authd_ticket" to "true" in hostd configuration. Folllow this KB  about configstorecli. Use the following snippet to update the configuration properties: {    "plugins": {       "vmsvc": {          "allow_authd_ticket": true       }    } } HTH, Plamen
Hello After a look at the logs, it seems you are using ESXi 8.0. It also seems Converter uses some deprecated functionality that has been removed in 8.0. Converter 6.3 supports up to vSphere 7.*, s... See more...
Hello After a look at the logs, it seems you are using ESXi 8.0. It also seems Converter uses some deprecated functionality that has been removed in 8.0. Converter 6.3 supports up to vSphere 7.*, so this is not really a bug. If my analysis proves correct, this will be fixed in the next release. Unfortunately, as of this moment, I can't think of a workaround except using an older vSphere destination. E.g. if you can install temporarily an ESXi 7.0 somewhere and then move the converted VM? Regards, Plamen
Hopefully this might help.
Hello,   Try P2V conversion (i.e. powered on source VM). This is volume based, though, not disk based (Converter sees the volume as it is seen by the GOS). Not sure whether this is simple enough, b... See more...
Hello,   Try P2V conversion (i.e. powered on source VM). This is volume based, though, not disk based (Converter sees the volume as it is seen by the GOS). Not sure whether this is simple enough, but that's what Converter can do.   HTH, Plamen
Hello and thank you for your input. We certainly have in mind extending the support for Ubuntu 18 and other new versions in Converter roadmap. As for how easy or hard this is, well... there are deve... See more...
Hello and thank you for your input. We certainly have in mind extending the support for Ubuntu 18 and other new versions in Converter roadmap. As for how easy or hard this is, well... there are development considerations that are not obvious when using the product. Regards, Plamen
Hi and thanks for the info. It basically justifies my suspicions - a single disk split into 8 partitions with basic volumes on them. I would say this is not the contemporary way of dealing with stor... See more...
Hi and thanks for the info. It basically justifies my suspicions - a single disk split into 8 partitions with basic volumes on them. I would say this is not the contemporary way of dealing with storage. I'd recommend, if you can afford it, to you use the opportunity presented by converting the machine and make your volumes more flexible. I.e. leave only '/' (dev/sda10) and '/boot/efi' (/dev/sda9) on the destination disk, move all other volumes to a new virtual disk, and enable LVM on it.   Regards, Plamen
Hi Mr. Muthukumar, This probably means the disk contains the boot and/or system volume(s). In that case what is left is to move the other volumes to a new disk. There you can make them either basic ... See more...
Hi Mr. Muthukumar, This probably means the disk contains the boot and/or system volume(s). In that case what is left is to move the other volumes to a new disk. There you can make them either basic or logical (logical volumes are usually recommended). I am curious what the volumes on the source machine look like. Could you share that information? E.g. by pasting the options page in the wizard, 'data to copy', 'advanced', 'destination layout' view. Or the results of some command on the source that shows it (mount, df, blkid, ...)   Regards, Plamen
Hello Converter 6.3 is a revival of the product which has been discontinued for a few years. It doesn't add new functionality compared to 6.2. Newer versions are supposed to add more capabilities in... See more...
Hello Converter 6.3 is a revival of the product which has been discontinued for a few years. It doesn't add new functionality compared to 6.2. Newer versions are supposed to add more capabilities in the future.   Regards, Plamen