To clarify my original post/question: What does Qubes use from the physical machine's properties to set up an installation? I could not find any documentation on the site about this in the Wiki (I'm happy to contribute it to the Qubes wiki, if it can be explained here).
Some ideas I have that might cause issues with a single installation used across multiple configurations. - # of cores are used to pre-set all VMs to # of vCPUs (e.g. like Docker does) - amount of Memory used to pre-set all VMs to certain percentages (with a min). use swap for the rest. But, I don't know if Qubes does this or not. Could be plausible though, if it did read these values. I have one installation that uses the USB VM, and I think that is perfect. I can write custom scripts with that VM to look for and mount certain things depending on if they present or not (Logitech webcam on desktop, not on macbook pro, etc). As for the # of cores/memory, I could write a script in dom0 that would "adjust" the VMs according to the system properties, before they start. That doesn't seem like a big deal either. What I'd like to know if there is anything else specific, like graphics drivers or device drivers that are detected, installed and enabled as per the installation. Like, is there a specific Xen installation done on Qubes install? Thanks! Eric -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9177a7d9-99c1-4b34-b676-e8761e090971%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
