VM is "inaccessible"

Discussions related to using VirtualBox on Linux hosts.

Re: VM is "inaccessible"

Postby kjbucknum » 23. May 2011, 14:52

See post viewtopic.php?f=7&t=41695 for some others having the same problem. I'm still having it every day.

Virtualbox 4.0.8 running on Ubuntu 11.04 64 bit from deb http://download.virtualbox.org/virtualbox/debian natty contrib

Virtual machine was recreated multiple times before the trick of just removing the bad characters came along, so the machine at least was created using the version I'm running.

Disk image that this is running on was originally created under some version of Virtualbox 3 on Gentoo 64bit and runs Win 7 64 bit. It has actually been moved up and down from 3 to 4 several times. I tried 4 on Gentoo a couple times, but it was unstable so dropped back down to 3 with no problems. I switched to Ubuntu about 3 weeks ago, and ran under Ubuntu's OSE version for a couple weeks, but it was extremely unstable. It crashed 2-3 times a day. I switched to the version from Virtualbox about a week ago, and the crashes went away, but everytime I go to start the machine, I have to delete the control characters out of the file.
kjbucknum
 
Posts: 4
Joined: 20. May 2011, 14:07
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Win 7

Re: VM is "inaccessible"

Postby Perryg » 23. May 2011, 15:52

Try shutting down everything related to VirtualBox and instead of deleting the line replace the invalid characters with "4.0.8", save, & exit then see if starting the guest still corrupts the *.vbox file.
Perryg
Site Moderator
 
Posts: 34374
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VM is "inaccessible"

Postby kjbucknum » 23. May 2011, 16:18

Didn't help.

Powered off my two virtual machines. ps aux | grep virt showed nothing. Edited the file to remove the control characters, and then relaunched. Fired up outlook to check email, shut it down, and after it was down, control characters again.
kjbucknum
 
Posts: 4
Joined: 20. May 2011, 14:07
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Win 7

Re: VM is "inaccessible"

Postby Perryg » 23. May 2011, 16:29

I am unable to reproduce this error.
Add your name to this http://www.virtualbox.org/ticket/8948 ticket and post the *.vbox file (as attachment) It would not hurt to also post the guests log file (as attachment)
Perryg
Site Moderator
 
Posts: 34374
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VM is "inaccessible"

Postby dadaj » 24. May 2011, 03:15

Yesterday, I report the problem won't affect the VM machine created by the copy of VirtualBox repository(i.e.: "deb http://download.virtualbox.org/virtualbox/debian lucid contrib non-free"). The VM machine also is inaccessible today after Ubuntu LTS 10.04 started.
dadaj
 
Posts: 3
Joined: 23. May 2011, 04:53
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: win7

Re: VM is "inaccessible"

Postby toothless » 24. May 2011, 04:59

Same error for me after upgrading from vbox 4.0.6 to 4.0.8 on my Ubuntu 10.04 host (AMD64) and Win server 2008 guest:


PCDATA invalid Char value 3.
Location: '/home/user/.VirtualBox/Machines/WinServer2008_64bit/WinServer2008_64bit.xml', line 142 (3), column 36.
/home/vbox/vbox-4.0.8/src/VBox/Main/src-server/MachineImpl.cpp[679] (nsresult Machine::registeredInit()).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {d2de270c-1d4b-4c9e-843f-bbb9b47269ff}
toothless
 
Posts: 4
Joined: 9. Apr 2011, 05:05
Primary OS: Ubuntu other
VBox Version: OSE Debian
Guest OSses: multiple linux and windows

Re: VM is "inaccessible"

Postby oreomatic » 24. May 2011, 20:08

Same problem here, only solution I found was deleting the extra character created in the .vbox file. Ubuntu 11.04 x64 Host, vbox 4.0.8 from virtualbox.org with Windows 2008 x64 guest, I also have a Windows 7 x64 guest which doesn't produce the same issue. I took a screenshot with the line in question, If I remove the weird character it works fine. I'm in vboxuser group, have dkms installed and if it's any relevance I use compiz. The column is never right, but if you search for the line it's supposed to be on, gedit makes it fairly noticeable with a box place mark. This event happens everytime I close virtualbox and not always the same line affected but it is always seems to be adding a character after value eg; value="*<character here>" .

