Re: [qubes-users] HCL: HP Spectre X360 - 15" i7-8550u 16GB / 512GB / GeForce MX150 /Intel 802.11b/g/n/ac Wi-Fi

[David Schissler]

On Wednesday, August 29, 2018 at 2:50:09 PM UTC-5, pieter lems wrote:
> thank you for that i have the same laptop. when running multiple vm's the fan 
> spins up pretty hard tho.
> 
> 
> 
> On Aug 28, 2018 7:18 PM,   wrote:
> Hello,
> 
> I've successfully installed Qubes OS R4.0 on an HP Spectre x360 with the 
> following specs: 
> 
> 
> 
> 
> 
> CPU: 1.8GHz Intel Core i7-8550U (quad-core, 8MB cache, up to 4.0GHz with 
> Turbo Boost) 
> 
> Graphics: Nvidia GeForce MX150 (2GB GDDR5 RAM); Intel UHD Graphics 620
> 
> RAM: 16GB DDR4
> 
> Screen: 15.6-inch 4K UHD (3,840 x 2,160) IPS WLED backlit
> 
> Storage: 512GB SSD (PCIe NVMe M.2)
> 
> Ports: 1 x Thunderbolt 3, 1 x USB-C 3.1, 1 x USB 3.1 Type-A, 1 x HDMI, 1 x 
> 3.5mm audio jack, 1 x SD card reader
> 
> Connectivity: Intel 802.11b/g/n/ac Wi-Fi (2x2), Bluetooth 4.2
> 
> Camera: FHD webcam
> 
> 
> 
> Enabled virtualization in the BIOS and that was it.
> 
> 
> 
> Qubes OS works out of the box, everything I tested so far including the touch 
> screen.
> 
> 
> 
> Martin
> 
> 
> 
> -- 
> 
> 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...@googlegroups.com.
> 
> To post to this group, send email to qubes...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/5ca20ce1-88ec-4e10-ac1e-17c5ef5b3e87%40googlegroups.com.
> 
> For more options, visit https://groups.google.com/d/optout.



Pieter have you considered undervolting the notebook?  I bet that it runs Qubes 
a lot smoother afterwards.  I've accepted that I'm going to have to learn a few 
new tricks to get the most out of a 2018 ultrabook with a stock overheating 
setup.

Try the links in this repo as they appear to be more current and with better 
docs.
https://github.com/mihic/linux-intel-undervolt

-- 
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/5fb660cd-bf53-4776-a4c2-41ee4b253a8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL: HP Spectre X360 - 15" i7-8550u 16GB / 512GB / GeForce MX150 /Intel 802.11b/g/n/ac Wi-Fi

[David Schissler]

I was looking at this model a lot a month ago and wondering about this.  Now 
I'm looking at the Matebook X Pro and the just barely released Thinkpad X1 
Extreme.  This is pretty good for the $1500 on Amazon US but it doesn't have a 
3/2 screen like the Matebook X Pro and also the MXP seems to have a large Linux 
following.  Also if the reviews of the X1 Extreme continue to come out good 
then for $600 more the X1 Extreme seems to just be much better and with 0.7lbs 
less (mmm minus the higher res screen).

I'll be in the market for a new machine in about 6 weeks.  Does anyone know 
what the latest root host kernel is?  For once during a new purchase I'll not 
be scrambling to replace a broken or stolen machine and so I'll be able to 
spend the time to adjust into using Qubes

Also what about Qubes 4.1?  I don't want to have to deal with a messy upgrade 
soon after getting everything setup to be productive.

-- 
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/bb1c67b9-8c06-438b-aef3-3753a9a0a81e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Can I set an unencrypted external HD as /home folder for a VM

[Chris Laprise]

On 08/31/2018 01:40 PM, Guy Frank wrote:

On Friday, August 31, 2018 at 12:17:54 PM UTC-5, js...@bitmessage.ch wrote:

Guy Frank:

One question I had is whether there is any way to set an unencrypted (or 
encrypted?) external HD as the /home folder for a VM?

Guy


Hi Guy,

I'm not sure about setting it as /home but i think it's possible. But
it's easy to attach an external HD to a vm and save your files to it.

https://www.qubes-os.org/doc/usb/

Also it's pretty easy to encrypt it with luks for security, it just
takes a little longer each time.

--
Jackie


Thanks Jackie for your reply!

