search for: knorri

Knorrie and I just discussed our plans for sid and buster, on the phone. Here's my notes of the discussion. Plan is to upload Knorrie's 4.11 packages to experimental, to make them more public, while we fix the bugs in them. There's a list of Salsa issues and the BTS bugs list. This duplic...

...and kernel team list, Ian Jackson Cc: Stefan Bader, maintainer of xen packages in Ubuntu Hi all, Short version: Hi! I'd like to help with the Xen packaging in Debian. Long version: Q: Who are you? How are you related to Debian an the Xen project? A: Hi, I'm Hans van Kranenburg, nickname Knorrie, I live in the Netherlands. I'm a Debian user since 2002, and have been using Debian and Xen at work (Mendix) since 2006, which has grown from a handful dom0s with 4GiB memory each to a bunch of clusters with let's say somewhere between 10TiB and 20TiB of physical memory in the dom0s toget...

...h has been done to arrive at this point from the previous 4.8 packages is visible at: https://salsa.debian.org/xen-team/debian-xen/commits/master The source package built from that commit (see README.source about how), and signed with my GPG key, ...32180C2A55 is available at: https://syrinx.knorrie.org/~knorrie/xen/ After uploading, we should notify the qemu team to trigger a rebuild of their packages, which will pick up the libxen build dependency. Thanks, Hans -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signatur...

...helping out with xen packaging. I am trying to dig into the dpkg-shlibdeps issues - I built it successfully on one box but haven?t been able to reproduce. Either way, I will plan to hang around in IRC to help where I can. Stephen > On Jan 9, 2018, at 4:05 PM, Hans van Kranenburg <hans at knorrie.org> wrote: > > Hi, > > On 12/22/2017 02:01 AM, Hans van Kranenburg wrote: >> To: Debian xen and kernel team list, Ian Jackson > > I'm replying to my own email, since there has not been a reply on the > lists to it yet. > > For Ian Jackson: There's a...

...d I liked figuring out things while following your hints. ---- >8 ---- I have some additional questions about the way in which I'm creating my own boot images now. I just created a mirror of the pvgrub2 and pvhgrub2 repositories from Mendix into my salsa account: https://salsa.debian.org/knorrie-guest/pvgrub2 https://salsa.debian.org/knorrie-guest/pvhgrub2 The first one, pvgrub2 is what we've been using since 2014. It's a simple debian package, which just build-depends on grub-xen... https://salsa.debian.org/knorrie-guest/pvgrub2/blob/debian/master/debian/control ...which provi...

Package: xen-utils-common Version: 4.17.0-1 Severity: normal Dear Xen Maintainers, xen-utils-common currently ships two /etc/init.d scripts (xen, xendomains) and relies on systemd-sysv-generator(8) to integrate with systemd (Debians default init system). Please improve the integration by providing native systemd unit files. When doing so, you can also take advantage of newer features, like

...use it's my own tool, gbp pq would be better, too, even though it's not as good as git-debrebase.) Particularly, now that we have more people making substantial contributions, it is important to have something that works for as many as possible, and that is low friction for common tasks. Knorrie wrote on irc: ... I only want to discuss it if you have packaging scenarios and want to do them in both ways and then discuss the result, so we can discuss based on actual work/commands/etc instead of feelings Well, I don't propose to actually try doing the same task two different ways...

...ebian-xen/commits/master The only commit which is not in master yet is the actual package release: https://salsa.debian.org/xen-team/debian-xen/commit/7f8ce30800d9a29b3f4a9ad0a88e18c02dd65212 The source package built from that commit, and signed with my GPG key, is available at: https://syrinx.knorrie.org/~knorrie/xen/ If the package gets accepted, I'll merge that commit, and put a tag on it. ---- >8 ---- The current state of the package is "Step 1. Make it work". Besides fixing everything that was needed to make the package build and do useful things after changing to 4.10...

