search for: weide

...ecial handling to > always mean, some DMA address translation? Can't there be > any other kind of special handling needs, that has nothing to do with > DMA address translation? I don't think it is illegal per se. It is however completely broken if we do that decision on a system weide scale rather than properly requesting it through a per-device flag in the normal virtio framework.

...6.18, the network fails start and xend fails too. The network adaptor is Intel 82567LM Gigabit Network Connection. Does anybody else get the same problem? I cannot figure it out whether this is caused by driver support of xen or faulty configuration. Need your help and thanks a lot. 2009-01-15 Weide Zheng _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello all! I've "Queue Log Analyzer" installed [http://www.micpc.com/qloganalyzer] to check Asterisk main stats. There's an option of "CALLS COMPLETED [ALL]" where I can see the completed calls that entered any of the queues. There, there's a column that displays the extention number of the Agent who received each call, for example, it displays: Agent/202 So

Hi List, I have a problem with dovecot 2.2.12 and sieve-filter call: su -c 'sieve-filter -D -v -W -C -u account at domain.tld /var/vmail/domain.tld/account/.sieve INBOX.Refilter' vmail gives me sieve-filter(vmail): Error: user account at domain.tld: Auth USER lookup failed sieve-filter(vmail): Fatal: Internal error occurred. Refer to server log for more information. on log file I see

Hi list Im currently run debian sarge / testing. I upgraded my dovecot this morning on my mail server this morning, and my dovecot stopped working for my mail users email clients. I told debconf to replace the dovecot.conf (Baring in mind I saved my conf file). The output I was getting was as so: ====================================================================== Aug 11 10:09:56 mail dovecot:

sev_active() is gone now in linux-next, at least as a global API. And once again this is entirely going in the wrong direction. The only way using the DMA API is going to work at all is if the device is ready for it. So we need a flag on the virtio device, exposed by the hypervisor (or hardware for hw virtio devices) that says: hey, I'm real, don't take a shortcut. And that means on

sev_active() is gone now in linux-next, at least as a global API. And once again this is entirely going in the wrong direction. The only way using the DMA API is going to work at all is if the device is ready for it. So we need a flag on the virtio device, exposed by the hypervisor (or hardware for hw virtio devices) that says: hey, I'm real, don't take a shortcut. And that means on