[SOLVED] Linux VM won't boot after p2v from Clonezilla

[Razgriz7575]

Hello,

I've had problems to make an old linux (Ubuntu 6.10, Linux 2.6.17) boot. I p2ved the physical machine (that is on an old HP ML350G5 with a raid array) using CloneZilla. I then tried to restore this machine on a virtual disk. The thing is, with the RAID array, the root filesystem is on /dev/cciss/c0d0p1 and after using CloneZilla it's on /dev/sda1. After this, I normally boot on a live-cd and restore a path to the root filesystem (/dev/sda1).
I have tried restoring grub with grub-install but I get an error "/dev/cciss/c0d0p1 does not have any corresponding bios drive", even though fstab is good and fdisk returns /dev/sda1 as the bootable partition.
The procedure worked with VmWare Workstation and Virtualbox. However on Proxmox after trying multiple settings and trying different options the vm still gives up waiting for the root filesystem. I have also tried on XCP-ng and the vm did not boot either.
I have also tried importing a virtual disk from Virtualbox using qm importdisk but it did not boot either.
I don't really know where to continue to troubleshoot this issue. Any hints would be appreciated.
Thank you.


proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve) pve-manager: 6.3-2 (running version: 6.3-2/22f57405) pve-kernel-5.4: 6.3-1 pve-kernel-helper: 6.3-1 pve-kernel-5.4.73-1-pve: 5.4.73-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.4-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.16-pve1 libproxmox-acme-perl: 1.0.5 libproxmox-backup-qemu0: 1.0.2-1 libpve-access-control: 6.1-3 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.2-6 libpve-guest-common-perl: 3.1-3 libpve-http-server-perl: 3.0-6 libpve-storage-perl: 6.3-1 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.3-1 lxcfs: 4.0.3-pve3 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.0.5-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.4-3 pve-cluster: 6.2-1 pve-container: 3.3-1 pve-docs: 6.3-1 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.1-3 pve-ha-manager: 3.1-1 pve-i18n: 2.2-2 pve-qemu-kvm: 5.1.0-7 pve-xtermjs: 4.7.0-3 qemu-server: 6.3-1 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 0.8.5-pve1

 

[Dominic]

trying multiple settings and trying different options the vm

Including both BIOS settings for the VM? Have you made sure to always check the bootorder of the VM?

 

[Razgriz7575]

Hello, thank you for your response.

I found a solution. The virtual disk was set in VirtIO and I set it to IDE. Even though it works on the other solutions in Sata, IDE was the only way to make the linux boot. I also had to set the disk's UUID on the grub's config file to make it work

root=UUID=...

.

This post made me think of trying with the disk attached in IDE.
https://forum.proxmox.com/threads/e...starts-but-not-boot-vmdk-considerations.6282/

Thank you for your support.