Added second disk, VM won't boot

[jnojr]

I attached the disk from another VM and tried to boot. Getting: "Failed to open a session for the virtual machine. No error info." The details say:

Result Code: NS_ERROR_CALL_FAILED (ox800706BE
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

I'm thinking maybe VirtualBox is getting confused about which disk to boot from, but I don't see any settings to help it make up its' mind.

[Perryg]

From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

[jnojr]

Code: Select all

flamingo:~ joliver$ VBoxManage showvminfo Debian --details
Name:            Debian
Groups:          /
Guest OS:        Debian (64 bit)
UUID:            ef56d9e8-a849-4cdf-87b2-0a56a188a97e
Config file:     /Users/joliver/VirtualBox VMs/Debian/Debian.vbox
Snapshot folder: /Users/joliver/VirtualBox VMs/Debian/Snapshots
Log folder:      /Users/joliver/VirtualBox VMs/Debian/Logs
Hardware UUID:   ef56d9e8-a849-4cdf-87b2-0a56a188a97e
Memory size:     1024MB
Page Fusion:     off
VRAM size:       16MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
Synthetic Cpu:   off
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): HardDisk
Boot Device (2): DVD
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
PAE:             off
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Hardw. virt.ext exclusive: off
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
State:           aborted (since 2013-09-04T20:01:01.075000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      2
Storage Controller Bootable (1):        on
IDE (1, 0): Empty
SATA (0, 0): /Users/joliver/VirtualBox VMs/Debian/Debian.vmdk (UUID: 36eebb65-fc64-4c8d-a2f9-ab60ed308f76)
SATA (1, 0): /Users/joliver/VirtualBox VMs/Debian/deb2.vmdk (UUID: 4a37c0ac-8dea-497b-a370-d3c6784fc5a2)
NIC 1:           MAC: 08002713EB6D, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:           MAC: 0800276A1C65, Attachment: Host-only Interface 'vboxnet0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: CoreAudio, Controller: AC97)
Clipboard Mode:  disabled
Drag'n'drop Mode:  disabled
VRDE:            disabled
USB:             enabled
EHCI:            disabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

VRDE Connection:    not active
Clients so far:     0

Guest:

Configured memory balloon size:      0 MB

[Perryg]

So when you connected deb2.vmdk the guest will not boot. If you remove deb2.vmdk does it in fact boot as usual?

What is on deb2.vmdk and how was it created?

[jnojr]

So when you connected deb2.vmdk the guest will not boot. If you remove deb2.vmdk does it in fact boot as usual?

Correct.

What is on deb2.vmdk and how was it created?

It's basically the same disk that was on another VM and had "stuff" done to it. We just gzipped it it up and copied it over.

[Perryg]

If it were me I would release the deb2 drive and move it to a new folder, even one created in the same level as the original guest and then attach it. You may be confusing VBox with two bootable drives in the same top level folder.

[mpack]

or two drives with the same signature? Is LVM being used here?

[jnojr]

If it were me I would release the deb2 drive and move it to a new folder, even one created in the same level as the original guest and then attach it. You may be confusing VBox with two bootable drives in the same top level folder.

Now I get:


Failed to open the hard disk /Users/joliver/lima-confluence/deb2.vmdk.

Could not find file for the medium '/Users/joliver/lima-confluence/deb2.vmdk' (VERR_FILE_NOT_FOUND).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: Medium
Interface: IMedium {29989373-b111-4654-8493-2e1176cba890}
Callee: IVirtualBox {3b2f08eb-b810-4715-bee0-bb06b9880ad2}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

[jnojr]

or two drives with the same signature? Is LVM being used here?

No LVM.

[Perryg]

When you moved this did you remove it from the guest first?
You may need to stop all instances of VirtualBox including the VBoxSVC for 20 or so seconds to allow time for everything to unregister and then add it back again.

[jnojr]

When you moved this did you remove it from the guest first?
You may need to stop all instances of VirtualBox including the VBoxSVC for 20 or so seconds to allow time for everything to unregister and then add it back again.

The other VM is on another host. The VM was shut down before copying the disk off. I had VirtualBox completely shut down, strated it, and tried to attach the disk again. No dice.

[Perryg]

I have to say this is strange and one that I have never had happen. You might try to attach it to the IDE chain instead of the sata chain but other than that you would need to post a ticket at bugtracker

[jnojr]

I have to say this is strange and one that I have never had happen. You might try to attach it to the IDE chain instead of the sata chain but other than that you would need to post a ticket at bugtracker

LOL! Thanks for your efforts. I went back to the other host and re-copied everything to a new directory, and got it to work this time. I figure I probably fat-fingered something somehow. But all's well that ends well! I do appreciate all the input!