VirtualBox vs KVM vs XEN

I apologize in advance for the blank question I am asking…

Hardware:
ASUS M5A99X EVO motherboard
32 GB RAM
128 GB SATA-6 SSD (OS and software)
750 GB SATA-6 WD Black (home)

I had VirtualBox running just fine on Debian 7.6 64-bit… but due to a failure to fully understand UEFI, I tried openSUSE 12.3 instead and liked it (KDE4 desktop was a great change from Gnome3)… at first I was missing time and resources to try bringing everything up (was focused on why I couldn’t see an LTO-3 tape drive attached to an old SCSI card). Now that I understand why I am not seeing the tape, I have moved on and upgraded to 13.1 and installed more software, especially VirtualBox.

I can start virtualbox, change settings for each virtual machine, change global preferences, install extensions packs… BUT, when I start a VM, it locks up everything… NO CTL+ALT+F1, mouse frozen in place, keyboard unresponsive, ONLY recourse is the reset button to force a reboot (YES, I DID wait for HOURS to see if it would unlock or timeout… no joy… reboot ONLY solution)

So, I have followed every thread here and at forums.virtualbox.org that mentions freeze or lock with no joy from attempting any potential fix. (My Version 4.3.16 r95972 from the Oracle repository)

I am so screwed up now, I have lost my notes on what I have added for VBox and I am considering dumping VirtualBox and installing either KVM or XEN unless I can find a way to make VB work.

What information do I need to add so there is hope of help? I liked VBox on the Debian install, but either a workable VBox or a different and better solution for openSUSE 13.1 would be nice

Please post:

zypper se -si virtual vbox kernel make gcc

Here goes:


zypper se -si virtual vbox kernel make gcc
Loading repository data...
Reading installed packages...


