[qubes-users] Re: How to qvm-attach VM volume to another VM?

[aphidfarmer]

On Wednesday, November 1, 2017 at 7:40:01 PM UTC-7, Chris Laprise wrote:
> I'm trying to repair a debian-9 root volume by first attaching it to an 
> appVM, but the new syntax doesn't seem to allow it. I tried the 
> following so far:
> 
> qvm-block attach tempvm lvm:qubes_dom0/vm-debian-9-root
> qvm-block attach tempvm dom0:qubes_dom0/vm-debian-9-root
> qvm-block attach tempvm dom0:/dev/mapper/qubes_dom0-vm--debian--9--root


I'm also interested in a replacement for the old qvm-block -A functionality.

In the meantime I use losetup to get a block device for use with the new 
qvm-block, works for me but it's messier.

-- 
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/d349c8be-d943-4832-b846-0776adacf06a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] How to qvm-attach VM volume to another VM?

[Chris Laprise]

I'm trying to repair a debian-9 root volume by first attaching it to an 
appVM, but the new syntax doesn't seem to allow it. I tried the 
following so far:


qvm-block attach tempvm lvm:qubes_dom0/vm-debian-9-root
qvm-block attach tempvm dom0:qubes_dom0/vm-debian-9-root
qvm-block attach tempvm dom0:/dev/mapper/qubes_dom0-vm--debian--9--root


--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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/f6973d6a-57ca-201a-f147-376acdc55b20%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

AW: Re: [qubes-users] Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

['[799]' via qubes-users]

Hello,

>> I use these cheap flash drives I buy in bulk
>> off ebay. I'll go get a pricey one and see if it
>> makes a difference.

I've migrated my USB drives to only one Modell:
SanDisk
https://www.amazon.com/gp/aw/d/B01NARBPI7/

