similar to: connecting with the libvirt daemon on xen+debian

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Dear Maintainer, i changed toolkit to xl, after that i observe that my domU started as HVM domains. I found same problem here: http://mail-index.netbsd.org/port-xen/2012/04/11/msg007216.html When i manualy setup loop devices and specify it as disks in my VM conf file, domU started as PV. -- System Information: Debian Release: 7.1

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? I have a xen dom0 with more than one interface that I want to make bridges on * What exactly did you do (or not do) that was effective (or ineffective)? I have my own bridge making script that calls network-bridge for each interface. This used to work in

https://bugzilla.samba.org/show_bug.cgi?id=7489 Summary: rsyncd segfaults using daemon exclude filter Product: rsync Version: 3.0.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: michael.roberts at hp.com

I?m receiving the following error(s) messages when trying reloading dovecot (Debian wheezy). doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 73: Unknown setting: socket doveconf: Error: managesieve-login: dump-capability process returned 89 Configuration file /etc/dovecot/dovecot.conf : # If you only want to use dovecot-auth, you can set this to "none".

Hey All, I'm just wondering whether this is what caused my server to crash. Started last night in NZ land. Jun 20 19:22:11 elm dovecot: imap-login: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=attackerip, lip=10.0.0.3, session=<0C8LzpDfZQDINsQC> occasionally get Jun 20 19:22:52 elm dovecot: imap-login: Disconnected (no auth attempts in 1 secs):

After a few days, one of my DomU becomes unresponsive. Here''s the output of my DomU''s. root@xenII:/var/log/xen# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 7126 2 r----- 723932.0 redhat-sdsweb 11 4091 2 -b---- 92633.1 w2k8-AD

On Mon, 2014-04-21 at 15:43 +0200, Sjors Gielen wrote: > Package: xen-utils-4.1 > Version: 4.1.4-3+deb7u1 > Severity: important > > When an LVM LV that serves as the root disk for a Xen DomU contains a boot > loader (or possibly other data) in its volume boot record, pygrub fails to boot > it, printing "Error: boot loader didn't return any data" before exiting.

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When an LVM LV that serves as the root disk for a Xen DomU contains a boot loader (or possibly other data) in its volume boot record, pygrub fails to boot it, printing "Error: boot loader didn't return any data" before exiting. I think this is because of the function "is_disk_image" on line 45 of

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important Tags: security patch When you use xl toolstack, you can't reboot domUs. When you switch back to xm toolstack, than reboot works again. I think the problem with the debian packaged version is the same as in this thread: http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html I also think it's a security issue,

On 2 July 2013 09:58, Martin Kletzander <mkletzan@redhat.com> wrote: > I'd say this is a problem with sasl, nothing else. "No mechanism found" > may mean that libraries for configured mechanism aren't found or unknown > mechanism is being requested. I doubt that access to those libraries > would be a permisison problem, but you might be missing some >

Package: xcp-xapi Version: 1.3.2-15 Severity: normal I am trying to pass an SRIOV virtual function in a virtual machine but the attempt fails with the following errors shown in the xcp-xapi.log [20130829T19:29:17.909Z|debug|sriov1|314 UNIX /var/lib/xcp/xapi|VM.start R:9e8e10bd31bb|pciops] PCI devices from other-config:pci to attach: 0/0000:04:00.1 [20130829T19:29:18.012Z|debug|sriov1|314 UNIX

On 07/02/2013 10:13 AM, Maciej Gałkiewicz wrote: > On 2 July 2013 09:58, Martin Kletzander <mkletzan@redhat.com> wrote: > >> I'd say this is a problem with sasl, nothing else. "No mechanism found" >> may mean that libraries for configured mechanism aren't found or unknown >> mechanism is being requested. I doubt that access to those libraries

Package: libxen-dev Version: 4.1.4-3+deb7u1 Severity: wishlist Dear Maintainer, I want to make some fine monitoring of my xen machines and the xentop utility does not exactly fits my needs I saw in the sources that it uses some kind of library named libxenstat wich seems very acurate. This library is already built to make the xentop utility but the debian package does not makes it available as

Hi I am running following asterisk installed with apt on Debian 7.1. dpkg -l |grep asterisk ii asterisk 1:1.8.13.1~dfsg-3+deb7u1 amd64 Open Source Private Branch Exchange (PBX) ii asterisk-config 1:1.8.13.1~dfsg-3+deb7u1 all Configuration files for Asterisk ii asterisk-core-sounds-en-gsm 1.4.22-1 all asterisk PBX

> Hi > > I am running following asterisk installed with apt on Debian 7.1. > > dpkg -l |grep asterisk > ii asterisk 1:1.8.13.1~dfsg-3+deb7u1 > amd64 Open Source Private Branch Exchange (PBX) > ii asterisk-config 1:1.8.13.1~dfsg-3+deb7u1 > all Configuration files for Asterisk > ii

Hello, Since recently (not sure when), dsync stopped working. dsync -u klink mirror XXXX dsync-local(klink): Error: remote: dsync-server: invalid option -- 'l' dsync-local(klink): Error: remote: doveadm dsync-server [-u <user>|-A] [-S <socket_path>] dsync-local(klink): Error: read() from worker server failed: EOF I did not change anything on my setup but dovecot was

Package: xen-system-amd64 Version: 4.1.4-3+deb7u1 Severity: normal The xen kernel detects 3GB of memory instead of the full 4GB. When using the "normal" kernel 4GB is detected. On boot the 4GB is detected: root at ams-tc1-xen27:~# dmesg |grep Mem [ 0.000000] Memory: 3226132k/4980736k available (3426k kernel code, 788180k absent, 966424k reserved, 3312k data, 576k init) But only

Processing commands for control at bugs.debian.org: > reassign 745419 src:xen 4.1.4-3+deb7u1 Bug #745419 [xen-utils-4.1] xen-utils-4.1: Pygrub fails to boot from LVM LV when something installed in the volume boot record Bug reassigned from package 'xen-utils-4.1' to 'src:xen'. No longer marked as found in versions xen/4.1.4-3+deb7u1. Ignoring request to alter fixed versions of

Hello, I have problems running Xen (from Debian 7, i386 userspace) on Asus P3-AE5 system (M2V-TVM board) with Athlon 64 3000+ CPU (AM2, 1.8GHz). In short, Xen is not accessible from amd64 Linux kernels but works fine with 686 kernels. Long version: xen-system-i386 (4.1.4-3+deb7u1) works fine with linux-image-3.2.0-4-686-pae xen-system-amd64 (4.1.4-3+deb7u1) works fine with

Fix config file parsing for VMX domains. If we define "vif" in the config file, image.py will raise error "vmx: missing vbd configuration". The reason is "vif" is dealt with as a "vbd" device. This patch fixes this issue by dealing with "vbd" and "vif " separately, removing "macaddr" arg and parsing mac address from