S | Name                         | Type    | Version                    | Arch   | Repository                                         
--+------------------------------+---------+----------------------------+--------+----------------------------------------------------
i | VirtualBox-4.3               | package | 4.3.16_95972_openSUSE123-1 | x86_64 | Oracle_VirtualBox                                  
i | gcc                          | package | 4.8-2.1.2                  | x86_64 | openSUSE-13.1-Oss                                  
i | gcc48                        | package | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss                                  
i | kernel-default               | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update                               
i | kernel-default               | package | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update                               
i | kernel-default-devel         | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update                               
i | kernel-default-devel         | package | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update                               
i | kernel-desktop               | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update                               
i | kernel-desktop               | package | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update                               
i | kernel-desktop-devel         | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update                               
i | kernel-desktop-devel         | package | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update                               
i | kernel-devel                 | package | 3.11.10-21.1               | noarch | openSUSE-13.1-Update                               
i | kernel-devel                 | package | 3.11.10-17.2               | noarch | openSUSE-13.1-Update                               
i | kernel-firmware              | package | 20130714git-2.21.1         | noarch | openSUSE-13.1-Update                               
i | kernel-source                | package | 3.11.10-21.1               | noarch | openSUSE-13.1-Update                               
i | kernel-source                | package | 3.11.10-17.2               | noarch | openSUSE-13.1-Update                               
i | kernel-syms                  | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update                               
i | kernel-syms                  | package | 3.11.10-17.1               | x86_64 | openSUSE-13.1-Update                               
i | kernel-xen-devel             | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update                               
i | kernel-xen-devel             | package | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update                                                                                        
i | libgcc_s1                    | package | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss                                                                                           
i | libgcc_s1-32bit              | package | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss                                                                                           
i | libvirt-daemon-driver-vbox   | package | 1.2.8-435.1                | x86_64 | (System Packages)                                                                                           
i | make                         | package | 3.82-160.2.1               | x86_64 | openSUSE-13.1-Oss                                                                                           
i | makedev                      | package | 2.6-560.1.2                | noarch | openSUSE-13.1-Oss                                                                                           
i | nfs-kernel-server            | package | 1.2.8-4.13.1               | x86_64 | openSUSE-13.1-Update                                                                                        
i | python-virtualbox            | package | 4.3.14-126.1               | x86_64 | (System Packages)                                  
i | vboxgtk                      | package | 0.8.2-4.1.3                | noarch | openSUSE-13.1-Oss                                  
i | vboxgtk-lang                 | package | 0.8.2-4.1.3                | noarch | openSUSE-13.1-Oss                                  
i | vboxtool                     | package | 0.4-1.4                    | noarch | openSUSE BuildService - Virtualization (VirtualBox)
i | virtualbox                   | package | 4.3.14-126.1               | x86_64 | (System Packages)                                  
i | virtualbox-guest-kmp-default | package | 4.3.14_k3.11.10_21-126.1   | x86_64 | (System Packages)                                  
i | virtualbox-guest-kmp-default | package | 4.3.14_k3.11.10_21-124.3   | x86_64 | (System Packages)                                  
i | virtualbox-guest-kmp-default | package | 4.3.14_k3.11.10_21-124.2   | x86_64 | (System Packages)                                  
i | virtualbox-guest-kmp-default | package | 4.3.14_k3.11.10_21-124.1   | x86_64 | (System Packages)                                  
i | virtualbox-guest-kmp-default | package | 4.3.14_k3.11.10_21-123.1   | x86_64 | (System Packages)                                  
i | virtualbox-guest-kmp-desktop | package | 4.3.14_k3.11.10_21-126.1   | x86_64 | (System Packages)                                  
i | virtualbox-guest-kmp-desktop | package | 4.3.14_k3.11.10_21-124.3   | x86_64 | (System Packages)                                  
i | virtualbox-guest-kmp-desktop | package | 4.3.14_k3.11.10_21-124.2   | x86_64 | (System Packages)                                  
i | virtualbox-guest-kmp-desktop | package | 4.3.14_k3.11.10_21-124.1   | x86_64 | (System Packages)                                  
i | virtualbox-guest-kmp-desktop | package | 4.3.14_k3.11.10_21-123.1   | x86_64 | (System Packages)                                  
i | virtualbox-guest-tools       | package | 4.3.14-126.1               | x86_64 | (System Packages)                                  
i | virtualbox-guest-x11         | package | 4.3.14-126.1               | x86_64 | (System Packages)                                  
i | virtualbox-host-kmp-default  | package | 4.3.14_k3.11.10_21-126.1   | x86_64 | (System Packages)                                  
i | virtualbox-host-kmp-default  | package | 4.3.14_k3.11.10_21-124.3   | x86_64 | (System Packages)                                  
i | virtualbox-host-kmp-default  | package | 4.3.14_k3.11.10_21-124.2   | x86_64 | (System Packages)                                  
i | virtualbox-host-kmp-default  | package | 4.3.14_k3.11.10_21-124.1   | x86_64 | (System Packages)                                  
i | virtualbox-host-kmp-default  | package | 4.3.14_k3.11.10_21-123.1   | x86_64 | (System Packages)                                  
i | virtualbox-host-kmp-desktop  | package | 4.3.14_k3.11.10_21-126.1   | x86_64 | (System Packages)                                  
i | virtualbox-host-kmp-desktop  | package | 4.3.14_k3.11.10_21-124.3   | x86_64 | (System Packages)                                  
i | virtualbox-host-kmp-desktop  | package | 4.3.14_k3.11.10_21-124.2   | x86_64 | (System Packages)                                  
i | virtualbox-host-kmp-desktop  | package | 4.3.14_k3.11.10_21-124.1   | x86_64 | (System Packages)                                  
i | virtualbox-host-kmp-desktop  | package | 4.3.14_k3.11.10_21-123.1   | x86_64 | (System Packages)

It would seem there are two versions of VirtualBox on the system… I had tried to delete the earlier version when I first encountered this problem with freezing, and re-installed… when the “System Package” version didn’t show up in “Applications”, I added the Oracle repository and installed again…