I remember it being fairly easy to attach USB devices w/ the right clicks here 
& there.  So, yes, I'd have access to the files on my external HD.

But it would be more convenient if I could get Qubes to mount the home folder 
on the HD as the Home folder for the given virtual machine.  I imagine that's 
trickier and was wondering if there's a way to do it?

Maybe use a script to mount the attached USB drive home (/home/guyuser) over 
the Qubes home directory?  But then, if that's possible, some of the setup in 
the Qubes home directory might get missed.



The key to using it as /home would be to setup a new storage pool to 
hold that VM. Unfortunately the docs could use a rewrite:


https://www.qubes-os.org/doc/storage-pools/

The relevant commands are 'qvm-pool --add' and 'qvm-create --pool'.

--

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/b82ef887-5be1-fd5c-bcd2-2727101d5d0e%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4.0 qemu device controller mptsas1068 not seen by ReactOS

[Steve Coleman]

I saw that a while back a Qubes discussion on qemu's disk controller vs 
Windows support, which if I recall correctly required a modification to 
the qemu device being passed to the HVM. It appears that Qubes HVM is 
currently passing "-device mptsas1068 -id=scsi0" which appears to not be 
seen by ReactOS. I know that ReactOS used to work under Q3.2, but my 
current Q4.0 system doesn't present any drive at all to ReactOS, other 
than the cdrom from which to boot from.


How is windows being handled right now? The mptsas is working there I 
assume?


Is there any kind of user level qvm-prefs setting to change this device 
presentation based on the OS requirements? If not, is there any kind of 
configuration file for this kind of mod within QEMU itself?


thanks,

Steve.

--
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/033b1332-0e97-bddf-0bf5-20fdfd6b8ed9%40jhuapl.edu.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes-R4.0 : missing argument to qvm-create

[Ivan Mitev]

On 08/31/2018 08:42 PM, GDRUB wrote:
> Le 31/08/2018 à 14:43, GDRUB a écrit :
>> Le 31/08/2018 à 13:33, brendan.h...@gmail.com a écrit :
>>> On Thursday, August 30, 2018 at 4:43:42 PM UTC-4, GDRUB wrote:
 Thank you for those explanations.

 However, Windows 10 fails with error code : 0xc225 "a required
 device isn't connected or can't be accessed".

 win10.raw = 96.6 GB

 How to fix this error ?


 Le 30/08/2018 à 11:58, Ivan Mitev a écrit :
