similar to: about xen's net work

here is my problem: Parsing config file vir2.cfg Daemon running with PID 11570 Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 3.0.0 (root@localhost.localdomain) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Mon Oct 28 00:35:01 CST 2013 Command line: root=/dev/hda1 ro ACPI in unprivileged domain disabled released 0 pages

>> We tested the current lenny kernel linux-image-3.16.0-4-amd64 as well >> as the backport linux-image-4.1.0-0.bpo.1-amd64 on the dom0 as well >> as the domU. > > (I suppose you meant s/lenny/jessie/ ;-) Oops, yes :) > These are kernel ABI versions, the package release versions are things > like 3.16.7-ckt17-1 or 4.2.5-1~bpo8+1, which yu can either get from >

Can I ask you a quick question? I''ve set up bridge-networking for Xen 4.1 (xen-4.1.3-25.el5.22) and networking was being done properly for Dom0 and DomUs. However, I noticed that Dom0 receives a lot of network interrupts or network packets even when they were not actually meant for either Dom0 or DomU. Now, here are the questions: 1. Dom0 is acting in promiscuous mode, right? 2. If

Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the package maintainers as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host

Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the package maintainers as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: important A few minutes after starting a domU, network access is no longer possible from and to it. This does not always happen and is not easily reproducible, but seems to occur in all newly started domUs from some point in time on. However, also restarting the dom0 does not necessarily prevent the problem. At the moment when

Package: xen-utils-common Version: 4.0.0-1 Severity: important Tags: patch --- Please enter the report below this line. --- when you use "hardware" virtual machine (with qemu) with xen configured for bridging the network script treates a tap interface and then /etc/xen/scripts/qemu-ifup adds it to the bridge. That would be ok but tap interfaces have a random mac address and the bridge

Subject: xen-utils-4.1: /usr/lib/xen-default missing Package: xen-utils-4.1 Version: 4.1.3-1 Severity: important Dear Maintainer, when using paravirtualization with xen and libvirt the path for pygrub is: /usr/lib/xen-default/bin/pygrub But this path is not provided with xen-utils-4.1 and will brake upgrades to wheezy. With xen-utils-4.0 and debian squeeze this path is provided with

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal The grub.cfg created by a default Debian installation uses many configuration statements that pygrub does not recognize, and pygrub is unable to find any kernel to load. ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500,

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal pygrub does not recognize the include statement in extlinux.conf. The default Debian installation of extlinux creates a stub extlinux.conf which includes linux.cfg, where all the linux image entries are. This means that even if bugs 697407 and 697409 are fixed, pygrub still can't find the right kernel on a default Debian installation

Package: xen-utils-4.1 Version: 4.1.3-2 Severity: important Dear Maintainer, Creating a new HVM domU fails with the following error: map shared IO page returned error 22 I've narrowed it down to qemu-dm which fails to start: # /usr/lib/xen-4.1/bin/qemu-dm [...] qemu_map_cache_init nr_buckets = 10000 size 4194304 errno0 = 2 domid = -1 shared page at pfn 0 errno1 = 3 errno2 = 22 map shared IO

Hello All! I have a new OpenSuse 12.2 (with 3.4.33-2.24-xen kernel) + Xen 4.1.3 install on an IBM x3550 server. The system is booted via EFI with Grub2 bootloader and it boots up normally, either with or without Xen. But i have one trouble with it: I can''t get console access working with Xen. The strange thing is, despite the "WARNING: no console will be available to

Package: src:xen Version: 4.1.3-4 Severity: serious The bzimage loader used in both libxc and the hypervisor lacks XZ support. Debian kernels since 3.6 are compressed with XZ and can't be loaded. Support for XZ compression was added in changeset 23002:eb64b8f8eebb somewhere last year. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990,

Hi, I am trying to understand the exception handler of Xen. In xen/arch/x86/x86_64/entry.S, the entry of the page fault handler is : ENTRY(page_fault) movl $TRAP_page_fault,4(%rsp) jmp handle_exception Here I did not get why to put the exception vector ($TRAP_page_fault) to stack before calling handle_exception? Thanks, -- Xinxin

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3-3 Severity: normal Forwarded: http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1789 Dear Debian Xen Team, after an upgrade from Squeeze to Wheezy I see about ten of these per second filling my system log (about 8 MB/h): Nov 23 00:15:37 acromantula kernel: [ 462.544193] powernow-k8: fid trans failed, fid 0x2, curr 0x0 Nov 23 00:15:37 acromantula

Hi all, Has anyone noticed this behaviour in samba-tool? I was trying to do the Apache Single Sign on authentication: https://wiki.samba.org/index.php/Authenticating_other_services_against_AD#Apache_Single_Sign-On > root at bnedevdc0:~# samba-tool domain exportkeytab /root/httpd.keytab --principal=HTTP/svn.myrealm.mydomain at MYREALM.MYDOMAIN -d10 > INFO: Current debug levels: >

When running totem to play a move (e.g. mpeg-1 file), it fails with the message: "A MPEG-1 System Stream demuxer plugin is required to play this stream, but not installed." After reading docs and trying various things I've reduced the source of the problem to the package gstreamer-plugins-ugly-0.10.11-1.el5.rf.i386.rpm # rpm --rebuilddb # rpm -q libdvdread libdvdread-4.1.3-1.el5 #

Hi all, The first couple of xen machines we setup used the default xen bridging setup for dom0. I am sure there are many other people out there with this setup. Now that I know a bit more there are probably better ways out there to configure the xen box for firewalling, most notably assigning the red card to a domU and running shorewall in there. But in the meantime I would like to further

Package: src:xen Severity: important Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 I recently upgrade from Squeeze to Wheezy on a system which had the xen-linux-system-686-pae metapackage (one of two which Provides: xen-linux-system). After dist-upgrade I had the new xen-utils-common and xenstore-utils (and a few others) but not the xen-utils-4.1 or xen-hypervisor-4.1-i386 or xen-hypervisor-amd64

The time has come for another round of stable releases. Please send (or resend) any outstanding backport requests for 4.0.4 and 4.1.3 before Friday 20 April. Note that 4.0.4 will likely be the last release in the 4.0.x branch. Ian.