On Wed, Jun 07, 2017 at 02:23:45PM -0700, Vít Šesták wrote: > Boot-time race condition sounds plausibly: > > * It could explain not having this issue on my old laptop (SSD+HDD mix – > Debian's root.img stored on SSD, volatile.img stored on HDD) and having the > issue on the new one (SSD only), despite having almost the same config. (But > I've performed a clean install, so I can't exclude other influences.) > * The VM it works with has somewhat larger /rw/config/rc.local. It performs > various tasks (installing some VM-specific software, adding a new trusted CA, > enabling and starting few services etc.), none of them is directly related to > environment variables. So, maybe either some load or delay in rc.local causes > the race condition to be won. > > Regards, > Vít Šesták 'v6ak'
It does sound plausible. But how is it that a vanilla template on SSD doesnt show the problem? If this were the case I would have thought there would be many reports. If you put a long delay in to rc.local in one of the problematic qubes does that solve the problem? -- 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/20170607221445.GA5307%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
