[SOLVED] Problem after upgrade VBox 4.3 to Vbox 5.0
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You said then you upgraded to 5, and got the VM's working. And why is it a problem to just import them one-by-one?
That is another PC which is now running without problem.
I have 2 PCs with same configure;
Host Ubuntu 14.04 desktop
VMs Ubuntu/Windows/Mint/etc
both running Virtualbox 5.0 installed on repo
The only difference is;
PC1-working PC
both Host and VMs installed on 1TB SSD
PC2-spare PC (encountering problem mentioned on this posting)
Ubuntu 14.04 Host installed on 120G SSD
VMs installed on WD HD
I suspect whether the problem coming from cable connection of the HD, the hardware problem. I'll check it later. According to my recollection I encountered similar problem before.
What are the perms on
/media/satimis/xxxx
and
/media/satimis/xxxx/VirtualBox VMs ?
Code:
for i in /media/satimis/xxxx "/media/satimis/xxxx/VirtualBox VMs" ; do ls -ld $i ; done
post results.
On a personal note: I've reached my limit on helping users who insist on using non-repo software.
What's wrong with 4.3.18?
I have checked the PC (spare) and found cables to HD and SSD connected properly.
⟫ for i in /media/satimis/xxxxxx "/media/satimis/xxxxxx/VirtualBox VMs" ; do ls -ld $i ; done
Code:
drwxr-xr-x 6 satimis satimis 4096 Apr 23 2015 /media/satimis/xxxxxx
ls: cannot access /media/satimis/xxxxxx/VirtualBox: No such file or directory
ls: cannot access VMs: No such file or directory
On Home
Devices -> 1.0 TB Volume (HD)
it displays
Data
lost+found
VirtualBox VMs
-> VirtualBox VMs
it displays all VMs
On each VM
it displays
VM1
Logs
vm1.vbox
vm1.vbox-prev
vm1-disk1.vmdk
VM2
Logs
vm2.vbox
vm2.vbox-prev
vm2-disk1.vmdk
etc.
all files on Data folder can be evoked/read.
Quote:
What's wrong with 4.3.18?
This spare PC hasn't been run for sometimes. Several days before I tried to backup files from the working PC to it. After starting Ubuntu update software reminded me to update/upgrade the system. I did and it came to present situation
I have checked the PC (spare) and found cables to HD and SSD connected properly.
⟫ for i in /media/satimis/xxxxxx "/media/satimis/xxxxxx/VirtualBox VMs" ; do ls -ld $i ; done
Code:
drwxr-xr-x 6 satimis satimis 4096 Apr 23 2015 /media/satimis/xxxxxx
ls: cannot access /media/satimis/xxxxxx/VirtualBox: No such file or directory
ls: cannot access VMs: No such file or directory
On Home
Devices -> 1.0 TB Volume (HD)
it displays
Data
lost+found
VirtualBox VMs
-> VirtualBox VMs
it displays all VMs
On each VM
it displays
VM1
Logs
vm1.vbox
vm1.vbox-prev
vm1-disk1.vmdk
VM2
Logs
vm2.vbox
vm2.vbox-prev
vm2-disk1.vmdk
etc.
all files on Data folder can be evoked/read. This spare PC hasn't been run for sometimes. Several days before I tried to backup files from the working PC to it. After starting Ubuntu update software reminded me to update/upgrade the system. I did and it came to present situation
...which brings us full-circle, back to "didn't you already DO THIS BEFORE??? As in UPGRADE from 4.x to 5.x???" Seems like you're describing the exact same problem as before...the size of the hard drive won't matter at all.
This spare PC hasn't been run for sometimes. Several days before I tried to backup files from the working PC to it. After starting Ubuntu update software reminded me to update/upgrade the system. I did and it came to present situation
Regards
satimis
Virtualbox 5 doesn't show here as an update. So did you add a PPA for it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.