I really don’t want to have to have a Microsoft box just to update maps on my GPS or program my radios… it is so much easier to fire up a VM, do what I need to, and tuck the evil desktop away until the next time… There is so much I like about openSUSE 13.1 (and KDE4) that I don’t really want to go back to Debian

Only the Oracle-Repo (VirtualBox-4.3) or the Version from openSUSE, not both.

Then it should work.

Delete all virtualbox- and vbox stuff.

My VirtualBox, kernel and make:

zypper se -si virtual vbox kernel make gcc
S | Name                       | Typ   | Version                    | Arch   | Repository          
--+----------------------------+-------+----------------------------+--------+---------------------
i | VirtualBox-4.3             | Paket | 4.3.16_95972_openSUSE123-1 | x86_64 | VirtualBox_4.3      
i | automake                   | Paket | 1.13.4-2.1.2               | noarch | openSUSE-13.1-Oss   
i | gcc                        | Paket | 4.8-2.1.2                  | x86_64 | openSUSE-13.1-Oss   
i | gcc-c++                    | Paket | 4.8-2.1.2                  | x86_64 | openSUSE-13.1-Oss   
i | gcc-info                   | Paket | 4.8-2.1.2                  | x86_64 | openSUSE-13.1-Oss   
i | gcc-locale                 | Paket | 4.8-2.1.2                  | x86_64 | openSUSE-13.1-Oss   
i | gcc33                      | Paket | 3.3.3-41.1.3               | x86_64 | openSUSE-13.1-Oss   
i | gcc33-locale               | Paket | 3.3.3-41.1.3               | x86_64 | openSUSE-13.1-Oss   
i | gcc48                      | Paket | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss   
i | gcc48-c++                  | Paket | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss   
i | gcc48-info                 | Paket | 4.8.1_20130909-3.2.1       | noarch | openSUSE-13.1-Oss   
i | gcc48-locale               | Paket | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss   
i | kernel-desktop             | Paket | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update
i | kernel-desktop             | Paket | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update
i | kernel-desktop-devel       | Paket | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update
i | kernel-desktop-devel       | Paket | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update
i | kernel-devel               | Paket | 3.11.10-21.1               | noarch | openSUSE-13.1-Update
i | kernel-devel               | Paket | 3.11.10-17.2               | noarch | openSUSE-13.1-Update
i | kernel-firmware            | Paket | 20130714git-2.21.1         | noarch | openSUSE-13.1-Update
i | kernel-source              | Paket | 3.11.10-21.1               | noarch | openSUSE-13.1-Update
i | kernel-source              | Paket | 3.11.10-17.2               | noarch | openSUSE-13.1-Update
i | libgcc_s1                  | Paket | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss   
i | libgcc_s1-32bit            | Paket | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss   
i | libvirt-daemon-driver-vbox | Paket | 1.1.2-2.32.1               | x86_64 | openSUSE-13.1-Update
i | make                       | Paket | 3.82-160.2.1               | x86_64 | openSUSE-13.1-Oss   
i | makedumpfile               | Paket | 1.5.4-3.1.4                | x86_64 | openSUSE-13.1-Oss   
i | makeinfo                   | Paket | 4.13a-36.1.2               | x86_64 | openSUSE-13.1-Oss   
i | nfs-kernel-server          | Paket | 1.2.8-4.13.1               | x86_64 | openSUSE-13.1-Update

DONE.
This is what remains…


zypper se -si virtual vbox kernel make gccLoading repository data...
Reading installed packages...


