[qubes-users] Re: How to qvm-attach VM volume to another VM?
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] Re: Qubes 4.0-rc2 :: VMs fail to start
On Wednesday, October 25, 2017 at 10:26:51 AM UTC-7, [799] wrote:
> Hello,
>
> As at least one other Qubes user has the same problem, that VMs won't start,
> I'll add this as special topic.
>
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot
> the VMs.
> This includes sys-net, sys-firewall, but also others.
>
> I tried to check the logs but I don't get any valuable information.
> See screenshot.
>
> I started the following command in dom0:
>
> watch -n 1 xl list
>
> When I try to launch a VM I can see that the VMs appears in the xl list
> output, but the State is -- and the Time(s) is 0.0.
> After ~30sec the start is aborted with error message: Cannot execute
> qrexec-daemon.
>
> Questions:
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> 2) is someone additionaly running Coreboot?
> 3) I am running the Qubes Installation with the default settings, any options
> to tweak on the Grub command line
>
> [799]
>
>
>
>
>
> Gesendet von ProtonMail mobile
I'm testing Qubes 4.0rc2 on an X230 with SeaBIOS+Coreboot.
I can start sys-net always but cannot start sys-firewall and other VMs
consistently ("Cannot execute qrexec-daemon").
One difference between our setups may be, I am not using the stock Intel wifi
card but an Atheros one instead.
--
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/e83d6b06-1ea7-4343-aef2-c1f7cc2bf8ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: The issue of non-proprietary BIOS and Qubes OS
On Wednesday, June 21, 2017 at 2:23:18 AM UTC-7, Holger Levsen wrote:
> On Wed, Jun 21, 2017 at 09:57:25AM +0200, math blanc wrote:
> > Installing Qubes OS 3.x on a X200 sounds like a bad idea to me, isn't ?
>
> I'd rather choose an x220 or x230, where you can also clean the ME.
Complete removal (atm possible for Intel Core 2 Duo and prior, e.g. X200) is
better than partial removal ("cleaning"), which is the best that can currently
be done for later CPUs (such as on the X220, X230, Purism Librem).
There is some more about this here: [1][2]
But this will be moot in the future since Qubes 4.x doesn't support Core 2 Duo
anyway.
[1] https://mail.coreboot.org/pipermail/coreboot/2017-May/084372.html
[2] Management Engine section of
https://web.archive.org/web/20170404144825/https://minifree.org/product/libreboot-x220/
--
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/e05dd5bb-e66f-4c8b-bce8-90a0a52b9a82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: The issue of non-proprietary BIOS and Qubes OS
Revised list of example systems, with corrections, price estimates, citations. Coreboot with all components open source; fully removed management engine: * Lenovo X200/T400/T500 w/ Coreboot, CPU: T9600 (dual core, each core about 50% of a modern i7-7920HQ [2]). Max 8 GB RAM. Cost: 75 USD used.[4] These systems run Intel Core 2 Duo CPUs, which lack EPT [5], so don't meet Qubes 4.x minimum requirements. Coreboot with open source RAM init but some minor blobs; partially removed management engine: * Lenovo T530 w/ Coreboot. CPU: i7-3840QM (quad-core, each core about 80% of a modern i7-7920HQ core [2]). Max 16GB RAM. Cost: 300 USD, used. [4] * Lenovo W530 w/ Coreboot. Not officially supported, but someone made it work. Max 32 GB RAM. Coreboot with proprietary RAM init; partially removed management engine * Purism Librem 15. CPU: i7-6500U (dual core, each-core about 80% of i7-7920HQ [2]). Max 16GB RAM. Cost: 2000 USD new.[3] * Purism Librem 13. CPU: i5-6200U (dual core, each core about 70% of i7-7920HQ [2]). Max 16GB RAM. Cost: 1700 USD new. [3] For a list of blobs included in Coreboot, see [1]. All the Lenovo systems above require manual Coreboot compiling and an external flasher. The Purism systems can be flashed with coreboot from software (maybe only certain laptop revisions?) and can be preinstalled with Qubes. References: [1]List of coreboot blobs - https://www.coreboot.org/Binary_situation [2]CPU performance comparison - https://www.notebookcheck.net/Mobile-Processors-Benchmark-List.2436.0.html Uncheck "Still available" find the older CPUs. Performance estimates based on Cinebench R10 32 scores. [3]Purism 15 - https://puri.sm/shop/librem-15/ and https://puri.sm/shop/librem-13/ [4]e.g. eBay [5]List of CPUs without EPT - http://ark.intel.com/Search/FeatureFilter?productType=processors&ExtendedPageTables=false -- 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/fb481725-51f7-425d-a60b-254e67ec2b6f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: The issue of non-proprietary BIOS and Qubes OS
Here is Qubes on a Lenovo T400 with Coreboot: https://groups.google.com/d/msg/qubes-users/D9slVaqF1u4/84fFLfuYEwAJ Some additional notes: * Everything I wrote there, also holds for the T500 as well. * Unfortunately, Libreboot still doesn't have the Coreboot IOMMU change yet. * if you build Coreboot without microcode, there may be crashes during high CPU or Windows HVM usage. So you may need to add microcode (by adding ucode=scan to Xen command line). If you are searching for a laptop and care about firmware blobs, here are some example systems: Coreboot with no blobs, no management engine: * Lenovo X200/T400/T500 w/ Coreboot, CPU performance-per-core about 50-60% of Skylake i7-7920HQ. Max 2 cores. Max 8 GB RAM. Coreboot with partially removed management engine, open source RAM init, some minor blobs: * Lenovo T530 w/ Coreboot, high-end configurations have CPU performance-per-core about 70-80% of Skylake i7-7920HQ. Max 4 cores. Max 16GB RAM. * Lenovo W530 w/ Coreboot. Not officially supported, but someone made it work. Max 32 GB RAM. Coreboot with partially removed management engine, proprietary RAM init * later versions of Purism Librem Useful links: List of coreboot blobs - https://www.coreboot.org/Binary_situation CPU performance comparison - https://www.notebookcheck.net/Mobile-Processors-Benchmark-List.2436.0.html Hope this is helpful. -- 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/93441d99-5305-46ad-a8fe-e08649eda39d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