It has a good performance (I have installed Qubes on of those to showcase it to 
friends and colleques.

[799]

-- 
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/5ILM-tb116toA7ujD1-281zzymNU56buNw6e97HN_i71UBFmSsqpgHNJH8yQkcjLlHMQyYpd-jwuVBS1b24w6EBavfVdHvlikbDT7SpKIfw%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

['[799]' via qubes-users]

Hello,

>> Hi all sergio matta mention to remove the
>> iommu=no-igfx. this solve the problem and i
>> think it will solve 90% of you the issue . so
>> the credit is for you sergio . Thanks . R

I've reinstalled Qubes 4rc2 and removed the line "iommu=no-igfx" upon first 
restart (after installing Qubes).

I found a small bug/typo in Grub, where it says that I should press Enter to 
boot, while the correct command is Ctrl+X.

Currently the installer is installing the default AppVMs. I'll keep you updated.
So far it looks good.

[799]

-- 
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/ijUiNaExeZ6NH-dFiY-Hp3ETjjycNLesDTZ8yU7Duhv7FEnnQI5XGyA9wO2x0OHyF2br6ak_hi0DKqqmAdKatWUDEqKv7NqLFAKnrJuyiRI%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

[billollib]

Yeah, I'll do that.  On the other hand, it may be a Fedora thing.  Just for 
giggles, I downloaded F26, and it won't install, either -- it times out, though 
it gives a different error when it does.

I use these cheap flash drives I buy in bulk off ebay.  I'll go get a pricey 
one and see if it makes a difference.  But I gotta say, these same drives work 
fine for ubuntu and KDE neon.

-- 
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/10648d61-c265-45af-85f3-876c95bd3250%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

[awokd]

On Wed, November 1, 2017 20:26, billol...@gmail.com wrote:
> OK, I updated the BIOS.  That got rid of the microcode error, alright.
> However, it still hangs.
>
> I now get the error:
>
> [2.040734] Couldn't get size: 0x8 0e
> [2.527013] usb 1-1:string descriptor 0 read error-71

Try a different brand flash drive? Maybe it's going bad.

-- 
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/2fe3937152adde172acfee5fe9d7fc64%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Properly setup a qube dns cache server

[nicholas roveda]

Please, someone?

-- 
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/8fb316bb-a6d6-404e-8b31-2da2db4d2324%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

[billollib]

OK, I updated the BIOS.  That got rid of the microcode error, alright. However, 
it still hangs.

I now get the error:

[2.040734] Couldn't get size: 0x8 0e
[2.527013] usb 1-1:string descriptor 0 read error-71

Just for giggles, I tried a different usb port for my flash drive.  On the 
second port, I get just:

[2.039925] Couldn't get size: 0x8...0e

and it hung, without the usb 1-1 error

and for the third port, it's the same, with a different first number:

[2.037575' Couldn't get size: 0x80...0e

with the "..." being a bunch of zeros


One other thing, there's a series of four lines that pops up quickly, but 
disappears faster than I can write them down, that something about UEFI booting 
or some such.  Then the screen blacks out and these errors appear.


As an aside, I'm running a dual boot machine with Windows 10 and KDE neon.

billo

-- 
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/aa71655e-f3e6-4879-807e-0c740b5fd909%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

[billollib]

Thanks, I'll give it a try.  Now I just have to figure out how to update my 
BIOS.  Once I look that up, I'll report back...

-- 
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/2344e295-e0d7-4dfb-8075-c1b7af0704a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Unable to Attach ISO to Windows HVM

[yuraeitha]

On Wednesday, November 1, 2017 at 4:34:50 PM UTC, turb...@gmail.com wrote:
> среда, 1 ноября 2017 г., 16:21:40 UTC+3 пользователь yura...@gmail.com 
> написал:
> > On Wednesday, November 1, 2017 at 1:05:41 AM UTC, Person wrote:
> > > I created a Windows 10 HVM on Qubes (I know Windows 10 isn’t supported, 
> > > but I know some people succeeded with it, so I’m trying it), and when I 
> > > attached the ISO to the HVM, I get an error message: 
> > > “libvirt.libvirtError: internal error: libxenlight failed to create new 
> > > domain ‘windows-10’”.
> > > 
> > > I don’t believe that there is anything wrong with the ISO, because it was 
> > > a download directly from Microsoft; and I don’t believe that I messed up 
> > > the command, because it worked previously. It booted up a picture of the 
> > > Windows logo and then suddenly crashed.
> > > 
> > > One of the solutions I found online was to use “systemctl start 
> > > xendriverdomain”, but I don’t seem to have this service and I don’t know 
> > > how to install it.
> > 
> > Instead try use the graphical tool, it should work.
> > Do the qvm-create etc. first to make the HVM, then afterwards go to the 
> > Qube-menu and select the new Qube menu you just made, open VM-Settings for 
> > this VM, and click "Advanced". Here click on the "Boot qube from CDROM". 
> > Which despite it's name, works for USB, local files, local files in another 
> > VM, and of course an actual CD-Rom drive as well. 
> > 
> > If it doesn't work, then at least you made sure you didn't misstype 
> > anything.
> > 
> 
> 
> It doesn't work. Sad but true.

Weird :/ 
I'll give it a try with Win10 later today or tomorrow, I'll share with you if I 
can repeat the issue or if it works. Stay tuned.

-- 
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/476093fa-503f-49ed-b440-ece7d3f0a2cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Unable to Attach ISO to Windows HVM

[turboacan]

среда, 1 ноября 2017 г., 16:21:40 UTC+3 пользователь yura...@gmail.com написал:
> On Wednesday, November 1, 2017 at 1:05:41 AM UTC, Person wrote:
> > I created a Windows 10 HVM on Qubes (I know Windows 10 isn’t supported, but 
> > I know some people succeeded with it, so I’m trying it), and when I 
> > attached the ISO to the HVM, I get an error message: “libvirt.libvirtError: 
> > internal error: libxenlight failed to create new domain ‘windows-10’”.
> > 
> > I don’t believe that there is anything wrong with the ISO, because it was a 
> > download directly from Microsoft; and I don’t believe that I messed up the 
> > command, because it worked previously. It booted up a picture of the 
> > Windows logo and then suddenly crashed.
> > 
> > One of the solutions I found online was to use “systemctl start 
> > xendriverdomain”, but I don’t seem to have this service and I don’t know 
> > how to install it.
> 
> Instead try use the graphical tool, it should work.
> Do the qvm-create etc. first to make the HVM, then afterwards go to the 
> Qube-menu and select the new Qube menu you just made, open VM-Settings for 
> this VM, and click "Advanced". Here click on the "Boot qube from CDROM". 
> Which despite it's name, works for USB, local files, local files in another 
> VM, and of course an actual CD-Rom drive as well. 
> 
> If it doesn't work, then at least you made sure you didn't misstype anything.
> 


It doesn't work. Sad but true.

-- 
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/11651486-fc56-432e-9ebe-e066cdffedd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Caleb Smith]

Hey y'all, I have found some workarounds for getting VMs to boot. If you
change the virt_mode to pv instead of hvm, usually sys-usb and sys-firewall
will begin to boot regularly. I also increased the qrexec-timeout to 120
per someone's recommendation here, and that seemed to help sys-whonix boot
better. Also running VMs in "debug mode" in the VM Settings UI seems to
help a little bit.

Hope this helps!

- Caleb Smith

On Wed, Nov 1, 2017, 9:19 AM awokd  wrote:

> On Wed, November 1, 2017 00:25, '[799]' via qubes-users wrote:
>
> > Or am I missing something and there is some action on the developer
> > mailing list?
>
> I was looking forward to trying out 4.0rc2 as well. Was a bit disappointed
> to hit a roadblock, but I understand not all issues are going to be
> smoothed out at this early stage. One idea I saw in here that might help
> some test is to install 4.0rc2 directly to another USB stick and boot from
> there for testing, but it could be slow.
>
> I suspect the developers are probably spending most of their time working
> on items in here! https://github.com/QubesOS/qubes-issues/issues .
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "qubes-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/qubes-users/viQYrFSv48E/unsubscribe.
> To unsubscribe from this group and all its topics, 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/7f892ffac16ea218945b37025d0a20a1%40elude.in
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO67bxM0A9_tRXzfFYWfamA%3DVz6stpvjR9Vw299a%2BfA3GZ0UfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[awokd]

On Wed, November 1, 2017 00:25, '[799]' via qubes-users wrote:

> Or am I missing something and there is some action on the developer
> mailing list?

I was looking forward to trying out 4.0rc2 as well. Was a bit disappointed
to hit a roadblock, but I understand not all issues are going to be
smoothed out at this early stage. One idea I saw in here that might help
some test is to install 4.0rc2 directly to another USB stick and boot from
there for testing, but it could be slow.

I suspect the developers are probably spending most of their time working
on items in here! https://github.com/QubesOS/qubes-issues/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/7f892ffac16ea218945b37025d0a20a1%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0rc2 install on corebooted Lenovo G505s (AMD)

[awokd]

On Tue, October 31, 2017 21:25, William Bormann wrote:
> I also experienced problems with item 2.  The progress meter would simply
> stop and the system would appear to be locked up.  I was installing RC2 to
> a USB stick.

Thanks for the suggestion. I tried again and let it sit for 6 hours but
sadly, never made it past the first template (which happened to be
fedora-25 this time around.) I think mine is a hard lockup because the
mouse pointer stops responding and caps and numlock lights on the keyboard
stop working too.



-- 
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/b2037549360e3da76b22ae71181b93ad%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Why is there no qubes manager in V4.0?

[yuraeitha]

On Wednesday, November 1, 2017 at 12:54:23 PM UTC, Desobediente wrote:
> Could the Qubes 4 users ellaborate what things I should be doing on Qubes 3 
> to get used to not having the Qubes Manager available all the time?
> 
> 
> 
> -- 
> 
> 
> 
> 
> iuri.neocities.org

I forgot to mention, in addition to the above, Qubes-Windoes-Tools appears to 
not have been updated for Qubes 4 yet. Which means it's tricky to start your 
Windows due to memory management, and you can't transfer text of files outside 
or into Windows. You may perhaps be able to get internet working if you can 
tweak it yourself, but I haven't personally ventured there yet, so I don't know 
if it's easy or a lot of work to do yourself. 
You can find out more about the RAM issue in my post here: 
https://groups.google.com/forum/#!topic/qubes-users/i48rHs1rBfU 

-- 
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/e2aecd42-143f-4b68-a5ed-ba16b1761cec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Why is there no qubes manager in V4.0?

[yuraeitha]

On Wednesday, November 1, 2017 at 12:54:23 PM UTC, Desobediente wrote:
> Could the Qubes 4 users ellaborate what things I should be doing on Qubes 3 
> to get used to not having the Qubes Manager available all the time?
> 
> 
> 
> -- 
> 
> 
> 
> 
> iuri.neocities.org

Sure, though I might not be able to cover it all, but here are some things to 
start with.

- Qubes 4 uses terminal to create or restore backups, there is as of yet no 
graphic menu anymore. It might seem frightening at first, but it's not that 
difficult to use. The most annoying thing is if you want to exclude some 
Templates or AppVM's, since it'll otherwise restore all your VM's. After you 
type in your backup password, just put -x "AppVM name" -x "AppVM name" without 
the exclamation markers. It takes a few minutes of concentration the first time 
around, but it's not exactly "difficult", just different and takes a bit 
longer. 
Type in "qvm-backup-restore -h" for help on commands if needed, or find a Qubes 
doc guide on the official website. The commandline appears the same in Qubes 
3.2 as it is in 4.0-RC2, so you can practice in Qubes 3.2 with a few test 
AppVM's. 


- Also, from what I hear, it takes a lot longer to restore backups if you run 
it through Dom0. Apparently it goes a lot faster if you i.e. make a USB-Qube 
and restore your backup through an AppVM. I cannot verify if it goes faster 
since my touch-screen on my laptop is tied to my USB, therefore I cannot create 
a USB-QUbe. Which meant I had to go for the slow one through Dom0. It took 
about 10 hours or so for about 60-70 GB of backup data.

- Be sure to turn off suspend or hibernate while you run your backup. 

- Qubes 4-RC2 appears to have some template difficulties, primarily debian and 
whonix, but also sometimes fedora. The way I solved it was during the install, 
I allowed the install of Whonix templates. However during the last-step for 
configuration setup, I removed Whonix in the configuration setup. I also 
removed the automatic easy "Personal, Work" AppVM setup configuration. I only 
selected the first line. For whatever reason, if I selected any other 
configurations below the first, it causes python code errors. Afterwards fedora 
template works fine, and Whonix is easily fixed with the Qubes official Whonix 
install guide on the official website. It's basically just to create the 
sys-whonix and tie the whonix-gw and whonix-ws to the syswhonix for networking. 

- debian won't run for me, I still haven't found a way to fix it. Instead I 
just made an extra copy of my Fedora template, and use that template for my 
packages etc. that I don't want installed in my more secure template/AppVM's. 

- Qubes 4-RC2 sometimes freezes during install, it'll depend on your hardware. 
For my case, it only froze once. I restarted and started over, no changes to 
settings. This time it made it through. Qubes 4-RC1 always froze for me, no 
matter how many times I tried. The takeaway is, it sometimes helps to restart 
and try again. 

- If Qubes 4 succesfully installs, but you get python errors or templates don't 
appear despite that you installed them, try re-install everything. I believe 
the late-stage Qubes configuration is what makes the difference. See above step 
a few steps up.

- Find another way to monitor your RAM/CPU use. For example I use "Xl list" in 
Dom0 to see how much memory Dom0 and all the other Templates/AppVM's are using. 
The widget shoes Template/AppVM memory use, but it doesn't show you how much 
memory you got in Dom0. The Dom0 RAM may be nice to know, so you know how much 
memory you got left for new VM's you plan to start up. 

- There appears to be a new method to update Templatee VM's. Fedora still works 
the old way. But Debian and Whonix doesn't. I haven't found any Qubes guides or 
post about this yet, and haven't had the time to experiment to find out how it 
works now. But basically, Fedora template updates work. Whonix might also work. 
I had a lot of trouble with the Debian template system though. Either way, just 
go with Fedora for now until a guide or post is availale on this matter, or 
till the error is fixed (if there is any errors and it simply is just a user 
mistake). 

- Given the situation, without insider knowledge (aka I simply dont know, this 
is just a guess), I believe there will be a Qubes 4-RC3 release. All these 
python errors and template nightmare, and careful picking Qubes configuarion to 
minimize these issues, seems to be too much to fix with just some updates. 
However if you can get the Fedora template working, you can just re-install the 
other templates whenever a fix becomes available. 

- Qubes 4 appears to come with SALT enabled by default. I haven't ventured too 
much into this new area much yet, however it seemingly adds a security layer to 
VM and VM files so that they can't be changed (Possibly? It's still new to me 
after all, I can't say for sure). Presumably as long it's on the SALT 
configuration 

Re: [qubes-users] Qubes 3.2 HVMs not working - screen stays black ??

['Marek Jenkins' via qubes-users]

On Wednesday, November 1, 2017 at 2:03:05 PM UTC+1, Desobediente wrote:
> 2017-11-01 9:20 GMT-02:00 marek jenkins via qubes-users 
> :
> 
> 
> 
> How exactly do you create/setup the Tails HVM or any HVM for that matter ?
> 
> Did I miss something in my terminal commands ?
> 
> 
> 
> I typed exactly the aforementioned commands
> 
> 
> On the dom0 xfce-terminal:
> 
> 
> $ qvm-create tails --hvm --label red
> 
> $ qvm-start tails --cdrom=disp1:/home/user/Downloads/tails-amd64-3.2.iso
> 
> 
> 
> 
> If I would do it "for real", I would have read the whole manual and attempt 
> to tweak every possible thing, it would take much longer to do the same thing.
> 
>  
> 
> Maybe Fedora 26 LXDE doesn't work because of LXDE, which desktop version of 
> Fedora 24 do you use exactly (KDE,LXDE,Xfce,etc) ?
> 
> 
> 
> If I understood what you meant, this doesn't make any sense. The AppVM isn't 
> bothered by the DE you're using on dom0.
> 
> -- 
> 
> 
> 
> 
> iuri.neocities.org

Thanks for your reply, thats weird. I really don't know why my system is having 
such issues with HVMs.. I also read all man pages on HVMs and the majority of 
the documentation as well.

Initially I thought it could be the boot-up kernel issues described here 
(https://www.qubes-os.org/doc/linux-hvm-tips/) but I am not 100% sure, because 
the fixes didn't really apply to my situation. The fix was to replace "rhgb" in 
GRUB, but my GRUB file didn't include it at all..

Therefore, for now I will continue to try different versions/distros. But 
mainly I am interested in getting Debian and Fedora to work as HVMs.

So far I only created "Standalone HVMs" with the terminal. 
I will now try to create "TemplateHVMs" or "TemplateBasedHVMs" and keep you 
posted. I hope it works ;)

Do you have any other ideas ?

PS: By Fedora 26 LXDE i meant that I used a spin of Fedora 26 that uses LXLE. 
Its an official release just with a more light-weight DE. I didn't mean the DE 
on dom0.

Kind regards,
Marek

-- 
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/125f8013-de4d-43c3-ae3a-caef3af67902%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Unable to Attach ISO to Windows HVM

[yuraeitha]

On Wednesday, November 1, 2017 at 1:05:41 AM UTC, Person wrote:
> I created a Windows 10 HVM on Qubes (I know Windows 10 isn’t supported, but I 
> know some people succeeded with it, so I’m trying it), and when I attached 
> the ISO to the HVM, I get an error message: “libvirt.libvirtError: internal 
> error: libxenlight failed to create new domain ‘windows-10’”.
> 
> I don’t believe that there is anything wrong with the ISO, because it was a 
> download directly from Microsoft; and I don’t believe that I messed up the 
> command, because it worked previously. It booted up a picture of the Windows 
> logo and then suddenly crashed.
> 
> One of the solutions I found online was to use “systemctl start 
> xendriverdomain”, but I don’t seem to have this service and I don’t know how 
> to install it.

Instead try use the graphical tool, it should work.
Do the qvm-create etc. first to make the HVM, then afterwards go to the 
Qube-menu and select the new Qube menu you just made, open VM-Settings for this 
VM, and click "Advanced". Here click on the "Boot qube from CDROM". Which 
despite it's name, works for USB, local files, local files in another VM, and 
of course an actual CD-Rom drive as well. 

If it doesn't work, then at least you made sure you didn't misstype anything.

Also yes, Windows 10 should technically work in Qubes, you just won't get Qubes 
supported tools, such as text and file sharing between Win10 and the rest of 
Qubes system, no easy internet setup, graphic/screen Qubes driver, and so forth.
Basically, it should run, but it might not run optimal. You may be able to 
passthrough some USB devices, or iso files, but otherwise, it'll be completely 
isolated in its own little world. Unlike Windows 7, which can properly 
communicate with Qubes. Basically Windows 10 will theoretically appear like 
Windows 7, just without the Qubes-Windows-Tools installed. 

-- 
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/570161a4-5522-42a7-b11e-354fd222cf49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Why is there no qubes manager in V4.0?

[Richard Musselwhite]

On Wed, Nov 1, 2017, at 08:54 AM, Desobediente wrote:
> Could the Qubes 4 users ellaborate what things I should be doing on
> Qubes 3 to get used to not having the Qubes Manager available all
> the time?> 
> -- 
> iuri.neocities.org
> 


> --
>  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/CAF0bz4TdnXihBjPobqc%3DQ2NB8BCZMYzASPoOHNeLGEzH-toFHA%40mail.gmail.com[1].>
>   For more options, visit https://groups.google.com/d/optout.

I donate monthly to the Qubes OpenCollective fund. My understanding is
that it is dedicated to paying for user-friendly improvements such as
the ones being discussed in this thread. When there's some feature I
wish were included in a Qubes release, donating to the project helps me
to feel more confident that the Qubes team will be able to pay someone
to write them someday. https://opencollective.com/qubes-os.
Links:

  1. 
https://groups.google.com/d/msgid/qubes-users/CAF0bz4TdnXihBjPobqc%3DQ2NB8BCZMYzASPoOHNeLGEzH-toFHA%40mail.gmail.com?utm_medium=email_source=footer

-- 
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/1509542346.3097689.1158036408.31810878%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Unable to Attach ISO to Windows HVM

[Desobediente]

Not trying to give false hope, but yet the same error may mean you mistyped
the qvm-start line, for example the iso full path.

-- 
iuri.neocities.org

-- 
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/CAF0bz4SAJgQs2MHS0yO%3DfscamFpVvMZRmo0DnN6%3DgfJB%3DN2_DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Win7 'Start fix' (Qubes 4-RC2) - A quick temporary semi-solutuon

[yuraeitha]

Hola, 

For those of you who can't start your Windows 7 on Qubes 4, i.e. from your 
backup, here is something quick and simple you may want to try to get it 
working. Albeit it will not run perfectly, since it won't give you internet or 
moving files between VM's and the Window HVM. This is because there appears to 
be no Qubes-Windows-Tools for Qubes 4 as of yet. But it'll give you access to 
your Windows files and applications. Which can be important if you don't want 
to install Qubes 3.2. again just to access your Windows data.

List to do:
- Disable Dynamic Memory in Qubes VM-Settings.
- Increase the minimum memory, i.e. my  was 4000 MB. Any less, and it would 
crash at login screen on my system, not start at all, or crash a few minutes 
after login. For my case, 4000MB was the minimum for a stable running Windows, 
without the Qubes-Windows-Tools to handle the memory. 
- For my system, Windows only starts if it's in HVM mode. Dom0 terminal: 
"qvm-prefs Win7 virt_mode hvm". May apply to you as well.
- Increase the system partition in Qubes settings, since Qubes backup trimmed 
it down to critical minimum levels to save backup space.
- Increase the system partition in the Windows partition settings to match the 
given space in the above step. This is especially important to things like 
page-file, updates and other system functions can function.
- Restart Windows if needed.

This will allow Windows and function without Qubes-Windows-Tools, but it's a 
pain without internet, text and file sharing between VM's, and dynamic memory 
on low RAM computers. Albeit, at least you can start it up to access your files 
and applications.


Tip 1:
For example in Qubes 3.2. I could run Windows 7 just fine with even just 2500 
MB and without dynamic memory enabled (the very same install, from the backUp).
However for whatever reason, even if nothing in Windows itself was changed, it 
won't run without 3.500 MB RAM, and not stable without 4000 MB RAM. This may 
apply for you as well, watch out for this scenario.

Tip 2:
If you have little RAM, like my laptop which has only 8000 MB RAM, then close 
most of the other VM's, or Windows won't even start at all. If there are not 
enough memory, then no errors appear, nothing visual, no warnings, it just 
simply won't budge. Make sure you have enough memory to start Windows. Type in 
"XL list" in Dom0 terminal, to see how your RAM is allocated. Make sure Dom0 
has enough RAM to dynamically give away to Windows's high amount of non-dynamic 
memory. For example if you give Win7 4000MB, then Dom0 should have at the very 
least 5000+ MB RAM, so it retains some for itself.

-- 
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/3567d69b-66e1-4e48-b8a6-3eb77dcb0907%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 3.2 HVMs not working - screen stays black ??

[Desobediente]

2017-11-01 9:20 GMT-02:00 auslandstarife via qubes-users <
qubes-users@googlegroups.com>:

>
> How exactly do you create/setup the Tails HVM or any HVM for that matter ?
> Did I miss something in my terminal commands ?
>

I typed exactly the aforementioned commands

On the dom0 xfce-terminal:

$ qvm-create tails --hvm --label red
$ qvm-start tails --cdrom=disp1:/home/user/Downloads/tails-amd64-3.2.iso


If I would do it "for real", I would have read the whole manual and attempt
to tweak every possible thing, it would take much longer to do the same
thing.


> Maybe Fedora 26 LXDE doesn't work because of LXDE, which desktop version
> of Fedora 24 do you use exactly (KDE,LXDE,Xfce,etc) ?
>

If I understood what you meant, this doesn't make any sense. The AppVM
isn't bothered by the DE you're using on dom0.

-- 
iuri.neocities.org

-- 
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/CAF0bz4QhuMTzp-YqJ2Q48zMG-oxU8yxrLCbZbjnkCd7OMZaVSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Why is there no qubes manager in V4.0?

[Desobediente]

Could the Qubes 4 users ellaborate what things I should be doing on Qubes 3
to get used to not having the Qubes Manager available all the time?

-- 
iuri.neocities.org

-- 
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/CAF0bz4TdnXihBjPobqc%3DQ2NB8BCZMYzASPoOHNeLGEzH-toFHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Ledger Nano S on Qubes OS R3.2

[rodin]

On Sunday, April 30, 2017 at 3:02:23 AM UTC-7, 0x...@secure.mailbox.org wrote:
> Hi, 
> Does anyone actually make Qubes OS R 3.2 working with Ledger Nano S hardware 
> wallet? 

Dave C's instructions also work on 4.0rc2.

I wrote a script that allows me to move the Ledger between AppVMs with a global 
keyboard shortcut:
https://gist.github.com/opposablebrain/fbf2884ab24b3f0c8ff0c36280bec838

-- 
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/44eb9074-9712-491c-8a07-d3cf3edc3309%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] unikernel-firewall: anyone tried this / anyone who wants to help/ already hvm template to download?