S | Name                 | Type    | Version              | Arch   | Repository          
--+----------------------+---------+----------------------+--------+---------------------
i | gcc                  | package | 4.8-2.1.2            | x86_64 | openSUSE-13.1-Oss   
i | gcc48                | package | 4.8.1_20130909-3.2.1 | x86_64 | openSUSE-13.1-Oss   
i | kernel-default       | package | 3.11.10-21.1         | x86_64 | openSUSE-13.1-Update
i | kernel-default       | package | 3.11.10-17.2         | x86_64 | openSUSE-13.1-Update
i | kernel-default-devel | package | 3.11.10-21.1         | x86_64 | openSUSE-13.1-Update
i | kernel-default-devel | package | 3.11.10-17.2         | x86_64 | openSUSE-13.1-Update
i | kernel-desktop       | package | 3.11.10-21.1         | x86_64 | openSUSE-13.1-Update
i | kernel-desktop       | package | 3.11.10-17.2         | x86_64 | openSUSE-13.1-Update
i | kernel-desktop-devel | package | 3.11.10-21.1         | x86_64 | openSUSE-13.1-Update
i | kernel-desktop-devel | package | 3.11.10-17.2         | x86_64 | openSUSE-13.1-Update
i | kernel-devel         | package | 3.11.10-21.1         | noarch | openSUSE-13.1-Update
i | kernel-devel         | package | 3.11.10-17.2         | noarch | openSUSE-13.1-Update
i | kernel-firmware      | package | 20130714git-2.21.1   | noarch | openSUSE-13.1-Update
i | kernel-source        | package | 3.11.10-21.1         | noarch | openSUSE-13.1-Update
i | kernel-source        | package | 3.11.10-17.2         | noarch | openSUSE-13.1-Update
i | kernel-syms          | package | 3.11.10-21.1         | x86_64 | openSUSE-13.1-Update
i | kernel-syms          | package | 3.11.10-17.1         | x86_64 | openSUSE-13.1-Update
i | kernel-xen-devel     | package | 3.11.10-21.1         | x86_64 | openSUSE-13.1-Update
i | kernel-xen-devel     | package | 3.11.10-17.2         | x86_64 | openSUSE-13.1-Update
i | libgcc_s1            | package | 4.8.1_20130909-3.2.1 | x86_64 | openSUSE-13.1-Oss   
i | libgcc_s1-32bit      | package | 4.8.1_20130909-3.2.1 | x86_64 | openSUSE-13.1-Oss   
i | make                 | package | 3.82-160.2.1         | x86_64 | openSUSE-13.1-Oss   
i | makedev              | package | 2.6-560.1.2          | noarch | openSUSE-13.1-Oss   
i | nfs-kernel-server    | package | 1.2.8-4.13.1         | x86_64 | openSUSE-13.1-Update

I suspect that I can now pick, say VirtualBox-4.3, to install… am I better off using zypper or YaST(2) to handle the installation? I tend to do command line for most things, but I have noticed that when I do

zypper up

the system seems to get confused and will stick the update icon in the task bar, even though there is nothing to do… and this, in turn, confuses me and makes me nervous. I had no trouble with “apt-get” on the command line with Debian, and used the Synaptic package manager when trolling for new applications. I am so new to openSUSE that the tools are not that familiar as yet, and the difference in desktops between Gnome and KDE is just enough to add confusion…

Only one Programm can use libzypp.
If the Update-Aplett is using it, zypper in Konsole will not work and vice versa. Also with Yast----Software-Installation.

Install Virtualbox with:

zypper in VirtualBox-4.3

DONE!

I had a VERY long backup running (650 GB to the Cloud) and thought I had better wait until it finished, which, as it turns out, was a very good decision (see below)

And here is where I am now…

zypper se -si virtual vbox kernel make gcc
Loading repository data...
Reading installed packages...


