Hmmmm... you want to run hypervisor in hypervisor which is not good idea except for tests, even it is possible.
Once you converted successfully this is not the right forum to ask questions.
HTH
Hmmmm... you want to run hypervisor in hypervisor which is not good idea except for tests, even it is possible.
Once you converted successfully this is not the right forum to ask questions.
HTH
This seems the correct way to convert your server, (the consistent unfixable error is not good for your file-system at all)
I have tried everything listed in this post, and everywhere else I have searched, but I am still getting this same issue.
I have tried putting my domain account in the local admin group of both source machine and converter server, I have tried using local admin accounts, and I have tried multiple versions of converter (5.1 and 5.3). My environment is vSphere 5.5, and does have some strict security settings in place, so I am leaning to that as a possible issue. What I have not been able to find is a listing of required User Right Assignments, or Security settings needed for converter to work as expected.
Anyone have any further information?
Terry
Have you try to run the GUI 'as administrator'? When convert the 'local machine' the user should be 'administrator' or elevated administrator.
I'm trying to convert a physical Linux server to a virtual ESXi server. I am using VMWare converter to convert the machine and VMWare workstation to run the virtual ESXi server on. Both software are the lastest versions.
When running the conversion software I get no warnings or errors when running the set up, the conversion gets all the way to 97% and errors.
The error message I get is
FAILED: An error occurred during the conversion: 'GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 1, and message: Installing GRUB2 on (hd0)... /usr/sbin/grub-setup: warn: This GPT partition label has no BIOS Boot Partition; embedding won't be possible!. /usr/sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged.. /usr/sbin/grub-setup: error: if you really want blocklists, use --force. Installing GRUB2 on (hd0) failed. Installing GRUB2 on /dev/sda... /usr/sbin/grub-setup: warn: This GPT partition label has no BIOS Boot Partition; embedding won't be possible!. /usr/sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged.. /usr/sbin/grub-setup: error: if you really want blocklists, use --force. Error installing GRUB Command: grub-install --no-floppy /dev/sda Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root /usr/lib/vmware-converter/installGrub.sh: line 143: /mnt/p2v-src-root: Is a directory '
I also have the diagnotics report as well.
Can anyone help me?
Thanks in advance.
I vouch for that to !
With vConverter Standalone 5.5 I had the Grub problem but once vConverter was update the convertion was done without a hickup !
The VMWare website and KB's are at times very confusing. I cannot seem to find an answer to my issue. Was hoping you all can help. Do any of the VMWare converters support Hyper-V 2012 R2 U1? I get an error saying not supported when trying to do a source guest on a Hyper-V server. U1 has been out a long time and I find it hard to believe that its not supported yet. From a security perspective its a mandatory patch. I was hoping I am just doing something wrong or missing a step.
I am able to do a powered on conversion but in my environments the servers I am trying to convert will have changed too much in the time it takes to convert across the network and since the network is required for conversion the service will be up.
Thanks in advance!
Chris
HyperV2 is not supported for powered off conversions, however you can convert your machines as physical sources. In case of heavy loaded machines there is an incremental conversion that could help you.
HTH
This could be true.
If you mean that you can convert when you have VMware infrastructure server, this could be true.
The standalone converter requires a VMWare Infrastructure server. I don't understand how they could call this a standalone product because it won't work without a infrastructure server. I don't understand what standalone means.
Using 6.0.0 release of VMWare Standalone Converter, did anyone manage to convert physical Ubuntu Server machine?
It seems this standalone product requires a VMWare server. I don't know it that is a new feature in 6.0.0.
Is this possible? Are there alternatives? Products that can do an actual standalone conversion? WIthout additinoal server components?
Yes, both under local admin and domain admin logins. I can get the converter agent installed on the source machine when I start the convert server wizard, but after the agent installs, it is unable to get system details, which is where I get the access denied.
Like I said, I have a network with significant security settings in place, so I would be surprised if that was the issue. What I can't figure out, is what sort of permissions converter server, or agent, needs to to have permissions to work.
The local administrator will not help you to access remote machines or remote VMs if you haven't rights to access for them,
In your case - you need to log in source machine as ".\Administrator" or administrator user and UAC disabled.
HTH
Can you upload the agent's log from source machine?
Hi.
I have to convert one Hyper-V's VM to vSphere, it is a windows server 2008 r2 (both HV and VM) and HV have simple default installation.
First step: with source as Hyper-V I had got a problem at 1% such "FAILED: An error occured while opening a virtual disk. Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts.". I think it is not commonly problem at HV, because neighboured test VM converted ok, but it is very pure in environment - have no software as MSSQL and big vhd. And I think if I make google-search more then I can resolve problem (or write additionaly here:). Commonly, one thought was that raid-5 was degraded at that moment, and maybe in fast reading via HV it was timeouts, dont know. (I brought disk to raid 5 just yesterday and try again HV convert tonight.)
Second step: with source as physical (yep, why not) it converted ok, despite that I forgot or can't turn off programs/processes to give VM easy way for convert.
And now I have a question:
Is I should to try convert from HV directly or it enough to do as physical?
Is a principal difference in resulted VM (more clear virtualization layer or windows in VM) when I do one or enother thing?
Finaly I didnt understand a principal need of HV conversion as it. Except several situations: when we can't run source VM for physical conversion (f.e. havnt free CPU/RAM/etc or it is like archive and not for run to prevent state change); when we need fast conversion (without virtual layer from source VM to HV); and when we want to exclude VM's process works effect.
Also just now I thought that it is 3rd way by convert from files, if I bring them directly to converter's side. but I dont see this way.
Yes, HypervV2 is not supported but Windows 2012 is supported. You can transfer your VMs as 'Powered on' sources.
HTH
You may choose whatever approach you like, there is no substantial difference. V2V (cold clone) gives you full consistency, some prefer it mainly becuase of that. Using P2V with change synchronization and stopping important services before the sync ensures enough consistency for practical purposes.
As for the 'third way' - select a Worstation destination type. Be aware WS and ESX formats differ slightly, though.
HTH
Plamen
Plamen, thank you for answer.
Its clear now, after search little about conversion work method. Ok, I will examine conversion with running DBs by myself in case of various DBs.
About 3rd way that I meaned for third method, it is to get source VM in cold state via manual transport files to converter (or simply, as examle, make smb share on HV and map to conveter's side). And in that situation I can't catch how changing destination type (and it no need finaly - I wish to place VM in vSphere) may help me to get source, when my source cant be recieved via first two methods. Realy, i checked conveter master's way for this way, and didnt see anything useful for my goal. I suggest that I had bad explanation of this task in English at my previous post. Is I'm right?
p.s. finaly I got run conversion, problem was in network settings, namely that vmware hosts (and converter too) used DNS, but HV was can't resolve their names.
Now my problem in long time of conversation about 2days and over (turning off a SSL in worker's xml dont help much), and it will be separate googlesearch or topic.
RGRDS.
Hi, If I set up a converter job where source is a standalone ESXi and destination is also a standalone esxi, how do traffic go, will source send directly to destination or will traffic run through where I run the Converter Standalone software?