Did I just brick proxmox 8 by installing libguestfs-tools?

Inlakesh

Well-Known Member
Jan 13, 2019
74
4
48
Installed libguestfs-tools on proxmox 8..0.4 cause of being able to edit qcow4 files in an easy way. After the install in proxmox gui I see this:
(did I break some functions in proxmox by installing libguestfs-tools, if so, what can I do to fix this?)


Oct 17 21:47:52 pv2 dbus-daemon[19834]: [system] Reloaded configuration
Oct 17 21:47:52 pv2 dbus-daemon[19834]: [system] Reloaded configuration
Oct 17 21:47:53 pv2 systemd[1]: Reloading.
Oct 17 21:47:54 pv2 systemd[1]: /run/systemd/transient/245.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:54 pv2 systemd[1]: /run/systemd/transient/138.scope:4: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:54 pv2 systemd[1]: /run/systemd/transient/131.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:54 pv2 systemd[1]: /run/systemd/transient/108.scope:3: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:54 pv2 systemd[1]: /run/systemd/transient/192.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:54 pv2 systemd[1]: /run/systemd/transient/194.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:54 pv2 systemd[1]: /run/systemd/transient/141.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:54 pv2 systemd[1]: /run/systemd/transient/217.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:54 pv2 systemd[1]: /run/systemd/transient/609.scope:6: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.

Oct 17 21:47:55 pv2 systemd[1]: Starting apt-daily.service - Daily apt download activities...
Oct 17 21:47:55 pv2 systemd[1]: apt-daily.service: Deactivated successfully.
Oct 17 21:47:55 pv2 systemd[1]: Finished apt-daily.service - Daily apt download activities.
Oct 17 21:47:55 pv2 groupadd[2846753]: group added to /etc/group: name=uuidd, GID=116
Oct 17 21:47:55 pv2 groupadd[2846753]: group added to /etc/gshadow: name=uuidd
Oct 17 21:47:55 pv2 groupadd[2846753]: new group: name=uuidd, GID=116
Oct 17 21:47:55 pv2 useradd[2846766]: new user: name=uuidd, UID=109, GID=116, home=/run/uuidd, shell=/usr/sbin/nologin, from=/dev/pts/3
Oct 17 21:47:55 pv2 systemd[1]: Reloading.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/245.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/138.scope:4: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/131.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/108.scope:3: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/192.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/194.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/141.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/217.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/609.scope:6: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/237.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/171.scope:4: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/167.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:56 pv2 systemd[1]: /run/systemd/transient/195.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.


Oct 17 21:47:57 pv2 systemd[1]: Reloading.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/245.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/138.scope:4: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/131.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/108.scope:3: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/192.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/194.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/141.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/217.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/609.scope:6: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/237.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/171.scope:4: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:47:58 pv2 systemd[1]: /run/systemd/transient/167.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.

Oct 17 21:48:08 pv2 systemd[1]: Reloading.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/245.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/138.scope:4: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/131.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/108.scope:3: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/192.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/194.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/141.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/217.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/609.scope:6: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/237.scope:7: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/171.scope:4: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/167.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/195.scope:8: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.
Oct 17 21:48:10 pv2 systemd[1]: /run/systemd/transient/145.scope:3: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon.

Oct 17 21:48:10 pv2 systemd[1]: mdadm-shutdown.service - Prepare mdadm shutdown initramfs was skipped because of an unmet condition check (ConditionFileIsExecutable=/usr/bin/dracut).
Oct 17 21:48:10 pv2 dbus-daemon[19834]: [system] Reloaded configuration
Oct 17 21:48:10 pv2 dbus-daemon[19834]: [system] Reloaded configuration
 
Maybe apt remove libguestfs-tools and apt install fuse (which was removed) is enough? You can then clean-up with apt autoremove, after everything works again.
 
Thanks for your inputs. Yeah, what is in the attached text file is all of the putput it gave during install.
Don't want to uninstall the package yet, appreciate any inputs tremendously.
 
That surprised me too. People who install something that needs fuse3 do get a warning about removing proxmox IIRC. I do hope the attached output was complete and I did not overlook something.
I reproduced it and it just installs it. I don't see what's not working afterwards. fuse3 has a backwards compatible programs/aliases so that every program relying on it will also work.

@Inlakesh Can you specify what is not working? Just having those systemd message is no error. At least not fuse related.
 
I reproduced it and it just installs it. I don't see what's not working afterwards. fuse3 has a backwards compatible programs/aliases so that every program relying on it will also work.

@Inlakesh Can you specify what is not working? Just having those systemd message is no error. At least not fuse related.
Thanks a lot for taking your time to reproduce it, much appreciated.

Everything is working so far, just got a bit worried about all output from proxmox GUI syslog, was thinking that if I have to restart the server in future, will these output make themself reminded and creat problems.
 
Everything is working so far, just got a bit worried about all output from proxmox GUI syslog, was thinking that if I have to restart the server in future, will these output make themself reminded and creat problems.
Linux can be a bit overwhelming for users that are not used to a lot of output in logfiles.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!