search for: 703586

close 703586 4.4.1-3 On Sun, Sep 14, 2014 at 04:55:41PM +0100, Ian Campbell wrote: > On Sat, 2014-09-13 at 17:00 +0200, John Keates wrote: > > But having xen.efi in the package would be a ton of help already. Who > > do I stalk to make that happen? > > I'm looking into it already beca...

On Sat, 2014-09-13 at 17:00 +0200, John Keates wrote: > Well, there is one more thing: If kernel 3.17 manages to get in before > the kernel freeze, full-fledged Xen-EFI support will be baked into the > kernel by default! > 3.17 has been patched to provider hypercall support for Xen to get the efivars facility (and pretty much anything and everything else EFI) working for Dom0. >

On Wed, 10 Sep 2014 20:22:54 +0100 Ian Campbell <ijc at hellion.org.uk> wrote: > On Sun, 2014-09-07 at 13:42 +0200, John Keates wrote: > > 1. Rebuild the debian package with a small change > > > > Do your usual apt-sourcing and build-depping, but add the pep target to debian/rules: > > > > (I put it right underneath include debian/rules.defs) > >

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-2 Severity: important I've installed wheezy Linux successfully (ref. bug 703469). Installed xen-linux-system-amd64, with the diversion in http://wiki.debian.org/Xen#Prioritise_Booting_Xen_Over_Native followed by "grub-install". Xen appears to boot (messages go by fast), then I get a blank screen, followed seconds later by a

As an addition to anyone having issues with booting but only getting 1 CPU and a ton of devices that misbehave, check to see if you have an RSDP in Xen and Linux. You should have both (I use xl and not xm): sudo xl dmesg | grep RSDP (XEN) ACPI: RSDP DDA4A000, 0024 (r2 SUPERM) and sudo dmesg | grep RSDP [ 0.000000] ACPI: RSDP 00000000000f0010 000024 (v02 SUPERM) I?m running this on a

On Sun, 2014-09-07 at 00:02 +0200, John Keates wrote: > How do I assist with getting this in for Jessie? > > I have this working in a fairly easy setup, it basically only requires > the pep target to be on for debian?s Xen package, What is "pep"? > and a tiny bit of infrastructure to get xen.efi, vmlinuz, an initrd > and a xen.cfg on to the ESP partition and letting

I?ll explain what?s happening first, and list the steps after that. First: pep is short for the Xen target x86_64-pep. It?s a target you can enable when configuring Xen to create an EFI binary. What is happening with Xen on UEFI via Grub is that it doesn?t give the kernel any info on the ACPI root pointer. Basically, this means that Linux won?t be able to do ACPI, and therefore a ton of hardware

How do I assist with getting this in for Jessie? I have this working in a fairly easy setup, it basically only requires the pep target to be on for debian?s Xen package, and a tiny bit of infrastructure to get xen.efi, vmlinuz, an initrd and a xen.cfg on to the ESP partition and letting the efibootmgr know about it. I already have a oneliner to do this manually, but it isn?t that hard to

I?m so sorry for mailing in a bunch of times, I now see that this is for a different version. The UEFI bug is still valid, but the fix is only for Jessie (Xen 4.4+). Earlier Xen versions have no official EFI patches or support. Sorry! I should probably find the bug report for Jessie + Xen 4.4 where the default setup with EFI and Xen is still broken? It also requires a relatively new kernel (I?m

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703586 Ideas how to move this forward? Debugging techniques? I''m guessing that it''s specific to my hardware, since I''m not seeing anyone else complaining. Anyone else succeed in doing this on an EliteBook?