S | Name                 | Type    | Version                    | Arch   | Repository          
--+----------------------+---------+----------------------------+--------+---------------------
i | VirtualBox-4.3       | package | 4.3.16_95972_openSUSE123-1 | x86_64 | Oracle_VirtualBox   
i | gcc                  | package | 4.8-2.1.2                  | x86_64 | openSUSE-13.1-Oss   
i | gcc48                | package | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss   
i | kernel-default       | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update
i | kernel-default       | package | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update
i | kernel-default-devel | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update
i | kernel-default-devel | package | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update
i | kernel-desktop       | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update
i | kernel-desktop       | package | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update
i | kernel-desktop-devel | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update
i | kernel-desktop-devel | package | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update
i | kernel-devel         | package | 3.11.10-21.1               | noarch | openSUSE-13.1-Update
i | kernel-devel         | package | 3.11.10-17.2               | noarch | openSUSE-13.1-Update
i | kernel-firmware      | package | 20130714git-2.21.1         | noarch | openSUSE-13.1-Update
i | kernel-source        | package | 3.11.10-21.1               | noarch | openSUSE-13.1-Update
i | kernel-source        | package | 3.11.10-17.2               | noarch | openSUSE-13.1-Update
i | kernel-syms          | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update
i | kernel-syms          | package | 3.11.10-17.1               | x86_64 | openSUSE-13.1-Update
i | kernel-xen-devel     | package | 3.11.10-21.1               | x86_64 | openSUSE-13.1-Update                                                                                                
i | kernel-xen-devel     | package | 3.11.10-17.2               | x86_64 | openSUSE-13.1-Update                                                                                                
i | libgcc_s1            | package | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss                                                                                                   
i | libgcc_s1-32bit      | package | 4.8.1_20130909-3.2.1       | x86_64 | openSUSE-13.1-Oss                                                                                                   
i | make                 | package | 3.82-160.2.1               | x86_64 | openSUSE-13.1-Oss                                                                                                   
i | makedev              | package | 2.6-560.1.2                | noarch | openSUSE-13.1-Oss                                                                                                   
i | nfs-kernel-server    | package | 1.2.8-4.13.1               | x86_64 | openSUSE-13.1-Update

And STILL, the system freezes (mouse no move nor effect; keyboard no effect; can not do CTL+ALT+F1) and I must use reset button to reboot, so the situation seems unchangedA

Just one wild-out-of-left-field suggestion…

Could your input focus be in your VM?
ie. Press the RT-CTL key to release the mouse from the Guest.

If not, maybe after so many mis-steps your system could be messed up considerably… It’s a natural result when installing apps from source, you may not be able to remove them completely. If this is the case…

  1. First option is to consider a re-install (or new side by side install if you have plenty of space). Start with a clean slate. If you don’t have a lot of custom settings and install, this might be the easiest and most certain way to go.

  2. Continue to attempt to repair. It could be difficult to ferret out all the existing Virtualbox (and maybe other) files from every possible source. A start might be to first uninstall using zypper to remove the managed files, then do a search for anything with a virtualbox name. But, that still might not identify every possible file that might cause a problem.

  3. An experimental approach would be to install Docker, a Desktop (if you don’t want to experiment with a GUI-less virtualbox), and virtualbox. This is somewhat similar to a side by side install and could work because Docker is isolation and not emulation. Be forewarned though, I’ve been trying to setup an easy to use Docker/openSUSE/Desktop for a week now and am still working through a number of issues.

I’m sure without mis-steps, a clean install should be no problem.

HTH,
TSU

The keyboard is also frozen solid - RIGHT-CTL does NOTHING, whether with or without an added function

I have certainly considered that VirtualBox is really messed up and confused, and short of a complete reinstall, I may not be able to get VB to work properly
I don’t think this particular “oddity” has anything to do with my VB issues but:


ls: cannot access var/run/user/1000/gvfs: Permission deniedtotal 0
d????????? ? ?    ?      ?            ? gvfs

I have never seen a file/directory that seems to be as buggered up as that

I have room, but I have been using this machine since early Summer, and avoided adding VirtualBox until recently - the system has loads of “custom settings”… I have actually considered going back to Debian (I still have the disk image from before the install of openSUSE) but that poses a whole different set of rather scary issues

I have used zypper to remove VirtualBox from both the Oracle and openSUSE repositories, as suggested by Sauerland, and searched for files related before installing from the Oracle repository

Since I have been mis-stepping all over the lot with this VirtualBox mess, I think I’ll pass… I know ZERO about Docker, and given your forewarning, I think I am better off either sneaker-netting to my wife’s Windows 7 machine when I have no other alternative, or diving back into Debian where I lived happily amongst the Gnomes, Sarge, Etch, Squeeze, and Wheezy

