On Monday, January 29, 2018 at 1:06:13 PM UTC+1, ludwig jaffe wrote: > Problem after some diskfull errors: > see my post: "data panic (disc full) / want to mount nas with nfs and backup > all in /var/lib/cubes", where I managed to recover the data and to repair the > file systems. > -- > the box is up and running, but .... > -- > The Qubes-VM-Manager only shows running VMs and not all the VMs that are > there, but from the menue button one can start the shells of these VMs, > which causes the vms to be started. > > Also I can not change the disk size of private.img in the shutdown > personal vm. And maybe others. > > What happened to qubes-vm manager? > -> Disk got full and maybe, it could not write configs correncty > -> I deleted some not needed VMs by hand > rm -rf /var/lib/qubes/appvm/some_stupid_appliance in order to get space, > before I started the recovery with the nas and kali linux > > > so could be, that qubes vm manager did not like this. > > How to fix qubes vm manager?!
Now I know you're talking about Qubes 3.2. here, but this issue might possibly be related to Qubes 4. The Qubes VM Manager was originally planned to be out-phased in Qubes 4 and was supposed to become a relic of the past. But due to many people having an easier time having a visual GUI that the VM Manager provides, the Qubes developers brought it back recently in Qubes 4. However it still needs some updates and fixes before it can run a bit more smooth. So here's thhe thing. Due to limited time and busy schedules to make everything for Qubes, I suspect that some of the updates designed for Qubes 4 has also arrived and mixed in with Qubes 3.2. to some extent. For example updates in qvm-usb, updates to the Qubes-tools, and so forth. Now that doesn't mean all packages that resides on both Qubes 3.2. and Qubes 4 are equally updated. All I'm suspecting here, is that "some" might slip through to Qubes 3.2. Basically, in Qubes 4 the Qubes mechanics has become so different, that the VM-Manager will take major re-work to make it work properly again. However it's already been brought back to a state where it's useful, albeit a bit slow. But the cool thing with the Qubes 4 VM-Manager is that the window now can be re-sized, although it doesn't yet remember the previous window size, but hopefully that's fixed sometime soon. Either way, this could be a possible explanation, but I'm no expert, and this is only and merely a suspicion. Qubes 4 required a lot of work, and they're not quite done yet either. They're busy with it, and it's probably taken longer than anyone ever expected, although it has brought about some really good results so it's imho been well worth it. Thing is though, Qubes 3.2. was probably not meant to be around this long, and it might be starting to show. But that's just be postulating, there might be another possible explanation. But for what it's worth, having used Qubes 4 since RC-2, it's actually become quite stable now. If RC-4 is not out soon, then maybe upgrade to Qubes 4 RC-3? Also updates meant for RC-4 has been posted to Qubes 4 RC-3 current-testing too. Although it reamins to be seen whether a re-install is recommended between RC-3 and the yet to be released RC-4, the developers will tell us on the release day in the release news article, if any of the previous releases procedures is to go by. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cd373c07-d7c5-493e-93a0-456df31fc429%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
