Hello,
We have a few older servers that we want to virtualize using Proxmox VE. We have had success creating new VMs on Proxmox using both CentOS and FreeBSD as guest OSs, but I have not had any luck with migrating a live server.
For testing I attempted both the Clonezilla disk-to-remote method as well as the dd method of a FreeBSD server running 103, but no luck. When I boot up the VM after doing the Clonezilla method, It hangs on "Booting from Hard Disk". When I do the dd method, it skips over the drive saying it's not bootable.
The Clonezilla method seems easy enough, but I must be missing something. The source server is using hardware raid 1, and Clonezilla saw the drive as a single drive. When I boot from a liveCD on the VM and run gpart show, it looks like the partitions are good. I ran a fsck against the disk, and it does seem to remain dirty after running it several times. I would think that FreeBSD would at least start it's boot process before giving errors if it was just a dirty disk issue. Any thoughts? I've tried QEMU32, QUEMU64, KVM64 and Host for the CPU. Tried IDE and SCSI for the VM hard drive.
Let me know what i can provide for further info, and I'll send it along!
Thank you,
Matt
We have a few older servers that we want to virtualize using Proxmox VE. We have had success creating new VMs on Proxmox using both CentOS and FreeBSD as guest OSs, but I have not had any luck with migrating a live server.
For testing I attempted both the Clonezilla disk-to-remote method as well as the dd method of a FreeBSD server running 103, but no luck. When I boot up the VM after doing the Clonezilla method, It hangs on "Booting from Hard Disk". When I do the dd method, it skips over the drive saying it's not bootable.
The Clonezilla method seems easy enough, but I must be missing something. The source server is using hardware raid 1, and Clonezilla saw the drive as a single drive. When I boot from a liveCD on the VM and run gpart show, it looks like the partitions are good. I ran a fsck against the disk, and it does seem to remain dirty after running it several times. I would think that FreeBSD would at least start it's boot process before giving errors if it was just a dirty disk issue. Any thoughts? I've tried QEMU32, QUEMU64, KVM64 and Host for the CPU. Tried IDE and SCSI for the VM hard drive.
Let me know what i can provide for further info, and I'll send it along!
Thank you,
Matt