search for: zakaz

...lnull mail 4096 ??? 26 15:08 iif drwx-w---- 3 mailnull mail 4096 ??? 11 15:53 jack drwx------ 2 mailnull mail 4096 ??? 27 09:28 Maildir drwx-w---- 3 mailnull mail 4096 ??? 27 09:25 test Why did dovecot create Maildir folder??? And what mean this lines at the end of debug.log. Aug 27 09:28:42 imap(zakaz at badmltd.dn.ua): Debug: Namespace : type=shared, prefix=shared/%n/, sep=/, inbox=no, hidden=no, list=children, subscriptions=no Aug 27 09:28:42 imap(zakaz at badmltd.dn.ua): Debug: shared: root=/var/run/dovecot, index=, control=, inbox= Aug 27 09:28:42 imap(zakaz at badmltd.dn.ua): Debug: acl:...

...pool/vmail/domains/badmltd.dn.ua/jack/Maildir/.&BCcENQRABD0EPgQyBDgEOgQ4-/dovecot- acl not found Aug 26 15:48:03 imap(jack at badmltd.dn.ua): Debug: acl vfile: file /var/spool/vmail/domains/badmltd.dn.ua/jack/Maildir/dovecot-acl not found Aug 26 15:48:03 auth: Debug: master in: USER 1 zakaz at badmltd.dn.ua service=lib-storage Aug 26 15:48:03 auth: Debug: sql(zakaz at badmltd.dn.ua): SELECT home, uid, gid FROM users WHERE id = 'zakaz' AND active = 'Y' Aug 26 15:48:03 auth: Debug: master out: USER 1 zakaz at badmltd.dn.ua home=/var/spool/vmail/domains...

...ion Message-ID: <20110309120540.GA2446 at wavehammer.waldi.eu.org> References: <87hbbdh022.fsf at tac.ki.iif.hu> <4D76EF8D.1090401 at goirand.fr> <1299659530.3731.25.camel at localhost.localdomain> <874o7co9bq.fsf at tac.ki.iif.hu> <1299670593.17339.558.camel at zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1299670593.17339.558.camel at zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) On Wed, Mar 09, 2011 at 11:36:33AM +0000, Ian Campbell wrote: > Did pvops in...

...om: Ian Campbell <Ian.Campbell@citrix.com> > To: Qrux <qrux.qed@gmail.com> > Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> > Subject: Re: [Xen-devel] Xen domU Timekeeping (a.k.a TSC/HPET issues) > Message-ID: <1329480365.3131.50.camel@zakaz.uk.xensource.com> > Content-Type: text/plain; charset="UTF-8" > > I''m afraid I don''t know the answer to most of your questions (hence I''m > afraid I''ve trimmed the quotes rather aggressively) but here''s some of > what I do kno...

The default make targets in the top level makefile set DESTDIR which gets applied when the stubdom makefile tries to do a make install within gmp to install libgmp.a to the cross root. Ian, do you want to apply this to your tree and commit the whole thing or would you prefer I roll out a fresh new patch set with all updates applied? Signed-off-by: Matthew Fioravante

Hello, When start a domU through xl create. The domU associated ip in the configuration file is not recorded in the xenstore. For this reason vif-common.sh antispoof scripts fails. *xl create * /usr/bin/xenstore-ls /local/domain/0/backend/vif/5/0 frontend = "/local/domain/5/device/vif/0" frontend-id = "5" online = "1" state = "4" script =

Package: xen-utils-common Version: 4.0.0-1 Severity: important Xen domains should be shutdown before iSCSI if that is installed. This can be accomplished by adding the following to /etc/init.d/xendomains: # Should-Start: iscsi # Should-Stop: iscsi -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64)

I''ve encountered a rather unusual bug while I''m implementing live migration on arndale board. After resume, domU kernel starts invoking hypercalls and at some point the hypercall parameters delivered to xen are corrupted. After some debugging (with the help of HW debugger), I found that cache polution happens, and here is the detailed sequence. 1) DomU kernel allocates a local

