Re: [qubes-users] Running Windows from Qubes VM ?

Hi, Seems to work better even if I am still not able to boot my windows. With "fdisk" I can see that my bootable HDD is "sdc1". >From Dom0, when doing a : qvm-start vm-test --hddisk /dev/sdc1, I do have a >popup from my Windows drive. Booting from CDROM error code failaure 2 Booting

[qubes-users] Re: Qubes Manager is coming back in Qubes 4.0-rc4!

P.S. Can you please update https://www.qubes-os.org/doc/releases/4.0/schedule/ -- 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] Re: Qubes Manager is coming back in Qubes 4.0-rc4!

Great news. Thank you. I would prefer a fully functional Qubes Manager since a widget that requires mouse click or hover is a pain in the butt to keep as a running dashboard. That is what I like about the 3.2 version... that I can keep it in one of my extra monitors. Seeing CPU spikes

[qubes-users] rc3: Split-gpg + enigmail frequent "qubes.Gpg" prompts

On Qubes 4.0-rc3 I recently setup Enigmail in Thunderbird to access my Split-gpg configuration, which I was already using with git. But every time I encounter a signed message, I'm prompted by a dom0 "qubes.Gpg" dialog box as many as 4 times in a row (the back-end vm prompts me only once for the

Re: [qubes-users] Re: QSB #37: Information leaks due to processor speculative execution bugs (XSA-254, Meltdown & Sepctre)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-12 04:24, haaber wrote: >>> >>> so people saying the intel meltdown bios patch slows >>> performance. I got an increase in performance lmao. probably >>> depends on os though. >> >> but also in my particular case they also addressed

Re: [qubes-users] Qubes Manager is coming back in Qubes 4.0-rc4!

Woohoo! Thanks all! On Fri, Jan 12, 2018 at 8:57 PM, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > The Qubes VM Manager will be returning in Qubes 4.0-rc4, which is > scheduled for release next week. The returning Qubes Manager will be >

[qubes-users] Qubes Manager is coming back in Qubes 4.0-rc4!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The Qubes VM Manager will be returning in Qubes 4.0-rc4, which is scheduled for release next week. The returning Qubes Manager will be slightly different from the 3.2 version. Specifically, it will not duplicate functionality that is already

Re: [qubes-users] Qubes 4.0-rc3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-12 07:58, awokd wrote: > On Fri, January 12, 2018 1:04 pm, Tom Zander wrote: >> On Friday, 12 January 2018 11:18:19 GMT 'awokd' via qubes-users >> wrote: >> >>> Would it be of value if I went through the published Docs and >>> added

Re: [qubes-users] Qubes 4.0-rc3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-12 08:00, 'awokd' via qubes-users wrote: > On Fri, January 12, 2018 1:09 pm, Holger Levsen wrote: > >> I'm not so sure, why not use git branches? > One reason that comes to mind: Segregating the documentation into two different

Re: [qubes-users] qubes app menu keeps old templatevm entries.

> > On Qubes xfce 3.2 I had the entries in ~/.local/share/applications > and the directories in ~/.local/share/desktop-directories > > not sure if it is the right place to clean up however... It worked for me. Got rid of the old fedora-23 and debian-8 listings by doing as suggested above. ie.

Re: [qubes-users] validate IOMMU support

On 01/12/2018 06:31 AM, 'awokd' via qubes-users wrote: On Fri, January 12, 2018 8:23 am, Wim Vervoorn wrote: Hello, Thanks. I tried this. Now I am running into problems with the PCI devices I am using. Qubes can't reset those. For some reason they are not exposing the FLR capability. I am

Re: [qubes-users] Re: porting to ARM

On 01/12/2018 12:45 PM, 'awokd' via qubes-users wrote: > On Fri, January 12, 2018 8:59 am, Ph.T wrote: >> . my initial motivation for ARM was that >> intel seemed more prone to #spectre than ARM; >> https://developer.arm.com/support/security-update >> "majority of Arm processors are not impacted

Re: [qubes-users] Running Windows from Qubes VM ?

On Fri, January 12, 2018 2:53 pm, ThierryIT wrote: > Hello, > > > I am not able to use "qvm-start" because the HVM I have created is > "Empty". > Dom0 is able to see my Windows 7 hard drive: > /dev/sdc2 /run/media/user/32E...CCB type fuseblk > > > From Dom0 I am able to have access to all my

Re: [qubes-users] Running Windows from Qubes VM ?

Hello, I am not able to use "qvm-start" because the HVM I have created is "Empty". Dom0 is able to see my Windows 7 hard drive: /dev/sdc2 /run/media/user/32E...CCB type fuseblk >From Dom0 I am able to have access to all my Window 7 files. Any ideas ? Thx Le vendredi 12 janvier 2018 13:59:56

Re: [qubes-users] Qubes 4.0-rc3

On Fri, January 12, 2018 1:09 pm, Holger Levsen wrote: > I'm not so sure, why not use git branches? It doesn't sound like that's the route the Qubes team wants to take right now, but at least splitting the content on the same page would make it easier to migrate to that approach if they change

Re: [qubes-users] Qubes 4.0-rc3

On Fri, January 12, 2018 1:04 pm, Tom Zander wrote: > On Friday, 12 January 2018 11:18:19 GMT 'awokd' via qubes-users wrote: > >> Would it be of value if I went through the published Docs and added >> these version headers? Should newer versions be added at the top (so 4.0 >> before 3.2 content)?

Re: [qubes-users] Qubes 4.0-rc3

On Friday, 12 January 2018 13:09:35 GMT Holger Levsen wrote: > I'm not so sure, why not use git branches? That has my preference still, but I'm ok for any workable solution. -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel -- You received this

