Custom Query (16363 matches)
Results (2101 - 2103 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2991 | duplicate | Cloned HD of CentOS 5.2 can not boot | ||
| Description |
A HD cloned from another HD of CentOS 5.2 using the following: VBoxManage clonehd centos5.2_1.vdi centos5.2_2.vdi can not boot up due to volume error. The cloning seems to finish successfully, but when I tried to boot the cloned HD, I got the following error on the boot screen: Red Hat nash version 5.1.19.6 starting
Reading all physical volumes. This may take a while...
No volume groups found
Volume group "VolGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: no such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
-
Then everything stops there forever. The original HD still can boot without problem. The cloned HD is smaller than the original one. Original HD: UUID: e5bcd5c4-6154-405f-a53c-46856f3482d4 Accessible: yes Logical size: 8192 MBytes Current size on disk: 5387 MBytes Type: normal Storage format: VDI In use by VMs: CentOS 5.2 (UUID: 3943ae27-f626-4e10-90b8-a9d196d180dd) Cloned HD: UUID: 7a895493-5d70-4c68-ada8-c775084bf68b Accessible: yes Logical size: 8192 MBytes Current size on disk: 4952 MBytes Type: normal Storage format: VDI In use by VMs: CentOS 5.2 (2) (UUID: 217d6c3e-e69b-4b5e-985c-87a073ae3135) Host and Guest info:
|
|||
| #11694 | obsolete | Cloned VMs are not able to mount ISO images | ||
| Description |
VMs cloned either through the GUI or CLI, are not able to mount ISO images. If set before booting the clone vm, you receive the following error Failed to open a session for the virtual machine Win7-x64 Clone. DrvVD: Configuration error: Both "ReadOnly" and "Discard" are set (VERR_PDM_DRIVER_INVALID_PROPERTIES). Failed to attach driver below us! The driver properties were invalid, and as a consequence construction failed. Caused my unusable media or similar problems. (VERR_PDM_DRIVER_INVALID_PROPERTIES). PIIX3 cannot attach drive to the Secondary Master (VERR_PDM_DRIVER_INVALID_PROPERTIES). Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392} The original VM can mount ISO images without issue. Both VMs can attach to the host's CD-ROM drive. Affects both linked and full clones. |
|||
| #9673 | obsolete | Clonehd variant not working | ||
| Description |
Trying to clone and using the following fails due to the variant. debian@debian:~$ VBoxManage clonehd /drive/tara1/VirtualBox-VMs/Ubuntu-10.04/Ubuntu-10.04.vdi /drive/tara1/VirtualBox-VMs/Ubuntu-10.04/Ubuntu-10.04-test.vmdk --format vmdk --variant ESX Progress state: VBOX_E_FILE_ERROR VBoxManage: error: Failed to clone hard disk VBoxManage: error: Could not create the clone medium '/drive/tara1/VirtualBox-VMs/Ubuntu-10.04/Ubuntu-10.04-test.vmdk' (VERR_VD_INVALID_TYPE) VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Medium, interface IMedium VBoxManage: error: Context: "int handleCloneHardDisk(HandlerArg*)" at line 719 of file VBoxManageDisk.cpp Following the CLI help below it looks like it should work. VBoxManage clonehd <uuid>|<filename> <uuid>|<outputfile>
Following the user with this issue here: https://forums.virtualbox.org/viewtopic.php?f=6&t=45000 If I leave the variant off the clone succeeds, but the OP wants the ESX variant. |
|||

