I tested the new version 7.2 of VirtualBox (specifically 7.2.4) and they fixed the problem. I consider this thread closed. Thanks for everything.
Yes. It works with the BIOS in Legacy mode, but not in UEFI mode. So I think it's confirmed to be a bug in VirtualBox 7.1, which I assume will be fixed in future versions.
Well, in my case, it's still the same. Clonezilla "lite server" doesn't initiate the restore on virtual machines with UEFI enabled in VirtualBox version 7.1, although it does connect to the PXE server. However, I've tested with the latest version (7.0.24) and it does work, with the same scenario (3 virtual machines with UEFI enabled, one with Clonezilla "lite server" and the other two clients for the restore). Apparently, this is an issue with VirtualBox version 7.1 that has already been reported...
Today I tried with the latest version of Clonezilla (2025.03.03-oracular) and with the one we used in the previous course that worked well (2023.04.26-lunar). With both it fails in the same way. I think the problem is in VirtualBox, because last year we used version 7.0 and this year the new 7.1. Also the screen that indicates the PXE connection is different. I'm going to ask the question in the VirtualBox forum.
I'll try the latest release and report back here. I understand that the firewall can't be a problem, because VirtualBox doesn't create one as far as I know, and the PXE connection that Cloneizlla makes doesn't support it, right?
Hello. I am a high school teacher and I have been using Clonezilla Lite Server for some time to do an internship with students. We use VirtualBox to clone a virtual machine (server) into two others (clone1 and clone2). The fact is that it has always worked well, but this year it fails. We are using this version that we downloaded in September 2024 (at the beginning of the course): clonezilla-live-20240715-noble-amd64 I think it may be a bug in this version that is fixed in later versions, but I have...
It happens with virtual disks of VirtualBox (VDI extensions). I have no tried with other types of virtual disks. El sáb., 10 dic. 2022 10:51, Steven Shiau steven_shiau@users.sourceforge.net escribió: Is this only reproducible on VirtualBox? Do you have any issue about physical machine? Steven =?UTF-8?Q?Clonezilla_recognizes_VirtualBox_virtual_machine_dis?= =?UTF-8?Q?ks_that_are_larger_than_they_actually_are_B=C3=A1ez?= https://sourceforge.net/p/clonezilla/discussion/Help/thread/0b0f684ce5/?limit=25#cd28...
Thanks... I will try. But there is between 5-8 GB more. Now the solution for me is resize the VDI disk of VirtualBox to the correct size, although is a lot of work. But my question is why there is 5GB more?. If I have a virtual machine of 80GB (for example), in the Virtual Media Administrator of VirtualBox the VDI has 80GB... if I boot the virtual machine with Gparted live, there is 3 partitions (sda1(/), sda2(/home), sda3(swap)) that sum 80GB, and THERE IS 5GB at the end of the hard disk without...