similar to: Bug#503046: xen-utils-3.2-1: inadequate error handling for the case of a failure to use a loopback device

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

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

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-utils-common Version: 3.2.0-2 Severity: normal When file: sources are used for Xen block devices the Xen system will use a loopback device for each one. It's quite common for DomUs to be configured with two block devices (one for storage and one for swap) and not uncommon to have a block device for each filesystem (which makes it easier to grow filesystems). Therefore the

Package: xenstore-utils Version: 4.0.1-2 all it says is: "Description: Xenstore utilities for Xen This package contains the Xenstore utilities." Wow, i never would have guessed that a package called xenstore-utils might contain Xenstore utilities. I'm glad that's cleared up! that just leaves a few tiny, niggling questions: 1. WTF are the Xenstore utilities? 2. What are

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

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

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

Is it expected that running btrfsck more than once will keep reporting errors? Below is the end of a btrfsck output when run the second time. backpointer mismatch on [111942471680 32768] owner ref check failed [111942471680 32768] ref mismatch on [111942504448 40960] extent item 1, found 0 Incorrect local backref count on 111942504448 root 5 owner 160739 offset 3440640 found 0 wanted 1 back

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal When a block device name is wrong (the device does not exist) it should say "block device /dev/foo/bar does not exist" instead of waiting for ages and giving the following error: Using config file "/etc/xen/ha2". Error: Device 768 (vbd) could not be connected. Hotplug scripts not working. Also the following parsing

Package: xen-utils-4.4 Version: 4.4.1-9 Severity: normal # /usr/lib/xen-4.4/bin/xl create -c /etc/xen/katana Parsing config from /etc/xen/katana libxl: error: libxl_utils.c:217:logrename: failed to rotate logfile - could not rename /var/log/xen/qemu-dm-katana.log.6 to /var/log/xen/qemu-dm-katana.log.7: Permission denied Segmentation fault The above happens repeatably when I run xl on a system

It was suggested to me that I forward this message to you. ---------- Forwarded Message ---------- Subject: privsep in ssh Date: Fri, 19 Sep 2003 12:22 From: Russell Coker <russell at coker.com.au> To: SE Linux <selinux at tycho.nsa.gov> Cc: Colin Watson <cjwatson at debian.org> #ifdef DISABLE_FD_PASSING if (1) { #else if (authctxt->pw->pw_uid == 0 ||

- This minor patch implements the missing stub function security_label_to_details in the dummy module. This stub function is necessary to create domains with network interfaces for modules that do not implement the security_label_to_details function. Signed-off-by: George Coker <gscoker@alpha.ncsc.mil> _______________________________________________ Xen-devel mailing list

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave Justification: renders package unusable qemu-dm sends out this: - supported machines are: pc Standard PC (default) isapc ISA-only PC - instead of: - Supported machines are: xenfv Xen Fully-virtualized PC (default) xenpv Xen Para-virtualized PC - this renders any tries to use HVM fail. -- System Information:

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal When my domU uses this configuration: --- root = '/dev/sda2 ro' disk = [ 'phy:/dev/volume0/lenny.vandervlis.nl-swap,sda1,w', 'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w', ] --- Pygrub gives the error "Error: Boot loader didn't return

Package: logcheck-database Version: 1.2.25 Severity: normal postfix/smtpd\[[0-9]+\]: lost connection after (CONNECT|DATA|RCPT|RSET|EHLO|HELO|MAIL) from Please include the above line in the ignore.d/server/postfix file. That catches messages that occur very often on busy Postfix servers. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable')

All, similar to some mail threads found in this forum and some other xen-related threads, I had problems with the network performance of my test system: * software base of dom0/domU: RHEL5 (Xen 3.0.3, Redhat 2.6.18-8el5xen SMP kernel) * ibm x306 servers with 3Ghz P4 /MT support; coupled via Gigabit Ethernet switch * standard xen bridging network configuration * test tool: iperf * Xen