Thanks Greg! I'll try it this weekend On Thu, May 25, 2017 at 9:43 AM, Greg Treantos <[email protected]> wrote:
> boot a rescue disk, chroot your system and rebuilt initrd. Here are short > steps.. > > > Set mount points for chroot environment > > mount -t proc none /media/proc > > mount -o bind /dev /media/dev > > mount -t devpts devpts /media/dev/pts > > mount -o bind /sys /media/sys > > update /etc/fstab with the new partition names > > update /etc/default/grub with the new partition names and uuids > > > > sudo dracut --regenerate-all --force && sudo grub2-mkconfig -o > /etc/grub2.cfg > > > On Wed, May 24, 2017 at 11:15 PM, Mark Creamer <[email protected]> wrote: > >> Using the Clonezilla method, I was able to clone and restore the KVM to a >> new VM. It booted fine the first time, so I first did a yum update (it's a >> CentOS 6.7 VM). After that, it will no longer boot, and there are no >> errors. It just hangs after the initial BIOS screen. If anyone has any >> ideas, I'd love to try to make this work. Otherwise dd with netcat is my >> next try but I suspect the exact same thing will happen since I think >> that's exactly what Clonezilla is doing (making an exact copy of the >> virtual disk). >> >> On Sun, May 14, 2017 at 4:31 PM, Peter Kelm <[email protected]> >> wrote: >> >>> In our migrations we uninstalled the VMWare guest tools first and also >>> installed the Windows virtio block and net drivers before dd’ing the disk >>> over to SmartOS KVM. >>> >>> Am 12.05.2017 um 15:36 schrieb Sriram Narayanan <[email protected]>: >>> >>> Did you also install the vmware guest tools after the migration? >>> >>> We're there any kvm guest tools installed earlier? >>> >>> You may want to ensure that the right version of the tools are in place >>> and that stale tools are removed after the migration. >>> >>> I'd also reboot the VMs once and then verify the guest tools status via >>> vcentre. You may also want to migrate the VMs between VMWare hosts to >>> ensure that you don't care any migration issues in the future due to vmdk >>> disk structure issues, etc. I've no clue if this is still an issue, but I'd >>> faced issues with linked clones when the original vm was created using dd. >>> >>> Ram >>> >>> On Friday, May 12, 2017, Peter Kelm <[email protected]> wrote: >>> >>>> Mark, >>>> >>>> We folloed Mark Slatem’s blog post to accomplish the migration - truly >>>> simple: >>>> >>>> - Boot both your VSphere/ESXi VM and the KVM machine on SmartOS using a >>>> Linux "rescue CD" (we used sysresccd). >>>> - On the target machine: Launch netcat so that it listens on port 9000 >>>> and pipe its output into dd (to the target disk). >>>> - On the source machine: dd the real VSphere VM disk and pipe to netcat >>>> (port and IP address as above). >>>> >>>> http://blog.smartcore.net.au/smartos-kvm-screencast-part-2/ >>>> >>>> Peter >>>> >>>> Am 11.05.2017 um 16:12 schrieb Mark Creamer <[email protected]>: >>>> >>>> I would like to move my few remaining KVM servers to my legacy VMware >>>> server so the SmartOS systems are all running native OS zones. Has anyone >>>> successfully used VMware Converter for this task? Or is there a better way >>>> other than rebuilding from scratch and moving the apps and data over? >>>> >>>> -- >>>> Mark >>>> >>>> >>>> >>> >> >> >> -- >> Mark >> > > > > -- > Greg > > http://www.linkedin.com/in/gregtreantos > *smartos-discuss* | Archives > <https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/23055384-4ad60763> | > Modify > <https://www.listbox.com/member/?&;> > Your Subscription <http://www.listbox.com> > -- Mark ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