> On 08/30/2018 11:10 AM, gd...@gmail.com wrote:
>> Hi, 
>>
>> I'm trying to run the following command:
>>
>> $ qemu-img convert -O raw *.vmdk win10.raw
>> $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > 
>> /home/user/win10-root.img
>> $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from 
>> /home/user/win10-root.img
>>
>> qvm-create: error: unrecognized arguments: --hvm --mem=4096
>>
>> Source : https://www.qubes-os.org/doc/hvm/
> You're using 3.2 commands, see the "R4.0: ..." paragraph below in the doc.
>
> The following command should do the trick:
>
> qvm-create win10 \
>   --class StandaloneVM \
>   --property virt_mode=hvm \
>   --property kernel='' \
>   --label=red \
>   --property memory=4096 \
>   --property maxmen=4096 \
>   --root-move-from /home/user/win10-root.img
>
>
>
>> How to create a new PVH instead of HVM in Dom0 with the root image from 
>> R4.0 ?
>>
>> Thank you so much for your help.
>>
>> Best regards.
>>
>>> I think the issue of > 10GB images being truncated via ---root-copy-from 
>>> during create still exists. See this Issue is still open in the tracker: 
>>>
>>> https://github.com/QubesOS/qubes-issues/issues/3422
>>>
>>> You'll likely need to qvm-create w/o the root-copy-from, then 
>>> qvm-grow-root, then copy the image to the right volume listed in 
>>> /dev/mapper.
>>>
>>> See this thread (and choose commands wisely!):
>>>
>>> https://groups.google.com/forum/#!topic/qubes-users/vBk-jjvoeT0
>>>
>>> Brendan
>>>
>> Hi Brendan,
>>
>> It seems to be the solution to this problem.
>>
>> I'll test this with caution.
>>
>> Thank you so much for your help.
>>
> missing binary in PATH ! :-(
> 
> $ qvm-grow-root win10 100g
> 
> bash : qvm-grow-root : command not found

qvm-grow-root is a R3.2 command, on R4.0 you have to use `qvm-volume`:

https://www.qubes-os.org/doc/resize-disk-image/#expand-disk-image-r40

eg.:

qvm-volume resize win10:root 100G

-- 
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/829cc36b-7477-663f-e3b0-ee8a0a873636%40maa.bz.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes-R4.0 : missing argument to qvm-create

[Alain BERNARD]

Le 31/08/2018 à 19:42, GDRUB a écrit :
> Le 31/08/2018 à 14:43, GDRUB a écrit :
>> Le 31/08/2018 à 13:33, brendan.h...@gmail.com a écrit :
>>> On Thursday, August 30, 2018 at 4:43:42 PM UTC-4, GDRUB wrote:
 Thank you for those explanations.

 However, Windows 10 fails with error code : 0xc225 "a required
 device isn't connected or can't be accessed".

 win10.raw = 96.6 GB

 How to fix this error ?


 Le 30/08/2018 à 11:58, Ivan Mitev a écrit :
> On 08/30/2018 11:10 AM, gd...@gmail.com wrote:
>> Hi, 
>>
>> I'm trying to run the following command:
>>
>> $ qemu-img convert -O raw *.vmdk win10.raw
>> $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > 
>> /home/user/win10-root.img
>> $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from 
>> /home/user/win10-root.img
>>
>> qvm-create: error: unrecognized arguments: --hvm --mem=4096
>>
>> Source : https://www.qubes-os.org/doc/hvm/
> You're using 3.2 commands, see the "R4.0: ..." paragraph below in the doc.
>
> The following command should do the trick:
>
> qvm-create win10 \
>   --class StandaloneVM \
>   --property virt_mode=hvm \
>   --property kernel='' \
>   --label=red \
>   --property memory=4096 \
>   --property maxmen=4096 \
>   --root-move-from /home/user/win10-root.img
>
>
>
>> How to create a new PVH instead of HVM in Dom0 with the root image from 
>> R4.0 ?
>>
>> Thank you so much for your help.
>>
>> Best regards.
>>
>>> I think the issue of > 10GB images being truncated via ---root-copy-from 
>>> during create still exists. See this Issue is still open in the tracker: 
>>>
>>> https://github.com/QubesOS/qubes-issues/issues/3422
>>>
>>> You'll likely need to qvm-create w/o the root-copy-from, then 
>>> qvm-grow-root, then copy the image to the right volume listed in 
>>> /dev/mapper.
>>>
>>> See this thread (and choose commands wisely!):
>>>
>>> https://groups.google.com/forum/#!topic/qubes-users/vBk-jjvoeT0
>>>
>>> Brendan
>>>
>> Hi Brendan,
>>
>> It seems to be the solution to this problem.
>>
>> I'll test this with caution.
>>
>> Thank you so much for your help.
>>
> missing binary in PATH ! :-(
>
> $ qvm-grow-root win10 100g
>
> bash : qvm-grow-root : command not found
>
>
Sorry : |qvm-volume extend :root |

-- 
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/f0e4b585-7fff-7edd-6f8d-d459ab98ed40%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes-R4.0 : missing argument to qvm-create

[GDRUB]

Le 31/08/2018 à 14:43, GDRUB a écrit :
> Le 31/08/2018 à 13:33, brendan.h...@gmail.com a écrit :
>> On Thursday, August 30, 2018 at 4:43:42 PM UTC-4, GDRUB wrote:
>>> Thank you for those explanations.
>>>
>>> However, Windows 10 fails with error code : 0xc225 "a required
>>> device isn't connected or can't be accessed".
>>>
>>> win10.raw = 96.6 GB
>>>
>>> How to fix this error ?
>>>
>>>
>>> Le 30/08/2018 à 11:58, Ivan Mitev a écrit :
 On 08/30/2018 11:10 AM, gd...@gmail.com wrote:
> Hi, 
>
> I'm trying to run the following command:
>
> $ qemu-img convert -O raw *.vmdk win10.raw
> $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > 
> /home/user/win10-root.img
> $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from 
> /home/user/win10-root.img
>
> qvm-create: error: unrecognized arguments: --hvm --mem=4096
>
> Source : https://www.qubes-os.org/doc/hvm/
 You're using 3.2 commands, see the "R4.0: ..." paragraph below in the doc.

 The following command should do the trick:

 qvm-create win10 \
--class StandaloneVM \
--property virt_mode=hvm \
--property kernel='' \
--label=red \
--property memory=4096 \
--property maxmen=4096 \
--root-move-from /home/user/win10-root.img



> How to create a new PVH instead of HVM in Dom0 with the root image from 
> R4.0 ?
>
> Thank you so much for your help.
>
> Best regards.
>
>> I think the issue of > 10GB images being truncated via ---root-copy-from 
>> during create still exists. See this Issue is still open in the tracker: 
>>
>> https://github.com/QubesOS/qubes-issues/issues/3422
>>
>> You'll likely need to qvm-create w/o the root-copy-from, then qvm-grow-root, 
>> then copy the image to the right volume listed in /dev/mapper.
>>
>> See this thread (and choose commands wisely!):
>>
>> https://groups.google.com/forum/#!topic/qubes-users/vBk-jjvoeT0
>>
>> Brendan
>>
> Hi Brendan,
>
> It seems to be the solution to this problem.
>
> I'll test this with caution.
>
> Thank you so much for your help.
>
missing binary in PATH ! :-(

$ qvm-grow-root win10 100g

bash : qvm-grow-root : command not found


-- 
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/84167296-7970-71fe-0cc4-e4e267c4f5a6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Can I set an unencrypted external HD as /home folder for a VM

[Guy Frank]

On Friday, August 31, 2018 at 12:17:54 PM UTC-5, js...@bitmessage.ch wrote:
> Guy Frank:
> > One question I had is whether there is any way to set an unencrypted (or 
> > encrypted?) external HD as the /home folder for a VM?  
> > 
> > Guy
> 
> Hi Guy,
> 
> I'm not sure about setting it as /home but i think it's possible. But
> it's easy to attach an external HD to a vm and save your files to it.
> 
> https://www.qubes-os.org/doc/usb/
> 
> Also it's pretty easy to encrypt it with luks for security, it just
> takes a little longer each time.
> 
> -- 
> Jackie

Thanks Jackie for your reply!  

I remember it being fairly easy to attach USB devices w/ the right clicks here 
& there.  So, yes, I'd have access to the files on my external HD.  

But it would be more convenient if I could get Qubes to mount the home folder 
on the HD as the Home folder for the given virtual machine.  I imagine that's 
trickier and was wondering if there's a way to do it?  

Maybe use a script to mount the attached USB drive home (/home/guyuser) over 
the Qubes home directory?  But then, if that's possible, some of the setup in 
the Qubes home directory might get missed.

-- 
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/649e63f8-fe19-4efc-98da-9ae82fd33a04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Custom Configuration files for AppVMs

[airelemental]

In Qubes 4.0,  I think the default config for all VMs is:
   /usr/share/qubes/templates/libvirt/xen.xml
and you can override it for  by placing a config file in 
  /etc/qubes/templates/libvirt/xen/by-name/.xml
Simply copying the former to the latter is probably a good place to start.

31. Aug 2018 15:51 by 3mp...@gmail.com :


> On Tuesday, July 9, 2013 at 4:29:18 AM UTC+2, Marek Marczykowski-Górecki 
> wrote:
>> On 29.06.2013 08:23, Olivier Médoc wrote:
>> > On 06/29/13 06:58, AndrewX192 wrote:
>> >> Is it possible to permanently set or override options in the autogenerated
>> >> configuration files, and if so - what is the best way to implement these
>> >> changes?
>> >>
>> > If you change your vm config filename and you edit qubes manager xml file 
>> > to
>> > match the new filename, this file will be considered as custom and won't be
>> > generated anymore during the vm startup. Check in 
>> > /var/lib/qubes/appvms/yourvm
>> > and /var/lib/qubes/qubes.xml.
>> > 
>> > You will probably have to restart the qubes manager once you changed the 
>> > file.
>> > I'm not sure about that.
>>
>> Qubes manager should automatically detect qubes.xml modification (inotify
>> based watch).
>>
>> -- 
>> Best Regards,
>> Marek Marczykowski-Górecki
>> Invisible Things Lab
>
> I have the same problem in Qubes 4.0 but I can't find the VM configuration 
> file... I tried modifying the qubes.xml file, tried virsh edit the VM with no 
> luck, the config file of the VM I can't find is always regenerated when the 
> VM starts.
>
> There is a workaround when the VM is started with xl block-attach which is 
> working and probably can be automated with qubes-rpc but I'm looking for a 
> more elegant way like Olivier's solution for Qubes 4.0
>
> Any directions ?
>
> -- 
> 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/edced9d8-73ca-48e4-9b50-f0cd4fa5fc5c%40googlegroups.com
>  
> >
>  .
> 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/LLFsNcy--3-1%40tutanota.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Can I set an unencrypted external HD as /home folder for a VM

[jsnow]

Guy Frank:
> I tried Qubes once before but gave up because the hardware I had wasn't 
> compatible.  I'm now giving Qubes another try w/ a new machine and had a 
> couple questions.  Keep in mind I'm a newbie.
> 
> One question I had is whether there is any way to set an unencrypted (or 
> encrypted?) external HD as the /home folder for a VM?  
> 
> This would make it much more convenient for me to move my work between Qubes 
> and a non-Qubes desktop.  I realize this is a security hole, but the 
> alternative of simply sticking with Ubuntu is even less secure.
> 
> Guy

Hi Guy,

I'm not sure about setting it as /home but i think it's possible. But
it's easy to attach an external HD to a vm and save your files to it.

https://www.qubes-os.org/doc/usb/

Also it's pretty easy to encrypt it with luks for security, it just
takes a little longer each time.

-- 
Jackie

-- 
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/c68838ae-93ec-9908-3270-24ac58316601%40bitmessage.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Materials for BIOS flash procedure

[Qubes N00b]

So I got the opportunity to buy myself a Lenovo G505S, and did so. It is 
the quad-core. It came with Windows 8, so I ran Speccy on it, and can 
send details from Speccy if need be.


I'm trying to gather the materials for the coreboot/seabios flash 
procedure, and want to reduce the wait times. I especially don't want to 
wait three weeks for the 30-pin AWM 20624 cable, which is what I'm being 
quoted right now.


Since they are sold in packs of ten or more, I wonder if anyone here has 
finihed this project and has a few just sitting around. I would also 
take help with gathering any other necessary materials that don't come 
more or less off the shelf, if you aren't planning on using them in the 
future.


In case it matters, I have the bus pirate, sparkfun #12942. I live on 
the east coast of the U.S.


TIA, folks.

--
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/4543413a610d493d53646602d20b1d66%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Can I set an unencrypted external HD as /home folder for a VM

[Guy Frank]

I tried Qubes once before but gave up because the hardware I had wasn't 
compatible.  I'm now giving Qubes another try w/ a new machine and had a couple 
questions.  Keep in mind I'm a newbie.

One question I had is whether there is any way to set an unencrypted (or 
encrypted?) external HD as the /home folder for a VM?  

This would make it much more convenient for me to move my work between Qubes 
and a non-Qubes desktop.  I realize this is a security hole, but the 
alternative of simply sticking with Ubuntu is even less secure.

Guy

-- 
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/f157c9bf-d671-4316-a6af-ed6b2f17763b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Custom Configuration files for AppVMs

[3mptyy]

On Tuesday, July 9, 2013 at 4:29:18 AM UTC+2, Marek Marczykowski-Górecki wrote:
> On 29.06.2013 08:23, Olivier Médoc wrote:
> > On 06/29/13 06:58, AndrewX192 wrote:
> >> Is it possible to permanently set or override options in the autogenerated
> >> configuration files, and if so - what is the best way to implement these
> >> changes?
> >>
> > If you change your vm config filename and you edit qubes manager xml file to
> > match the new filename, this file will be considered as custom and won't be
> > generated anymore during the vm startup. Check in 
> > /var/lib/qubes/appvms/yourvm
> > and /var/lib/qubes/qubes.xml.
> > 
> > You will probably have to restart the qubes manager once you changed the 
> > file.
> > I'm not sure about that.
> 
> Qubes manager should automatically detect qubes.xml modification (inotify
> based watch).
> 
> -- 
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab

I have the same problem in Qubes 4.0 but I can't find the VM configuration 
file... I tried modifying the qubes.xml file, tried virsh edit the VM with no 
luck, the config file of the VM I can't find is always regenerated when the VM 
starts.

There is a workaround when the VM is started with xl block-attach which is 
working and probably can be automated with qubes-rpc but I'm looking for a more 
elegant way like Olivier's solution for Qubes 4.0

Any directions ?

-- 
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/edced9d8-73ca-48e4-9b50-f0cd4fa5fc5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes-R4.0 : missing argument to qvm-create

[GDRUB]

Le 31/08/2018 à 13:33, brendan.h...@gmail.com a écrit :
> On Thursday, August 30, 2018 at 4:43:42 PM UTC-4, GDRUB wrote:
>> Thank you for those explanations.
>>
>> However, Windows 10 fails with error code : 0xc225 "a required
>> device isn't connected or can't be accessed".
>>
>> win10.raw = 96.6 GB
>>
>> How to fix this error ?
>>
>>
>> Le 30/08/2018 à 11:58, Ivan Mitev a écrit :
>>> On 08/30/2018 11:10 AM, gd...@gmail.com wrote:
 Hi, 

 I'm trying to run the following command:

 $ qemu-img convert -O raw *.vmdk win10.raw
 $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > 
 /home/user/win10-root.img
 $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from 
 /home/user/win10-root.img

 qvm-create: error: unrecognized arguments: --hvm --mem=4096

 Source : https://www.qubes-os.org/doc/hvm/
>>> You're using 3.2 commands, see the "R4.0: ..." paragraph below in the doc.
>>>
>>> The following command should do the trick:
>>>
>>> qvm-create win10 \
>>> --class StandaloneVM \
>>> --property virt_mode=hvm \
>>> --property kernel='' \
>>> --label=red \
>>> --property memory=4096 \
>>> --property maxmen=4096 \
>>> --root-move-from /home/user/win10-root.img
>>>
>>>
>>>
 How to create a new PVH instead of HVM in Dom0 with the root image from 
 R4.0 ?

 Thank you so much for your help.

 Best regards.

> I think the issue of > 10GB images being truncated via ---root-copy-from 
> during create still exists. See this Issue is still open in the tracker: 
>
> https://github.com/QubesOS/qubes-issues/issues/3422
>
> You'll likely need to qvm-create w/o the root-copy-from, then qvm-grow-root, 
> then copy the image to the right volume listed in /dev/mapper.
>
> See this thread (and choose commands wisely!):
>
> https://groups.google.com/forum/#!topic/qubes-users/vBk-jjvoeT0
>
> Brendan
>
Hi Brendan,

It seems to be the solution to this problem.

I'll test this with caution.

Thank you so much for your help.

-- 
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/944cfb62-b580-df18-207d-8180e09e32fe%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Importing a VM from R3.2 and shortcuts

[GDRUB]

Le 31/08/2018 à 11:00, GDRUB a écrit :
> I'll test this.
>
> In the debian-9 VM:
>
> $ apt-ket exportall > /tmp/keys.txt
> $ qvm-copy-to-vm /tmp/keys.txt
>
> In the debian-8 VM:
>
> $ apt-key import ~/QubesIncoming/debian-9/keys.txt
>
> Le 30/08/2018 à 22:58, GDRUB a écrit :
>> Thank you for those explanations.
>>
>> I have adjusted the documentation on my restored template (debian 8.0).
>>
>> $ qvm-copy /etc/apt/sources.list.d/qubes-r4.list
>>
>> I have bypassed step 4, so I get :
>>
>> W: GPG error: http://deb.qubes-os.org stretch Release: The following
>> signatures couldn't be verified because the public key is not available:
>> NO_PUBKEY 43B760F197CA1BF5
>>
>> How to fix this error ?
>>
>> Le 30/08/2018 à 12:05, Ivan Mitev a écrit :
>>> On 08/30/2018 12:49 PM, gdru...@gmail.com wrote:
 Hi,

 Qubes OS version: Qubes-R4.0

 After restoring VM from a backup (R3.2), all applications have been 
 automatically included in the list of available apps. They appear in the 
 VM’s submenu ("start menu" in dom0).

 When I click on shortcut, the assigned application is not running in its 
 AppVM.
>>> IIRC non working shortcuts were a symptom of using imported R3.2
>>> standaloneVMs/templateVMs.
>>> You should:
>>> - configure your imported R3.2 AppVMs to use R4.0's templates
>>> - or upgrade the imported R3.2 templateVMs:
>>>
>>> https://github.com/Qubes-Community/Contents/blob/master/docs/system/restore-3.2.md
>>>
>>>
 I can start an AppVM only from command line :

 $ qvm-run -a personal terminator

 How can I fix it ?

 Thank you so much for your help.

 Best regards.

ERRATUM

In the debian-9 VM:

$ apt-ket exportall > /tmp/keys.txt
$ qvm-copy /tmp/keys.txt

In the debian-8 VM:

$ apt-key add ~/QubesIncoming/debian-9/keys.txt

It worked like a charm.

Thx Ivan

-- 
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/5e424dde-e868-cf57-f2ab-7a6b0ad67d41%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes-R4.0 : missing argument to qvm-create

[brendan . hoar]

On Thursday, August 30, 2018 at 4:43:42 PM UTC-4, GDRUB wrote:
> Thank you for those explanations.
> 
> However, Windows 10 fails with error code : 0xc225 "a required
> device isn't connected or can't be accessed".
> 
> win10.raw = 96.6 GB
> 
> How to fix this error ?
> 
> 
> Le 30/08/2018 à 11:58, Ivan Mitev a écrit :
> >
> > On 08/30/2018 11:10 AM, gd...@gmail.com wrote:
> >> Hi, 
> >>
> >> I'm trying to run the following command:
> >>
> >> $ qemu-img convert -O raw *.vmdk win10.raw
> >> $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > 
> >> /home/user/win10-root.img
> >> $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from 
> >> /home/user/win10-root.img
> >>
> >> qvm-create: error: unrecognized arguments: --hvm --mem=4096
> >>
> >> Source : https://www.qubes-os.org/doc/hvm/
> > You're using 3.2 commands, see the "R4.0: ..." paragraph below in the doc.
> >
> > The following command should do the trick:
> >
> > qvm-create win10 \
> > --class StandaloneVM \
> > --property virt_mode=hvm \
> > --property kernel='' \
> > --label=red \
> > --property memory=4096 \
> > --property maxmen=4096 \
> > --root-move-from /home/user/win10-root.img
> >
> >
> >
> >> How to create a new PVH instead of HVM in Dom0 with the root image from 
> >> R4.0 ?
> >>
> >> Thank you so much for your help.
> >>
> >> Best regards.
> >>

I think the issue of > 10GB images being truncated via ---root-copy-from during 
create still exists. See this Issue is still open in the tracker: 

https://github.com/QubesOS/qubes-issues/issues/3422

You'll likely need to qvm-create w/o the root-copy-from, then qvm-grow-root, 
then copy the image to the right volume listed in /dev/mapper.

See this thread (and choose commands wisely!):

https://groups.google.com/forum/#!topic/qubes-users/vBk-jjvoeT0

Brendan

-- 
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/d685dd94-3b2d-4363-aa15-c950e6f5991e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Importing a VM from R3.2 and shortcuts

[Ivan Mitev]

On 08/30/2018 11:58 PM, GDRUB wrote:
> Thank you for those explanations.
> 
> I have adjusted the documentation on my restored template (debian 8.0).
> 
> $ qvm-copy /etc/apt/sources.list.d/qubes-r4.list
> 
> I have bypassed step 4, so I get :
> 
> W: GPG error: http://deb.qubes-os.org stretch Release: The following
> signatures couldn't be verified because the public key is not available:
> NO_PUBKEY 43B760F197CA1BF5
> 
> How to fix this error ?

In fedora you have to import the key with rpm, simply copying the file
to /etc/... is not enough. I'm not familiar with debian but the link
below suggests you have to import the key with `apt-get install yourkey'

https://askubuntu.com/questions/291035/how-to-add-a-gpg-key-to-the-apt-sources-keyring



> 
> Le 30/08/2018 à 12:05, Ivan Mitev a écrit :
>>
>> On 08/30/2018 12:49 PM, gdru...@gmail.com wrote:
>>> Hi,
>>>
>>> Qubes OS version: Qubes-R4.0
>>>
>>> After restoring VM from a backup (R3.2), all applications have been 
>>> automatically included in the list of available apps. They appear in the 
>>> VM’s submenu ("start menu" in dom0).
>>>
>>> When I click on shortcut, the assigned application is not running in its 
>>> AppVM.
>> IIRC non working shortcuts were a symptom of using imported R3.2
>> standaloneVMs/templateVMs.
>> You should:
>> - configure your imported R3.2 AppVMs to use R4.0's templates
>> - or upgrade the imported R3.2 templateVMs:
>>
>> https://github.com/Qubes-Community/Contents/blob/master/docs/system/restore-3.2.md
>>
>>
>>> I can start an AppVM only from command line :
>>>
>>> $ qvm-run -a personal terminator
>>>
>>> How can I fix it ?
>>>
>>> Thank you so much for your help.
>>>
>>> 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/54182713-7afe-22e9-7579-ccc50beaf9b7%40maa.bz.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes-R4.0 : missing argument to qvm-create

[Ivan Mitev]

On 08/30/2018 11:43 PM, GDRUB wrote:
> Thank you for those explanations.
> 
> However, Windows 10 fails with error code : 0xc225 "a required
> device isn't connected or can't be accessed".
> 
> win10.raw = 96.6 GB
> 
> How to fix this error ?

Sorry, no idea...

(PS: please do not top post)

> 
> 
> Le 30/08/2018 à 11:58, Ivan Mitev a écrit :
>>
>> On 08/30/2018 11:10 AM, gdru...@gmail.com wrote:
>>> Hi, 
>>>
>>> I'm trying to run the following command:
>>>
>>> $ qemu-img convert -O raw *.vmdk win10.raw
>>> $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > 
>>> /home/user/win10-root.img
>>> $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from 
>>> /home/user/win10-root.img
>>>
>>> qvm-create: error: unrecognized arguments: --hvm --mem=4096
>>>
>>> Source : https://www.qubes-os.org/doc/hvm/
>> You're using 3.2 commands, see the "R4.0: ..." paragraph below in the doc.
>>
>> The following command should do the trick:
>>
>> qvm-create win10 \
>>  --class StandaloneVM \
>>  --property virt_mode=hvm \
>>  --property kernel='' \
>>  --label=red \
>>  --property memory=4096 \
>>  --property maxmen=4096 \
>>  --root-move-from /home/user/win10-root.img
>>
>>
>>
>>> How to create a new PVH instead of HVM in Dom0 with the root image from 
>>> R4.0 ?
>>>
>>> Thank you so much for your help.
>>>
>>> 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/3534b73b-dd58-734e-aed2-e16eb1d6f4da%40maa.bz.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Importing a VM from R3.2 and shortcuts

[GDRUB]

I'll test this.

In the debian-9 VM:

$ apt-ket exportall > /tmp/keys.txt
$ qvm-copy-to-vm /tmp/keys.txt

In the debian-8 VM:

$ apt-key import ~/QubesIncoming/debian-9/keys.txt

Le 30/08/2018 à 22:58, GDRUB a écrit :
> Thank you for those explanations.
>
> I have adjusted the documentation on my restored template (debian 8.0).
>
> $ qvm-copy /etc/apt/sources.list.d/qubes-r4.list
>
> I have bypassed step 4, so I get :
>
> W: GPG error: http://deb.qubes-os.org stretch Release: The following
> signatures couldn't be verified because the public key is not available:
> NO_PUBKEY 43B760F197CA1BF5
>
> How to fix this error ?
>
> Le 30/08/2018 à 12:05, Ivan Mitev a écrit :
>> On 08/30/2018 12:49 PM, gdru...@gmail.com wrote:
>>> Hi,
>>>
>>> Qubes OS version: Qubes-R4.0
>>>
>>> After restoring VM from a backup (R3.2), all applications have been 
>>> automatically included in the list of available apps. They appear in the 
>>> VM’s submenu ("start menu" in dom0).
>>>
>>> When I click on shortcut, the assigned application is not running in its 
>>> AppVM.
>> IIRC non working shortcuts were a symptom of using imported R3.2
>> standaloneVMs/templateVMs.
>> You should:
>> - configure your imported R3.2 AppVMs to use R4.0's templates
>> - or upgrade the imported R3.2 templateVMs:
>>
>> https://github.com/Qubes-Community/Contents/blob/master/docs/system/restore-3.2.md
>>
>>
>>> I can start an AppVM only from command line :
>>>
>>> $ qvm-run -a personal terminator
>>>
>>> How can I fix it ?
>>>
>>> Thank you so much for your help.
>>>
>>> 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/dcc25820-fb85-61af-f136-4f1bc7760bd5%40gmail.com.
For more options, visit https://groups.google.com/d/optout.