For a totally off the wall approach, what if I were to uninstall VirtualBox, as suggested, and install either Xen or KVM - I can convert my virtual images, so that wouldn’t be an issue, but I know ZERO about either (hence the subject of my original post - I half expected someone to suggest a change to either Xen or KVM)

I highly endorse KVM, it may require a slight change of perspective…

Apps like Virtualbox, VMware Workstation/Player, etc are generally designed more as desktop applications whereas KVM (with libvirt) would be considered more of a Production type deployment. This doesn’t mean that you can’t or shouldn’t use KVM as a desktop app, it’s just that some things may not be as obvious or automatic as Virtualbox.

You shouldn’t run into any contention or re-occurring problems related to your Virtualbox experience, AFAIK <all> libraries and app files are completely different.

As others have posted elsewhere, use the YAST “Install virtualization” applet and choose the KVM option to get best results, followed up by an immediate “zypper up.” Do <not> enable the Virtualization repo, the packages from the standard repos are more stable and known to be problem-free…

When completed, you should see a “vm manager” menu option to manage running vms and create/configure virtual networks using Linux Bridge Devices.

You should also find 2 different apps for creating Guests,

  • From vm manager’s menu you can invoke “vm intall”
  • From the desktop menu(there are other ways, too) you can invoke virt-install.

Both apps will create Guests just fine, but you may find one or the other offers choices the other doesn’t.

Good Luck,
TSU

On 10/03/2014 02:16 PM, w4kh wrote:
>
> tsu2;2667684 Wrote:
>> Just one wild-out-of-left-field suggestion…
>>
>> Could your input focus be in your VM?
>> ie. Press the RT-CTL key to release the mouse from the Guest.
>
> The keyboard is also frozen solid - RIGHT-CTL does NOTHING, whether with
> or without an added function
>
> tsu2;2667684 Wrote:
>> If not, maybe after so many mis-steps your system could be messed up
>> considerably… It’s a natural result when installing apps from source,
>> you may not be able to remove them completely. If this is the case…
>
> I have certainly considered that VirtualBox is really messed up and
> confused, and short of a complete reinstall, I may not be able to get VB
> to work properly
> I don’t think this particular “oddity” has anything to do with my VB
> issues but:
>
> Code:
> --------------------
>
> ls: cannot access var/run/user/1000/gvfs: Permission deniedtotal 0
> d??? ? ? ? ? ? gvfs
>
> --------------------
>
> I have never seen a file/directory that seems to be as buggered up as
> that
>

That is not a file it is a directory that is created/used by Gnome. gvfs
stands for Gnome Virtual File System.

Ken

Which begs several questions: why in the world would there be a directory there when I never installed Gnome? Why is the directory showing permissions “???” ? Why are owner and group also “?” ? and, why can not root remove or update any part of it, let alone get near it? Even a “find” command that crosses the /var/run/user/1000 directories gets the same “Permission Denied”…

On Sun 05 Oct 2014 12:16:02 AM CDT, w4kh wrote:

kensch;2667874 Wrote:
>
> On 10/03/2014 02:16 PM, w4kh wrote:
> >
> > ls: cannot access var/run/user/1000/gvfs: Permission deniedtotal
> > 0 d??? ? ? ? ? ? gvfs
> >
> > --------------------
> >
> > I have never seen a file/directory that seems to be as buggered up
> > as that
> >
>
> That is not a file it is a directory that is created/used by Gnome.
> gvfs stands for Gnome Virtual File System.
>
> Ken

Which begs several questions: why in the world would there be a
directory there when I never installed Gnome? Why is the directory
showing permissions “???” ? Why are owner and group also “?” ? and,
why can not root remove or update any part of it, let alone get near it?
Even a “find” command that crosses the /var/run/user/1000 directories
gets the same “Permission Denied”…

Hi
It’s GIO, not GNOME;

gvfs - GIO virtual file system. GIO provides a VFS API to GLib
applications.


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

On 10/04/2014 09:06 PM, malcolmlewis wrote:
>

