search for: meurer

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen

Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.

On Wed, 2014-11-05 at 17:56 +0100, Jonas Meurer wrote: [...] > So the question is: why does the VM run stable on xen1 while it > crashes all the time on xen2. If I compare xen1 and xen2, only > real difference is mainboard (Supermicro X8 on xen1; Supermicro > X9 on xen2) and CPU (Xeon L5939 on xen1; E5-2609 on xen2) > > As a n...

reassign 758622 linux-image-3.16.0-4-amd64 thanks Hi Ben, thanks for your response. Am 2014-11-05 21:40, schrieb Ben Hutchings: > On Wed, 2014-11-05 at 17:56 +0100, Jonas Meurer wrote: > [...] >> So the question is: why does the VM run stable on xen1 while it >> crashes all the time on xen2. If I compare xen1 and xen2, only >> real difference is mainboard (Supermicro X8 on xen1; Supermicro >> X9 on xen2) and CPU (Xeon L5939 on xen1; E5-2609 on xe...

Package: logcheck Version: 1.2.27 Severity: wishlist hello, in ignore.d.server/oidentd you have: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ oidentd\[[0-9]+\]: Connection from \ [._[:alnum:]-]+ \([0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\):[0-9]{1,5}$ anyway, some oidentd logs don't have a hostname: oidentd[34562]: Connection from 241.145.24.135:2353 therefore you have to add: ^\w{3} [

And some more information ... Am 2014-10-13 12:04, schrieb Jonas Meurer: > Am 2014-08-19 12:26, schrieb Jonas Meurer: >> I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU >> with the >> stock kernel. The dom0 runs the same linux kernel and >> xen/4.1.4-3+deb7u1. > > the bug is still reproducible with the latest kerne...

Hey again, Am 2014-08-19 12:26, schrieb Jonas Meurer: > I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU with > the > stock kernel. The dom0 runs the same linux kernel and > xen/4.1.4-3+deb7u1. the bug is still reproducible with the latest kernel and Xen packages from Debian Wheezy. Unfortunately it seems like a corn...

hello, What is the current situation with xen on amd64? the debian/sid archive keeps no linux-image-2.6.22-2-xen-amd64, and I was not able to compile a 2.6.22 dom0 kernel with debian xen patches applied on my amd64 system. I have linux-source-2.6.22 and linux-patch-debian-2.6.22 installed, and followed the instructions from the workaround for

Package: src:linux Version: 3.2.41-2 Severity: important Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel