Page 2 of 2

Re: Fail to start VM

Posted: 22. Nov 2020, 20:55
by fth0
You must have overlooked the word contents. ;)

Please create a zip file containing the two files and add it as an attachment to your next post.

Re: Fail to start VM

Posted: 23. Nov 2020, 04:10
by satimis
fth0 wrote:You must have overlooked the word contents. ;)

Please create a zip file containing the two files and add it as an attachment to your next post.
Oh, sorry. Did it again.

$ zip multisite00.zip multisite00.vbox VirtualBox.xml

Code: Select all

  adding: multisite00.vbox (deflated 61%)
  adding: VirtualBox.xml (deflated 76%)
  
$ ls

Code: Select all

multisite00.vbox  multisite00.zip  VirtualBox.xml
multisite00.zip is attached here. Thanks

Re: Fail to start VM

Posted: 23. Nov 2020, 10:51
by fth0
If the VM files for multisite00 are still in the /home/satimis/VirtualBox\ VM/multisite00/ folder, you can reboot the host, make a backup of the two files you've sent and replace them with the two files in this post's attachment. You can compare the files to see that I've changed the two paths matching the current location of the files.

Re: Fail to start VM

Posted: 23. Nov 2020, 16:10
by satimis
fth0 wrote:If the VM files for multisite00 are still in the /home/satimis/VirtualBox\ VM/multisite00/ folder, you can reboot the host, make a backup of the two files you've sent and replace them with the two files in this post's attachment. You can compare the files to see that I've changed the two paths matching the current location of the files.
I have other VMs installed and running on this group.

$ ls /home/satimis/VirtualBox\ VM/

Code: Select all

 childhood-ub2004pciessd   multisite03         opera-ub2004pciessd
 cuisine-ub2004pciessd    'New group 2'        satimis-ub2004pciessd
 LAMP-ub2004pciessd       'New group 3'        ub2004pciessd-00
 multisite00              'New group 4'        ub2004pciessd-01
 multisite01              'New group 5'        ub2004pciessd-02
 multisite02               now-ub2004pciessd
If I replace the existing VirtualBox.xml with your edited VirtualBox.xml would it affect other VMs?

Regards

Re: Fail to start VM

Posted: 23. Nov 2020, 19:21
by fth0
satimis wrote:If I replace the existing VirtualBox.xml with your edited VirtualBox.xml would it affect other VMs?
I suggested to reboot the host before replacing the files for the following reason: Only if neither the VirtualBox Manager nor any of the VMs is running, the VBoxSVC process also is not running, and only then you can safely replace the files. If the VBoxSVC is running when replacing the files, they probably will be ignored and overwritten with their old contents later on, when the VBoxSVC process is terminated.

Other than that, compare my modified files with your original files, and you'll see that I only corrected the wrong paths of multisite00.

Re: Fail to start VM

Posted: 24. Nov 2020, 06:01
by satimis
fth0 wrote:
satimis wrote:If I replace the existing VirtualBox.xml with your edited VirtualBox.xml would it affect other VMs?
I suggested to reboot the host before replacing the files for the following reason: Only if neither the VirtualBox Manager nor any of the VMs is running, the VBoxSVC process also is not running, and only then you can safely replace the files. If the VBoxSVC is running when replacing the files, they probably will be ignored and overwritten with their old contents later on, when the VBoxSVC process is terminated.

Other than that, compare my modified files with your original files, and you'll see that I only corrected the wrong paths of multisite00.
I did following steps before;

Created a folder on /home/satimis/Videos/multisite00_compare_folder
Extracted your .zip file on a new folder /home/satimis/Videos/multisite00_edited_folder

Copied the old VirtualBox.xml from /home/satimis/.config/VirtualBox/ to multisite00_compare_folder and renamed it as VirtualBox_old.xml

Copied your edited VirtualBox.xml from ~/multisite00_edited_folder/multisite00/ to multisite00_compare_folder and renamed it as VirtualBox_new.xml

$ cd ~/multisite00_compare_folder

ran;
$ sort VirtualBox_old.xml VirtualBox_old.xml.sorted

$ sort VirtualBox_new.xml VirtualBox_new.xml.sorted

$ diff VirtualBox_old.xml.sorted VirtualBox_new.xml.sorted

Code: Select all

80c80
<       <MachineEntry uuid="{8fc0fb5b-e5c4-4e31-9bfc-b03a100e4f53}" src="/home/satimis/VirtualBox VM/multisite00/multisite00/multisite00.vbox"/>
---
>       <MachineEntry uuid="{8fc0fb5b-e5c4-4e31-9bfc-b03a100e4f53}" src="/home/satimis/VirtualBox VM/multisite00/multisite00.vbox"/>
You have changed the path of "src" on the edited VirtualBox.xml

Thanks

I have about 20 VMs installed but not all running at the same time. Before start I'll reboot PC, not only restarting Oracle VM VirtualBox Manager to make sure all VMs not started.

