similar to: Bug#491793: xen-hypervisor-3.2-1-i386: should update GRUB with a trigger

Howdy, The following bug in Markdown was reported to the Debian bug tracking system. ----- Forwarded message from Pierre THIERRY <nowhere.man@levallois.eu.org> ----- From: Pierre THIERRY <nowhere.man@levallois.eu.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: Bug#368413: markdown: two lists without separating text are messed up Date: Mon, 22 May 2006

Package: xen-hypervisor-3.2-1-i386 Version: 3.2.0-4 Severity: important in etch there was an automated generated entry in the menu-list of grub in this version the grub-menu is not updated also found following links: http://lists.xensource.com/archives/html/xen-users/2007-09/msg00328.html -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500,

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: normal Hello, I've this message in dmesg that I can't understand: [ 4.032472] ------------[ cut here ]------------ [ 4.032521] WARNING: at /build/buildd-linux-2.6_2.6.32-26-amd64-KkHF2p/linux-2.6-2.6.32/debian/build/source_amd64_xen/mm/page_alloc.c:1833 __alloc_pages_nodemask+0x177/0x5f5() [ 4.032590] Hardware name:

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1~rc3-1 Severity: normal Hi, I upgrade one server from lenny to squeeze, to start testing xen-hypervisor-3.4 and xen-hypervisor-4.0, but it seems to don't work. The error : xm create -c /etc/xen/slhoka.cfg Using config file "/etc/xen/slhoka.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. The error

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Followup-For: Bug #423006 FYI, I experience the very same problem here. The machine reboots immediately after the error... I had to reboot outside xen to standard Linux kernel, and then it works... Hope this helps -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500,

Package: xen-hypervisor-4.2-amd64 Version: 4.2.1-2 Severity: critical Tags: upstream Justification: breaks the whole system Dear Maintainer, After migration from Xen 4.1 to 4.2 all VMs have disapeared and I am unable to "re-create" my VM from the configfiles. When I try "xm new com-web" i get a python message : Using config file "./com-web". Error:

Package: xen-hypervisor-3.0.3-1-i386 Version: 3.0.3-0-1 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, When you have a HVM domain running, if you try to boot a regular paravirtualized domain, dom0 (or maybe the hypervisor) crashes immediately (reboot). The opposite (trying to boot a HVM domain while a regular paravirtualized domain is running) crashes the system as well. I

Package: xen-hypervisor-4.0-i386 Version: 4.0.1~rc3-1 Severity: critical Tags: upstream patch Justification: breaks the whole system Using 2.6.32 and xen 4.0, balloon driver crash Upstream patch seems to be available : http://lists.xensource.com/archives/html/xen-devel/2010-06/msg00601.html Thanks -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500,

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-4 Severity: normal Tags: squeeze -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xen-hypervisor-4.0-i386 depends on

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, We are having a problem on several Supermicro servers (I'll include more details on the configuration later) : when booting Linux 3.2 linux-image-3.2.0-4-amd64 (Wheezy) as a DOM0 on Xen 4.1 (xen-hypervisor-4.1-amd64 from Wheezy), the system hangs after : [ 3.716174] scsi1 : ata_piix [

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Hi, I set the severity to important as it seems that current xen tools does not allow to load amd64 Debian kernel in DomU. I also put the debian-kernel ML in CC as I'm not sure the problem comes from xen tools or the kernel itself. Here is my configuration: Hypervisor: xen-hypervisor-3.2-1-amd64 3.2.1-2

Package: xen-3.0 Version: 3.0.3-0-2 Severity: normal Hi, Currently, ext2fs and reiserfs pygrub modules are not necessarily built because setup.py can't find ext2_fs.h and reiserfs.h when e2fslibs-dev and libreiserfs0.3-dev are not installed. xen-3.0 should hence build-dep on e2fslibs-dev and libreiserfs0.3-dev Samuel -- System Information: Debian Release: 4.0 APT prefers testing APT

Package: xen-hypervisor-4.1-amd64 Version: 4.1.1-3 Severity: important Whenever I try to start a domU, xm create failed for 'Boot loader didn't return any data!'. % sudo xm create -c squeeze.cfg Using config file "/etc/xen/squeeze.cfg". Error: Boot loader didn't return any data! It seems related to the following error in dmesg [1440.163935] pygrub[3654] trap invalid

After the last round of patches to febootstrap, the image-based test in libguestfs still failed. It turned out that this happens because Debian started replacing /var/run and /var/lock with symlinks that point to a tmpfs mounted to /run. The symlinks were copied to the appliance but /run/lock did not exist, so pvcreate refused to run (script 'images/guest-aux/make-debian-img.sh'). After I

Hi Ghislain, I think you might be comparing two versions of R with different BLAS implementations, one that is single threaded (is your 3.3.2 used with reference blas?) and one that is multi threaded (3.4.1 with openblas). Could you check with "perf"? E.g. run your benchmark with "perf record" in both cases and you should see the names of the hot BLAS functions and this

Dear all, As the object of this mail suggests, the methods package is not loaded by default in R2.13 when using Rscript whereas it is loaded when using an interactive session. An example with the metafor package : library(metafor) example(addpoly.rma) this works in an interaction R shell, but put it in a .R file and use it with Rscript, it won't work until you added library(methods)

Hi Ghislain, The documentation at https://cran.r-project.org/doc/manuals/r-release/R-admin.html#BLAS provides a fair bit of information. What specifically would you like to see added? Best, Ista On Mon, Aug 21, 2017 at 10:13 AM, Ghislain Durif <ghislain.durif at inria.fr> wrote: > Hi Tomas, > > Thanks for your answer. > > Indeed, I checked and my R-3.4.1 installed from the

On Tue, 9 Oct 2018 at 21:47, Yves Bellefeuille <yan at storm.ca> wrote: > > I had CentOS 6 installed on an MBR hard disk. I converted the disk to > GPT (with UEFI) and installed CentOS 7 on a new partition. > Was CentOS6 bootable after you converted the disk to GPT? My luck with getting it to work has not been good as the conversion usually changes something very important to

Hi Ista, Maybe a little comment in the 'matmult {base}' doc page or on the 'options {base}' in the field 'matprod' would be useful to remind users to be cautious regarding BLAS multi-threading? I understand why this is a BLAS related issue and not directly an R related issue. Nonetheless, my concern was for non-advanced R users, that may don't even know what BLAS

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 Severity: grave Justification: renders package unusable Hi, I was running Debian Wheezy (amd64) and xen-hypervisor 4.1 on a Dell PowerEdge R720. Xen was working fine. Xen was configured with LVM Now, I'm trying Debian Jessie (amd64) and I have a strange problem. After booting, Xen seems to be working : /etc/init.d/xen status ? xen.service