-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: Cannot dynamically attach #5
Comments
I was never able to fully get rid on this type of errors in the network qubes installer. It happens because sometimes qubes are extremely slow to start in the first few runs. Suggest you re-run the installer, usually it helps. On slower machines (I'm talking m3-Y70) I have to re-run the installer 3-4 times to succeed. As for e2fsprogs, this was wrong for me to assume everyone has it installed. This commit fixes it. |
I found the reason. I have no wireless, only ethernet. And Sys-net is running with the pci attached. It needs to be stopped befor core-net starts. I added this lines to 2.Network/install.sh after line 456 message "SETTING DEFAULT NETVM, CLOCKVM AND UPDATEVM" |
Thanks, the proposed fix looks helpful. I pushed a commit with these extra 2 lines. Can you elaborate on why you need to run uninstall.sh? Because you'r left with a system without properly set default netvm? BTW, I changed default uninstall editor to nano as well. |
With this extra 2 lines, it works. But before, it stops with the message error: no such property netvm. |
I prefere vi over nano. Have you checked the sgdisk man. |
Can you check if you have $EDITOR or $VISUAL set? Unset for me :( I can easily use $EDITOR or $VISUAL if set and default to vim otherwise. Switching to sgdisk requires a proper testing, that's a longish excersise. |
This is something I can't quite get to the bottom of, as I'm getting the same issue sometimes. Every vm has netvm property, I can't quite understand how it can not exist. Will investigate...
I'll make a setting for this :)
Try '$HOME/bin/lq-xterm core-net' or '~/bin/lq-connect' from dom0, both should work.
That's the downside of not having xorg running in every qube, you lose standard applets. I'll make an alternative applet (network, tor, sound, vpn printing) fol liteqube, but not a priority ATM. And if you are wondering how I live without these applets currently, I have a nice awesome vm setup that works around this by creating alternative applets. But I can't recommend all liteqube users to install awesome vm :( |
Can you share your awesome config. I just changed to awesome and have just the defaults. |
Seems like liteqube does nothing to enforce NetworkManager to activate a wifi connection. This means we just need to issue a proper instruction to NetworkManager at core-net start and we're good. Two ways you can achieve this:
|
I sure can, but not keen to setup a repo for this as the code isn't really ready for public consumption. Is there a way on github to share something with you privately? Otherwise I'll set up a repo an will kill it once you clone. |
Thanks for the network hints. If you set up the repo, I'll fast clone it. Thank you very much! |
I created qubes-awesome repo with my full config. Note that you need material design icons webfont from here: https://materialdesignicons.com/ |
Thank you very much! |
I got this error during installation. I had also to install e2fsprogs by hand.

The text was updated successfully, but these errors were encountered: