On Thu, Aug 4, 2016 at 4:45 PM, <[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. > > Also Libvirt, libvchan and gui-daemon needed minor changes: > > https://github.com/WetwareLabs/qubes-core-libvirt/tree/xen-4.7 > 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 > > 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. > > 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 :) > > Br, > Marcus >
would you happen to have an iso i can test as I am one of the users that cannot use Qubes right now due to pci passthru issues for greater then 6+ months being unresolved. > > -- > 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/0f8acb48-7dd6-4b2c-bc59-768836c02b9f%40googlegroups.com > <https://groups.google.com/d/msgid/qubes-devel/0f8acb48-7dd6-4b2c-bc59-768836c02b9f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAKYr3zxF%2BFA2FvC3k0H05W9t%2B65Jtm60bM-_MwX0%2Bt8xFvE1Rg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