.... * I have built packages for stretch-backports by adding a changelog entry and building with pbuider targeting stretch. Great success. ---- >8 ---- 2. Put the packages in a repository I use reprepro for our own package repos at work. I have a small repo named 'xen' on http://packages.knorrie.org/ that I use for testing xen. When adding the result with reprepro include, this happens: No section specified for 'xen_4.11.1~pre.20180911.5acdd26fdc+dfsg-2~bpo9+1.dsc' in '/home/knorrie/pbuilder/result/4.11-stretch-backports/xen_4.11.1~pre.20180911.5acdd26fdc+dfsg-2~bpo9+1_amd64...

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: important I've a Debian Lenny AMD64 as production server, where it has important HVMs that runs correctly. The problem occurs when i try to create a HVM from a Debian Squeeze AMD64 iso file. At first, the VNC display specified shows perfectly the Debian Installer menu, but when I choose an option (Install or Graphical Install),

Package: xen Severity: important User: bluca at debian.org Usertags: missing-systemd-service Dear Maintainer(s), xen has been flagged by Lintian as shipping a sysv-init script without a corresponding systemd unit file. The default init system in Debian is systemd, and so far this worked because a transitional sysv-init-to-unit generator was shipped by systemd. This is in the process of being

This is awesome! What needs to be done before this can make it to unstable? I’d love to help if there’s anything I can do. Stephen On Fri, Oct 5, 2018 at 8:00 PM Hans van Kranenburg <hans at knorrie.org> wrote: > On 10/05/2018 08:04 PM, Ian Jackson wrote: > > I have now finished totally rewriting the Xen package in Debian, from > > scratch. Amazingly as soon as I got a package which was lintian-clean > > and would install, it worked first time ! > > \:D/ Congra...

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: critical Justification: breaks the whole system Dear Maintainer, -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8,

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal When a DomU is defined as using a file: device the loopback driver will be used to make it appear to be a regular block device. The loopback driver will by default only support 8 nodes so this is a limited resource. http://etbe.coker.com.au/2008/10/22/kernel-issues-with-debian-xen-and-centos-kernels/ If there is a problem that prevents

Hi Colin, Thanks for the quick reply. On 1/5/19 8:04 PM, Colin Watson wrote: > On Thu, Jan 03, 2019 at 01:02:47AM +0100, Hans van Kranenburg wrote: >> In december, Xen PVH support has been committed in grub master: >> https://www.mail-archive.com/grub-devel at gnu.org/msg28125.html >> >> The last pieces needed in the Linux kernel to boot PVH with grub2 landed >>

Hans van Kranenburg writes ("Re: [PATCH 08/13] xen init script: rewrite xenstored start logic"): > So the question we should answer first is: What do we allow the user to > set as value? /bin/bash? And how should the init script deal with that? If they specify an absolute path, it should be used. Eg, /home/alice/Xen/xen/tools/xenstore/xenstore If the user specifies /bin/bash

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u4 Severity: important Dear Maintainer, I installed a fresh Debian Jessie amd64 on our new server with Intel Xeon E3-1270 v5 Skylake CPU and EFI. Linux without Xen boots flawlessly and shows 8 CPU cores. I then tried all combinations of Xen 4.4 (with xsave=off for Skylake support), Xen 4.6 (crashes after a few seconds during boot) and

Initially out there as #965245. I strongly prefer to build ARM64 packages on non-ARM systems. Something about my main build machine having twice the cores and twice the clock speed. As such after many builds I've managed to generate a set of patches which appear to mostly function to get functioning cross-builds of Xen. These are NOT a 100% solution. Some packaging hacks were needed. In

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: normal With SE Linux it's desirable to give utilities and daemons the minimum privileges. That includes not permitting general utilities to create directories under /var/run. I think it would be best if /var/run/xen-hotplug was created by an init script such as /etc/init.d/xen (or by systemd-tmpfiles when using systemd units).

Package: xen-system-amd64 Version: 4.6.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, I installed fresh from ALPHA5, no UEFI, with two disks. Each disk got a partition for /boot and one for /, joined each by RAID 1. Then I just installed "xen-system-amd64", nothing more. After rebooting, selecting on grub to boot XEN, it hangs on mdadm: no devices