[ludwig jaffe]

Hi I found an interesting approach of having a small unikernel firewall,
that does not eat up too much RAM, especially useful for a laptop and also
as there is a different ip-stack than in Linux one has an advantage against
common errors:
(if there is a flaw in the linux kernel it affects sys-net and sys-firewall,
if there is a flaw in uni-kernel-firewall it only affects the firewall and if
there is a flaw in the kernel then it affects sys-net and not sys-firewall!)

look here for the project:
http://roscidus.com/blog/blog/2016/01/01/a-unikernel-firewall-for-qubesos/ 
https://github.com/talex5/qubes-mirage-firewall.git


would be nice to have the mirage-os based firewall as an install option,
by downloading a signed template with a tested mirage-os based firewall.

Is there anyone who has experience with it?
I would like to try it and help developing it further. Who else wants?

Cheers,

Ludwig


-- 
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/47b87496-5a00-4ec0-b699-a08ef956911b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 3.2 HVMs not working - screen stays black ??

['Marek Jenkins' via qubes-users]

UPDATE:

I generally suspect it to be a graphics issue. Because the screen of the HVM 
stays black and in the top of the HVM window you can see a white cursor or 
something similar - but it never boots.

During Installation I had a Nvidia graphics card attached to the mainboard. But 
then I removed it because of Boot problems. Without the Nvidia card therer are 
no problems. 

