Package Details: cros-container-guest-tools-git r157.5a5206c-1

Git Clone URL: (read-only)
Package Base: cros-container-guest-tools-git
Description: Guest tools for the Crostini containers on ChromeOS
Upstream URL:
Keywords: chromeos containers lxc
Licenses: custom
Submitter: ava1ar
Maintainer: ava1ar
Last Packager: ava1ar
Votes: 4
Popularity: 0.307554
First Submitted: 2018-05-23 06:53
Last Updated: 2019-06-08 15:59

Latest Comments

1 2 Next › Last »

ava1ar commented on 2019-07-14 23:05

Thanks, @mrln! I will check this out on my Pixelbook and will incorporate into this package if it works.

mrln commented on 2019-07-14 21:50

I temporarily got gpu running using a hacky trick. I'm using a HP X360 chromebook, Chrome OS 76.0.3809.38 and crostini archlinux container. The way i got it working:

Backup virtio_gpu_dri and symlink the google virtio_gpu_dri
mv /usr/lib/dri/ /usr/lib/dri/
ln -s /opt/google/cros-containers/lib/ /usr/lib/dri/
Enable gpu

Open cros shell using Ctrl+alt+t

vmc stop termina
vmc start --enable-gpu termina

Open linux terminal Run glxinfo -B, it segfaults with unknown architecture error.

Restore backup virtio_gpu_dri overwriting symlink.
mv /usr/lib/dri/ /usr/lib/dri/

Now glxinfo -B show virgil as driver. Steam games work. Oh, and somewhere during testing i had to install libc++ from aur because "LIBGL_DEBUG=verbose glxinfo" was complaining about it missing.

ava1ar commented on 2019-06-23 07:01

rawkode, Do you have GPU acceleration enabled when getting this error?

rawkode commented on 2019-06-20 13:32

sommelier-x unable to start

-- The job identifier is 472.
Jun 20 08:23:12 penguin sommelier[380]: MESA-LOADER: failed to open virtio_gpu (search paths /usr/lib64/dri)
Jun 20 08:23:12 penguin sommelier[380]: failed to load driver: virtio_gpu
Jun 20 08:23:12 penguin sommelier[380]: MESA-LOADER: failed to open kms_swrast (search paths /usr/lib64/dri)
Jun 20 08:23:12 penguin sommelier[380]: failed to load driver: kms_swrast
Jun 20 08:23:12 penguin sommelier[380]: MESA-LOADER: failed to open swrast (search paths /usr/lib64/dri)
Jun 20 08:23:12 penguin sommelier[380]: failed to load swrast driver
Jun 20 08:23:12 penguin sommelier[380]: error: couldn't get display device
Jun 20 08:23:12 penguin systemd[59]: sommelier-x@0.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support:

In-order to resolve:

 sudo pacman -S xwayland xorg-server-xwayland
 sudo cp /usr/lib64/dri/ /usr/lib64/dri/
 sudo cp /opt/google/cros-containers/lib/ /usr/lib64/dri/
 systemctl --user restart sommelier-x@0.service

ava1ar commented on 2019-06-08 16:01

Just pushed an update which should fix xxd dependency issue and also "Linux Files" with recent systemd (thanks @kitakar5525 for investigation). Please report any other issues you see.

I am currently looking into making GPU acceleration work with Arch.

kitakar5525 commented on 2019-05-29 00:22

Garcon seems incompatible with systemd 242.19-1

When I tried to mount Linux files on the Files app, I got the following error:

$ tail -f /var/log/messages
2019-05-29T08:29:17.169951+09:00 ERR vm_cicerone[6721]: Failed to set up user: failed to enable linger: Could not enable linger: Read-only file system

It seems that our issue is related to this systemd issue: - loginctl enable/disable-linger error: read-only file system · Issue #12401 · systemd/systemd

As suggested in the above issue, adding ReadWritePaths=/etc /run /var/lib/systemd/linger to /usr/lib/systemd/system/systemd-logind.service worked as a workaround for our issue, too.

(Sorry I removed my previous comment by mistake.)

jmogens commented on 2019-05-03 17:09

Garcon seems incompatible with systemd 242.19-1. Downgrading systemd to 241.93-1 fixes Chrome OS Files integration and launching from the Terminal app.

redsky17 commented on 2019-05-01 00:44

I had to downgrade systemd to version 241.7-2 in order to get garcon to work again.

seongmin commented on 2019-04-30 00:52

Hello. First of all thanks a lot for the package!

I have the same problem with @uncon. I can't seem to run vim after updating to the latest release, because of "unresolvable package conflicts" with xxd-standalone. Anyone know how to work around this?

mrln commented on 2019-04-06 09:21

On chromeos 75.0.3753.0, i had to change pkgver to r134.7dac7e9 and remove xxd-standalone from depends to get it up & running.