similar to: Please review control changes

On Sat, May 02, 2015 at 07:04:34AM +0200, Salvatore Bonaccorso wrote: > the following vulnerability was published for xen. I consider this issue as unimportant. Not sure how I can mark it this way in the security tracker. Bastian -- Knowledge, sir, should be free to all! -- Harry Mudd, "I, Mudd", stardate 4513.3

Hi folks PV-GRUB built from Xen 3.3.0 is not able to read from devices without a partition table: | grubdom> root (hd0) | Filesystem type unknown, using whole disk Part of the config: | disk = [ "phy:vg0_sledgehammer/servext_root,xvda,w" ] Device: | # file -s /dev/vg0_sledgehammer/servext_root | /dev/vg0_sledgehammer/servext_root: symbolic link to

Hello, I have an annoying little issue. I am currently running Samba 2.2.5-10 as a Primary Domain Controller and have a number of shared drives with a variety of differing users and user rights all over the place. In my smb.conf file, I have the following share: [emergpo] path = /share/purchasing/emergpo force directory mode = 0770 create mode = 0770

Source: xen Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 Severity: important - x86: Make asmlinkage explicitly a no-op, and avoid usage in arch/x86 Build-fix, done different in Debian. - tools/ocaml: Fix 2 bit-twiddling bugs and an off-by-one Relevant for xcp. - x86_64: Fix off-by-one error setting up the Interrupt Stack Tables Hypervisor code running with wrong stack. Breaks error handling

Whoops, wrong recipient. On Thu, Jun 10, 2010 at 05:54:28PM +0200, Bastian Blank wrote: > I'm currently thinking about which version of Xen supporting in Squeeze. > There are two possibilities: 3.4 and 4.0. 3.4 is currently in testing > and unstable, 4.0 is in experimental. > > Xen 3.4 > ======= > Pros > - Proofed to be stable > Cons > - NUMA-mode only opt-in,

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

# HG changeset patch # User Bastian Blank <waldi@debian.org> # Date 1204887078 -3600 # Node ID 5fb1c83d7ec89eb83c7c32eb7ee3b7a6b796478f # Parent 968faff41008504641c5cb700c4e83c6aaa3c009 Remove deprecated and unused features from LaTeX source. Signed-off-by: Bastian Blank <waldi@debian.org> diff -r 968faff41008 -r 5fb1c83d7ec8 docs/src/interface.tex --- a/docs/src/interface.tex Fri

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Dear Maintainer, i changed toolkit to xl, after that i observe that my domU started as HVM domains. I found same problem here: http://mail-index.netbsd.org/port-xen/2012/04/11/msg007216.html When i manualy setup loop devices and specify it as disks in my VM conf file, domU started as PV. -- System Information: Debian Release: 7.1

I''m trying to get ceph working with decent performance (currently getting kb/second write performance!) and it seems that maybe the Debian wheezy kernel is just a bit too ancient. The 3.8 kernel from experimental works on bare metal, but when booting as dom0 under the xen hypervisor it crashes. I just figured out how to redirect xen output to my IPMI/BMC serial port and I see this:

Hi folks XenSource published a trademark policy[1]. I don't think we will be able to follow it if we want to support installation of different versions at the same time. Bastian [1]: http://www.xensource.com/company/legal.html -- There are some things worth dying for. -- Kirk, "Errand of Mercy", stardate 3201.7 -------------- next part -------------- A non-text attachment was

Hi folks With the lack of responses to my restructuring the last weeks, it looks like pkg-xen is dead. Now, what to do? My favorite is to merge it into the kernel repository where I have my infrastructure (archive and autobuilders for snapshots for example) to properly work on it. Bastian -- No one wants war. -- Kirk, "Errand of Mercy", stardate 3201.7 -------------- next part

Hi folks Some proposed changes: * Fixiate the API/ABI of some libs, for the stable version, including - libxenctrl, - libxenstat, - libxenstore. As upstream don't know what abinames are for, roll own abinames. * Add libxenctrlX, libxenstatX, libxenstoreX, if abinames may be different or libxenX if the abinames should the same for all libs. * Add libxen-dev including - static

Hi folks I propose the following changes for 3.1: - Rename source to xen-3. Upstream stripped one part of the version, so the next should be 3.2. - pygrub as extra package. - Rename i386 to i386-nonpae - Rename i386-pae to i386. PAE is upstream default now and pae images works with a 64bit hypervisor. We should think about supporting libvirt. It provides an AFAIK stable interface on the

Source: xen Version: 4.4.1-9 Severity: normal Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for xen. CVE-2015-3340[0]: | Xen 4.2.x through 4.5.x does not initialize certain fields, which | allows certain remote service domains to obtain sensitive information | from memory via a (1) XEN_DOMCTL_gettscinfo or (2) | XEN_SYSCTL_getdomaininfolist request.

Hi folks The current package in unstable is able to use xl. It is still a bit edgy but seems to work. Because the old xm with xend and xl clashs and one should only use one, this needs some more setup to provide a proper upgrade path. I propose the following: - Add a script "xen" that wraps xl and xm depending on the config for use by all the scripts. Most parts are command line

Package: xen-utils-common Version: 3.4.2-2 Severity: important The network setup uses not longer supported iptables operations: | physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, "Day of the Dove", stardate

On Sun, Apr 26, 2015 at 10:50:16AM +0200, Daniel Pocock wrote: > On 26/04/15 10:45, Bastian Blank wrote: > > Well, if you can pursuade the release team. We have grub2 for Xen > > in Jessie now and it can be used on Wheezy as well. > Can you be more specific? If somebody is running a wheezy dom0 and > they install grub2 in their domU before rebooting it the first time, >

Hi folks I tried to find a solution for the update problem. Currently I have 3 kernels, 2.6.16-16, 2.6.16-17 and 2.6.17-6 and each of them needs another hypervisor. As it is the goal of Debian to not break on updates completely, I propose the following change: * Introduce xen-common source which provides xen-utils-common binary packages. This package provides a dispatcher for the installed

Hi folks There are two components, which are currently not included in the main utils package: ioemu, xenfb. ioemu is currently shipped in its own package, xenfb is not shipped at all. Should we fold them into the main utils package for simplicity? ioemu adds 300k to the package and 4300k in one dependency (libsdl1.2debian). xenfb adds another 200k to the package and 200k in one dependency

Hi I finally did the merge for Xen 4.0. For this I decided to rename the source package back to xen. The packages are available via http://hermes.jura.uni-tuebingen.de/~blank/debian/xen-test. ec1482e14f2515bd6878da0d2229b725993601fa libxen-dev_4.0.0-1~experimental.1_amd64.deb 7c394f7158ca387225935f3bbe26bdc5518a1934 libxenstore3.0_4.0.0-1~experimental.1_amd64.deb