Could this hardware change have to do with the weird behaviour of HVMs ?

Thank you very much for advise.

Kind regards,
Marek

-- 
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/17eb097b-06f2-4d5b-973a-efcf30a06a09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 3.2 HVMs not working - screen stays black ??

[auslandstarife via qubes-users]

On Wednesday, November 1, 2017 at 6:00:53 AM UTC+1, Desobediente wrote:
> Tails 3.2 working for me in a standalone HVM.
> 
> It's very weird to have Tails as an AppVM with network routed through Whonix 
> inside Qubes, though. Feels like I'm trying to find the ultimate question for 
> 42 or something.
> 
> 
> 
> -- 
> 
> 
> 
> 
> iuri.neocities.org


Thanks for your efforts to help!

True, I thought about running Tails without Whonix Gateway, just with the 
Firewall.

How exactly do you create/setup the Tails HVM or any HVM for that matter ?
Did I miss something in my terminal commands ?

Maybe Fedora 26 LXDE doesn't work because of LXDE, which desktop version of 
Fedora 24 do you use exactly (KDE,LXDE,Xfce,etc) ?

Best regards!

-- 
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/8d5e268b-86a4-4b94-bf40-502b876989c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] fixed problems with destorted sound with pulseaudio on qubes 3.2 -> change request for config file

[ludwig jaffe]

Hi I use qubes 3.2 and sometimes I listend to music using youtube on a 
user vm.
Now I had the following problems:
the sound was often distorted, sounded like overdriven pre amplifier,
but if one stops the sound source (youtube in browser, press pause) there was
a trailing 1 second of destorted sound. Like if there was a buffer that was not
served in time and wants to empty out.

So I looked around and found that there is a configuration to be changed:

take a terminal in dom0:

sudo su
(now I am root)
vi /etc/pulse/default.pa

find a section and modify like I did:
### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
##modified 01.11.17
#load-module module-udev-detect
##against glitches 
load-module module-udev-detect tsched=0
##-end-modified 01.11.17


So add tsched=0, this disables PulseAudio's timer-based scheduling
 and uses the classic interrupt-driven approach
why? see: http://0pointer.de/blog/projects/pulse-glitch-free.html

now say :wq to your vi
then in your root shell of dom0 say
pkill pulseaudio and it restarts, now without distortion or glitches.

My audio hw is:
Creative Labs EMU20K1 (Soundblaster X-Fi Series)
Having a decent sound board one wants no lowfi destorted sound...

So have fun with better audio.
@qubes-os developer. Maybe, you should patch the file
/etc/pulse/default.pa for dom0 accordingly.

