search

dgzyk / phpvirtualbox

Automatically exported from code.google.com/p/phpvirtualbox
Other
0 stars 0 forks source link

how to get the -r500 revision installed #691

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 

What steps will reproduce the problem?
1. installing phpvirtualbox4.2-4 in ubuntu 12.04 server and php5 via zip file 
2. running vbox4.2.12 with proper extpack
3. trying to take snapshots 

What is the expected output? What do you see instead?
the expected output is an error free snapshot.  what happens is i get error 
saying VirtualBox error: Invalid managed object reference 
"8c525ff421f7d5da-000000000000025a"
also when i start a vm via phpvirtualbox it starts but i can't acces via ssh 
and my port forwarding rules even though they are listed in networking.  
however if i start the same vm via command line with VBoxHeadless --startvm it 
works fine.  

What version of phpVirtualBox, VirtualBox, and PHP are you using? On what
operating system?
see above

Please provide any additional information below.
have already been told this is an issue using the pre-zipped versions for 
installing and was advised to "get the latest revision (r500) with a svn 
checkout and not use the pre-zipped version, as it does not containt the fix."
my problem is i have no idea how to get or install this revised version. could 
you post the steps for me as well as confirm this will fix my problem.  also to 
clarify something: should i register vm's before adding them to phpvirtualbox 
or just add them and phpvirtualbox registers them.

Original issue reported on code.google.com by d.gec...@gmail.com on 6 Jun 2013 at 11:18

GoogleCodeExporter commented 8 years ago 
This version will be released shortly (today) and you can download the zip.

Original comment by imooreya...@gmail.com on 11 Jul 2013 at 4:38

GoogleCodeExporter commented 8 years ago 
thanks for your response, and following up.  i will keep in mind it is now 
available as a .zip.  i did however get it working prior by using svn and the 
entire trunk instead of the previous .zip, and it worked as expected that way.  
i was still getting some warning from time to time, but it didn't seem to 
effect functionality.  sorry i forget the exact warning at this time or i would 
have included it.
thanks again.

Original comment by d.gec...@gmail.com on 11 Jul 2013 at 11:00