I'm trying to move an old Win2008 server from KVM to VMware ESXi 6.7.
I realize the Win2008 VM is old and beyond EoS but need to keep this in place for now and is in a VLAN that is not internet accessible.
I tried to follow recommendations from Convert qcow2 to vmdk and make it ESXi 6.0 Compatible and steps I found on the web:
Shutdown VM on KVM
qemu-img convert -p -f qcow2 -O vmdk win2008.qcow2 win2008.vmdk using qemu v4.2.1
vmkfstools -i win2008.vmdk -d thin win2008_v2.vmdk on the VMware host
Attach the newly created win2008_v2.vmdk file to a newly created guest with default settings
However I'm stuck with a Windows Error Recovery: Windows failed to start. A recent hardware or software change might be the cause. screen at boot up.
I tried to use some conversion options like qemu-img convert -p -f qcow2 -O vmdk -o adapter_type=lsilogic,subformat=streamOptimized,compat6 win2008.qcow2 win2008.vmdk and tried moving between the 3 available scsi controllers (LSI Logic SAS, LSI Logic Parallel, VMware Paravirtual) to no avail.
When I boot the guest in Safe mode, I see a bunch of sys files get loaded properly until it's stuck after Loaded: \Windows\system32\drivers\crcdisk.sys.
Does anyone have an idea on how to move this guest properly? Any other conversion options to try? Driver install on the running guest (in KVM) first?
Note I'm not running vCenter.
Do you try to use VMware Converter Tool ? I think that is the easy way to move your server to VMware. You can download the tool it is free.
https://www.vmware.com/products/converter.html
Related
I'm trying to convert an openVZ container to VMware.
Since this is planned for roughly 1000 instances, I'm looking for a different approach than reinstalling from scratch.
I followed the steps in the last post:
https://communities.vmware.com/message/1719787#1719787
However, when booting from a live CD, it can't find any linux partition.
I also tried yum install kernel-xx which had no effect on the live CD not finding a partition so I'm assuming there's an error while converting.
Does anyone know of a solution or some tweaks to the one I posted?
The OS in this case is CentOS 7 on openVZ 6.
Long story short: Convert openVZ to KVM, then convert to VMWare.
create a KVM with the same OS as your container
mount the KVM image file
rsync all data to that image file
umount image file and start and stop KVM
convert img to vmdk with qemu-img
move vmdk file to esxi host
convert to thin-provisioned vmdk with vmkfstools
I had to tackle (and still am) multiple issues to make it boot, like recrating initrams, reinstalling policykit, reconfiguring networking, adjusting grub.
Hope this helps someone.
It looks like you will have to go the OpenVZ -> KVM -> VMware route. This post by Roman Pertl explains how he did it, plus it also links to some other tutorials.
rsync --exclude=/var/lib/initramfs-tools/* --exclude=/var/lock --exclude=/etc/fstab --exclude=/etc/modules --exclude=/etc/mtab --exclude=/boot/* --exclude=/proc/* --exclude=/lib/modules/* --exclude=/tmp/* --exclude=/dev/* --exclude=/sys/* -e ssh --delete-after --numeric-ids -avpogtStlHz / root#sourcevm:22/
I'm trying to automate VMWare Desktop on Windows 7 to suspend all vm's before I do a backup job each night. I used to have a script that did this but I've noticed now that it won't suspend anymore with the same command that used to work.
If I do vmrun list I get a list of the running vms with no issue.
If I do vmrun suspend "V:\Virtual Machines\RICHARD-DEV\RICHARD-DEV.vmx" it just hangs and I have to kill the command with CTRL+C.
I've even tried a newer command using -T to specify it's workstation, ie vmrun -T ws suspend "V:\Virtual Machines\RICHARD-DEV\RICHARD-DEV.vmx" and still no love.
If I have the vm already stopped, I can issue vmrun start "V:\Virtual Machines\RICHARD-DEV\RICHARD-DEV.vmx" and it starts fine.
As well as the suspend command, the stop command also does not work. I'm running VMWare Workstation 11.1.3 build-3206955 on Windows 7.
Any ideas?
Update:
I installed latest VMWare Tools on the guest, as well as the latest Vix on the Host so everything should be up to date.
I can start a vm using vmrun with no problem using vmrun -T ws start <path to vmx> but the command doesn't come back to the command prompt, so I'm assuming it's not getting confirmation from the vm that it is now running.
If I cancel the 'start' command and now try and suspend I'm getting the same lack of communication from the guest. If I manually suspend the vm, once it's suspended I get an 'Error: vm is not running' and the 'suspend' command finally times out and comes back.
So, it looks to me like there is no communication from vmrun to the guest about what state it's in etc. Is there a way to debug the communication from the host to the guest using vmrun or other means? Are there ports I need open in the guest OS?
So, I never did get vmrun to work properly on my main system, although I did get it behave ok on my laptop so there is something weird happening on this machine. I also installed a trial of the latest VMWare 12 and the same thing happens.
As a workaround, I ended up changing the power management settings in my guest OS so that it would 'sleep' after 1 hr of inactivity. When this happens VMWare detects it and automatically suspends the guest which is really what I'm looking for. Not the most slick solution but it does manage to unlock the files I need to be backed up in a nightly backup.
I followed the steps below, but I'm getting an error.
Install Virtual Box (version 5.0.0) running on Windows 7 host machine.
Install Ubuntu server version 14.04.02 on it.
git clone https://github.com/openstack-dev/devstack.git
cd devstack; cp samples/local.conf .
After that i ran ./stack.sh but came with this error after running for approx 30 minutes:
2015-07-21 20:04:18.841 | ERROR (ConnectionRefused): Unable to establish connection to 10.0.2.15:8774/v2/c199aa06389a4c8c85dffddad18fce1b/flavors/… 2015-07-21 20:04:20.433 | + exit 1 deb#Devstack:~/devstack$
Please help me in resolving the issue
Try re-running the stack. Thats the best hack i found for DevStack debugging.
You need to do some specific network settings in virtual box to overcome this error.
From the Network section, change Attached to to Bridged Adapter, Adapter Type to Paravirtualized Network (virtio-net) and Promiscuous Mode to Allow All.
Check Enable Nested VT-x/AMD-v from System > Processor .
Select USB Tablet as the Pointing Device from System > Motherboard.
Then restart the virtual machine and check ifconfig for a new IP, add it in local.conf and then try install script again.
It should work this time :-)
I've stumbled on this issue after installing and configuring cloudstack 4.4.
I'm trying to setup cloudstack wiht VMWARE hypervisor, i've followed all the step from the cloudstack documentation, but I have 2 issues.
can not start the System Storage VM it fails?
When I add a template or ISO on cloudstack the ISO does not upload?
I will try to explain the configuration I have:
cloudstack 4.4 is installed on CentOS 6.5
Hypervisor VMware esxi5.5
VCenter server
Primary storage iSCSI vmfs
Secondsry NFS (seperate from cloudstack)
If anyone can help me or point me to what the issue might be I would greatly appreciate it. Thanks!
On your Management Server, run one of the following cloud-install-sys-tmplt command to retrieve and decompress the system VM template. If your secondary storage mount point is not named /mnt/secondary, substitute your own mount point name.
/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/
secondary -u http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova -h vmware -s -F
When the script has finished, unmount secondary storage and remove the created directory
umount /mnt/secondary
rmdir /mnt/secondary
Ok, here's a very short and to the point question. When trying to import a virtual PC 2004 Windows 2003 Server VM in VM Workstation 6.0.2 I'm getting an error 'unable to determine guest operating system'. Soo how to fix?
From here:
Make sure that that the VM is not currently running in VMware Server.
Make sure that VMware Server does not have a lock on the VM’s files. You have have to stop all VMware Server Services and/or reboot the (VMWare) server.
Make sure you have appropriate permissions to the VM’s files.
This is a fairly generic error from VMware Converter so I would try the following:
Step 1. Make sure you are running the latest version of VMware Converter. Updates seem to come pretty often for this tool.
Step 2. Check the VMware Converter log file. More often than not you will find the source of your problem here.