See screenshot/logs attached
Attachments
linms2008.jpg
linms2008.jpg (103.85 KiB) Viewed 12091 times
VBox.log.3.txt
(76.61 KiB) Downloaded 72 times
LinMSS2008.vbox.txt
(11.64 KiB) Downloaded 43 times
oreomatic
 
Posts: 1
Joined: 24. May 2011, 14:42
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Server 2008

Re: VM is "inaccessible"

Postby Perryg » 24. May 2011, 20:18

All of those that have not need to add their names and information at the ticket posted above!
It's the only way this is going to be fixed.
Perryg
Site Moderator
 
Posts: 34374
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VM is "inaccessible"

Postby dadaj » 25. May 2011, 02:49

thanks oreomatic:

Following your instruction, the VM machine run smoothly without reapplying settings again.
dadaj
 
Posts: 3
Joined: 23. May 2011, 04:53
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: win7

Re: VM is "inaccessible"

Postby otobyt » 27. May 2011, 20:18

Similar issue running 10.04 LTS host and Windows 7 guest under virtualbox 4.0.8:
Code: Select all   Expand viewCollapse view
PCDATA invalid Char value 3.
Location: '/home/arrt/.VirtualBox/Machines/W7/W7.vbox', line 142 (3), column 36.
/home/vbox/vbox-4.0.8/src/VBox/Main/src-server/MachineImpl.cpp[679] (nsresult Machine::registeredInit()).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {d2de270c-1d4b-4c9e-843f-bbb9b47269ff}


only fix I've found so far is to remove '' character from referenced line of .vbox file... don't know yet how to keep VirtualBox from re-writing that character every time I run the VM. I have an XP guest that seems to run fine after the upgrade from 4.0.6 to 4.0.8 however... will be curious to hear any solutions to this issue.
otobyt
 
Posts: 10
Joined: 28. Sep 2010, 18:47
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Windows 7

Re: VM is "inaccessible"

Postby kjbucknum » 27. May 2011, 20:25

Solution is in the ticket linked above. Have add a registry entry in Windows.
kjbucknum
 
Posts: 4
Joined: 20. May 2011, 14:07
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Win 7

Re: VM is "inaccessible"

Postby otobyt » 31. May 2011, 20:57

otobyt
 
Posts: 10
Joined: 28. Sep 2010, 18:47
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Windows 7

Re: VM is "inaccessible"

Postby rey » 21. Jul 2015, 14:07

Hi!

Good day, Please help me in my problem.. We're running virtualbox as server in our office, when suddenly the host crashes and my guest OS become inaccessible. We have snapshots as backup, but I think the .vbox file is corrupted so snapshots are useless. I tried the solutions on the internet but no luck.

I tried using the.vbox-prev as .vbox
Also there is no special characters on .vbox file.

Below is the error;
Extra Content at the end of the document.

Please please help me.. :(

Thank you.
rey
 
Posts: 5
Joined: 21. Jul 2015, 13:40

Re: VM is "inaccessible"

Postby noteirak » 21. Jul 2015, 14:55

One issue per thread please. Open a new topic, make sure you've read Minimum information needed for assistance and provide zipped attachment of the VM log file and the guest settings in the new topic.
Hyperbox - Virtual Infrastructure Manager - https://kamax.io/hbox/
Manage your VirtualBox infrastructure the free way!
noteirak
Site Moderator
 
Posts: 5192
Joined: 13. Jan 2012, 11:14
Primary OS: Debian other
VBox Version: OSE Debian
Guest OSses: Debian, Win 2k8, Win 7

Previous

Return to VirtualBox on Linux Hosts

Who is online

Users browsing this forum: No registered users and 9 guests