Hi, did someone try to program qubes-* and qvm-* specific
"autocompletes" in the terminal, like
qvm-start w[TAB] to obtain qvm-start work
qvm-shutdown v[TAB] to obatin qvm-shutdown vault
Since Q4 trained me to use a terminal for everything, I think that an
autocomplete really speeds up
you need the device entry of the cdrom, usually /dev/sr0 or /dev/cdrom. if you
mount the cdrom, and type "mount" you should it in the first column. its been a
long time since doing this. you can also download the windows 7 installer from
microsoft here,
Can you clarify which specter variants will be mitigated and how?
--
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
Mike Keehan:
> It sounds a bit ambitious to run 10gb per sec from one VM through
> another and onto the wire. I suspect you are memory speed limited
> if you are using a straightforward desktop pc.
I'm not sure what is the limiting factor (memory speed, xen overhead?), but I
just did an iperf
On Wed, 31 Jan 2018 22:03:03 -0500, wrote:
dd command to creat an .iso from the win7 cdrom please
dd if=/dev/cdrom of=/home/user/win7.iso bs=1M
BTW, any suggested amount of RAM or HD space to allocate in the HVM for
win7 ?
That I don't know.
I don't see any
Whatever you do, don't create a new issue when you know it's a duplicate
of the old one! That causes confusion and creates extra work, which
takes time away from working on the actual problem.
[...]
Please don't send emails to individual developers or create issues you
know are
Hi all!
I have sometimes big problem with Qubes 3.2.
Just now, by writing an email... suddenly my laptop rebooted. Without
any errors. Blackscreen and reboot.
This was the second time, but after rather large period.
how can i manage it??
greets
evo
--
You received this message because you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-01-31 08:25, ThierryIT wrote:
> Le mardi 30 janvier 2018 10:05:57 UTC+2, Ivan Mitev a écrit :
>> On 01/30/18 09:36, ThierryIT wrote:
>>> Hi,
>>>
>>> Why are you closing a ticket before knowing if the modification you have
>>> made, to
dd command to creat an .iso from the win7 cdrom please
I'm trying to create a win7 HVM and am getting stuck at the magic
glowing windows logo and I discovered in the reference doc's eventually:
https://github.com/QubesOS/qubes-issues/issues/2488
only problem, Is I don't think the original doc,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Qubes Community,
We're pleased to announce the fourth release candidate for Qubes 4.0!
This release contains important safeguards against the [Spectre and
Meltdown attacks][qsb-37], as well as bug fixes for many of the issues
discovered in the
On Wednesday, January 31, 2018 at 11:56:29 PM UTC, Unman wrote:
> I'm just pushing up some PRs to remove zesty and institute build support
> for artful (17.10).
> If you cant wait there's a ready built 3.2 template you can try at:
> http://qubes.3isec.org/Templates
>
> unman
What about Q4, are
qvm-usb command shows you how to attach USB devices to VMs. There is no GUI
method like there is for block devices.
Remember, Yubikey is not a storage/block device. It is a USB that acts more
like a HID keyboard.
Mine works on 3.2 just fine using sys-usb, then attaching to whatever VM
I'm just pushing up some PRs to remove zesty and institute build support
for artful (17.10).
If you cant wait there's a ready built 3.2 template you can try at:
http://qubes.3isec.org/Templates
unman
--
You received this message because you are subscribed to the Google Groups
"qubes-users"
sgid/qubes-users/4d452c25-598c-4130-84e0-edece6028077%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Qubes-HCL-Dell_Inc_-Precision_5520-20180131-230512.yml
Description: Binary data
On Wednesday, 31 January 2018 12:15:01 UTC, Jarle Thorsen wrote:
> Alex Duboise:
> > Interested to find out too. Have you tried from FirewallVM?
>
> Same slow performance when iperf is run from a FirewallVM that is connected
> to the netvm.
>
> > Could you also test what happen when during the
'awokd' via qubes-users:
> On Wed, January 31, 2018 2:39 pm, jaya...@gmail.com wrote:
>> What do you mean it is easy to do? Where do you get a compatible wireless
>> card, that is definitely supported by Qubes anyway?
You can purchase them many places online, even Amazon, for example, for
about
On Wed, January 31, 2018 2:39 pm, jaya...@gmail.com wrote:
> What do you mean it is easy to do? Where do you get a compatible wireless
> card, that is definitely supported by Qubes anyway?
>
> I somehow imagined that getting appropriate driver should be simpler :/
It's not necessarily a driver
On Wed, 31 Jan 2018 05:23:19 -0800 (PST)
Jarle Thorsen wrote:
> Ilpo Järvinen:
> > Please also check that GSO (generic-segmentation-offload) is on at
> > the sending appvm eth0 (I don't remember if the depency logic
> > causes it to get toggled off when SG was off'ed
What do you mean it is easy to do? Where do you get a compatible wireless card,
that is definitely supported by Qubes anyway?
I somehow imagined that getting appropriate driver should be simpler :/
On Wednesday, January 31, 2018 at 3:33:23 PM UTC+4, bobos wrote:
> On Wednesday, January 24,
Le mardi 30 janvier 2018 10:05:57 UTC+2, Ivan Mitev a écrit :
> On 01/30/18 09:36, ThierryIT wrote:
> > Hi,
> >
> > Why are you closing a ticket before knowing if the modification you have
> > made, to correct the bug, is working ? I mean, why can't you wait for the
> > user to add the
How did you attached it ? I am trying without success ... I can attached it
from dom0 using: qvm-block a vm_name dom0:sdd
Is it correct under Qubes4.0r3 ?
Le mardi 23 janvier 2018 09:51:17 UTC+2, Kushal Das a écrit :
> On Tue, Jan 23, 2018 at 12:17 PM, ThierryIT wrote:
> > Hello,
> >
> > I
There is no sys-usb and I do not have installed qubes-usb-proxy
Le mercredi 31 janvier 2018 16:10:08 UTC+2, ThierryIT a écrit :
> Hi,
>
> I have moved from R3.2 to 4.0R3.
> And I am still dealing with the same problem, and I don't know if for 4.0R3
> the documentation provided is still
Hi,
I have moved from R3.2 to 4.0R3.
And I am still dealing with the same problem, and I don't know if for 4.0R3 the
documentation provided is still updated.
All my Keys are detected by dom0:
Device dom0:4-2 - Neowave_Keydo-AES_0989876... is available
Device dom0:sdd - Keydo-AES () available
Ilpo Järvinen:
> Please also check that GSO (generic-segmentation-offload) is on at
> the sending appvm eth0 (I don't remember if the depency logic causes it to
> get toggled off when SG was off'ed and cannot check it ATM myself).
Yes, GSO is automatically turned on when SG is enabled.
> >
On Wed, 31 Jan 2018, Jarle Thorsen wrote:
> Ilpo Järvinen:
> > Scatter-Gather.
> >
> > > Are you talking about enabling sg on the virtual network device in the
> > > netvm?
> > >
> > > Something like "sudo ethtool -K vif12.0 sg on" ?
> >
> > Yes. For both that and the eth0 in appvm.
>
>
Ilpo Järvinen:
> Scatter-Gather.
>
> > Are you talking about enabling sg on the virtual network device in the
> > netvm?
> >
> > Something like "sudo ethtool -K vif12.0 sg on" ?
>
> Yes. For both that and the eth0 in appvm.
This made a huge performance boost! (single threaded iperf went
Alex Duboise:
> Interested to find out too. Have you tried from FirewallVM?
Same slow performance when iperf is run from a FirewallVM that is connected to
the netvm.
> Could you also test what happen when during the load test you start a
> disposable VM? Does it drop
Running iperf in the
On Wed, 31 Jan 2018, Jarle Thorsen wrote:
> onsdag 31. januar 2018 11.12.33 UTC+1 skrev Ilpo Järvinen følgende:
> > On Wed, 31 Jan 2018, Jarle Thorsen wrote:
> > > onsdag 31. januar 2018 10.50.09 UTC+1 skrev Jarle Thorsen følgende:
> > > > My netvm (Fedora 26 template) has a 10gbe network card,
onsdag 31. januar 2018 11.12.33 UTC+1 skrev Ilpo Järvinen følgende:
> On Wed, 31 Jan 2018, Jarle Thorsen wrote:
> > onsdag 31. januar 2018 10.50.09 UTC+1 skrev Jarle Thorsen følgende:
> > > My netvm (Fedora 26 template) has a 10gbe network card, and from
> > > within the netwm I have no problem
On Wednesday, 31 January 2018 08:28:01 UTC, jay...@gmail.com wrote:
> So... no go?
For the wireless you could check support for it with Fedora community (netVM
runs Fedora 26).
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe
On Wednesday, January 24, 2018 at 8:47:28 AM UTC+1, jay...@gmail.com wrote:
> I decided to try Qubes OS 4 on my XPS 9350 laptop, from USB drive. Mostly it
> went ok (had to manually specify EFI file in BIOS to make it load), but
> networking is completely unavailable. I think the reason might be
onsdag 31. januar 2018 10.50.09 UTC+1 skrev Jarle Thorsen følgende:
> My netvm (Fedora 26 template) has a 10gbe network card, and from within the
> netwm I have no problem saturating the 10Gbit link using iperf to an external
> server.
>
> However, in any vm sending traffic through this netvm I
My netvm (Fedora 26 template) has a 10gbe network card, and from within the
netwm I have no problem saturating the 10Gbit link using iperf to an external
server.
However, in any vm sending traffic through this netvm I can only get around
2Gbit max using the same iperf command against the same
So... no go?
--
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
34 matches
Mail list logo