I had similar problem yesterday (but not the same).
It is not a vBox problem, it is that when you created new machine with VBox, and copied the disk using VBox you have changed the UUID of the disk.
And in you system (whatever it is), you have your old UUID in /etc/fstab. You have to boot this new machine from a rescue CD (maybe ubuntu, or dsl. Anything that supports the filesysytem you have on that vritual disk). Then check UUID of your disk using blkid command as root. And put this new UUID in fstab, in an entry that specified the boot disk. Maybe you are also using UUID in some other place, that you have to change too.
Another solution is: try to COPY all the virtual disks for this VM and the virtualmachine definition files in your host system, using any copy mechanism you have, but not the VirtualBox Clone or export. And open this machine on new PC (but it will only work on another PC, not on the same). If that does not work, then I do not know.
Additional question: did you try cloning the VM to the same PC. Clone the disk using VirtualBox clone, then create new machine, and update the /etc/fstab?
Hint: in VirtualMachines you can switch from UUID entries in fstab to old /dev/sda entries.
Another idea: If you are using LargeVolumeManager then you have setup that too. And I do not know how to do it, because I am not using LVM.
发布评论
评论（2）
转到文件 -> 导出设备并导出虚拟机，这将创建 .ovf 和 .vmdk 文件，然后您可以将其导入到另一台计算机上。
Go to File->Export Appliance and export the virtual machine, that will create .ovf and .vmdk files you can then import on another machine.
我昨天遇到了类似的问题（但不一样）。
这不是 vBox 问题，而是当您使用 VBox 创建新机器并使用 VBox 复制磁盘时，您更改了磁盘的 UUID。
在您的系统中（无论它是什么），您的旧 UUID 位于
/etc/fstab中。您必须从救援 CD（可能是 ubuntu 或 dsl。任何支持该虚拟磁盘上的文件系统的东西）启动这台新机器。然后以 root 身份使用blkid命令检查磁盘的 UUID。并将这个新的 UUID 放入 fstab 中指定启动磁盘的条目中。也许您还在其他地方使用 UUID，您也必须更改。另一个解决方案是：尝试使用您拥有的任何复制机制（但不是 VirtualBox 克隆或导出）来复制该 VM 的所有虚拟磁盘以及主机系统中的虚拟机定义文件。并在新电脑上打开这台机器（但它只能在另一台电脑上工作，不能在同一台电脑上工作）。如果这不起作用，那么我不知道。
附加问题：您是否尝试将虚拟机克隆到同一台 PC。使用 VirtualBox 克隆克隆磁盘，然后创建新机器，并更新 /etc/fstab？
提示：在 VirtualMachines 中，您可以从 fstab 中的
UUID条目切换到旧的/dev/sda条目。另一个想法：如果您使用 LargeVolumeManager，那么您也可以进行设置。我不知道该怎么做，因为我没有使用 LVM。
I had similar problem yesterday (but not the same).
It is not a vBox problem, it is that when you created new machine with VBox, and copied the disk using VBox you have changed the UUID of the disk.
And in you system (whatever it is), you have your old UUID in
/etc/fstab. You have to boot this new machine from a rescue CD (maybe ubuntu, or dsl. Anything that supports the filesysytem you have on that vritual disk). Then check UUID of your disk usingblkidcommand as root. And put this new UUID in fstab, in an entry that specified the boot disk. Maybe you are also using UUID in some other place, that you have to change too.Another solution is: try to COPY all the virtual disks for this VM and the virtualmachine definition files in your host system, using any copy mechanism you have, but not the VirtualBox Clone or export. And open this machine on new PC (but it will only work on another PC, not on the same). If that does not work, then I do not know.
Additional question: did you try cloning the VM to the same PC. Clone the disk using VirtualBox clone, then create new machine, and update the /etc/fstab?
Hint: in VirtualMachines you can switch from
UUIDentries in fstab to old/dev/sdaentries.Another idea: If you are using LargeVolumeManager then you have setup that too. And I do not know how to do it, because I am not using LVM.