A while back I used an extremely simple fix for a similar issue, which may or may not work in this specific situation described.
In my case I had assigned a network card/controller to the Sys-Net VM, which Qubes hated so much compatibility-wise that it subsequently refused to boot altogether, simply because attempt to initialize that net card caused such catastrophic failure on startup that the entire OS became non-startable. However, since devices assigned to VM's have specific serial identifiers that Qubes is looking for on bootup to assign to chosen VM, and since Qubes was in this case itself installed on a flash drive, it stood to reason that by simply booting it on a completely different laptop which did not have that relevant network card and serial number present, Qubes would simply ignore the requested assignment and boot normally, with no network card (not even the one in the second laptop) assigned to Sys-net upon boot completion. And this is exactly what happened. >From there, with system successfully booted on second laptop without problem >card, it is/was still necessary to use Qubes Manager to graphically edit >settings for that Sys-net VM, and look in its list of assigned devices, which >*appears* empty but is not really (because a non-present device is still >assigned to it "invisibly"). Because of this, it was needed to click the >"unassign all" button (two arrows pointing left: << ) and then save settings, >so that even non-visible/present devices (the problem card) became unassigned >to that Sys-Net VM. After that, I shut down and placed Qubes flash drive back in original laptop, booted, and everything worked fine. Problem network card was back to Dom0 and not assigned to Sys-Net, and all worked fine (with no networking, obviously, but still usable system). This approach may or may not work for de-assigning USB controller from USB-VM, since when booted on a different laptop, that specific USB controller won't be found, and the assign request will be ignored, and you can unassign-all-devices from USB-VM on that second laptop, before shutting down and then booting again on original machine. Like I said, possibly this tactic won't work for some unpredictable reason, but it worked in my case when network card was the "accidentally" assigned device causing non-startable system. -- 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/9e824b5b-bae7-4e15-b49a-d5191adfb453%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
