Re: [qubes-users] Error installing Debian-12 template
+1 Same problem here. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d44e2700-5ba2-0cec-6725-3aad2ee3433d%40riseup.net.
Re: [qubes-users] dependency problem after upgrading standalone debian 11 VM
When creating a backup while the broken VM was still running I noticed the text saying that the VM backup will contain the VM's state before it booted, which was a perfect solution to revert everything I did since the VM started. This should solve my problem by restoring that newly created backup. thank you anyway for your help! -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/771c3d49-f3e7-3862-1e97-27b92d76225c%40riseup.net.
Re: [qubes-users] dependency problem after upgrading standalone debian 11 VM
Hi unman, I'd probably be rolling back most of your recent changes, and starting again, after making sure that I have a decent backup of the qube in its current state. You need to roll back those packages, and -f should work for the install. I have some old templates hanging about - if you can wait until tomorrow I'll pull one and work through the process in the morning. thanks that is very kind, I'll wait until tomorrow then. thank you! -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5c010d4a-4136-ebae-bb3e-9e96a28678c1%40riseup.net.
Re: [qubes-users] dependency problem after upgrading standalone debian 11 VM
Hi uman, thanks for your reply. 'unman' via qubes-users: Exactly this issue arose on GitHub - it is, as you say, because you did not update the qubes repository definition in timely way. You can read the issue [here](https://github.com/qubesos/qubes-issues/issues/7865) The resolution is to follow the steps in the upgrade script - courtesy of Marek: ``` The source of the problem is that in R4.1 we actually stopped shipping own duplicated xen packages, and are relying on those from official Debian repositories. But the upgrade path requires manual step because of that. The in-place R4.0 -> R4.1 upgrade tool handle that automatically, but in case of manual upgrade, see this part: https://github.com/QubesOS/qubes-dist-upgrade/blob/release4.0/scripts/upgrade-template-standalone.sh#L37-L72 ``` Yes I know about this github ticket, I mentioned in my last email, but I have the impression that these step can not be used _after_ running 'apt update; apt upgrade; apt dist-upgrade' anymore - which is the situation I'm in. Is there also a way to recover a system after the 'apt upgrade' step happened already? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/34701d44-dc66-5341-c051-1c42da8fb5e6%40riseup.net.
Re: [qubes-users] dependency problem after upgrading standalone debian 11 VM
Do you have any recommendation on how to solve this issue? I also tried: https://github.com/QubesOS/qubes-dist-upgrade/blob/release4.0/scripts/upgrade-template-standalone.sh#L37-L72 found via: https://github.com/QubesOS/qubes-issues/issues/7865#issuecomment-1407236960 but running: apt-get install --allow-downgrades -y \ 'xen-utils-common=4.14*' \ 'libxenstore3.0=4.14*' \ 'xenstore-utils=4.14*' fails because I did run 'apt upgrade; apt dist-upgrade' already: Reading package lists... Done Building dependency tree... Done Reading state information... Done Selected version '4.14.5+94-ge49571868d-1' (Debian-Security:11/stable-security [amd64]) for 'xen-utils-common' Selected version '4.14.5+94-ge49571868d-1' (Debian-Security:11/stable-security [amd64]) for 'libxenstore3.0' Selected version '4.14.5+94-ge49571868d-1' (Debian-Security:11/stable-security [amd64]) for 'xenstore-utils' You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: qubes-core-agent : Depends: xen-utils-guest but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). exit Is there a way out? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4614fb88-814a-90a8-d68a-c52782b785ce%40riseup.net.
[qubes-users] dependency problem after upgrading standalone debian 11 VM
Hello! a while ago when migrating Qubes 4.0 to Qubes 4.1 I restored a standalone debian VM (created on r4.0) on a fresh r4.1 system and did not notice that I also should replace the r4.0 repos _in_ the VM to r4.1 repos but it still worked fine. Today I replaced this line: deb [arch=amd64] https://deb.qubes-os.org/r4.0/vm bullseye main with this: deb [arch=amd64] https://deb.qubes-os.org/r4.1/vm bullseye main in the standalone VM. After an apt update apt upgrade apt dist-upgrade I'm running into this error: The following additional packages will be installed: xen-utils-guest The following NEW packages will be installed: xen-utils-guest 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 36 not fully installed or removed. Need to get 0 B/30.1 kB of archives. After this operation, 53.2 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 242630 files and directories currently installed.) Preparing to unpack .../xen-utils-guest_4.14.5-20+deb11u1_amd64.deb ... Unpacking xen-utils-guest (4.14.5-20+deb11u1) ... dpkg: error processing archive /var/cache/apt/archives/xen-utils-guest_4.14.5-20+deb11u1_amd64.deb (--unpack): trying to overwrite '/lib/systemd/system/xendriverdomain.service', which is also in package xen-utils-common 2001:4.8.5-42+deb11u1 Errors were encountered while processing: /var/cache/apt/archives/xen-utils-guest_4.14.5-20+deb11u1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Do you have any recommendation on how to solve this issue? thanks! -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4a0c67be-0d8a-662e-3c53-52bf8dcdef31%40riseup.net.
[qubes-users] U2F Proxy Support for OpenSSH / python-fido2
Hello! the U2F proxy supports browsers according to the documentation: https://www.qubes-os.org/doc/u2f-proxy/ Approximately how far in the future will it support ssh as well? Github issues: https://github.com/QubesOS/qubes-issues/issues/6480 https://github.com/QubesOS/qubes-issues/issues/5501 thanks! -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cf0ce96b-242b-e6f0-378e-dad44bae3679%40riseup.net.
Re: [qubes-users] debian 10 VM: "Unable to init server: Could not connect: Connection refused."
solved: the disk of the template was full -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a354f75a-4aea-302a-8100-8b2637586263%40riseup.net.
[qubes-users] debian 10 VM: "Unable to init server: Could not connect: Connection refused."
Hi, Since today I'm unable to start any GUI application (testing with gnome-terminal and xterm) within a debian 10 based AppVM: In Qubes Manager the VM shows the green state icon. To collect logs I connected via 'xl console': sudo xl console debian-10: journalctl -f Log output: qrexec-agent[599]: executed user:QUBESRPC qubes.VMShell dom0 pid 24766 qrexec-agent[24766]: pam_unix(qrexec:session): session opened for user user by (uid=0) systemd[1]: Started Session c17 of user user. qubes.VMShell-dom0[24775]: .[0;1;39m.[0;1;31m.[0;1;39mUnable to init server: Could not connect: Connection refused.[0m qrexec-agent[24766]: pam_unix(qrexec:session): session closed for user user qrexec-agent[599]: send exit code 1 qrexec-agent[599]: pid 24766 exited with 1 qrexec-agent[599]: eintr systemd[1]: session-c17.scope: Succeeded. The last updates according to /var/log/apt/history.log within that VM: Start-Date: 2021-02-01 Commandline: /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef dist-upgrade Install: linux-headers-4.19.0-14-amd64:amd64 (4.19.171-2, automatic), linux-headers-4.19.0-14-common:amd64 (4.19.171-2, automatic), linux-image-4.19.0-14-amd64:amd64 (4.19.171-2, automatic) Upgrade: linux-libc-dev:amd64 (4.19.160-2, 4.19.171-2), linux-compiler-gcc-8-x86:amd64 (4.19.160-2, 4.19.171-2), linux-image-amd64:amd64 (4.19+105+deb10u8, 4.19+105+deb10u9), linux-headers-amd64:amd64 (4.19+105+deb10u8, 4.19+105+deb10u9), lightning:amd64 (1:78.6.0-1~deb10u1, 1:78.7.0-1~deb10u1), thunderbird:amd64 (1:78.6.0-1~deb10u1, 1:78.7.0-1~deb10u1), linux-kbuild-4.19:amd64 (4.19.160-2, 4.19.171-2) Any help to further debug or solve this issue is greatly appreciated. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a481cfc2-248d-b408-8650-babcb09bf4c6%40riseup.net.
[qubes-users] update error: Jinja variable 'dict object' has no attribute 'os'
Hi, I see the following error in the Qubes Update widget window after attempting to upgrade a Fedora 32 template: Rendering SLS 'base:update.qubes-vm' failed: Jinja variable 'dict object' has no attribute 'os' I switched the dvm template to fedora 32 as described in: https://www.qubes-os.org/news/2020/06/30/fedora-32-templates-available/ https://www.qubes-os.org/doc/templates/#switching I was not able to find an open issue about this on GH https://github.com/QubesOS/qubes-issues/issues Do you see the same error? thanks! -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f03e5a68-5ed7-0f2e-236f-c12ec617c766%40riseup.net.
Re: [qubes-users] Is Qubes Split GPG safe?
> As was pointed out in qubes-issues, this isn't the private key - it's a > key pair that Enigmail creates for some purpose. It cant be used to > encrypt/decrypt messages that use *your* key-pair. > There is no problem here. I'm glad my understanding of the setup is still valid then. Would be nice for other people if you could link to that said issue. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dff946f7-b461-02c4-9710-c09b0041185c%40riseup.net.
Re: [qubes-users] Is Qubes Split GPG safe?
Claudio Chinicz wrote: > All the idea behind this is to keep your keys in a safe place (VM > without network), isolated from your application VM. > > I've installed the work-gpg (keys vault) and created a mail VM with > Thunderbird and Enigmail. > > While Enigmail cannot create new keys on the vault (I have to > manually import them), it allows me to download/copy the contents of > my keys (private). > > So, if my mail VM is compromised my keys may be stolen/used > regardless of my keys being kept in a vault! > > So, what's the purpose of split gpg? The private keys should never touch the online VM running thunderbird. The keys should be generated on the offline VM and the only way to perform operations that require the private key must be via the split GPG setup. If you generated the key on the online VM it is probably best to start with a new one if you would like to get the benefit of the split GPG setup of Qubes. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1be27134-6fa7-75eb-69e8-2e2047734116%40riseup.net.
Re: [qubes-users] debian-10-minimal: no IP addresses on interfaces?
> Did you follow the advice in > https://www.qubes-os.org/doc/templates/debian-minimal ? Thanks for the pointer, now I run into this issue: apt install qubes-core-agent-networking results in: The following packages have unmet dependencies: qubes-core-agent-networking : Depends: qubes-core-agent (= 4.0.46-1+deb10u1) but 4.0.47-1+deb10u1 is to be installed E: Unable to correct problems, youhave held broken packages. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6a30bf09-1d56-63c1-bbea-8e31d27c80e1%40riseup.net.
[qubes-users] debian-10-minimal: no IP addresses on interfaces?
Hello! I installed the debian-10-minimal template from the itl-testing repository and used it for a proxyVM. When starting the appVM that uses the debian-10-minimal based proxyVM. The proxyVM gets the usual interfaces eth0 + vif.. but none of these interfaces have an IP address assigned and are in state DOWN. This issues does not occur when using the debian-10 (non minimal) version. Is this a known limitation of the minimal version? thanks! -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a6c66f59-e132-8404-d58a-5f5bb868cff3%40riseup.net.
Re: [qubes-users] dom0 updates not visible?
qubes-li...@riseup.net: > Hi, > > I fear I have an issue with dom0 updates. > > I noticed that there is a newer release > for > qubes-mgmt-salt-dom0-virtual-machines (4.0.16) > > but I still have: > > qubes-mgmt-salt-dom0-virtual-machines-4.0.15-1.fc25.noarch Just to verify: Do others have v4.0.16 installed for the package qubes-mgmt-salt-dom0-virtual-machines on your R4.0 systems without testing repos enabled? -- 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/8d44f9b2-68f0-7660-c7f9-032ec0434e28%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] dom0 updates not visible?
unman: > On Sun, Jul 07, 2019 at 01:40:00PM +, qubes-li...@riseup.net wrote: >> Hi, >> >> I fear I have an issue with dom0 updates. >> >> I noticed that there is a newer release >> for >> qubes-mgmt-salt-dom0-virtual-machines (4.0.16) >> >> but I still have: >> >> qubes-mgmt-salt-dom0-virtual-machines-4.0.15-1.fc25.noarch > > This is, unfortunately, a known issue. > You can manually install the "SKIPPED" packages by using dnf install. > Your "dnf clean all" has scuppered that. > Just try the update again, and if the same packages are downloaded, just > install them yourself. but the relevant package qubes-mgmt-salt-dom0-virtual-machines is not even listed as skipped. -- 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/0b956717-f232-bf99-2042-4fadc0be7e33%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] dom0 updates not visible?
Hi, I fear I have an issue with dom0 updates. I noticed that there is a newer release for qubes-mgmt-salt-dom0-virtual-machines (4.0.16) but I still have: qubes-mgmt-salt-dom0-virtual-machines-4.0.15-1.fc25.noarch An update in dom0 doesn't install the update: sudo qubes-dom0-update Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Last metadata expiration check: 0:35:59 ago on Sun Jul 7 14:57:27 2019. Dependencies resolved. Package Arch Version Repository Size Reinstalling: anaconda-corex86_64 1000:25.20.9-14.fc25 qubes-dom0-current 1.5 M anaconda-gui x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 386 k anaconda-tui x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 186 k anaconda-widgets x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 119 k garcon x86_64 1000:0.5.0-1.fc25 qubes-dom0-current 179 k python3-blivet noarch 2:2.1.6-5.fc25qubes-dom0-current 1.0 M python3-kickstartnoarch 1000:2.32-4.fc25 qubes-dom0-current 370 k qubes-anaconda-addon noarch 4.0.9-1.fc25 qubes-dom0-current 34 k xfwm4x86_64 1000:4.12.4-1.fc25qubes-dom0-current 636 k xorg-x11-drv-ati x86_64 18.0.1-1.fc25 qubes-dom0-current 168 k xorg-x11-drv-intel x86_64 2.99.917-32.20171025.fc25 qubes-dom0-current 696 k Transaction Summary Total size: 5.1 M Installed size: 19 M DNF will only download packages for the transaction. Downloading Packages: [SKIPPED] anaconda-core-25.20.9-14.fc25.x86_64.rpm: Already downloaded [SKIPPED] anaconda-gui-25.20.9-14.fc25.x86_64.rpm: Already downloaded [SKIPPED] anaconda-tui-25.20.9-14.fc25.x86_64.rpm: Already downloaded [SKIPPED] anaconda-widgets-25.20.9-14.fc25.x86_64.rpm: Already downloaded [SKIPPED] garcon-0.5.0-1.fc25.x86_64.rpm: Already downloaded [SKIPPED] python3-blivet-2.1.6-5.fc25.noarch.rpm: Already downloaded [SKIPPED] python3-kickstart-2.32-4.fc25.noarch.rpm: Already downloaded [SKIPPED] qubes-anaconda-addon-4.0.9-1.fc25.noarch.rpm: Already downloaded [SKIPPED] xfwm4-4.12.4-1.fc25.x86_64.rpm: Already downloaded [SKIPPED] xorg-x11-drv-ati-18.0.1-1.fc25.x86_64.rpm: Already downloaded [SKIPPED] xorg-x11-drv-intel-2.99.917-32.20171025.fc25.x86_64.rpm: Already downloaded Complete! The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Qubes OS Repository for Dom0 I don't use the testing/unstable dom0 repos, just current. I'm using sys-firewall (fedora-30) as update VM. I also tried sudo dnf clean all using Qubes R4.0 Do you have recommendations on how to debug this? thanks! -- 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/efc3bf7b-fd76-32df-b2ed-1f4fe78154d4%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] unable to use USB ports with R4.0.1-rc1 on X1 Carbon 6th
Hi, do you have any debugging hints to get USB ports working either in sys-usb or in dom0 on an X1 carbon 6th generation? the default sys-usb config does not work (usb functionality not available in VM) then I tried to get it to work in dom0 by unassigning the devices from the sys-usb VM and rebooting but with no success. I updated to the bios version 1.34 released in November 2018. thanks! -- 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/b5da53fb-7d5c-f867-19ce-940efb4c70c3%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] dispvm at 100% after starting (basically freezing)
Hi, lately my dispvm (Qubes 3.2) are frequently reaching 100% immediately after starting and basically freezing. dispvm based on f28 template. top shows the following to tasks in the running state: ksoftirqd/0 rcu_sched load: >12 does anyone else observe this or similar issues? -- 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/dba632dd-539e-2b79-4911-6ba374beefe9%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] DispVM broken in 3.2? (xen-4.6.6-37)
I used the following commands in dom0 to restore dispVM functionality: qubes-dom0-update xen-libs-4.6.6-36.fc23.x86_64 xen-hypervisor-4.6.6-36.fc23.x86_64 xen-runtime-4.6.6-36.fc23.x86_64 xen-hvm-4.6.6-36.fc23.x86_64 xen-4.6.6-36.fc23.x86_64 xen-license-4.6.6-36.fc23.x86_64 dnf downgrade xen-libs-4.6.6-36.fc23.x86_64 xen-hypervisor-4.6.6-36.fc23.x86_64 xen-runtime-4.6.6-36.fc23.x86_64 xen-hvm-4.6.6-36.fc23.x86_64 xen-4.6.6-36.fc23.x86_64 xen-license-4.6.6-36.fc23.x86_64 (downgrading the packages in the template was not necessary) -- 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/f0a7a149-c5ed-c234-89ab-6ca26457f0d1%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] DispVM broken in 3.2?
What would be the step to downgrade to the previous version to get dispVMs working again? qubes-dom0-update --action=downgrade xen something like this or is it necessary to specify all packets individually? >>> >>> Depending on how attached you are to Fedora, you might want to temporarily >>> try the Debian template instead of downgrading Xen? >> >> >> I get the same error after switching to debian-9 as the dispVM template. >> >> So switching to debian-9 for dispVM is unfortunately _not_ a possible >> workaround for this. > > You're using Testing arent you? Yes, to be precise: qubes-dom0-current-testing is _not_ enabled. qubes-dom0-security-testing _is_ enabled. > You could downgrade to the 36 version of xen-libs and runtime etc. That > should fix your problem until 6-38 is released What would be the recommended way of downgrading? (and wouldn't it be better to revert all packages of the given upgrade?) qubes-dom0-update --action=downgrade xen-libs xen-runtime xen-hvm Maybe lets add generic downgrade instructions for such cases (dom0) to the documentation? -- 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/720d2245-2082-d12e-2d79-7abbe485b90c%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] unexpected hard reboot on xen-4.6.6-37 (in security-testing repo)
Hi, this is just a warning for those that have qubes-dom0-security-testing enabled and did not upgrade yet. Besides breaking dispVM functionality [1] I also had a strange unexpected hard reboot since I upgraded to xen-4.6.6-37. I don't know the root cause of the reboot but it _might_ be related to the xen update. So if you enabled the dom0 security-testing repo you might want to avoid upgrading just yet. [1] https://github.com/QubesOS/qubes-issues/issues/3711 -- 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/6fa1fbd5-17d4-364a-b805-8a4993280f15%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] DispVM broken in 3.2?
awokd: > On Sat, March 17, 2018 7:57 pm, qubes-li...@riseup.net wrote: > >> What would be the step to downgrade to the previous version to >> get dispVMs working again? >> >> qubes-dom0-update --action=downgrade xen something like this or is it >> necessary to specify all packets individually? > > Depending on how attached you are to Fedora, you might want to temporarily > try the Debian template instead of downgrading Xen? I get the same error after switching to debian-9 as the dispVM template. So switching to debian-9 for dispVM is unfortunately _not_ a possible workaround for this. -- 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/0f840e7d-5614-5db5-5338-33f436c84fc0%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] DispVM broken in 3.2?
Andrew David Wong: > On 2018-03-17 11:40, qubes-li...@riseup.net wrote: > >>> Have you made sure that you have updated the packages in the >>> template and regenerated the DispVM? That's a common source of >>> these problems and fixed it for me. > >> Yes I've updated and regenerated the dispvm after the dom0 update. > > > Same here. Updating and regenerating did not resolve the issue. > Tracking: > > https://github.com/QubesOS/qubes-issues/issues/3711 thank you for filing it on gh! Assuming the latest updates introduced this regression: What would be the step to downgrade to the previous version to get dispVMs working again? qubes-dom0-update --action=downgrade xen something like this or is it necessary to specify all packets individually? -- 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/1379ed33-c305-a7fd-77ea-d1ccfb3023a8%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] DispVM broken in 3.2?
> Have you made sure that you have updated the packages in the template > and regenerated the DispVM? > That's a common source of these problems and fixed it for me. Yes I've updated and regenerated the dispvm after the dom0 update. -- 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/ce5666fd-bf86-f2f0-25c7-7b0ce3fb9758%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] DispVM broken in 3.2?
DispVM functionality does no longer work for me in Q3.2 since yesterday.
First I assumed the template is broken but after reinstalling the fedora-26
template
from the rpm repo and recreating the DVM I get the very same error.
Has anyone else the same problem after installing the latest dom0 updates?
from the dom0 yum.log the latest installed updates were (2018-03-15):
libgcc-5.3.1-6.qubes1.fc23.x86_64
2001:xen-licenses-4.6.6-37.fc23.x86_64
2001:xen-libs-4.6.6-37.fc23.x86_64
2001:xen-hypervisor-4.6.6-37.fc23.x86_64
2001:xen-runtime-4.6.6-37.fc23.x86_64
libstdc++-5.3.1-6.qubes1.fc23.x86_64
2001:xen-hvm-4.6.6-37.fc23.x86_64
2001:xen-4.6.6-37.fc23.x86_64
qubes-gpg-split-dom0-2.0.28-1.fc23.x86_64
libgomp-5.3.1-6.qubes1.fc23.x86_64
I also tried a reboot but that did not change anything either.
This is the error I get when trying to start xterm (or anything else) in a
DispVM:
echo xterm| /usr/lib/qubes/qfile-daemon-dvm qubes.VMShell dom0 DEFAULT red
time=1521287074.5, qfile-daemon-dvm init
time=1521287074.51, creating DispVM
time=1521287075.04, collection loaded
time=1521287075.05, VM created
time=1521287075.06, VM starting
time=1521287075.06, creating config file
time=1521287075.06, calling restore
Traceback (most recent call last):
File "/usr/lib/qubes/qfile-daemon-dvm", line 217, in
main()
File "/usr/lib/qubes/qfile-daemon-dvm", line 205, in main
dispvm = qfile.get_dvm()
File "/usr/lib/qubes/qfile-daemon-dvm", line 167, in get_dvm
return self.do_get_dvm()
File "/usr/lib/qubes/qfile-daemon-dvm", line 103, in do_get_dvm
dispvm.start()
File
"/usr/lib64/python2.7/site-packages/qubes/modules/01QubesDisposableVm.py", line
193, in start
domain_config, libvirt.VIR_DOMAIN_SAVE_PAUSED)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4405, in
restoreFlags
if ret == -1: raise libvirtError ('virDomainRestoreFlags() failed',
conn=self)
libvirt.libvirtError: internal error: libxenlight failed to restore domain
'disp1'
--
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/70bf5c3f-2eb2-023e-0944-1a3d1d31d47f%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
