On Thu, 2017-12-14 at 01:51 -0500, haaber wrote:
> Thank you both for comments. That must be a *very* slow boot, it is
> up
> for 12h now, and still no xterm available, neither via qubes-menu,
> nor
> via qvm-run in dom0 :)) Anyhow, it seems better to download the
> template.
>
> How to you get th
On Thursday, 14 December 2017 01:14:55 CET Jon Solworth wrote:
> On Tuesday, December 12, 2017 at 9:05:30 PM UTC-5, Andrew David Wong
wrote:
> > We'll announce this as soon as we can. We usually can't say
> > for certain whether an in-place upgrade will be possible until very
> > close to the stab
Hi,
will Qubes OS 3.2 work with the 8700K desktop CPU that was just released? I've
heard conflicting reports. If not, will 4.0 support it? I read that you need
Kernel 4.12 (I believe) but even Qubes 4.0 seems to be stuck with 4.8...
Is this just a matter of "perfect" support or are they talking
On 12/13/2017 07:30 PM, '[799]' via qubes-users wrote:
Hello Chris,
Original-Nachricht
An 13. Dez. 2017, 19:15, Chris Laprise schrieb
> Increased CPU usage is a known issue.
> You can see it in the 'xentop' listing.
> This may be one of the core tradeoffs
> when moving to
Another partial workaround, you can change virt_mode from hvm back to pv for
trustworthy VMs, like vault, etc...
The bug: https://github.com/QubesOS/qubes-issues/issues/2849
For me it amounts to an overhead of 10% x cpu core per hvm, according to xentop.
--
You received this message because yo
Hi,
After the last upgrade of Qubes + QubesVMs my usb mouse is not working.
If I run lsusb in sys-usb I can see the device, but apparently is not detected
as a mouse, I think.
[user@sys-usb ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 8087:8000
On Mon, 11 Dec 2017 02:45:23 -0800 (PST)
Piers Saye wrote:
> Dell XPS 15 (9560) 1TB 32GB HiRes Touchscreen
>
> 3.2 running fine with the previously documented fixes.
>
>
> When I try and install 4.0 rc3 the installer hangs often prior to
> getting to the GUI installer with a soft lock on CPU #
On Thu, Dec 14, 2017 at 09:56:23AM +0100, Johannes Graumann wrote:
> On Thu, 2017-12-14 at 01:51 -0500, haaber wrote:
> > Thank you both for comments. That must be a *very* slow boot, it is
> > up
> > for 12h now, and still no xterm available, neither via qubes-menu,
> > nor
> > via qvm-run in dom0
> I see.. But currently I am using Qubes 3.2 and 4.0 last time I tried was
> VERY unpolished, I am not sure I am going to look at it before support
> for 3.2 expires...
Same here, and my pc doesn't have vt-d nor slat (second level addres
tranlation); both required for Qubes 4
> It's not like I wo
On Thu, Dec 14, 2017 at 08:24:26AM -0800, Adrian Rocha wrote:
> Hi,
>
> After the last upgrade of Qubes + QubesVMs my usb mouse is not working.
> If I run lsusb in sys-usb I can see the device, but apparently is not
> detected as a mouse, I think.
>
> [user@sys-usb ~]$ lsusb
> Bus 001 Device 001
Hello,
it looks like I got hit by a severe problem that prevents me from starting an
appvm
I searched the bugtracker and it looks like:
https://github.com/QubesOS/qubes-issues/issues/2054
I also renamed a VM and it no longer starts.
The folder under
/var/lib/qubes/appvms/oldname
is still p
On Thu, Dec 14, 2017 at 08:59:06PM -, joonas.lehto...@openmailbox.org wrote:
> Hello,
>
> it looks like I got hit by a severe problem that prevents me from starting an
> appvm
>
>
> I searched the bugtracker and it looks like:
>
> https://github.com/QubesOS/qubes-issues/issues/2054
>
> I
> That's a wireless mouse isn't it and what you see there is the USB
> receiver? You may be right that it isn't triggering the input proxy.
>
> When you say "upgrade" do you mean that or simply "update"? I mean are
> you still running 3.2?
> What template are you using for the sys-usb? What were y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/12/2017 05:27 AM, taii...@gmx.com wrote:
> You can simply assign disable sys-usb then assign the USB
> controllers to sys-net via the VM manager. Please note that any non
> PCI-e network interface is going to be have terrible performance
> and
On Wednesday, September 13, 2017 at 7:49:35 PM UTC-3, qubester wrote:
> Fedora25 fails updates unless I reboot the machine 9.13.17
>
> 2 or 3 times now, are others having this problem? is there some
> particular remedy or just let it go?
>
> "failed to syncronize cache"
I confirme the issue
I found the problem.
When I updated the template I uninstalled Thunderbird, and the qubes-usb-proxy
and other related tools are considered unused dependencies. I think that this
is a bug in the template. I solved the issue installing the necessary packages.
$ sudo dnf remove thunderbird
Dependen
> Does anyone have an idea what the difference livecd-iso-to-disk make,
> compared to isohybrid? If possible, we'd like to installation iso work
> out of the box on UEFI systems, including new ones...
No, but I have what seems like another data point. On my Lenovo
T520 under UEFI, trying to boot
Here's a screenshot of the above-described boot error:
https://photos.google.com/photo/AF1QipMO-vL-kcyiORVEZ5P4ydjpdBJwwzzTZ00JuNm1
On Thu, Dec 14, 2017 at 10:04 PM, wrote:
> > Does anyone have an idea what the difference livecd-iso-to-disk make,
> > compared to isohybrid? If possible, we'd like
OK, here is (I hope) a *public* version of said screen shot:
https://photos.google.com/share/AF1QipMRlHUC5EOV-PQD5kfWWfCp9BDroAHDXGAFdWcq_SrmJhfhnHHOF6ZvYU7-JenLOA?key=MlJxWFRyZm1OTHBnWXpHd1pfUXNVYzJjMmJsTlRR
(Just learning Google Photo, Google+, gmail, etc., for purposes of this post.
Until now
On Thursday, November 30, 2017 at 1:30:28 AM UTC-8, quenti...@gmail.com wrote:
> Trying to create an HVM for tails 3.3 in 4.0-rc3 (upgraded from rc2).
>
> Fails on the `qvm-start HVM_tails-3_3
> --cdrom=untrusted1:/home/user/Downloads/tails.iso` step in the
> https://www.qubes-os.org/doc/tails/
20 matches
Mail list logo