Opened 12 years ago
Closed 11 years ago
#11741 closed defect (worksforme)
hdds become inaccessible when Using VM groups
Reported by: | harmscon | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 4.2.12 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Mac OS X |
Description
After moving a VM into a VM group via the GUI, the hdd storage devices attached to that virtual machine become inaccessible. No indication is given at the time of the move. This new state, inaccessible, was not obvious until I restarted VirtualBox and the media check reported the issue.
VM guest details: SATA controller + 12 SATA disks. After the move into a new VM group, only disk 0 is accessible to the guest.
VBoxManage list hdds output for one of the inaccessible disks before and after moving the VM into a VM group:
UUID: 7ddbfa41-73c8-49eb-b8ae-a818361ce5d2 Parent UUID: base Format: VDI Location: /users/user1/VirtualBox VMs/Ubuntu-11.10-i386/test3.vdi State: created Type: normal Usage: Ubuntu-11.10-i386 (UUID: f5405560-938d-4321-9900-9861b6945edf)
after:
UUID: 7ddbfa41-73c8-49eb-b8ae-a818361ce5d2 Parent UUID: base Format: VDI Location: /users/user1/VirtualBox VMs/Ubuntu-11.10-i386/test3.vdi State: inaccessible Type: normal Usage: Ubuntu-11.10-i386 (UUID: f5405560-938d-4321-9900-9861b6945edf)
Restoring the VM to it's original place in the GUI VM list returns the state to "created".
Change History (2)
comment:1 by , 12 years ago
comment:2 by , 11 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
I can't reproduce this problem so far, moving the VM between groups works just fine here.