Hello,
I cloned the disk (online-vm1-20140305-disk1.vmdk) of my VM (ubuntu). the clone didn't finish with success. but now the guest system is on "read-only" mode.
have you an idea ? thanks a lot for your help
some informations
----------------------
vboxmanage showhdinfo online-vm1-20140305-disk1.vmdk
UUID: 313d0acd-7e14-487b-b3c5-e06b848a064b
Parent UUID: base
State: created
Type: normal (base)
Location: /home/vbox/VirtualBox VMs/Prs (VM1)/online-vm1-20140305-disk1.vmdk
Storage format: VMDK
Format variant: dynamic default
Capacity: 204800 MBytes
Size on disk: 91036 MBytes
----------------------------
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/mapper/spics--online--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=3bdf1ff2-7f26-461f-b263-abd65d3d729e /boot ext2 defaults 0 2
/dev/mapper/spics--online--vg-swap_1 none swap sw 0 0
issue with linux VM after clonehd
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: issue with linux VM after clonehd
I'm not seeing where the data you provided says what you say it does. I see nothing about the VM being frozen, all I'm seeing is hdinfo for some VMWare format disk (a disk is only one component of a PC), and I'm not seeing the relevance of that fstab stuff at all.
What would be useful is too know how you were cloning the VM, i.e. what command or options you used. Also, any error you receive when you try to run the original VM.
What would be useful is too know how you were cloning the VM, i.e. what command or options you used. Also, any error you receive when you try to run the original VM.
Re: issue with linux VM after clonehd
hello,
I use this command : vboxmanage clonehd online-vm1-20140305-disk1.vmdk vm2.vhd --format VHD but I didn't save the error message sorry
I use this command : vboxmanage clonehd online-vm1-20140305-disk1.vmdk vm2.vhd --format VHD but I didn't save the error message sorry
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: issue with linux VM after clonehd
The clonehd command only clones hard disks, it does not affect any VM, so it can't possibly have left a source VM in a frozen state. If the hd cloning operation failed you can just try it again.
I'm also curious why you would want to convert a VMDK (ok format) to a VHD (terrible format choice), and on a Linux host? What uses VHD on a Linux host?
I'm also curious why you would want to convert a VMDK (ok format) to a VHD (terrible format choice), and on a Linux host? What uses VHD on a Linux host?
Re: issue with linux VM after clonehd
if I understood correctly, the state "read-only" of my guest isn't a result of my clonehd test? in this case have you an idea to change the state of my guest's system ?
we try some others solution of hypervisor (cloud, on prem), and in the bench we need to move a VM (virtualbox) to anothers hypervisor without operations (or with a minimum operations).
thanks for your time
we try some others solution of hypervisor (cloud, on prem), and in the bench we need to move a VM (virtualbox) to anothers hypervisor without operations (or with a minimum operations).
thanks for your time
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: issue with linux VM after clonehd
If you want to move a VirtualBox VM to a different hypervisor use "File|Export Appliance..." and use the corresponding appliance import feature in the other software. The other software is beyond the scope of these forums.
If you want to move a VirtualBox VM to another VirtualBox instance (i.e. on a different host) see Howto: Move a VM.
If the VM was unusable after these operations then you must have done something else to the VM, for example moving critical files around outside of VirtualBox's control. Without being there to look over your shoulder there is very little I can say on this.
If you want to move a VirtualBox VM to another VirtualBox instance (i.e. on a different host) see Howto: Move a VM.
If the VM was unusable after these operations then you must have done something else to the VM, for example moving critical files around outside of VirtualBox's control. Without being there to look over your shoulder there is very little I can say on this.