I’ll pile on top of this: domUs crash with the kernel as well, with a GPF.
Looks like any Xen + 4.9.0-7 = Crash, regardless of it being a domU or dom0.
John
> On 15 Jul 2018, at 21:55, Sebastien KOECHLIN wrote:
>
> Package: src:linux
> Followup-For: Bug #903821
>
> When booting with the new
.
John
> On 1 Mar 2018, at 00:14, Hans van Kranenburg <h...@knorrie.org> wrote:
>
> Hey,
>
> On 02/28/2018 12:59 AM, John Keates wrote:
>>
>> [...]
>>
>> 1. Install Xen with OVMF support
>> 2. Install OVMF (which basically just gets you the
HI Hans,
We probably should update the mailing list anyway since not everybody will be
on GitLab anyway. Here is how you can test it:
1. Install Xen with OVMF support
2. Install OVMF (which basically just gets you the binary file, package is
called ovmf)
3. Get an EFI-bootable image, the
Package: openvswitch-switch
Version: 2.6.2~pre+git20161223-3
Severity: important
Dear Maintainer,
I setup openvswitch-switch with a small number of switches that have one
physical interface each. Upon boot, they get configured extremely slow, taking
over half an hour to get basic networking
Have you tried building the package instead? I find that ‘make install’ often
doesn’t do what you expect when a project is engineered to work as a package.
Try the following:
- run apt-get source and apt-get build-sep as you did
- Edit rules.real in the debian directory, you can add configure
you
can’t boot HVM machines without EFI.
Where would I go to make a request for approval from the release team?
Thanks,
John
> On 29 Mar 2017, at 12:51, Ian Jackson <ian.jack...@eu.citrix.com> wrote:
>
> Control: tags -1 patch
>
> John Keates writes ("Bug#858962: Requ
clear results, I hope it's sufficient.
Regards,
John Keates
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (650, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE
On 23 Jan 2017, at 16:14, Ian Jackson wrote:
>
> Michael Bilow writes ("Bug#852069: DomU guests with pygrub as bootloader do
> not start after, upgrade from Xen 4.1 (wheezy) to Xen 4.4 (jessie)"):
>> Under Xen 4.1 in Debian 7 (wheezy), the following works when
Package: gdm3
Version: 3.14.1-3
Severity: normal
Dear Maintainer,
I upgraded my system from Wheezy to Jessie a few months ago, but as of a few
weeks I cannot
log in to gnome-shell from gdm3 anymore. Changing the session to Gnome on
Wayland does log
me in to a Wayland session, but the normal
On Wed, 10 Sep 2014 20:22:54 +0100 Ian Campbell i...@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
it, I can give it a go, manuals and tutorials everywhere anyway.
John
On 07 Sep 2014, at 08:12, Ian Campbell i...@hellion.org.uk wrote:
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
ACPI. (I don’t really know if
that is true, just thinking out loud)
Another reason why booting might not work is if you have the older e-801 issue.
Both are solved with running Xen without Grub, straight on UEFI.
John
On Sun, 7 Sep 2014 13:42:46 +0200 John Keates j...@keates.nl wrote:
Iíll
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
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
14 matches
Mail list logo