Re: [qubes-users] Re: HCL DELL PRECISION M4800

[Scott Mason]

Solved:

I have found this and I think it would serve the entire Qubes community 
when checking hardware requirements:

*How do I know if my CPU supports VT x or AMD-V?*

Method 3: Visit Intel’s product specification site. Visit Intel’s product 
specification site (*https://ark.intel.com/* ) and 
follow these steps:

   1. 
   
   Once on the site, enter the processor information you noted above in the 
   search box located on the right-hand side of the page. 
   2. 
   
   Under “Advanced Technologies” on the product page for your processor, *you 
   will see* whether Intel® Virtualization Technology (VT-x) is supported 
   or not.   It will show *Yes* or *No*
   
*If you do this before you purchase or attempt to install Qubes you will 
have some assurance that Qubes will work.*

*My configuration for the *Processor Intel(R) Core(TM) i7-4710MQ CPU @ 
2.50GHz, 2501 Mhz, 4 Core(s), 8 Logical Processor(s) says:

   - 
   
 Intel® Virtualization Technology (VT-x) ‡ Yes 
   - 
   
   Intel® Virtualization Technology for Directed I/O *(VT-d) **‡** No* 
   
*I don't know of other options I can try.  I am sure an expert could tweak 
this.  I just don't have the time.*
On Saturday, August 29, 2020 at 6:20:42 PM UTC-7 Scott Mason wrote:

> Yes.
>
> Both UEFI and Legacy.
>
> I set BIOS to Legacy and try to re-install.  I get:
>
> IOMMU/VT-d/ADM-Vi, Interrupt Remapping  
>
>  i7-4710MQ CPU  
>
> This is a i7 24Mb laptop I bought just for Quebes.  I am going to have to 
> sell this laptop or give up on Quebes.  :/
>
> > Processor Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz, 2501 Mhz, 4 
> Core(s), 8
> > Logical Processor(s)
> > BIOS Version/Date Dell Inc. A14, 5/19/2015
> > SMBIOS Version 2.7 
>
> I don't know what else I can do.  ???
>  
> On Monday, August 24, 2020 at 2:33:16 PM UTC-7 Qubes wrote:
>
>> On 8/24/20 11:03 PM, Scott Mason wrote: 
>> > Saw this post about Dell M4800 working well below. I bought one and 
>> > attempted to install Q ubes 4.0. 
>> > 
>> > I am getting IOMMU/VT-d/ADM-Vi, Interrupt Remapping warning. 
>> > 
>> > It will partially install with the warning(s) above. Depending on the 
>> BIOS 
>> > setting I get 
>> > 
>> > IOMMU/VT-d/ADM-Vi 
>> > HAP/SLAT/ET/RVI warning. somtimes I get both errors 
>> > 
>> > 
>> > Can you suggest any BIOS settings I can change ? 
>> > 
>> > I have set it enable EUFI. 
>>
>> Have you tried with legacy boot, UEFI did not work for me either. 
>>
>> > I have set "Enable Legacy Option ROMs off/on (both) 
>> > I have set "Enable Intel Virtualization Technology enable/disable 
>> (both) 
>> > TPM enabled - does not work. 
>> > 
>> > I can find no combinations that works. 
>> > 
>> > Please help. 
>> > 
>> > 
>> > 
>> > System Manufacturer Dell Inc. 
>> > System Model Precision M4800 
>> > System Type x64-based PC 
>> > System SKU Precision M4800 
>> > Processor Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz, 2501 Mhz, 4 
>> Core(s), 8 
>> > Logical Processor(s) 
>> > BIOS Version/Date Dell Inc. A14, 5/19/2015 
>> > SMBIOS Version 2.7 
>> > Embedded Controller Version 255.255 
>> > BIOS Mode Legacy 
>> > BaseBoard Manufacturer Dell Inc. 
>> > BaseBoard Product 0V5GVY 
>> > BaseBoard Version A00 
>> > Platform Role Mobile 
>> > Secure Boot State Unsupported 
>> > PCR7 Configuration Binding Not Possible 
>> > Windows Directory C:\Windows 
>> > System Directory C:\Windows\system32 
>> > Boot Device \Device\HarddiskVolume1 
>> > Locale United States 
>> > Hardware Abstraction Layer Version = "10.0.18362.752" 
>> > User Name DESKTOP-TPUU4D3\User 
>> > Time Zone Eastern Daylight Time 
>> > Installed Physical Memory (RAM) 24.0 GB 
>> > Total Physical Memory 23.9 GB 
>> > Available Physical Memory 21.7 GB 
>> > Total Virtual Memory 27.8 GB 
>> > Available Virtual Memory 25.6 GB 
>> > Page File Space 3.88 GB 
>> > Page File C:\pagefile.sys 
>> > Kernel DMA Protection Off 
>> > Virtualization-based security Not enabled 
>> > Device Encryption Support Reasons for failed automatic device 
>> encryption: 
>> > TPM is not usable, PCR7 binding is not supported, Hardware Security 
>> Test 
>> > Interface failed and device is not Modern Standby, Un-allowed DMA 
>> capable 
>> > bus/device(s) detected, TPM is not usable 
>> > Hyper-V - VM Monitor Mode Extensions Yes 
>> > Hyper-V - Second Level Address Translation Extensions Yes 
>> > Hyper-V - Virtualization Enabled in Firmware Yes 
>> > Hyper-V - Data Execution Protection Yes 
>> > 
>> > [Hardware Resources] 
>> > 
>> > 
>> > 
>> > [Conflicts/Sharing] 
>> > 
>> > Resource Device 
>> > I/O Port 0x-0x0CF7 PCI Express Root Complex 
>> > I/O Port 0x-0x0CF7 Direct memory access controller 
>> > Memory Address 0xF790-0xF79F Intel(R) 8 Series/C220 Series PCI 
>> > Express Root Port #8 - 8C1E 
>> > Memory Address 0xF790-0xF79F SDA Standard Compliant SD Host 
>> > Controller 
>> > Memory Address 0xF400-0xF4FF NVIDIA Quadro K2100M 
>> > Memory Address 0xF400-0xF4FF P

Re: [qubes-users] No more Qubes available (except dom0) - How do I get them back?

['qubes os' via qubes-users]

Here's the solution: 
https://qubes-os.discourse.group/t/where-is-the-qubes-data-stored/262/17

Thank you all for your help!

unman schrieb am Sonntag, 30. August 2020 um 13:33:00 UTC+2:

> On Thu, Aug 27, 2020 at 02:32:33PM -0700, 'qubes os' via qubes-users wrote:
> > I need help recovering my OS!
> > 
> > When I have fully started QubesOS, only *dom0 is up and ready* for use - 
> > but *no Qube is booted up* whatsoever.
> > 
> > When I then try to start a Qube manually from the Qube Manager, i.e. 
> > "sys-ubs", then I get the error message:
> > 
> > "*volume qubes_dom0/vm-fedora-29-root missing*"
> > 
> > But I did certainly not delete anything from my system, so it cannot be 
> > missing. How can I get this up and running again?
> > 
> > (Btw, I got here because I had the following bug and ran the explained 
> > procedure: https://github.com/QubesOS/qubes-issues/issues/5160)
> > 
> > Thank you very much for any help!
> > 
>
> This tells you that the fedora-29 template is broken.
> You could copy the file from your installation media in to dom0 and
> install it by hand. (If necessary this may require that you allow dom0
> to access the USB devices, or that you boot from a live system.)
>
> Do you have recent backups?
>
> You can access the private data in each qube, as they are stored in
> volumes that you can find under /dev/dm-XXX.
> The familiar names are under /dev/qubes_dom0 - `ls -l` will show you the
> "real" volume under /dev
>
> You can try mounting important private disks and copying out the data,
> to be on the safe side.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/513d3a92-47c1-4d0e-80d2-8c6edc6c6987n%40googlegroups.com.

Re: [qubes-users] No more Qubes available (except dom0) - How do I get them back?

[unman]

On Thu, Aug 27, 2020 at 02:32:33PM -0700, 'qubes os' via qubes-users wrote:
> I need help recovering my OS!
> 
> When I have fully started QubesOS, only *dom0 is up and ready* for use - 
> but *no Qube is booted up* whatsoever.
> 
> When I then try to start a Qube manually from the Qube Manager, i.e. 
> "sys-ubs", then I get the error message:
> 
> "*volume qubes_dom0/vm-fedora-29-root missing*"
> 
> But I did certainly not delete anything from my system, so it cannot be 
> missing. How can I get this up and running again?
> 
> (Btw, I got here because I had the following bug and ran the explained 
> procedure: https://github.com/QubesOS/qubes-issues/issues/5160)
> 
> Thank you very much for any help!
> 

This tells you that the fedora-29 template is broken.
You could copy the file from your installation media in to dom0 and
install it by hand. (If necessary this may require that you allow dom0
to access the USB devices, or that you boot from a live system.)

Do you have recent backups?

You can access the private data in each qube, as they are stored in
volumes that you can find under /dev/dm-XXX.
The familiar names are under /dev/qubes_dom0 - `ls -l` will show you the
"real" volume under /dev

You can try mounting important private disks and copying out the data,
to be on the safe side.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200830113255.GA12213%40thirdeyesecurity.org.

[qubes-users] saltstack: user specific pillars in qubes

[liked2]

Hi!

What's the correct way to use user specific pillars in qubes salt stack?

My pillars are located in
/srv/salt/user_pillar/

To enable during a run them I'm running:
sudo qubesctl --show-output state.highstate --pillar-root=/srv/salt/user_pillar/

This works quite well, but when I'm running it towards a target:
sudo qubesctl --show-output --target myTarget state.highstate 
--pillar-root=/srv/salt/user_pillar/

I receive this error:
ERROR (exception list index out of range)


Any ideas to investigate? Should pillar files be enabled in a different way?


Thanks in advance! P.

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5911fd33-5772-148a-4e0f-77439388621f%40gmx.de.

[qubes-users] Re: No more Qubes available (except dom0) - How do I get them back?

['qubes os' via qubes-users]

No, not the first start of QubesOS at all - I've been using it for several 
years now.

load...@gmail.com schrieb am Sonntag, 30. August 2020 um 11:13:44 UTC+2:

> Is this your first start of Qubes OS after installation? Or you used 
> AppVM's before this problem?
>
> пятница, 28 августа 2020 г. в 00:32:33 UTC+3, qubes os: 
>
>> I need help recovering my OS!
>>
>> When I have fully started QubesOS, only *dom0 is up and ready* for use - 
>> but *no Qube is booted up* whatsoever.
>>
>> When I then try to start a Qube manually from the Qube Manager, i.e. 
>> "sys-ubs", then I get the error message:
>>
>> "*volume qubes_dom0/vm-fedora-29-root missing*"
>>
>> But I did certainly not delete anything from my system, so it cannot be 
>> missing. How can I get this up and running again?
>>
>> (Btw, I got here because I had the following bug and ran the explained 
>> procedure: https://github.com/QubesOS/qubes-issues/issues/5160)
>>
>> Thank you very much for any 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a725685b-fd21-4957-9c5b-93ac8c8a52afn%40googlegroups.com.

[qubes-users] Re: No more Qubes available (except dom0) - How do I get them back?

[load...@gmail.com]

Is this your first start of Qubes OS after installation? Or you used 
AppVM's before this problem?

пятница, 28 августа 2020 г. в 00:32:33 UTC+3, qubes os: 

> I need help recovering my OS!
>
> When I have fully started QubesOS, only *dom0 is up and ready* for use - 
> but *no Qube is booted up* whatsoever.
>
> When I then try to start a Qube manually from the Qube Manager, i.e. 
> "sys-ubs", then I get the error message:
>
> "*volume qubes_dom0/vm-fedora-29-root missing*"
>
> But I did certainly not delete anything from my system, so it cannot be 
> missing. How can I get this up and running again?
>
> (Btw, I got here because I had the following bug and ran the explained 
> procedure: https://github.com/QubesOS/qubes-issues/issues/5160)
>
> Thank you very much for any 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/01cb3e50-a0cd-4afa-92b9-5d1a01c4e8a8n%40googlegroups.com.