Cheers,

Ludwig

-- 
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/872ee463-9812-4383-9f5a-6c96a953072f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: really no support

[yuraeitha]

On Monday, October 30, 2017 at 8:43:53 PM UTC, Outback Dingo wrote:
> seriously still seems there is very little support ive sent multiple
> emails to the list and received no response, so let me ask again ?
> 
> how do i enlarge a vm file system with 4.0RC2
> basically my personal vm is out of space..

You got it all backwards. You shouldn't expect others to help, rather you 
should be happy when someone spends time to help you for free. People help each 
others around here, but the community is also not very big yet either. There 
are a limited amount of people hanging around spending their own private free 
time to help others, without getting anything in return. You should be happy 
that there are even such people around, and not make such ridiculous demands, 
as to getting something for free. It's a privilege to have others around who 
wants to help without getting something in return, it's not something you can 
just expect or demand.

You might want to scratch out that word "support" too while at it, after all, 
Qubes is a free, you're not paying for it like some other company product. 
"Support" here, is people taking up and spending their free time to help each 
others out, which is completely volunteer work.

It's also a bit annoying when the question you're asking is such a simple 
question, that most people figure out on their first day in Qubes (3.2. and 
version 4 alike). While I like the idea that Qubes should be made available to 
as many people as possible, it isn't there yet, and it may not even be the goal 
of the developers to go there either, who knows. But in its present state, 
Qubes is not for people who can't or won't spend time to figure out, at the 
very least, how the basics works. 

