search for: windowid

Hello, I've on my home PC CentOS 6 and Fedora 13 on different disks. When I log on the gnome enviroment at Fedora knows exactly which programm was started at which desktop (for example: thunderbird on desktop 1, firefox on desktop 2, nautilus on desktop 3, ..). The same procedure on Centos takes all programs on the first desktop, so I must arrange the programs on the right desktop.

Hi, I am making a game with Ruby/SDL and have run into trouble finding a GUI to cooperate. I have seen numerous examples of wxWindows in combination with SDL (wxPython and PyGame), but have yet to be able to do it in ruby (PyGame example: http://wiki.wxpython.org/index.cgi/IntegratingPyGame). I am not very good with wxRuby as this is my first time using it and thought some more knowledgable users

...rmance low latency guest to guest communication. It uses a new queue extension feature tentatively called VIRTIO_F_WINDOW which indicates that descriptor tables, available and used rings and Queue Data reside in physical memory ranges called Windows, each identified with an unique identifier called WindowID. Each queue is configured to belong to a specific WindowID, and during queue identification and configuration, the Physical Guest Addresses in the queue configuration fields are to be considered as offsets in octets from the start of the corresponding Window. For example for PCI, in the virtio_pc...

On 09.09.2015 08:40, Zhang, Yang Z wrote: > Claudio Fontana wrote on 2015-09-07: >> Coming late to the party, >> >> On 31.08.2015 16:11, Michael S. Tsirkin wrote: >>> Hello! >>> During the KVM forum, we discussed supporting virtio on top >>> of ivshmem. I have considered it, and came up with an alternative >>> that has several advantages

On 09.09.2015 08:40, Zhang, Yang Z wrote: > Claudio Fontana wrote on 2015-09-07: >> Coming late to the party, >> >> On 31.08.2015 16:11, Michael S. Tsirkin wrote: >>> Hello! >>> During the KVM forum, we discussed supporting virtio on top >>> of ivshmem. I have considered it, and came up with an alternative >>> that has several advantages

...to > guest communication. It uses a new queue extension feature tentatively > called VIRTIO_F_WINDOW which indicates that descriptor tables, > available and used rings and Queue Data reside in physical memory > ranges called Windows, each identified with an unique identifier > called WindowID. So if I had to summarize the difference from regular virtio, I'd say the main one is that this uses window id + offset instead of the physical address. My question is - why do it? All windows are in memory space, are they not? How about guest using full physical addresses, and hypervisor...

...to > guest communication. It uses a new queue extension feature tentatively > called VIRTIO_F_WINDOW which indicates that descriptor tables, > available and used rings and Queue Data reside in physical memory > ranges called Windows, each identified with an unique identifier > called WindowID. So if I had to summarize the difference from regular virtio, I'd say the main one is that this uses window id + offset instead of the physical address. My question is - why do it? All windows are in memory space, are they not? How about guest using full physical addresses, and hypervisor...

...ORBIT_SOCKETDIR=/tmp/orbit-charlie -SSH_AGENT_PID=2912 +SSH_AGENT_PID=2337 TERM=xterm SHELL=/bin/bash -XDG_SESSION_COOKIE=2dd5655fe15f1c42f474dd204c45c6b6-1311075950.779608-828425652 +XDG_SESSION_COOKIE=2dd5655fe15f1c42f474dd204c45c6b6-1311094181.613213-1540232224 WINDOW_MANAGER=/usr/bin/compiz -WINDOWID=75497510 -GNOME_KEYRING_CONTROL=/tmp/keyring-zWw2pV +WINDOWID=67108902 +GNOME_KEYRING_CONTROL=/tmp/keyring-fm8dqK GTK_MODULES=canberra-gtk-module:canberra-gtk-module USER=charlie LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;...

...H_AGENT_PID" "SSH_AUTH_SOCK" < [81] "TAR" "TERM" < [83] "TEXINPUTS" "UPSTART_EVENTS" < [85] "UPSTART_INSTANCE" "UPSTART_JOB" < [87] "UPSTART_SESSION" "USER" < [89] "WINDOWID" "XAUTHORITY" < [91] "XDG_CONFIG_DIRS" "XDG_CURRENT_DESKTOP" < [93] "XDG_DATA_DIRS" "XDG_GREETER_DATA_DIR" < [95] "XDG_MENU_PREFIX" "XDG_RUNTIME_DIR" < [97] "XDG_SEAT" "XDG_SEAT_PAT...

...t; "SSH_AUTH_SOCK" > < [81] "TAR" "TERM" > < [83] "TEXINPUTS" "UPSTART_EVENTS" > < [85] "UPSTART_INSTANCE" "UPSTART_JOB" > < [87] "UPSTART_SESSION" "USER" > < [89] "WINDOWID" "XAUTHORITY" > < [91] "XDG_CONFIG_DIRS" "XDG_CURRENT_DESKTOP" > < [93] "XDG_DATA_DIRS" "XDG_GREETER_DATA_DIR" > < [95] "XDG_MENU_PREFIX" "XDG_RUNTIME_DIR" > < [97] "XDG_SEAT" "...

...uest to guest > communication. It uses a new queue extension feature tentatively called > VIRTIO_F_WINDOW which indicates that descriptor tables, available and > used rings and Queue Data reside in physical memory ranges called > Windows, each identified with an unique identifier called WindowID. > Should we consider virtio-peer a pair-wise created device for two guests, where sending side driver is operating receive side virtqueue to drop packets directly? Do you have some architectural description of how guests are expected to use virtio-peer? Thanks. Mesut

...mmunication. It uses a new queue extension feature tentatively >> called VIRTIO_F_WINDOW which indicates that descriptor tables, >> available and used rings and Queue Data reside in physical memory >> ranges called Windows, each identified with an unique identifier >> called WindowID. > > So if I had to summarize the difference from regular virtio, > I'd say the main one is that this uses window id + offset > instead of the physical address. > > > My question is - why do it? > > All windows are in memory space, are they not? > > How abo...

...uest to guest > communication. It uses a new queue extension feature tentatively called > VIRTIO_F_WINDOW which indicates that descriptor tables, available and > used rings and Queue Data reside in physical memory ranges called > Windows, each identified with an unique identifier called WindowID. > Should we consider virtio-peer a pair-wise created device for two guests, where sending side driver is operating receive side virtqueue to drop packets directly? Do you have some architectural description of how guests are expected to use virtio-peer? Thanks. Mesut

...May this be a hint to a misconfiguration or a missed config? here are my environment: ######################################################## alexander@kubuntu:~/.wine/dosdevices$ printenv SSH_AGENT_PID=7670 TERM=xterm SHELL=/bin/bash GTK_RC_FILES=/etc/gtk/gtkrc:/home/alexander/.gtkrc-1.2-gnome2 WINDOWID=23068768 OLDPWD=/home/alexander/.wine USER=alexander LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=0...

...egister 'kio_http_cache_cleaner' -> number of clients is now 4 kio (kioslave): SlaveBase::checkCachedAuthInfo window = 46137349 url = http://localhost:901/ DCOP: register 'anonymous-28553' -> number of clients is now 5 kio (KPasswdServer): KPasswdServer::checkAuthInfo: User= , WindowId = 46137349 kio_http: (28553) ============ Sending Header: kio_http: (28553) GET / HTTP/1.1 kio_http: (28553) Connection: Keep-Alive kio_http: (28553) User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux) kio_http: (28553) Accept: text/html, image/jpeg, image/png, text/*, image/*, */* kio_http:...

...sched,rsvd,method=classic GTK2_RC_FILES=/etc/opt/gnome/gtk-2.0/gtkrc:/opt/gnome/share/themes//Qt/gtk-2.0/gtkrc:/root/.gtkrc-2.0-qtengine:/root/.kde/share/config/gtkrc-2.0 GTK_RC_FILES=/etc/opt/gnome/gtk/gtkrc:/root/.gtkrc:/root/.kde/share/config/gtkrc GNOME_PATH=:/opt/gnome:/usr GS_LIB=/root/.fonts WINDOWID=46137351 OLDPWD=/etc/asterisk QTDIR=/usr/lib/qt3 XSESSION_IS_UP=yes KDE_FULL_SESSION=true GROFF_NO_SGR=yes JRE_HOME=/usr/lib/jvm/java/jre USER=root LS_COLORS=no=00:fi=00:di=01;34:ln=00;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31:ex=00;32:*.cmd=00;32:*.exe=01;32:*.com=01;32:*.bat=...

...HLVL="2" declare -x SSH_AGENT_PID="2676" declare -x SSH_AUTH_SOCK="/run/user/1000/keyring-oPxj9T/ssh" declare -x TERM="xterm-256color" declare -x USER="rahman" declare -x USERNAME="rahman" declare -x VTE_VERSION="3406" declare -x WINDOWID="48234502" declare -x WINDOWPATH="1" declare -x XAUTHORITY="/run/gdm/auth-for-rahman-sjEjGp/database" declare -x XDG_MENU_PREFIX="gnome-" declare -x XDG_RUNTIME_DIR="/run/user/1000" declare -x XDG_SEAT="seat0" declare -x XDG_SESSION_ID=&qu...

...IR=/tmp/orbit-root PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin PWD=/root/Desktop SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2690,unix/unix:/tmp/.ICE-unix/2690 SHELL=/bin/bash SHLVL=3 SSH_AGENT_PID=2691 SSH_AUTH_SOCK=/tmp/keyring-Q8NLAk/socket.ssh TERM=xterm USER=root WINDOWID=29365969 WINDOWPATH=7 XAUTHORITY=/root/.Xauthority XDG_SESSION_COOKIE=2a071ee033f2806e361d3a1300000010-1349440548.28361-792141036 I have installed the following packages via yum: reinstall gnome-desktop-2.28.2-9.el6.centos.x86_64 install gdm-1:2.30.4-33.el6_2.x86_64 groupinstall "...

...debug2: channel 0: send open debug1: Entering interactive session. debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env SSH_AGENT_PID debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env XDG_SESSION_COOKIE debug3: Ignored env WINDOWID debug3: Ignored env GTK_MODULES debug3: Ignored env XTERM_SHELL debug3: Ignored env USER debug3: Ignored env SSH_AUTH_SOCK debug3: Ignored env GNOME_KEYRING_SOCKET debug3: Ignored env USERNAME debug3: Ignored env PATH debug3: Ignored env DESKTOP_SESSION debug3: Ignored env GDM_XSERVER_LOCATION debu...

...XDG_VTNR debug3: Ignored env SSH_AGENT_PID debug3: Ignored env XDG_SESSION_ID debug3: Ignored env XDG_GREETER_DATA_DIR debug3: Ignored env GPG_AGENT_INFO debug3: Ignored env GLADE_PIXMAP_PATH debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env XDG_MENU_PREFIX debug3: Ignored env WINDOWID debug3: Ignored env USER debug3: Ignored env LS_COLORS debug3: Ignored env XDG_SESSION_PATH debug3: Ignored env GLADE_MODULE_PATH debug3: Ignored env XDG_SEAT_PATH debug3: Ignored env SSH_AUTH_SOCK debug3: Ignored env SESSION_MANAGER debug3: Ignored env XDG_CONFIG_DIRS debug3: Ignored env PATH debu...