similar to: New CVE for Xen

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: grave Tags: squeeze sid Justification: causes non-serious data loss Live migration of a guest (running CentOS 5.5, Paravirtualized) crashes the target-host (Hardware: Dell R610, 2x Xeon 5620, 16Gb RAM, Perc/700-Raid) (XEN) ----[ Xen-4.0.1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 9 (XEN) RIP: e008:[<ffff82c4801151f6>]

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.

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

Package: xen-3 Version: 3.1.0-1 Severity: grave Tags: security patch Hi, the following CVE (Common Vulnerabilities & Exposures) id was published for xen-3. CVE-2007-5907[0]: | Xen 3.1.1 does not prevent modification of the CR4 TSC from | applications, which allows pv guests to cause a denial of service | (crash). CVE-2007-5906[1]: | Xen 3.1.1 allows virtual guest system users to cause a |

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

Package: xen Severity: grave Tags: security Please see http://www.openwall.com/lists/oss-security/2012/07/26/4 Cheers, Moritz

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: serious Tags: squeeze Hi there! Upgrading from Lenny to Squeeze left my box with xen-hypervisor-3.2-1-amd64 installed, and I had to "apt-get install xen-hypervisor-4.0-amd64" manually to have it installed after a dist-upgrade. This for sure, isn't the expected behavior. Also, after the dist-upgrade, I did: apt-get

Hi, I just upgraded to the latest SID after reinstalling my test server. Then, after a while, during the boot process, Xen seems to hang, then my server reboots. It's difficult for me to see anything, since I'm using a KVM over IP, using a quite slow link (from China to UK, using a FreeNX box that connects through a Java KVM over IP to the server), and I don't think it'd be easy

On 09/08/2014 04:59 PM, Chrysostomos Nanakos wrote: > On 2014-09-08 10:07, Thomas Goirand wrote: >> On 09/07/2014 01:44 AM, Chrysostomos Nanakos wrote: >>> dget -x >>> >>> http://mentors.debian.net/debian/pool/main/b/blktap/blktap_2.0.90-3.dsc >> >> Uploaded! Thanks for your contribution to Debian. >> >> Cheers, >> >> Thomas

Package: xen-utils-common Version: 4.1.2-4 Severity: serious Upgrading xen-utils-common from 4.1.2-2 to 4.1.2-4 fails with the following output: root at node4407:~# dpkg -i xen-utils-common_4.1.2-4_all.deb (Reading database ... 64228 files and directories currently installed.) Preparing to replace xen-utils-common 4.1.2-1 (using xen-utils-common_4.1.2-4_all.deb) ... insserv: Service xend has to

On 09/09/2014 05:15 AM, Nanakos Chrysostomos wrote: > On 08 ??? 2014, at 22:31, Thomas Goirand <zigo at debian.org> wrote: > >> On 09/08/2014 04:59 PM, Chrysostomos Nanakos wrote: >>> On 2014-09-08 10:07, Thomas Goirand wrote: >>>> On 09/07/2014 01:44 AM, Chrysostomos Nanakos wrote: >>>>> dget -x >>>>> >>>>>

On 08 ??? 2014, at 22:31, Thomas Goirand <zigo at debian.org> wrote: > On 09/08/2014 04:59 PM, Chrysostomos Nanakos wrote: >> On 2014-09-08 10:07, Thomas Goirand wrote: >>> On 09/07/2014 01:44 AM, Chrysostomos Nanakos wrote: >>>> dget -x >>>> >>>> http://mentors.debian.net/debian/pool/main/b/blktap/blktap_2.0.90-3.dsc >>>

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

Package: blktap-dkms Version: 2.0.91-1 Severity: normal After an update of the kernel in SID, I have noticed that blktap-dkms didn't automatically rebuild itself when I upgraded my server with a newer kernel version. My understanding is that it should have. Also, doing dpkg-reconfigure blktap-dkms or reinstalling the package did make it rebuild the kernel module. Thomas Goirand (zigo) --

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

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: normal Tags: upstream When creating Xen DomU's, at some point xend invokes the oom-killer and the entire machine restarts: Sep 5 12:04:59 arbiter kernel: [259697.101212] __ratelimit: 136 callbacks suppressed Sep 5 12:04:59 arbiter kernel: [259697.101218] xend invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0 Sep 5

Package: xcp-networkd Version: 1.3.2-13 Severity: serious If apt-get was used to install xcp-networkd instead of dpkg -i, then the debconf value selected for network-type wasn't respected. In other words, the users does: apt-get install xcp-networkd then selects "bridge" in debconf, then it's "openvswitch" which appears in /etc/xcp/network.conf instead of bridge.

Hi folks. We were made aware of a MITRE CVE assignment on OpenSSH for a remote DoS in sftp, described as: The (1) remote_glob function in sftp-glob.c and the (2) process_put function in sftp.c in OpenSSH 5.8 and earlier, as used in FreeBSD 7.3 and 8.1, NetBSD 5.0.2, OpenBSD 4.7, and other products, allow remote authenticated users to cause a denial of service (CPU and memory consumption) via