> On Sun 05 Oct 2014 12:16:02 AM CDT, w4kh wrote:
>
>
> kensch;2667874 Wrote:
>>
>> On 10/03/2014 02:16 PM, w4kh wrote:
>>>
>>> ls: cannot access var/run/user/1000/gvfs: Permission deniedtotal
>>> 0 d??? ? ? ? ? ? gvfs
>>>
>>> --------------------
>>>
>>> I have never seen a file/directory that seems to be as buggered up
>>> as that
>>>
>>
>> That is not a file it is a directory that is created/used by Gnome.
>> gvfs stands for Gnome Virtual File System.
>>
>> Ken
>
> Which begs several questions: why in the world would there be a
> directory there when I never installed Gnome? Why is the directory
> showing permissions “???” ? Why are owner and group also “?” ? and,
> why can not root remove or update any part of it, let alone get near it?
> Even a “find” command that crosses the /var/run/user/1000 directories
> gets the same “Permission Denied”…
>
>
>
>

> Hi
> It’s GIO, not GNOME;
>
> gvfs - GIO virtual file system. GIO provides a VFS API to GLib
> applications.
>
>

My bad, sorry.
I usually just delete the package gvfs. Any package that wants to hide
it’s contents in a directory in ~ makes me think it is spying on me.

Ken

On 2014-10-05 14:42, Ken Schneider wrote:

> My bad, sorry.
> I usually just delete the package gvfs. Any package that wants to hide
> it’s contents in a directory in ~ makes me think it is spying on me.

It does not hide its contents from you. It hides them from others’
prying eyes, to protect /your/ privacy.

cer@Telcontar:~> l .gvfs/
total 40
drwx------ 2 cer users 4096 May 29 2010 ./
drwxr-x— 177 cer users 36864 Oct 5 03:43 …/
cer@Telcontar:~>

As you see, the permissions display correctly.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

On 10/05/2014 09:25 AM, Carlos E. R. wrote:
> On 2014-10-05 14:42, Ken Schneider wrote:
>
>> My bad, sorry.
>> I usually just delete the package gvfs. Any package that wants to hide
>> it’s contents in a directory in ~ makes me think it is spying on me.
>
> It does not hide its contents from you. It hides them from others’
> prying eyes, to protect /your/ privacy.
>
> cer@Telcontar:~> l .gvfs/
> total 40
> drwx------ 2 cer users 4096 May 29 2010 ./
> drwxr-x— 177 cer users 36864 Oct 5 03:43 …/
> cer@Telcontar:~>
>
> As you see, the permissions display correctly.
>

Which is why your home folder (~) should be 700 (rwx------) and NOT 755
(rwxr-xr-x) which will keep prying eyes out.
But that has been debated before and I sahll not start again.

Ken

Carlos… the directory/file or whatever I am seeing is NOT in my home directory, and it is NOT a “hidden” file

l /var/run/user/1000ls: cannot access /var/run/user/1000/gvfs: Permission denied
total 0
lrwxrwxrwx 1 root root  17 Oct  3 15:07 X11-display -> /tmp/.X11-unix/X0
drwx------ 2 jack users 60 Oct  3 15:07 dconf
d????????? ? ?    ?      ?            ? gvfs
drwx------ 2 jack users 80 Oct  3 15:08 pulse
drwxr-xr-x 2 jack users 60 Oct  3 15:07 systemd

Note the lack of a leading “.” and the absolute path - I have NO such file/directory, hidden or not in /home/jack
So, if root can not get at the directory/file because of the weird permissions and ownership, what is this “thing” doing and why do I need it (or get rid of it)???
As root:


chown root:root gvfs
chown: cannot access ‘gvfs’: Permission denied

chmod 755 gvfs
chmod: cannot access ‘gvfs’: Permission denied

lsattr -d gvfs
lsattr: Permission denied while trying to stat gvfs

rm -r gvfs
rm: cannot remove ‘gvfs’: Is a directory

What is this thing’s “Krytonite”?

As Carlos wrote, try as user:

wolfi@amiga:~> id -u
500
wolfi@amiga:~> ls -l /run/user/500/
total 0
dr-x------ 2 wolfi users  0 Oct  6 11:37 gvfs
drwx------ 2 wolfi users 40 Oct  6 13:24 icedteaplugin-wolfi-S3ybl3
drwx------ 2 wolfi users 40 Oct  6 11:36 pulse
drwxr-xr-x 2 wolfi users 60 Oct  6 11:35 systemd
lrwxrwxrwx 1 root  root  17 Oct  6 11:35 X11-display -> /tmp/.X11-unix/X0
wolfi@amiga:~> ls -l /run/user/500/gvfs/
total 0

BUT:


wolfi@amiga:~> sudo ls -l /run/user/500/
ls: cannot access /run/user/500/gvfs: Permission denied
total 0
lrwxrwxrwx 1 root  root  17 Oct  6 11:35 X11-display -> /tmp/.X11-unix/X0
d????????? ? ?     ?      ?            ? gvfs
drwx------ 2 wolfi users 40 Oct  6 13:24 icedteaplugin-wolfi-S3ybl3
drwx------ 2 wolfi users 40 Oct  6 11:36 pulse
drwxr-xr-x 2 wolfi users 60 Oct  6 11:35 systemd
wolfi@amiga:~> sudo ls -l /run/user/500/gvfs/
ls: cannot access /run/user/500/gvfs/: Permission denied


Btw, this is a mount point used by gvfs:

wolfi@amiga:~> mount | grep gvfs
gvfsd-fuse on /run/user/500/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=500,group_id=100)
gvfsd-fuse on /var/run/user/500/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=500,group_id=100)

I think in earlier versions ~/.gvfs was used instead for the same thing.

On Mon 06 Oct 2014 02:36:01 PM CDT, w4kh wrote:

robin_listas;2668002 Wrote:
>
> It does not hide its contents from you. It hides them from others’
> prying eyes, to protect /your/ privacy.
>
> cer@Telcontar:~> l .gvfs/
> total 40
> drwx------ 2 cer users 4096 May 29 2010 ./
> drwxr-x— 177 cer users 36864 Oct 5 03:43 …/
> cer@Telcontar:~>
>
> As you see, the permissions display correctly.
>

Carlos… the directory/file or whatever I am seeing is NOT in my home
directory, and it is NOT a “hidden” file

Code:

l /var/run/user/1000ls: cannot access /var/run/user/1000/gvfs:
Permission denied total 0
lrwxrwxrwx 1 root root 17 Oct 3 15:07 X11-display
-> /tmp/.X11-unix/X0 drwx------ 2 jack users 60 Oct 3 15:07 dconf
d??? ? ? ? ? ? gvfs
drwx------ 2 jack users 80 Oct 3 15:08 pulse
drwxr-xr-x 2 jack users 60 Oct 3 15:07 systemd

Note the lack of a leading “.” and the absolute path - I have NO such
file/directory, hidden or not in /home/jack
So, if root can not get at the directory/file because of the weird
permissions and ownership, what is this “thing” doing and why do I need
it (or get rid of it)???
As root:

Code:

chown root:root gvfs
chown: cannot access ‘gvfs’: Permission denied

Code:

chmod 755 gvfs
chmod: cannot access ‘gvfs’: Permission denied

Code:

lsattr -d gvfs
lsattr: Permission denied while trying to stat gvfs

Code:

rm -r gvfs
rm: cannot remove ‘gvfs’: Is a directory

What is this thing’s “Krytonite”?

Hi
So you upgraded from 12.3 to 13.1?

On 13.1 my systems mount as /var/run/media/username/label your still
mounting at /var/run/user. It’s also using 1000 what is user ‘jack’
UID?


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

Those are two different things.

Udisks2 mounts things like external USB media, CD/DVDs, and so on to /var/run/media/username.
But gvfs is mounted to /var/run/user/uid/ on 13.1. And as I mentioned, in earlier versions it has been mounted to ~/.gvfs I think.