Currently PVHVM Linux guests after ddacf5ef684a "xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches from old kernel" hang when run against oxenstored because it does not handle the unknown XS_RESET_WATCHES operation and does not reply. The symptom of this issue is a hang during boot at this point: cpu 1 spinlock event irq 70 CPU 1 irqstacks, hard=dec94000

Package: xen Version: 4.1.0-3 Severity: important Tags: wheezy sid User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-4.6 ftbfs-werror This package builds with -Werror, and GCC 4.6 triggers new warnings which will make the package fail to build. Currently a Debian patch just passes -Wno-error=unused-but-set-variable and -Wno-error=unused-but-set-parameter to avoid build failures,

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: important I'm running a 32-bit Ubuntu 10.04 domU on a 32-bit Debian squeeze dom0. xm create works fine, but whenever I try to reboot this domU it fails with the following traceback in xend.log: [2010-10-23 17:48:58 1679] INFO (XendDomainInfo:2088) Domain has shutdown: name= onini id=2 reason=reboot. [2010-10-23 17:48:58 1679] DEBUG

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

...n.Campbell@citrix.com> To: Dmitry Morozhnikov <dmiceman@mail.ru> Cc: "xen-users@lists.xen.org" <xen-users@lists.xen.org>, xen-devel <xen-devel@lists.xen.org> Subject: Re: [Xen-users] libxl vs pygrub in 4.1.2 on rebooting domU Message-ID: <1337273527.7781.109.camel@zakaz.uk.xensource.com> Content-Type: text/plain; charset="UTF-8" On Wed, 2012-05-16 at 12:29 +0100, Dmitry Morozhnikov wrote: > Hello, all. > > There is a bug in 4.1.2, at least in gentoo. The question is if it > already fixed or not. > > If someone issue reboot comman...

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1306311631 -3600 # Node ID 6b1fe0cba8a2f0bcc1274c8e777da5b6c198b45d # Parent 8258c5a0ba35de937597e2c516bc88f8ebe1be35 libxl: use preferred syntax for network device creation with upstream qemu Markus Armbruster points out in <m3r582pzc1.fsf@blackfin.pond.sub.org> on qemu-devel that this is the prefered syntax

irq: Exclude percpu IRQs from being fixed up Xen spin unlock uses spurious ipi "lock_kicker_irq" to wake up blocked vCPUs waiting on that lock. This irq should always be disabled. However, when Dom0 is shuting down, function fixup_irqs is called which unmasks all irqs. Function unmask_irq effectively re-enables lock_kicker_irq and its irq handler is invoked which reports bug and crashes

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal This issue is similar to http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2011-March/003217.html but since I was not able to find a bug report I'm reporting this now. Steps to reproduce: 1) cat << EOF > config name = 'squeeze64' vcpus = '4' memory = '512' disk = [

There are basically three issues we''re waiting to sort out (see below for more info): * XSA-55 * cpu hotplug in qemu-upsream * The MMIO hole issue Unfortuantely, there is considerable uncertainty about how long it will take for each of those to complete. We''re hoping to be able to release maybe on the 19th, This information will be mirrored on the Xen 4.3 Roadmap wiki page:

The following series of patches fill in most of the gaps in the OCaml bindings to libxl, to make them useful for clients such as xapi/xenopsd (from XCP). There are a number of bugfixes to the existing bindings as well. I have an experimental version of xenopsd that successfully uses the new bindings. An earlier version of the first half of the series was submitted to the last by Ian Campbell on

Hello, in the last days I switched from Xen 4.2.1 to Xen 4.2.2 (source from git repository tag 4.2.2) commit a125ec6a4a2f028f97f0bdd8946d347a36dbe76b Author: Jan Beulich <jbeulich@suse.com> Date: Tue Apr 23 18:42:55 2013 +0200 update Xen version to 4.2.2 My "base system" is a debian squeeze. For Xen I use the xl toolstack. Since updating to 4.2.2 the autosave and

What are the outstanding things to do before we think we can start on the 4.2 -rc''s? Does anyone have a timetable in mind? hypervisor: * ??? - Keir, Tim, Jan? tools: * libxl stable API -- we would like 4.2 to define a stable API which downstream''s can start to rely on not changing. Aspects of this are: * event handling (IanJ working