Further questions
1) Do I need to replace your edited multisite00.vbox file ?
2) How to check VBoxSVC is not running ?

Regards

Re: Fail to start VM

Posted: 24. Nov 2020, 15:25
by fth0
satimis wrote:1) Do I need to replace your edited multisite00.vbox file ?
Yes. You've already seen that my VirtualBox.xml file contains the corrected link to the multisite00.vbox file. Similarly, my multisite00.vbox file contains the corrected link to the multisite00-disk1.vdi file.
satimis wrote:2) How to check VBoxSVC is not running ?
In a terminal, execute

Code: Select all

ps -e | grep -i VBoxSVC
.

Re: Fail to start VM

Posted: 24. Nov 2020, 16:00
by satimis
fth0 wrote:
satimis wrote:1) Do I need to replace your edited multisite00.vbox file ?
Yes. You've already seen that my VirtualBox.xml file contains the corrected link to the multisite00.vbox file. Similarly, my multisite00.vbox file contains the corrected link to the multisite00-disk1.vdi file.
satimis wrote:2) How to check VBoxSVC is not running ?
In a terminal, execute

Code: Select all

ps -e | grep -i VBoxSVC
.
Just test your command. Please see attached photo

1)
Oracle VM VirtualBox Manager is NOT running

Code: Select all

$ ps -e | grep -i VBoxSVC
1 satimis@PCIeSSD1T:~$ 
Why there is "1" in red color popup ?

2)
Oracle VM VirtualBox Manager is up but no VM is running

Code: Select all

$ ps -e | grep -i VBoxSVC
   5439 ?        00:00:00 VBoxSVC
What does "5439 ?" indicate?

Thanks

Re: Fail to start VM

Posted: 24. Nov 2020, 17:10
by scottgus1
satimis wrote:What does "5439 ?" indicate?
A quick google on the Linux 'ps' command seems to show this.

You can also log out and back in again on the host PC, and be sure no Virtualbox processes are set to nor auto-start. The VboxSVC only starts when a Virtualbox VM or the main window or a vboxmanage command has been running, and the service drops off after a few seconds when all Virtualbox processes are gone.

Re: Fail to start VM

Posted: 24. Nov 2020, 17:54
by fth0
satimis wrote:Why there is "1" in red color popup ?
I don't know. Depending on which Linux OS and which Linux shell you're using in the terminal, my command may be incorrect. But it seems to fulfill its purpose.
satimis wrote:What does "5439 ?" indicate?
If you use ps -e (without the rest of my suggested command), you'll also see the heading of the output (PID 5439, TTY ?). You can then use man ps in the terminal or in Google to learn what the output of ps means. To get even more output to wonder about, you could use ps -elf or ps aux for the full glory. I'm glad that I only suggested ps -e. ;)

Re: Fail to start VM

Posted: 25. Nov 2020, 10:53
by satimis
fth0 wrote:
satimis wrote:Why there is "1" in red color popup ?
I don't know. Depending on which Linux OS and which Linux shell you're using in the terminal, my command may be incorrect. But it seems to fulfill its purpose.
satimis wrote:What does "5439 ?" indicate?
If you use ps -e (without the rest of my suggested command), you'll also see the heading of the output (PID 5439, TTY ?). You can then use man ps in the terminal or in Google to learn what the output of ps means. To get even more output to wonder about, you could use ps -elf or ps aux for the full glory. I'm glad that I only suggested ps -e. ;)
Your advice noted and thanks

Performed following steps;

Boot up PC

$ ps -e | grep -i VBoxSVC

Code: Select all

1 satimis@PCIeSSD1T:~$ 
Rename old VirtualBox.xml

Code: Select all

$ mv /home/satimis/.config/VirtualBox/VirtualBox.xml /home/satimis/.config/VirtualBox/VirtualBox.xml.old
Renamed old multisite00.vbox

Code: Select all

$ mv /home/satimis/VirtualBox\ VM/multisite00/multisite00.vbox /home/satimis/VirtualBox\ VM/multisite00/multisite00.vbox.old
$ cp /home/satimis/Videos/multisite00_edited_folder/multisite00/VirtualBox.xml /home/satimis/.config/VirtualBox/

$ cp /home/satimis/Videos/multisite00_edited_folder/multisite00/multisite00.vbox /home/satimis/VirtualBox\ VM/multisite00/

Started Oracle VM VirtualBox Manager

multisite00 can be started. Also I have checked 3 VMs and they can be started as well.

Thanks

Regards

Furthermore where can I mark this thread SOLVED ?

Re: Fail to start VM

Posted: 25. Nov 2020, 11:18
by fth0
satimis wrote:Furthermore where can I mark this thread SOLVED ?
Edit your initial post and prepend "[SOLVED] " to the title.

Re: Fail to start VM

Posted: 25. Nov 2020, 11:24
by satimis
fth0 wrote:
satimis wrote:Furthermore where can I mark this thread SOLVED ?
Edit your initial post and prepend "[SOLVED] " to the title.
Noted and thanks

Regards