similar to: Bug#679533: Looks like the upgrade from Squeeze to Wheezy fixes this issue

retitle Traffic forwarding issue between Xen domU/dom0 thanks This week again this bug occurred again so we are trying to create some kind of reproduce algorithm. First we've created two virtual machines named koekiemonster.bofh.hq.mendix.net and netappsim.bofh.hq.mendix.net. We've added 29 vifs to koekiemonster.bofh.hq.mendix.net. During this tests we've always had a ping

Obviously i meant hyperthreading. Probably need more coffee:) -- Frank Baalbergen - System / Network Administrator T +31 (0)10 2760434 | frank.baalbergen at mendix.com | www.mendix.com

Kevin, Would you mind taking a look at #679533 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679533) and give some feedback about how similar this issue is to your report in #631102 here? There was a hint 631102 might be similar, but from the text in this bug report it's not clear to me if this is about the same issue. Maybe you could comment on it. First results of a big shoot-out

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.2 Hi, We're seeing weird behaviour regarding network traffic between a Xen dom0 and domU. I reported this issue yesterday to the openvswitch-discuss mailing list, but it seems this could also be a (regression?) bug in the xen hypervisor or the linux kernel... (we've upgraded xen-hypervisor-4.0-amd64 4.0.1-4 -> 4.0.1-5.2 and

Package: xen-utils-common Version: 4.1.2-3 Severity: normal When configurating a duplicate custom vifname for interfaces in the Xen dom0 that are added to a bridge (which is obviously a configuration error), the hotplug scripts fail silently to rename the new vifX.0 to the custom vifname, if it's already existing. The result of this, is that the domU will start normally, but no network

Whoops, that patch is obviously missing an extra line containing a fi statement. Fixed version attached. And configurating is obviously not english. :) -- Hans van Kranenburg - System / Network Engineer T +31 (0)10 2760434 | hans.van.kranenburg at mendix.com | www.mendix.com -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name:

Package: xen-utils-common Version: 4.1.4-2 Severity: normal Hi, During some research I encountered incorrect information in the man page of xm, about the dump-core functionality: The man page says: "Defaults to dumping the core without pausing the domain if no I<OPTIONS> are specified." When taking a look at the source code of this process, the default behaviour is to actually

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-8 Severity: normal Tags: patch The Xen hypervisor in Debian Jessie does not boot on recent HP server hardware (e.g. the current dl360 gen9 series) when using normal "legacy" boot. During boot, it panics with the message "System without CMOS RTC must be booted from EFI". This message was introduced in upstream commit

I am having an issue with Megacli when adding or removing virtual disks. I will post a link to fpaste that has the issue shown. In brief whenever i add, or remove, a virtual disk via MegaCli the attempt succeeds and the adapter is configured but the OS remounts dm-0 in read only. dm-0 is my root lv. This issue does not happen if i boot into the default, non Xen, CentOS kernel. On stock

Dom0 is Wheezy 64 bit with kernel 3.2.0-1-amd64 version 3.2.4-1, xen from xen-unstable.hg changeset 24823:b75664e53905 plus these patch for not fail build: http://xen.1045712.n5.nabble.com/PATCH-0-of-2-rename-libxl-yajl-gen-alloc-td5469362.html On boot start to load but after start ramdisk load server reboot without message on screen. The grub2 entry is: -----------------------------------------

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: grave File: xen Justification: renders package unusable Debian Squeeze Dom0, up to date. Networking is handled by OS scripts, such that br0 and br1 are bridge interfaces. Without warning, the DomU (Ubuntu 10.04 LTS) loses inbound connectivity. It tends to happen after several hours. It doesn't seem to be affected by throughput

Hi All, Running into temporary pauses in our VMs which correspond to these errors in dmesg on the dom0: [1721485.352560] SLUB: Unable to allocate memory on node -1 (gfp=0x20) [1721485.352563] cache: kmalloc-2048, object size: 2048, buffer size: 2048, default order: 3, min order: 0 [1721485.352566] node 0: slabs: 81, objs: 1296, free: 0 [1721485.352576] swapper: page allocation failure:

Hello everyone, i just updated from 4.2.1 to 4.2.2. If i try to fire up my win2k8 domU with a pci device attached, the dom0 machine hardcrashes. my system log (idrac) shows the following: CPU 2 has an internal error (IERR). A bus fatal error was detected on a component at bus 0 device 0 function 0. CPU 1 machine check detected. and plenty of other entries. The machine hardresets then. If i

https://bugzilla.samba.org/show_bug.cgi?id=10571 Summary: Fails to work from machine to machine after upgrade to Kubuntu 14.01 Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

Hello, I have a freshly setup postfix/dovecot mail server (after a server upgrade I decided to change my sendmail/popper conf to something more modern :) It mostly works, there is no problem in sending/receiving mails in local network, both using text clients like mutt or pine dealing with the incoming/outcoming mail directly. Also dovecot works fine with SSL authentication from the outside

hi,all. I found that use the ps -ef command to check a service status have some error. I test it . run puppetd --debug --tags apache2 ,get this message. ============= debug: Service[apache2](provider=debian): Executing ''ps -ef'' debug: Service[apache2](provider=debian): PID is 12062 ============ but the apache2 service is not running. and if I run ps -ef|grep apache2

Dear all, I've already install new samba 2.2.5 at Redhat 7.3. Some configuration of smb.conf has been tested using testparm and no error return. Using LinNeigborhood I can access some files and folders of windows PC. But from windows I can't access samba directories and files. Error report from windows is Network path was not found. Lan connection is ok if test ping. Can you suggest me

Hello, Thanks to everyone who responded. On 19.07.2018 17:55, Rowland Penny via samba wrote: > On Thu, 19 Jul 2018 16:36:45 +0700 > Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > >> Hello, >> >> Given: >> - Samba 3 domain is set up (runs on Samba 3.6.23, domain name "LAN") >> - Windows 10 Enterprise workstation >>

I'm just dumping all I got in here, after initial feedback we can see how to organize todo's around it. tl;dr: * Does not upgrade cleanly from 4.8 packages, so we have to prevent this from entering testing until we fix that. * Live migration is broken, explodes with memory allocation errors. ---- >8 ---- 1. Build packages * I have built salsa/master using pbuilder targeting sid.

Rowland Penny via samba wrote 2018-07-19 20:47: > On 19 Jul 2018 09:21:46 -0400 > Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > >> Hello, >> >> Thanks to everyone who responded. >> >> On 19.07.2018 17:55, Rowland Penny via samba wrote: >> > On Thu, 19 Jul 2018 16:36:45 +0700 >> > Konstantin Boyandin via samba