search for: e1xgrnn

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: minor In the file /etc/xen/xl.conf there's a suggestion that vif scripts should be named relative to the /etc/xen/scripts directory, which is not the case, since absolute paths have to be used. The manual page xl.conf(5) is also missing. Relevant snippet: # default vif script #vifscript="vif-bridge"

Your message dated Sun, 10 Aug 2014 12:00:17 +0000 with message-id <E1XGRnN-0007ak-6G at franck.debian.org> and subject line Bug#718898: fixed in xen 4.4.0-1 has caused the Debian Bug report #718898, regarding coreutils: cut no longer works with newline as delimiter to be marked as done. This means that you claim that the problem has been dealt with. If this is not the...

Package: xen-utils-common Version: 4.1.4-2 Severity: minor The syntax that the scripts use prevents one from creating a vif named "dev", for example. Attached is a patch for one script, but the syntax that skips using the "dev" keyword is present in other scripts, like vif-bridge. -------------- next part -------------- A non-text attachment was scrubbed... Name:

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal pygrub looks for extlinux config files "/boot/isolinux/isolinux.cfg" and "/boot/extlinux.conf", but the default Debian installation uses the config file "/boot/extlinux/extlinux.conf". (See /usr/lib/xen-4.1/bin/pygrub lines 405-407.) ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing

Package: xen Version: 4.0.1-5.11 Severity: important Tags: security, patch, fixed-upstream http://www.openwall.com/lists/oss-security/2013/11/21/2 Description: An inverted boolean parameter resulted in TLB flushes not happening upon clearing of a present translation table entry. Retaining stale TLB entries could allow guests access to memory that ought to have been revoked, or grant greater

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal The function is_disk_image in /usr/lib/xen-4.1/bin/pygrub at line 45 distinguishes a partitioned disk from a partition by looking for 0xaa55 at offset 0x1fe in the image, but this is the bootsector signature, not the partition table signature. extlinux and other bootloaders put this signature there on bootable partitions (which don't

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal The grub.cfg created by a default Debian installation uses many configuration statements that pygrub does not recognize, and pygrub is unable to find any kernel to load. ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500,

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal pygrub does not recognize the include statement in extlinux.conf. The default Debian installation of extlinux creates a stub extlinux.conf which includes linux.cfg, where all the linux image entries are. This means that even if bugs 697407 and 697409 are fixed, pygrub still can't find the right kernel on a default Debian installation

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Switching to the xl toolstack I expected my configuration to work unmodified, but it doesn't, and I couldn't find any documentation regarding this, since xl.cfg(5) is missing. Original version, used with xm: vfb = ['type=vnc,vnclisten=0.0.0.0:6369,vncdisplay=6369,vncpasswd=x'] Working xl version: vnclisten="0.0.0.0:6369"

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important Tags: security patch When you use xl toolstack, you can't reboot domUs. When you switch back to xm toolstack, than reboot works again. I think the problem with the debian packaged version is the same as in this thread: http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html I also think it's a security issue,

Package: xen-utils-4.3 Version: 4.3.0-3 Severity: important Tags: upstream patch When using Xen compiled with seabios-1.7.4-1 (now in unstable/testing), HVMs fail immediately upon starting with a VCPU triple fault: (XEN) HVM1: Loading SeaBIOS ... (XEN) hvm.c:1253:d1 Triple fault on VCPU0 - invoking HVM shutdown action 1. This is because SeaBIOS can now be greater than 128k, which breaks an