Your message dated Fri, 22 Feb 2019 16:38:36 +0100 with message-id <[email protected]> and subject line Re: xen-utils-3.2-1: ioemu routed networking on HVM guests fails has caused the Debian Bug report #554805, regarding xen-utils-3.2-1: ioemu routed networking on HVM guests fails to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 554805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554805 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Under this Xen setup, (Linux) HVM guests fail to have network active when running with *routed* networking, as some hosting providers require (in my case, OVH). In this scenario: * the host is a described below * the guest runs as HVM. * the guest runs exclusively with ioemu; virtual network drivers are not available (vanilla lenny guest, xen-vnif.ko does not exist, xen-netfront refuses to load despite the XenBus PCI device appearing) What xen/qemu-dm did is to build two network interfaces: * vifN.0 was used to send packets from the host to the guest routing was enabled towards this interface. No virtual hardware drivers took care of this network link, so all packets ended up dropped. * tapM was used by the guest to deliver packets from its virtual eth0. All packets were classified "martians" by the host and rejected. The reason why this happened is that the scripts/qemu-dm script *assumes* only bridging is ever used, and the scripts/vif-routing *assumes* only netfront is ever used. Here we have routing and ioemu, which causes the failure described above. -- Cyrille -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (800, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xen-utils-3.2-1 depends on: ii e2fslibs 1.41.9-1 ext2/ext3/ext4 file system librari ii iproute 20090324-1 networking and traffic control too ii libc6 2.9-25 GNU C Library: Shared libraries ii libgcrypt11 1.4.4-4 LGPL Crypto library - runtime libr ii libgnutls26 2.8.4-1 the GNU TLS library - runtime libr ii libncurses5 5.7+20090803-2 shared libraries for terminal hand ii libsdl1.2debian 1.2.13-2 Simple DirectMedia Layer ii libxenstore3.0 3.4.0-2 Xenstore communications library fo ii python 2.5.4-2 An interactive high-level object-o ii python-central 0.6.11 register and build utility for Pyt ii udev 146-5 /dev/ and hotplug management daemo ii xen-utils-common 3.3.1-2 XEN administrative tools - common ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime Versions of packages xen-utils-3.2-1 recommends: ii bridge-utils 1.4-5 Utilities for configuring the Linu ii xen-hypervisor-3.2-1-amd64 [x 3.2.1-2 The Xen Hypervisor on AMD64 Versions of packages xen-utils-3.2-1 suggests: pn xen-docs-3.2 <none> (no description available) -- no debconf information
--- End Message ---
--- Begin Message ---On 1/21/19 12:13 AM, Hans van Kranenburg wrote: > > Please note that unless there's a response within a month from now, we > will close the bug report. Closing now. Hans
--- End Message ---