Re: [qubes-users] Qubes 4.0-rc3

On Friday, 12 January 2018 11:18:19 GMT 'awokd' via qubes-users wrote: > Would it be of value if I went through the published Docs and added these > version headers? Should newer versions be added at the top (so 4.0 before > 3.2 content)? 4.0 might just be "TBD". I think that would be wonderful,

Re: [qubes-users] Re: Multiple usability issues Qubes 4RC3

On Fri, January 12, 2018 12:28 pm, aaq via qubes-users wrote: > Den fredag den 12. januar 2018 kl. 12.38.20 UTC+1 skrev awokd: > >> On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote: >> >> >>> 6) Resizing a urxvt window in my debian unstable to a certain >>> dimension (or fullscreen

Re: [qubes-users] Re: Multiple usability issues Qubes 4RC3

Den fredag den 12. januar 2018 kl. 12.38.20 UTC+1 skrev awokd: > On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote: > > > 6) Resizing a urxvt window in my debian unstable to a certain dimension > > (or fullscreen hotkey) crashes the terminal. If I have another window > > running the

Re: [qubes-users] Running Windows from Qubes VM ?

On Fri, January 12, 2018 6:48 am, ThierryIT wrote: > Hello, > > > I have a laptop with two internal Hard Drives. > One HD with Windows 7 the second Hard Drive with Qubes on it. > Is it possible to run Windows 7 from a VM's Qubes instead of building a > Win dows's VM ? You might be able to create

Re: [qubes-users] Re: porting to ARM

On Fri, January 12, 2018 8:59 am, Ph.T wrote: > . my initial motivation for ARM was that > intel seemed more prone to #spectre than ARM; > https://developer.arm.com/support/security-update > "majority of Arm processors are not impacted > by any variation of this side-channel speculation

Re: [qubes-users] Re: Multiple usability issues Qubes 4RC3

On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote: > 6) Resizing a urxvt window in my debian unstable to a certain dimension > (or fullscreen hotkey) crashes the terminal. If I have another window > running the VM, and that window already 'broke' the dimensions in > question, then

RE: [qubes-users] validate IOMMU support

On Fri, January 12, 2018 8:23 am, Wim Vervoorn wrote: > Hello, > > > Thanks. I tried this. Now I am running into problems with the PCI devices > I am using. Qubes can't reset those. For some reason they are not > exposing the FLR capability. I am trying to find out why because they > should

Re: [qubes-users] Qubes in a corporate network behind HTTP proxy

On Fri, January 12, 2018 8:03 am, pr0xy wrote: > > > SUCCESS! > > > Changing the /etc/apt/apt.conf.d in Debian and the /etc/dnf/dnf.conf in > Fedora, AND allowing the proxy IP on the firewall of EACH TemplateVM > finally allows me to update them via the sys-firewall. That's a huge speed >

Re: [qubes-users] Qubes 4.0-rc3

On Fri, January 12, 2018 4:20 am, Andrew David Wong wrote: > It shouldn't require much effort. In most cases, all you have to add > is `## Qubes 3.2` above the existing documentation, shift the rest of the > headers down one by adding a `#` in front of each one, then add `## Qubes > 4.0` above

Re: [qubes-users] Re: QSB #37: Information leaks due to processor speculative execution bugs (XSA-254, Meltdown & Sepctre)

>> >> so people saying the intel meltdown bios patch slows performance. I got an >> increase in performance lmao. probably depends on os though. > > but also in my particular case they also addressed other bugs, but intel > pushed the bios patch for meltdown, so worth a check from your

[qubes-users] Re: Multiple usability issues Qubes 4RC3

Den fredag den 12. januar 2018 kl. 10.45.02 UTC+1 skrev a...@it-minds.dk: > Den mandag den 8. januar 2018 kl. 14.29.06 UTC+1 skrev Ahmed Al Aqtash: > > Hello all! > > > > > > I apologise for the vague subject, but I have been trying all kinds of > > things, and I simply can't understand half of

[qubes-users] Re: Multiple usability issues Qubes 4RC3

Den mandag den 8. januar 2018 kl. 14.29.06 UTC+1 skrev Ahmed Al Aqtash: > Hello all! > > > I apologise for the vague subject, but I have been trying all kinds of > things, and I simply can't understand half of the issues, and the other half > I can't seem to find a solution to. > > > First

Re: [qubes-users] Re: porting to ARM

. my initial motivation for ARM was that intel seemed more prone to #spectre than ARM; https://developer.arm.com/support/security-update "majority of Arm processors are not impacted by any variation of this side-channel speculation mechanism." and is ARM saddled with ME or SMM? ...not sure. I've

RE: [qubes-users] validate IOMMU support

Hello, Thanks. I tried this. Now I am running into problems with the PCI devices I am using. Qubes can't reset those. For some reason they are not exposing the FLR capability. I am trying to find out why because they should according to the datasheet. Best regards, -Original Message-

Re: [qubes-users] Qubes in a corporate network behind HTTP proxy

On 2017-12-28 01:07, Unman wrote: > On Thu, Dec 21, 2017 at 10:57:26PM -0800, pr0xy wrote: >> On 2017-12-19 15:33, Unman wrote: >> > On Tue, Dec 19, 2017 at 03:09:05PM +0100, 'Tom Zander' via qubes-users >> > wrote: >> >> On Monday, 18 December 2017 10:13:48 CET pr0xy wrote: >> >> > I am still a

Re: [qubes-users] A question for the Qubes community: multiboot documentation

Great! Would you consider including instructions on how to multiboot between Qubes OS 3.2 (main system) and Qubes OS 4 (test/future system)? I'd love to test and play with 4RCx but need to have a stable environment for work (3.2). I can see where your coming from, but I dont know if it would be