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 upda
> 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
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 dispv
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?
>
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
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
t
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
Hello!
I'm trying to upgrade a standalone Debian 11 qube from Qubes OS 4.1
to Debian 12 on Qubes OS 4.2.
I started by making a backup from the standalone on Qubes OS 4.1.
Then I restored it on a fresh Qubes OS 4.2 installation.
Inside that restored standalone I run the upgrade script:
https://
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
> 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
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 va
> 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 ni
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
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-age
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
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
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
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 inst
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
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 w
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
+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://
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 re
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 sy
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-virtu
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 ha
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 rec
27 matches
Mail list logo
