similar to: Bug#799986: xen-utils-common: please create /var/run/xen-hotplug from an init script

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

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

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 duplication is not ideal. We agreed that new things should go to the BTS. For now we'll keep

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),

On Mon, Jan 07, 2019 at 08:44:50AM +0000, Colin Watson wrote: > On Mon, Jan 07, 2019 at 01:58:19AM +0100, Hans van Kranenburg wrote: > > Ok great. Since I'm not using (and probably not going to use) the > > multi-stage multiboot things, this is harder for me to help with. > > With any luck I should be able to work that bit out myself, since I > think stable's Xen

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 ! I have generated 18 patches to go upstream which I have sent to xen-devel. There are two more, xenstore ABI patches, which need a bit of tidying up. There is still room for improvement but it is now clearly ready

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 >>

Package: src:xen Version: 4.11.1-1 Currently, these are rdepends: -$ apt-cache rdepends libxenmisc4.11 libxenmisc4.11 Reverse Depends: libxen-dev xen-utils-4.11 collectd qemu-system-x86 libvirt-daemon collectd-core It's on the wishlist to start doing buster-backports for Xen. If the user has a cluster of servers and can make use of live migrate, then this allows the user to

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,

Hi Ian, after our conversation on IRC in #debian-xen today, I updated the packaging to the latest 4.10-stable commit (since there's no 4.10.1 release yet) and smoke-tested the package on a testing/unstable dom0 running a PVHv2 guest. Can you please review and sponsor the upload of a first Xen 4.10 package to Debian unstable? The work which has been done to arrive at this point from the

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Under this Xen setup, (Linux) HVM guests fail to have network active when running with *routed* networking, as some hosting providers require (in my case, OVH). In this scenario: * the host is a described below * the guest runs as HVM. * the guest runs exclusively with ioemu; virtual network drivers are not available (vanilla lenny

Hans van Kranenburg writes ("Re: Plans for buster"): > On 08/23/2018 07:12 PM, Ian Jackson wrote: > > IDK if this > > should have its own deb. Putting it in the libxenstore one is > > probably tolerable. > > Yes, shipping a 4.x specific file in libxenstore3.0 (which happens now) > is not right. But, if the library ABI is independent from the 4.x >

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

Hi, On 02/22/2018 01:03 AM, John Keates wrote: > > First of all, thanks for the great work! I was wondering about a patch I tried to send in a while ago which enables OVMF. It?s a single line in the rules setup and doesn?t have any build-time or run-time dependencies until you actually change a domU configuration to use OVMF. > > Currently I just rebuild all packages locally and add

On 1/6/19 11:21 AM, Colin Watson wrote: > On Sat, Jan 05, 2019 at 10:51:13PM +0100, Hans van Kranenburg wrote: >> On 1/5/19 8:04 PM, Colin Watson wrote: >>> I think I'm OK with cherry-picking the relevant patch stack. Presumably >>> this would need to be in new grub-xen-pvh-bin / grub-xen-pvh binary >>> packages, as is usual for separate platform builds?

Package: xen-hypervisor-4.6-amd64 Version: 4.6.0-1 Severity: normal Dear maintaners, I was using XEN 4.4 on that machine ("unstable") and want to switch to 4.6. All xen stuff was uninstalled (XEN 4.4), the machine restarted before installing 4.6. When I uninstall XEN 4.4 (libxenlight4.4) it deinstall also part of QEMU and when I reinstall QEMU libxenlight-4.4 aws reinstalled. First

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u4 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Running Backup Exec or a copy command to NFS-Share causes the VM regurarly to freeze. First message on VM-Console: ---------------------------------------------------------------------------------------------------------------

Hans van Kranenburg writes ("Re: Plans for buster"): > This can be done from tag debian/4.11.1_pre+1.733450b39b-1_exp1 (which > is right now the same as the master branch). Thanks for doing all this work. I have just sent it to experimental. I did some reviewing and diffing. I have some comments, or, at least, things I noticed. None of them were IMO blockers for experimental.

Package: xen-utils-common Version: 4.0.0-1 Severity: important After running modules_setup you need to have the following line: [ -x /sbin/restorecon ] && /sbin/restorecon -R /dev/xen The reason is that the module load causes the kernel to create device nodes in the devtmpfs. This bypasses the udev code for labelling the device node and results in xenstored being unable to access

Hi Ian, team, In the week of Feb 23 (time flies!:), we had a very productive day \o/ working on the stretch security/stable package and some irc discussions in oftc #debian-xen which ended with an open end. Ian, you were a bit surprised that 1) my debian-xen repo started with an import of a 4.8 package 2) it was not a git-pbuilder style repo with upstream source included, and asked me to at