similar to: Bug#603417: xen-hypervisor-4.0-amd64: domU fails to obtain IP address from dom0 dhcp server (dhclient complains about checksum error)

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Xen Networking[1] works by creating a new pair of virtual ethernet interfaces (vifN.M in dom0 and ethM in domU with id N) and connecting then by an internal "crossover ethernet cable". My understanding of the "internal crossover" thing is that networking statistics should be the same no matter if you measure

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: important *** Please type your report below this line *** Hello Debian Team, I have some strange behavior with a DL585 G7 with only two cpu sockets used (Opteron 6238 Interlagos). I use Debian 6.0 with a XEN Kernel. Every time when I start a DomU, the server makes a hard reset without any kernel panic or output. When I start the

Hello, when I boot DomU which uses DHCP to configure IPv4 address it does never get a lease. The packets travel to Dom0 where the dhcp server receives them, sends a reply, that travels to DomU where dhclient receives it, says the checksum is invalid, and discards it. The problem is documented here: http://old-list-archives.xen.org/archives/html/xen-users/2006-02/msg00152.html

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.2 Severity: important Tags: patch I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 / linux-image-2.6.26-2-xen-amd64 without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 / linux-image-2.6.32-5-xen-amd64 and now it does

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.8 Severity: critical We're seeing this too on 4.0.1-5.8, and it's causing major problems. Xen on Debian Squeeze is basically unusable with the latest packages. Is a fixed package in sight? Thanks, Ward. -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500,

On Thursday, 18 April 2019 11:53:39 CEST Richard W.M. Jones wrote: > Workaround for Ubuntu which uses this script to try to start a systemd > service. That won't work because systemd is not used inside the > appliance. See: > > https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236 > > Thanks: Ioanna Alifieraki > --- > appliance/init | 4 +++- > 1

Workaround for Ubuntu which uses this script to try to start a systemd service. That won't work because systemd is not used inside the appliance. See: https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236 Thanks: Ioanna Alifieraki --- appliance/init | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/appliance/init b/appliance/init index 4f2b55822..b1c4d09ea

I had tried this approach, to add /etc/dhcp/dhclient-enter-hooks.d/resolved to excludefiles, however it didn't work. As far as I know, this hook is included in the base image and according to [1], the current implementation does not apply excludefiles to the base image. Jo [1] https://github.com/libguestfs/supermin/blob/b2401285cd3e3d42006fc164ef1f046cc35a50c4/src/mode_build.ml#L137 On

On Thu, Apr 18, 2019 at 12:17:18PM +0100, Ioanna Alifieraki wrote: > I had tried this approach, to add /etc/dhcp/dhclient-enter-hooks.d/resolved > to excludefiles, however it didn't work. > As far as I know, this hook is included in the base image and according > to [1], the current implementation does not apply excludefiles to the base > image. Yes I think that is right. It

Hi, Is there any chance you will merge the suggested patch? Thanks, Jo On Thu, Apr 18, 2019 at 2:01 PM Richard W.M. Jones <rjones@redhat.com> wrote: > On Thu, Apr 18, 2019 at 12:17:18PM +0100, Ioanna Alifieraki wrote: > > I had tried this approach, to add > /etc/dhcp/dhclient-enter-hooks.d/resolved > > to excludefiles, however it didn't work. > > As far as I

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

On Wed, May 29, 2019 at 04:14:06PM +0100, Ioanna Alifieraki wrote: > Hi, > > Is there any chance you will merge the suggested patch? It's this one right? https://www.redhat.com/archives/libguestfs/2019-April/msg00129.html Yes I can push this. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog:

Processing commands for control at bugs.debian.org: > reassign 611278 xen-hypervisor-4.0-amd64 4.0.1-1 Bug #611278 [linux-2.6] linux-image-2.6.32-5-xen-amd64: boot fails when iommu is enabled in bios Bug reassigned from package 'linux-2.6' to 'xen-hypervisor-4.0-amd64'. Bug No longer marked as found in versions 2.6.32-30. Bug #611278 [xen-hypervisor-4.0-amd64]

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

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: grave Tags: squeeze sid Justification: renders package unusable -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8

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-i386 Version: 4.0.1~rc6-1 Severity: important --- Please enter the report below this line. --- Booting up the Xen Dom0 fails with an error in "i387.c:159" --- System information. --- Architecture: i386 Kernel: Linux 2.6.32-5-686-bigmem Kernel: Linux 2.6.32-5-xen-686 Debian Release: squeeze/sid 500 testing security.debian.org 500

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

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: important I upgraded today from Lenny to Squeeze. I upgraded via apt-get dist-upgrade and then installed the new xen-packages (including hypervisor and kernel). But I wasn't able to boot the system after the upgrade anymore with Xen enabled: On every boot-attempt, I just get "elf_init: not an ELF binary". I googled a

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