It's fine to ask questions, but seriously change your attitude. Both the 
developers and the community helping others, are doing a lot here for free.

-- 
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/11053432-e51a-4244-8bd3-50f4d7de2895%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Why is there no qubes manager in V4.0?

[yuraeitha]

On Saturday, October 28, 2017 at 4:51:52 PM UTC, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2017-10-27 23:24, taii...@gmx.com wrote:
> > While I do know how to use the cli tools I enjoy a gui for at a 
> > glance viewing and tasks, it is much easier to press start/stop on 
> > a nice list rather than type two commands.
> > 
> > Thanks ADW!
> > 
> 
> Thanks for your feedback in this thread, everyone. Just to briefly
> address the original question in the subject line, the reasons for
> removing the Qubes VM Manager from Qubes 4.0 are discussed in this
> issue:
> 
> https://github.com/QubesOS/qubes-issues/issues/2132
> 
> However, na-- recently opened a new issue that reflects many of the
> same concerns as in this thread:
> 
> https://github.com/QubesOS/qubes-issues/issues/3241
> 
> We're looking into what can be done to improve the user experience in
> 4.0. Thank you for testing, everyone!
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJZ9LWcAAoJENtN07w5UDAwmQ4P/jVhDfQPQKYxrTvK5psOS8aM
> dyOHae12t8Jkb0GrjfYIuk3u+/gNFaw+4dMG58BCfMAV6gZMKvBiTqtH13fX/RNT
> 3/D5owRtPgj+P6MjWumKO16D929HI/L3wHC51vZPhC8a+to7mi8cG6XEHlfvZcD7
> iJwXzRGyUz+qMD/fwGy0cbfqvyrmQgX5QULJMvfK4+YfvwwEs/M9dMsA30XE6s1p
> Sc8bc3pXbBFlwGQaN3RFOOa25QeqMHcdKgRmZpagqcdIJuzw01IwkDn4/IGwEOKU
> gyB2++1w0/q4a3M4btNHthZHWNnfEPSULCSpZVxL/IXTR5hIw5oAOR0B97HRnFKO
> qd1MULj2HUdLXH7oicIok+p/IGEK0SElXJtGTtgwturvyDfAr7BkRwxGF7BGdQBA
> 5NQfD7Ya87oSAM1PhI/X48HxG9Xia9izrqWHBAjT57gNhgYPZDv2YT1sVEfvhbyX
> jzDED9tubE8sSQHbyF/5L5d+5+213yhcmA+J+0FBB5MerD71Flr/+LsVMB7iKnmD
> dozUgjJFlopfneRcalotMWgf1XERGX/QC4bBnCJ3hpNmhKqJyk7I+xBPZiaMueoc
> FlMU8wYT9BR+PFkODDjOgqdrc/ACp9vXdPjpWJiaHLXZik8iZ0YuwTMY6LLn2i5r
> p08JqthOTHM4Gt74UXYM
> =+HEQ
> -END PGP SIGNATURE-

