VBoxSvc crash when running CloneVdi

Discussions related to using VirtualBox on Windows hosts.
Post Reply
JohnG
Volunteer
Posts: 77
Joined: 23. Feb 2008, 00:51
Location: Canada

VBoxSvc crash when running CloneVdi

Post by JohnG »

Running VboxManage/CloneVdi appears to crash VBoxSvc -- the crash happens at the end of the cloning process.
This is in v. 1.6, on a Vista32 Host.

John

-----------


Output from Command Window:


Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\MyUserFolder>cd\

C:\>cd program files\sun\xvm VirtualBox

C:\Program Files\Sun\xVM VirtualBox>VBoxManage.exe clonevdi "D:\VirtualBox\VirtualDrives\W98_1.vdi" "D:\VirtualBox\VirtualDrives\W98_1_test2.vdi"
VirtualBox Command Line Management Interface Version 1.6.0
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

C:\Program Files\Sun\xVM VirtualBox>



----------


Windows Error:


Problem signature:
Problem Event Name: APPCRASH
Application Name: VBoxSVC.exe
Application Version: 1.0.0.1
Application Timestamp: 4818d1c9
Fault Module Name: StackHash_1703
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 0000083c
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional Information 1: 1703
Additional Information 2: 2264db07e74365624c50317d7b856ae9
Additional Information 3: 1344
Additional Information 4: 875fa2ef9d2bdca96466e8af55d1ae6e

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409
fordp
Posts: 5
Joined: 5. Nov 2008, 10:45

Post by fordp »

I have a crash like that too !

Sorry more info.

I am using Virtual Box 2.0.4 on an Intel Quad Core and XP Pro SP3.

I hope this helps.

Roll on Virtual Box 2.0.5 ;)
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Post by mpack »

I assume that neither of you had VM guests running at the time the clonevdi command was used?

Otherwise this is puzzling, since clonevdi is little more than a simple file copy operation, ending with a header patch to change the UUID. The things that might trip it up are the things that might trip up any file copy: corrupted source, corrupted dest, write protection. Perhaps lack of admin privileges might be an issue on some hosts.
Post Reply