VirtualBox

Ticket #15134 (closed defect: obsolete)

Opened 5 years ago

Last modified 5 years ago

Die viertuelle Maschine ...konnte nicht gestartet werden

Reported by: ifs Owned by:
Component: virtual disk Version: VirtualBox 5.0.14
Keywords: vm wont start Cc:
Guest type: Windows Host type: Windows

Description

Die virtuelle Maschine faktura 2016a konnte nicht gestartet werden.

ahci#0: The target VM is missing a device on port 0. Please make sure the source and target VMs have compatible storage configurations [ver=8 pass=final] (VERR_SSM_LOAD_CONFIG_MISMATCH).

Fehlercode:E_FAIL (0x80004005) Komponente:ConsoleWrap Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Problem, is always here after setting a safepoint. often i have to create a complete new vm an relink the vm file, and activate all software again. lg

Attachments

VBoxHardening.log Download (406.2 KB) - added by ifs 5 years ago.
hardening file
VBox.log.1 Download (137.3 KB) - added by ifs 5 years ago.
log1
VBox.log.2 Download (137.1 KB) - added by ifs 5 years ago.
log2

Change History

Changed 5 years ago by ifs

hardening file

Changed 5 years ago by ifs

log1

Changed 5 years ago by ifs

log2

comment:1 Changed 5 years ago by frank

I would like to know the exact steps how your VM came into this state. The saved state of this VM has a hard disk attached at port 0. However, the VM configuration of your VM lacks of this hard disk. This cannot happen unless 1) there is a bug in VirtualBox or 2) you did some manual tweaks of the VM settings file. In case of 2) this is not a VirtualBox bug. In case of 1) please provide exact steps how to reproduce this problem.

comment:2 Changed 5 years ago by ifs

OK, i'll try to reproduce this for you. First i try to set a safepoint named the current date "12-02-16" then there is a failure message: Es konnte kein Sicherungspunkt der virtuellen Maschine faktura 2016a erstellt werden.

Medium 'G:\VMs\office 2013v2\office 2013v2-disk1.vmdk' is attached to a virtual machine with UUID {8acfb79f-ac5b-4cc8-a9af-7b4a494e390d}. No differencing media based on it may be created until it is detached.

Fehlercode:VBOX_E_INVALID_OBJECT_STATE (0x80BB0007) Komponente:MediumWrap Interface:IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

So now you just have to retry this and it will work. But then the connection to the vm disk is deleted. for my onpinion this is a buuuuuuug!!!

comment:3 Changed 5 years ago by ifs

Hello!!!! Anyone there?

comment:4 Changed 5 years ago by frank

Please attach a VBox.log file from the VM session when you tried to create the snapshot (Sicherungspunkt) the first time which failed. The VBox.log files you attached don't contain any .iso medium.

comment:5 Changed 5 years ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete

Please reopen if still relevant with a recent VirtualBox release and you provided the requested information.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use