While I initially didn't like the loss of the Qubes Manager either, I've grown 
pretty used to not having it in Qubes 4. Refusing to upgrade due to not having 
the old Qubes Manager, is imho just being conservative stubborn to old habits, 
refusing change. While true change can go from better to worse, refusing change 
altogether is not always a good thing. One should try give the layout in Qubes 
4 a chance. 

While true Qubes 4 has its interface shortcomings compared to Qubes 3.2, I 
think it's interface isn't far from being superior to Qubes 3.2. too, with some 
tweaks here and there. 

For example, expanding the widget to allow for more details, similar to how the 
old Qubes Manager worked. Perhaps even put in an option to make it 
detachable/moveable/sizeable from the widget icon to the desktop for those who 
prefer a window over a widget. 

Either way, despite the loss from the extras in the old QUbes Manager, despite 
it was a major pain to get the templates to work properly in the start from a 
fresh install, despite all that, I still enjoy Qubes 4 more than I did Qubes 
3.2. And if anything, Qubes 4 is more secure than 3.2., so refusing to upgrade 
for such minor things, seems to me quite weird. Albeit the complaints are 
understandable, but it doesn't make Qubes 4 inferior to Qubes 3.2, when 
counting all the pros and cons together.

We also have to remember Qubes 4 is laying the foundations to more features in 
the future. At least to my understanding, a lot in Qubes 4 is foundation work 
for more things to come in the future. Don't be so unsatisfied, it's work in 
progress, Qubes 4 is not a finished project. Think long-term, not short-term.

Imho, the Qubes team did a fantastic job with Qubes 4. They didn't have much 
time with the interface layout, given all the other things that was implemented 
in Qubes 4. After all, security takes president, and practical use is also a 
serious priority. Cosmetics and lesser user-ability have to take a second seat, 
given the paradigm and goals that's being followed, with so few resources. 

Just give it time people, the Qubes team did an amazing job. Being frustrated 
to such a high degree though, is uncalled for. We should at the very least 
appreciate their hard work.

-- 
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/d6792259-6b6a-4a7b-b5e9-0cc8e82b0f0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Unable to Attach ISO to Windows HVM

[Yethal]

W dniu środa, 1 listopada 2017 02:05:41 UTC+1 użytkownik Person napisał:
> I created a Windows 10 HVM on Qubes (I know Windows 10 isn’t supported, but I 
> know some people succeeded with it, so I’m trying it), and when I attached 
> the ISO to the HVM, I get an error message: “libvirt.libvirtError: internal 
> error: libxenlight failed to create new domain ‘windows-10’”.
> 
> I don’t believe that there is anything wrong with the ISO, because it was a 
> download directly from Microsoft; and I don’t believe that I messed up the 
> command, because it worked previously. It booted up a picture of the Windows 
> logo and then suddenly crashed.
> 
> One of the solutions I found online was to use “systemctl start 
> xendriverdomain”, but I don’t seem to have this service and I don’t know how 
> to install it.

You'd need Xen disk drivers installed within the VM for this to work. Xen 
drivers (along the rest of Qubes Windows Tools) haven't been ported to Windows 
10 yet.

-- 
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/1ad9e6ad-2d89-4d84-b192-51602193e415%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.