-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Thu, Aug 04, 2016 at 01:45:58PM -0700, [email protected] wrote: > Hi, > > this is just a heads-up about a preliminary work I've been doing to get Xen > 4.7.0 working on Qubes 3.2 rc2 (mainly motivated to see if any of the > massive amount of changes would have any effect on PCI/GPU passthrough). > > VMM-XEN: > https://github.com/WetwareLabs/qubes-vmm-xen/tree/xen-4.7 > > Most changes are straightforward modifications of Qubes patches > (surrounding lines in original files been changed and this causes patching > to fail). Some patches required a little bit more tinkering And few changes > were made to the build process.
Thanks! It's too late to have it in R3.2, but we surely want Xen 4.7 in Qubes 4.0. > Also Libvirt, libvchan and gui-daemon needed minor changes: > > https://github.com/WetwareLabs/qubes-core-libvirt/tree/xen-4.7 Take a look at core3-devel branch on my github - there is already libvirt 2.0.0. > https://github.com/WetwareLabs/qubes-core-vchan-xen > https://github.com/WetwareLabs/qubes-gui-daemon > > > With these modifications, it builds ok (in Fedora 23 AppVM on Qubes 3.1) > and can be installed from ISO. However there's now something wrong with > gui-daemon (I suspect): > VMs will start, but if any application (xterm for example) is started, the > green dot on QubesManager changes to yellow, and no window is created. If > another app is launched, then a window briefly flashes and closes again. > Every time this happens, there's this log (in guid.sys-firewall.log for > example): > ErrorHandler: BadValue (integer parameter out of range for operation) > Major opcode: 130 (MIT-SHM) > Minor opcode: 3 (X_ShmPutImage) > Value: 0x1f5 > Failed serial number: 88 > Current serial number: 89 Looks like your X server don't have shmoverride preloaded, or its startup failed. Check stderr of X server - if started from lightdm, it will be in /var/log/lightdm/x-0.log. > But with qvm-run I can run commands properly in this VM. > I tried looking into gui-daemon code, but it seems this error is created > somewhere else outside of gui-daemon (it's only catched by the daemon). > > Also there this line in libxl-driver.log: > libxl:error: libxl.c:1840:libxl_console_tty: unable to read console tty > path '/local/domain/4/console/tty': Function not implemented. > > But this appears at some point during/after boot, and I don't know if it's > related to this bug. The same is on Xen 4.6, harmless. > I didn't dare to make a pull request on GitHub, since this is currently in > broken state. But if you're moving to use 4.7.0 at some point (maybe Qubes > 4.0?), feel free to use this to avoid duplicate work :) :) - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXo7pyAAoJENuP0xzK19csDMcH/10g+19GhEUDCOxuHa64Tg57 DgQePoZ6PGEVDODoeoL0yeKrbPqGfDFVs2qyoRx0Dy3fHwn40D8O3jtIRfW+FYb+ MuLV0+1YcY44KSjgl+anGwmyg5yEbQypuM7/d5WClFavOyx0EJxUxWE4lDyoDNxi NVfK83DnhT2qGOElF3wi7FHsZ9cW0U9u7pAaAqLddw5yj8af+pZaSxkIVcoNTS34 6qa8loHcNICc/guzf+wvHEaGovsh5SZjWKtj03PL/Mpt/7QhmxSbrt2t6H4y4imv mvdWJ0fttCPjseDSd+Jlkv4yKF2kDFOz/U6LWgtlmPFHFFafaazjfkmEx8p7mus= =QYAU -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "qubes-devel" 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-devel/20160804215809.GI32095%40mail-itl. For more options, visit https://groups.google.com/d/optout.
