On Sun, Nov 20, 2016 at 8:44 PM, Drew White <[email protected]> wrote: > How do I reproduce the issue on upstream XEN when I run Qubes and keep > working and doing my stuff without wasting several weeks on testing it on > upstream XEN?
I don't know, but seeing as you're the only person who reports experiencing this issue, nobody else can test things to try to narrow it down for you. > Qubes is downstream XEN I assume from what you are saying, which means that > the version of XEN that Qubes uses is modified in some ways? > Which means that it's a different version of XEN altogether? Well, Qubes uses a slightly patched Xen -- the applied patches can be found here: https://github.com/QubesOS/qubes-vmm-xen My suggestions for you at this point: 1) Post your output of: $ cat /etc/qubes-release $ xl dmesg | head -1 to this list 2) See if there's any way you can get a serial console on your machine. Either via Intel AMT (definitely easiest if supported) or perhaps via an internal serial header someplace (if you have the necessary hardware and technical inclination) to see if xen produces any useful log output while it is actually hanging. Make sure your xen loglvl=all while doing so (which should be already set by the qubes installer). 3) Provide a full detailed description of the behavior you exhibit to the xen-users list. (And the first thing they will probably ask is if you can still reproduce the issue with the latest upstream un-patched Xen...) -- 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/CABQWM_AS9C1CZ0wtP-ZPnM7%3Ds9jMEiO_%2BwqbQ3yFB3M8TG6N4g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
