Search results for "Linux ./configure"

Re: [CentOS] Centos 6.3 - which repos to use?

by Bry8 Star

When using multiple repo, then how would i know, an app/lib from non-CentOS (that is, 3rd party repo) is going to conflict or not with CentOS core, base, essential app/lib packages ? We need to know CentOS core, base, essential components. According to this file: /usr/lib/anaconda/installclasses/rhel.py That is located inside the mounted image of this below file: http://mirror.centos.org/centos-6/6/os/x86_64/images/install.img or http://mirror.centos.org/centos-6/6/os/x86/images/install.img * A CentOS Basic Server has : base, console-internet, core, debugging, directory-client, hardware-monitoring, java-platform, large-systems, network-file-system-client, performance, perl-runtime, server-platform. * Database Server : Basic Server (shown above), and, mysql-client, mysql, postgresql-client, postgresql, system-admin-tools. * Web Server: Basic Server (shown above), and, mysql-client, php, postgresql-client, turbogears, web-server, web-servlet. So below command will show what app/lib/pkg are in "Basic Server", and should not be replaced by a 3rd party repo packages: yum groupinfo base core "Console internet tools" "Directory Client" "Java Platform" "Network file system client" "Server Platform" debugging large-systems performance perl-runtime hardware-monitoring --disablerepo=\* --enablerepo=base,extra,update --disableplugin=filter-data,priorities --disableexcludes=all in above, it is, one command-line, (text-based email-system will break it, so remove LF/CR char to get full command-line ) You must try to avoid replacing those, (centos essential packages). Copy the list in a text file, remove lines(LF/CR), make paragraphs, and print it out or keep the text file easily accessible location. So you can see it to decide, on 3rd party repo which package should be placed inside "exclude". If there is/are mistake(s) in above suggestion, please correct. Please post better, other way(s) to achieve these. Thanks, -- Bright Star. Received from Bry8 Star, on 2013-01-28 10:16 AM: > For PostgreSQL, i've done these (shown below) at initial/test stage: > (pls DO NOT follow/copy it, try to understand pattern and do what > fits for your case/need). > > From a VE instance inside HN: > > yum has these plugins: fastestmirror, filter-data, keys, list-data, > merge-conf, presto, priorities, security, verify. > > # CentOS-Base.repo > [CentOS-base] > #<...snip...> > enabled=1 > # i do not want below set from centos repo > # as these exacts are released by postgre devs > # but other postgre portions from others i do want > exclude=postgresql.* postgresql-contrib* postgresql-debuginfo* > postgresql-devel* postgresql-docs* postgresql-jdbc.* > postgresql-jdbc-debuginfo* postgresql-libs* postgresql-odbc.i686 > postgresql-odbc-debuginfo* postgresql-plperl* postgresql-plpython* > postgresql-pltcl* postgresql-server* postgresql-tcl.i686 > postgresql-tcl-debuginfo* postgresql-test* > priority=1 > > [CentOS-updates] > #<...snip...> > enabled=1 > exclude=postgresql.* postgresql-contrib* postgresql-debuginfo* > postgresql-devel* postgresql-docs* postgresql-jdbc.* > postgresql-jdbc-debuginfo* postgresql-libs* postgresql-odbc.i686 > postgresql-odbc-debuginfo* postgresql-plperl* postgresql-plpython* > postgresql-pltcl* postgresql-server* postgresql-tcl.i686 > postgresql-tcl-debuginfo* postgresql-test* > priority=1 > > [CentOS-extras] > #<...snip...> > enabled=1 > exclude=postgresql.* postgresql-contrib* postgresql-debuginfo* > postgresql-devel* postgresql-docs* postgresql-jdbc.* > postgresql-jdbc-debuginfo* postgresql-libs* postgresql-odbc.i686 > postgresql-odbc-debuginfo* postgresql-plperl* postgresql-plpython* > postgresql-pltcl* postgresql-server* postgresql-tcl.i686 > postgresql-tcl-debuginfo* postgresql-test* > priority=1 > > [CentOSplus] > #<...snip...> > enabled=1 > exclude=kernel.* kernel-firmware.* kernel-headers.* postgresql.* > postgresql-contrib* postgresql-debuginfo* postgresql-devel* > postgresql-docs* postgresql-jdbc.* postgresql-jdbc-debuginfo* > postgresql-libs* postgresql-odbc.i686 postgresql-odbc-debuginfo* > postgresql-plperl* postgresql-plpython* postgresql-pltcl* > postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo* > postgresql-test* > priority=1 > > # pgdg92-centos.repo > [pgdg92] > #<...snip...> > enabled=1 > priority=10 > > [pgdg92-source] > #<...snip...> > enabled=1 > priority=10 > > #scntflnx.repo > [SciLnx-6x-os] > #<...snip...> > enabled=1 > exclude=redhat-rpm-config.* postgresql.* postgresql-devel* > postgresql-docs* postgresql-contrib* postgresql-jdbc.* > postgresql-libs* postgresql-odbc* postgresql-plperl* > postgresql-plpython* postgresql-pltcl* postgresql-server* > postgresql-test* > priority=13 > > [SciLnx-6x-updates-fastbugs] > #<...snip...> > enabled=1 > exclude=postgresql.* postgresql-devel* postgresql-docs* > postgresql-contrib* postgresql-jdbc.* postgresql-libs* > postgresql-odbc* postgresql-plperl* postgresql-plpython* > postgresql-pltcl* postgresql-server* postgresql-test* > priority=13 > > [SciLnx-6x-updates-security] > #<...snip...> > enabled=1 > exclude=postgresql.* postgresql-devel* postgresql-docs* > postgresql-contrib* postgresql-jdbc.* postgresql-libs* > postgresql-odbc* postgresql-plperl* postgresql-plpython* > postgresql-pltcl* postgresql-server* postgresql-test* > priority=13 > > [SciLnx-6x-debuginfo] > #<...snip...> > enabled=0 > priority=13 > > [SciLnx-6x-SRPMS] > #<...snip...> > enabled=1 > priority=13 > > [pgdg92] > #<...snip...> > enabled=1 > priority=15 > > ... other repo & distro ... > > In above way, i get most from PosteGre repo, and other postgre > related side packages from other repos. if i were to place > exclude=postgre* then all packages would have gotten excluded, and > then the extra postgre pkg which are not released by postgre, would > get hidden/excluded as well, though, i could have used this approach > for to get that: > > includepkgs=related-extra-postgre-pkg > > to get those. but then i would need specific name, but what if new > extra pkg that i dont know yet, is included, but since i have not > specified specifically, those would get hidden/excluded. > (my repo inquiries have shown, many other repo has at-least 1 to 3 > or some up to 6 extra postgre related tools which are not released > by postgre devs themselves). > > Few patterns/logics which i like to follow: > > repo#1, rpm priority 1, srpm priority 50 > repo#2, rpm priority 10, srpm priority 40 > repo#3, rpm priority 15, srpm priority 30 > repo#4, rpm priority 20, srpm priority 20 > ... > > Priority numbering pattern/logic: > Since i'm using centos as my base, > so various DISTRO & REPO rpm/binary which > are closest to CentOS & CentOS's source RHEL, > those distro & repo will get lowest priority# > close to centos. > i like to think/visualize in this way ... > a LIST from top to down, now number them > from top to bottom 1, 2, 3.. CentOS is at > position 1, the top-most position. > The lowest priority number, is at highest, > upper position in the list, is chosen first > by yum/installer, and has highest priority, > if it(yum) wants to install something. > > my knol is this (i could be wrong): > RHEL based source -> > |-> CentOS base. > |-> Scientific Linux. > |-> Oracle Linux. > |-> ClearOS Linux. > > (Fedora stable source -> RHEL -> RHEL source). > > EPEL has extra small tools/apps/libs for > RHEL base apps/libs, and also for RHEL > based clone/derivative distros (few > mentioned above). > RPMforge/dag has many perl related stuff. > REMI has latest+stable PHP, MySql related stuff. > ELrepo is for hardware latest+stable drivers, kernels. > kdeRedhat is mostly for latest+stable KDE, QT, samba, etc. > RPMFusion has closed-source-free, open-source-free, non-free etc apps. > ATrpms has MythTV, Scientific Apps, etc. > LnxTechNet has audio,video,etc apps. > > And Fedora 17, 18 source/src/SRPMS are needed to be re-built on > cnetos for those apps/libs, then those can be used with centos. > > Pkg "Excluding" pattern/logic: > (means, Getting specific pkg from > Non-Centos repo): > Now for example if i want something specific > called "pkg-set-3" from repo#3, then i would have > to place those specific pkgs inside the "exclude" > line in repo(s) which are listed at upper position > on the repo-list, so that will be repo#2, repo#1, > so it will be: > # repo_1.repo file inside /etc/yum.repos.d > [repo_1] > exclude=pkg-set-3 > > # repo_2.repo file inside /etc/yum.repos.d > [repo_2] > exclude=pkg-set-3 > # in 'exclude' pkgs are 'space' separated > > Where & How to tweak & apply intelligence/knowledge > and experience and tricks , etc for repo-config ? > i like to call it HI (Human Intelligence), > multiple (or one) developer's initial > HI becomes AI in a software. > > Each repo file will most likely have > one or more section/channel like below: > [section-or-channel-name] > config_options=values > ... > > in repo#2, the "pkg-set-3" can be placed inside > all section/channel of that repo file. > > For setting repo#1 (in our case, this is centos), > we will have to do these: > > set "enabled=" to 0 in all new repo, > (except centos.repo), > or, by using yum command-line options > instruct "yum" to disable all repo, > then instruct yum to enable only > centos-base,centos-updates, etc repo only > and then do "yum check-update", like this: > > yum --disablerepo=\* --enablerepo=base,update,centosplus,extra > check-update > > ... above command will show if centos repo has new updates (or no > updates) for your system. > > then set enabled=1 in those section/channel which you need for the > app/lib (pk-set-3) which you wanted. > > then run do "yum check-update". > ... It will show list of app/lib which will be updated if you were > to run "yum update" or "yum upgrade". > > Also see other helpful yum commands. > > Since these yum commands will show app/lib name and which repo has > it, observe carefully and make a hand-written list first (or write > on a text file on the client computer from where you're connecting > to your centos server which you are trying to configure), a list, > apps/libs which you need to exclude from which repo. > > Other helpful YUM COMMANDS: > > yum list updates '*' --disableplugin=filter-data,priorities > --disableexcludes=all > > ... should show what updates will be in queue if all "excludes" are > ignored. > > yum list all available 'pkg-name*' > --disableplugin=filter-data,priorities --disableexcludes=all > > ... should show which of your repos has any package that are close > to the name "pkg-name" and will also show their version # and what > repo has it. > > Anytime you change any "somename.repo" file, > then its better to do first: > yum check-update > (but do not update, unless you are sure which app is coming from > which exact repo and if that is what you want or not). > > Please ADD/POST MORE/YOUR HELPFUL COMMANDS, > and tell us what it does, where useful. > > Since source/SRPMS is/are needed when you/i need to make src.rpm, so > distro & repo closest to CentOS gets higher priority, usually that > is in reverse order than the RPM/binaries. > > Please correct my mistakes and add your responses, ideas, > suggestions, logics, patterns, etc. > > Thanks in advance, > > -- Bright Star. > > > > Received from Johnny Hughes,, on 2013-01-28 12:50 AM: >> On 01/27/2013 06:20 PM, Rob Kampen wrote: >>> On 01/28/2013 04:43 AM, Mark LaPierre wrote: >>>> On 01/27/2013 08:18 AM, Bry8 Star wrote: >>>>> Hi Anthony, it would be really great, to see various types >>>>> of repo-configs on centos wiki, now if few helpful& >>>>> experienced users can grab this idea and come forward and >>>>> share their repo config (and their case/usage scenario >>>>> along with that), then that would be great. >>>>> >>>>> <snip> >>>>> >>>>> (Sorry for spelling& grammar mistakes in previous and in >>>>> this posting, pls kindly disregard, its not a grammar >>>>> discussion thread). >>>>> >>>>> -- Bry8Star. >>>>> >>>>> >>>>> >>>>> Received from Anthony K, on 2013-01-27 2:48 AM: >>>>>> On 26/01/13 14:59, Bry8 Star wrote: >>>>>>> CentOS webpage/site should also show to all users, some >>>>>>> example of using multiple repos and how to implement >>>>>>> effective includepkgs, exclude, priority etc directives >>>>>>> properly for some certain last& STABLE app(s) (which >>>>>>> is by default not in CentOS), so that others can >>>>>>> understand the pattern, or have a pointer for them. >>>>>>> Just mentioning about, that, there is such things >>>>>>> called "includepkgs=...", "exclude=..." ad now go do >>>>>>> it yourself (and sorry no example), obviously does not >>>>>>> help that much to users, and its CentOS's loss as well, >>>>>>> users go away to other distros, and ultimately many of >>>>>>> them are lost in the jungle. -- Bright Star >>>>>>> (Bry8Star). >>>>>> But you appear to be missing the "C" part in CentOS (or >>>>>> Community Enterprise OS). If you can contribute to the >>>>>> Wiki, then the immediate problem is solved in that such >>>>>> threads can be pointed to the Wiki and slows the growth >>>>>> of my CentOS list folder! >>>>>> >>>>>> Frankly, if you have a good point to make that would >>>>>> benefit the masses and you have spare time, then it's >>>>>> best to create a Wiki page for it. >>>>>> >>>>>> Cheers, ak. >>>>>> >>>> There is already a fine page on this subject on the wiki. >>>> >>>> http://wiki.centos.org/AdditionalResources/Repositories >>>> >>> The point being made is that various people have the knowledge >>> and experience to advise a startup setting for priority= for >>> each repo I know that what I'm using has caused conflicts that >>> have been quite time consuming to resolve - what works for >>> others would be most helpful I do recognise that this will vary >>> depending upon what tools are required but as a start: 1. >>> developer workstation - what repos and what priority 2. LAMP >>> server - probably just CentOS repos and something which deals >>> with later php / perl / ruby 3. web / internet workstation - >>> needs audio and video stuff working just my thoughts for >>> starters. >> >> That totally depends on what you need to install and what repo it >> is in. Since 3rd party repos are constantly adding new packages >> that they did not have last week, it is impossible to say what >> would be the proper priorities. >> >> I already posted what I personally do, which is: >> >> Install CentOS and set Base, updates, extras, and fasttrack to a >> Priority=1 >> >> I usually do not need to enable centosplus, but if I do, I set it >> to Priority=2 and I put "excludes=<pkg_names>" in the Priority=1 >> repos for the packages I want let CentOS plus replace in those >> repos. >> >> I then normally add EPEL and set the Priority=10 for that. >> >> Hopefully, that is all I need to add. >> >> If I have to add any more repositories, first make sure my >> packages are currently all updated by doing a yum upgrade. Then >> I add the new repos one at a time and I make them Priority=10 >> (the same as EPEL) ... and after I add them , i do a "yum >> update". If it tries to update, I look at the packages and >> decide if I am going to allow the update or not ... if I am ok to >> do the updates, then I do them and make sure it works. Then I >> would install the packages I need from that repo. Then I would >> add the next new repo till I get to the end. >> >> The best scenario is that all your 3rd party repos can co-exist >> at the same Priority setting and that is where I start (at >> Priority=10) ... and if something does not work, I troubleshoot >> it and take individual action. >> >> Each individual machine is going to require a unique and separate >> group of settings based on what you want to install ... which is >> why there is no official recommendations. >> >> I personally am using the following repos right now on my main >> Desktop, which is CentOS-6.3: >> >> adobe-linux-x86_64 >> | 951 B 00:00 base >> | 3.7 kB 00:00 cr >> | 3.0 kB 00:00 elrepo >> | 1.9 kB 00:00 elrepo-extras >> | 1.9 kB 00:00 extras >> | 3.5 kB 00:00 fasttrack >> | 3.5 kB 00:00 google-chrome >> | 951 B 00:00 google-musicmanager >> | 951 B 00:00 livna >> | 1.3 kB 00:00 nux-dextop >> | 2.7 kB 00:00 rpmforge >> | 1.9 kB 00:00 updates >> | 3.5 kB 00:00 >> >> All of the secondary repos are set to the same priorities and >> everything seems to work. >> >> Right now I have an "exclude=wxGtk*" for rpmforge for some >> reason. And an "exclude=nx freenx*" for Nux! repo. >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> CentOS mailing >> list CentOS(a)centos.org >> http://lists.centos.org/mailman/listinfo/centos >> > > > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos >

13 years, 2 months

Re: [Arm-dev] RPI3 and Gnome

by Robert Moskowitz

On 01/08/2017 02:40 AM, Paul R. Ganci wrote: > I am playing around with making a "desktop" workstation out of a > Raspberry PI3 using the armv7hl CentOS. I have had no problems > installing the OS and pretty much have everything working except a > Gnome desktop. > > I did: > > > yum groupinstall "GNOME Desktop" Does any other desktop work, like Xfce? > > and from what I can tell everything necessary is installed. However > when I try to start X up I see it try and start, the display blinks as > if everything is good and then drops back down to the console. The log > file shown below shows a single error ([ 2665.952] (EE) AIGLX: > reverting to software rendering). > > [ 2665.710] > X.Org X Server 1.17.2 > Release Date: 2015-06-16 > [ 2665.725] X Protocol Version 11, Revision 0 > [ 2665.731] Build Operating System: 4.5.7-fedora-4 > [ 2665.736] Current Operating System: Linux centos-rpi3 > 4.4.33-v7.1.el7 #1 SMP Mon Nov 21 18:48:06 UTC 2016 armv7l > [ 2665.736] Kernel command line: 8250.nr_uarts=0 dma.dmachans=0x7f35 > bcm2708_fb.fbwidth=1872 bcm2708_fb.fbheight=1168 > bcm2709.boardrev=0xa22082 bcm2709.serial=0x54bd9ed0 > smsc95xx.macaddr=B8:27:EB:BD:9E:D0 bcm2708_fb.fbswap=1 > bcm2709.uart_clock=48000000 vc_mem.mem_base=0x3dc00000 > vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 > console=tty1 root=/dev/mmcblk0p3 rootfstype=ext4 elevator=deadline > rootwait selinux=1 security=selinux enforcing=0 > [ 2665.756] Build Date: 09 November 2016 05:46:31PM > [ 2665.763] Build ID: xorg-x11-server 1.17.2-22.el7 > [ 2665.769] Current version of pixman: 0.34.0 > [ 2665.783] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 2665.783] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 2665.812] (==) Log file: "/var/log/Xorg.1.log", Time: Sat Dec 31 > 20:08:58 2016 > [ 2665.819] (==) Using config file: "/etc/X11/xorg.conf" > [ 2665.827] (==) Using system config directory > "/usr/share/X11/xorg.conf.d" > [ 2665.828] (==) ServerLayout "Default Layout" > [ 2665.828] (**) |-->Screen "Screen0" (0) > [ 2665.828] (**) | |-->Monitor "Monitor0" > [ 2665.829] (**) | |-->Device "VideocoreIV" > [ 2665.829] (**) |-->Input Device "Keyboard0" > [ 2665.829] (==) Automatically adding devices > [ 2665.829] (==) Automatically enabling devices > [ 2665.830] (==) Automatically adding GPU devices > [ 2665.830] (==) Max clients allowed: 256, resource mask: 0x1fffff > [ 2665.830] (==) FontPath set to: > catalogue:/etc/X11/fontpath.d, > built-ins > [ 2665.830] (==) ModulePath set to "/usr/lib/xorg/modules" > [ 2665.830] (II) The server relies on udev to provide the list of > input devices. > If no devices become available, reconfigure udev or disable > AutoAddDevices. > [ 2665.830] (WW) Hotplugging is on, devices using drivers 'kbd', > 'mouse' or 'vmmouse' will be disabled. > [ 2665.830] (WW) Disabling Keyboard0 > [ 2665.830] (II) Loader magic: 0x54cf7004 > [ 2665.830] (II) Module ABI versions: > [ 2665.830] X.Org ANSI C Emulation: 0.4 > [ 2665.830] X.Org Video Driver: 19.0 > [ 2665.830] X.Org XInput driver : 21.0 > [ 2665.830] X.Org Server Extension : 9.0 > [ 2665.831] (II) no primary bus or device found > [ 2665.831] (II) LoadModule: "glx" > [ 2665.832] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so > [ 2665.855] (II) Module glx: vendor="X.Org Foundation" > [ 2665.855] compiled for 1.17.2, module version = 1.0.0 > [ 2665.855] ABI class: X.Org Server Extension, version 9.0 > [ 2665.855] (==) AIGLX enabled > [ 2665.855] (II) LoadModule: "fbdev" > [ 2665.856] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so > [ 2665.857] (II) Module fbdev: vendor="X.Org Foundation" > [ 2665.857] compiled for 1.17.2, module version = 0.4.3 > [ 2665.857] Module class: X.Org Video Driver > [ 2665.857] ABI class: X.Org Video Driver, version 19.0 > [ 2665.857] (II) FBDEV: driver for framebuffer: fbdev > [ 2665.857] (++) using VT number 1 > > [ 2665.857] (WW) Falling back to old probe method for fbdev > [ 2665.857] (II) Loading sub module "fbdevhw" > [ 2665.857] (II) LoadModule: "fbdevhw" > [ 2665.858] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so > [ 2665.859] (II) Module fbdevhw: vendor="X.Org Foundation" > [ 2665.859] compiled for 1.17.2, module version = 0.0.2 > [ 2665.859] ABI class: X.Org Video Driver, version 19.0 > [ 2665.859] (II) FBDEV(0): using default device > [ 2665.859] (WW) VGA arbiter: cannot open kernel arbiter, no > multi-card support > [ 2665.860] (**) FBDEV(0): Depth 24, (--) framebuffer bpp 32 > [ 2665.860] (==) FBDEV(0): RGB weight 888 > [ 2665.860] (==) FBDEV(0): Default visual is TrueColor > [ 2665.860] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) > [ 2665.860] (II) FBDEV(0): hardware: BCM2708 FB (video memory: 8541kB) > > [ 2665.860] (II) FBDEV(0): checking modes against framebuffer device... > [ 2665.860] (II) FBDEV(0): mode "1920x1200" not found > [ 2665.860] (II) FBDEV(0): mode "1600x1200" ok > [ 2665.860] (II) FBDEV(0): mode "1280x1024" ok > [ 2665.860] (II) FBDEV(0): mode "1152x864" ok > [ 2665.860] (II) FBDEV(0): mode "1024x768" ok > [ 2665.861] (II) FBDEV(0): mode "800x600" ok > [ 2665.861] (II) FBDEV(0): mode "720x400" ok > [ 2665.861] (II) FBDEV(0): mode "640x480" ok > [ 2665.861] (II) FBDEV(0): checking modes against monitor... > [ 2665.861] (--) FBDEV(0): Virtual size is 1600x1200 (pitch 1600) > [ 2665.861] (**) FBDEV(0): Default mode "1600x1200": 162.0 MHz > (scaled from 0.0 MHz), 75.0 kHz, 60.0 Hz > [ 2665.861] (II) FBDEV(0): Modeline "1600x1200"x0.0 162.00 1600 > 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz d) > [ 2665.861] (**) FBDEV(0): Default mode "1280x1024": 108.0 MHz > (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz > [ 2665.861] (II) FBDEV(0): Modeline "1280x1024"x0.0 108.00 1280 > 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz d) > [ 2665.861] (**) FBDEV(0): Default mode "1152x864": 108.0 MHz > (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz > [ 2665.861] (II) FBDEV(0): Modeline "1152x864"x0.0 108.00 1152 1216 > 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz d) > [ 2665.861] (**) FBDEV(0): Default mode "1024x768": 65.0 MHz (scaled > from 0.0 MHz), 48.4 kHz, 60.0 Hz > [ 2665.861] (II) FBDEV(0): Modeline "1024x768"x0.0 65.00 1024 1048 > 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d) > [ 2665.861] (**) FBDEV(0): Default mode "800x600": 36.0 MHz (scaled > from 0.0 MHz), 35.2 kHz, 56.2 Hz > [ 2665.861] (II) FBDEV(0): Modeline "800x600"x0.0 36.00 800 824 > 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d) > [ 2665.862] (**) FBDEV(0): Default mode "640x480": 25.2 MHz (scaled > from 0.0 MHz), 31.5 kHz, 59.9 Hz > [ 2665.862] (II) FBDEV(0): Modeline "640x480"x0.0 25.18 640 656 > 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d) > [ 2665.862] (**) FBDEV(0): Display dimensions: (518, 324) mm > [ 2665.862] (**) FBDEV(0): DPI set to (78, 94) > [ 2665.862] (II) Loading sub module "fb" > [ 2665.862] (II) LoadModule: "fb" > [ 2665.863] (II) Loading /usr/lib/xorg/modules/libfb.so > [ 2665.864] (II) Module fb: vendor="X.Org Foundation" > [ 2665.864] compiled for 1.17.2, module version = 1.0.0 > [ 2665.865] ABI class: X.Org ANSI C Emulation, version 0.4 > [ 2665.865] (**) FBDEV(0): using shadow framebuffer > [ 2665.865] (II) Loading sub module "shadow" > [ 2665.865] (II) LoadModule: "shadow" > [ 2665.865] (II) Loading /usr/lib/xorg/modules/libshadow.so > [ 2665.865] (II) Module shadow: vendor="X.Org Foundation" > [ 2665.865] compiled for 1.17.2, module version = 1.1.0 > [ 2665.866] ABI class: X.Org ANSI C Emulation, version 0.4 > [ 2665.866] (==) Depth 24 pixmap format is 32 bpp > [ 2665.892] (==) FBDEV(0): Backing store enabled > [ 2665.894] (**) FBDEV(0): DPMS enabled > [ 2665.894] (==) RandR enabled > [ 2665.945] (II) SELinux: Disabled by boolean > [ 2665.952] (II) AIGLX: Screen 0 is not DRI2 capable > [ 2665.952] (EE) AIGLX: reverting to software rendering > [ 2665.998] (II) AIGLX: Loaded and initialized swrast > [ 2665.998] (II) GLX: Initialized DRISWRAST GL provider for screen 0 > [ 2666.260] (II) config/udev: Adding input device CM Storm QuickFire > Rapid keyboard (/dev/input/event0) > [ 2666.260] (**) CM Storm QuickFire Rapid keyboard: Applying > InputClass "evdev keyboard catchall" > [ 2666.260] (II) LoadModule: "evdev" > [ 2666.261] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so > [ 2666.263] (II) Module evdev: vendor="X.Org Foundation" > [ 2666.263] compiled for 1.17.2, module version = 2.9.2 > [ 2666.264] Module class: X.Org XInput Driver > [ 2666.264] ABI class: X.Org XInput driver, version 21.0 > [ 2666.264] (II) Using input driver 'evdev' for 'CM Storm QuickFire > Rapid keyboard' > [ 2666.264] (**) CM Storm QuickFire Rapid keyboard: always reports > core events > [ 2666.264] (**) evdev: CM Storm QuickFire Rapid keyboard: Device: > "/dev/input/event0" > [ 2666.264] (--) evdev: CM Storm QuickFire Rapid keyboard: Vendor > 0x2516 Product 0x4 > [ 2666.265] (--) evdev: CM Storm QuickFire Rapid keyboard: Found keys > [ 2666.265] (II) evdev: CM Storm QuickFire Rapid keyboard: > Configuring as keyboard > [ 2666.265] (**) Option "config_info" > "udev:/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/0003:2516:0004.000E/input/input13/event0" > [ 2666.265] (II) XINPUT: Adding extended input device "CM Storm > QuickFire Rapid keyboard" (type: KEYBOARD, id 6) > [ 2666.265] (**) Option "xkb_rules" "evdev" > [ 2666.270] (II) config/udev: Adding input device CM Storm QuickFire > Rapid keyboard (/dev/input/event1) > [ 2666.270] (**) CM Storm QuickFire Rapid keyboard: Applying > InputClass "evdev keyboard catchall" > [ 2666.270] (II) Using input driver 'evdev' for 'CM Storm QuickFire > Rapid keyboard' > [ 2666.270] (**) CM Storm QuickFire Rapid keyboard: always reports > core events > [ 2666.270] (**) evdev: CM Storm QuickFire Rapid keyboard: Device: > "/dev/input/event1" > [ 2666.271] (--) evdev: CM Storm QuickFire Rapid keyboard: Vendor > 0x2516 Product 0x4 > [ 2666.271] (--) evdev: CM Storm QuickFire Rapid keyboard: Found keys > [ 2666.271] (II) evdev: CM Storm QuickFire Rapid keyboard: > Configuring as keyboard > [ 2666.271] (**) Option "config_info" > "udev:/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.1/0003:2516:0004.000F/input/input14/event1" > [ 2666.271] (II) XINPUT: Adding extended input device "CM Storm > QuickFire Rapid keyboard" (type: KEYBOARD, id 7) > [ 2666.271] (**) Option "xkb_rules" "evdev" > [ 2666.623] (II) evdev: CM Storm QuickFire Rapid keyboard: Close > [ 2666.623] (II) UnloadModule: "evdev" > [ 2666.623] (II) evdev: CM Storm QuickFire Rapid keyboard: Close > [ 2666.623] (II) UnloadModule: "evdev" > [ 2666.703] (II) Server terminated successfully (0). Closing log file. > > I used this /etc.X11/xorg.conf: > > Section "ServerLayout" > Identifier "Default Layout" > Screen 0 "Screen0" 0 0 > InputDevice "Keyboard0" "CoreKeyboard" > EndSection > > Section "InputDevice" > Identifier "Keyboard0" > Driver "kbd" > Option "XkbModel" "pc105" > Option "XkbLayout" "us" > EndSection > > Section "Device" > Identifier "VideocoreIV" > VendorName "Broadcom" > BoardName "RPI3Graphics" > Driver "fbdev" > EndSection > > Section "Monitor" > Identifier "Monitor0" > VendorName "Dell" > ModelName "Ultrasharp U2410" > DisplaySize 518 324 > HorizSync 30.0 - 81.0 > VertRefresh 56.0 - 75.0 > Option "DPMS" > EndSection > > Section "Screen" > Identifier "Screen0" > Device "VideocoreIV" > Monitor "Monitor0" > DefaultDepth 24 > SubSection "Display" > Viewport 0 0 > Depth 24 > Modes "1920x1200" "1600x1200" "1280x1024" > "1152x864" "1024x768" "800x600" "720x400" "640x480" > EndSubSection > EndSection > > Does anybody see what I am doing wrong? Like I said it looks like the > desktop wants to startup but then just crashes. > > Thanks for your help.

9 years, 3 months

Re: [CentOS] OT: a very big problem with ipsec-tools on CentOS5 (SOLVED)

by Nicolas Sahlqvist

Could you be a little bit more specific, what are those needs..? / Nicco On 10/13/07, Ross S. W. Walker <rwalker(a)medallion.com> wrote: > > Not if one intends to modify it to suite racoon's specific needs... > > -Ross > > > > -----Original Message----- > > From: Nicolas Sahlqvist [mailto:nicco77@gmail.com] > > Sent: Friday, October 12, 2007 8:04 PM > > To: CentOS mailing list; Ross S. W. Walker > > Subject: Re: [CentOS] OT: a very big problem with ipsec-tools > > on CentOS5 (SOLVED) > > > > Does it not more sense to make a symlink rather then copying > > the file..? > > > > > > / Nicolas > > > > On 10/13/07, carlopmart <carlopmart(a)gmail.com> wrote: > > > Buf ... Solved. Problem was that /etc/pam.d/racoon doesn't > > exists (I found > > > this > > > tip on NetBSD ipsec pages). Simply I have copied > > /etc/pam.d/passwd to > > > /etc/pam.d/racoon and now all works as expected. > > > > > > Many thanks for your help Ross. > > > > > > > > > > > > Ross S. W. Walker wrote: > > > > > > > > I think it might just use another one like /etc/pam.d/remote > > > > cause I audited the package and it wasn't there. > > > > > > > > Does the "users" group exist and charlie a member of it? > > > > > > > > -Ross > > > > > > > >> -----Original Message----- > > > >> From: carlopmart [mailto:carlopmart@gmail.com] > > > >> Sent: Friday, October 12, 2007 6:54 PM > > > >> To: Ross S. W. Walker > > > >> Subject: Re: [CentOS] OT: a very big problem with ipsec-tools > > > >> on CentOS5 > > > >> > > > >> hi ross, > > > >> > > > >> Yes I compiled with pam option. But I don't have any ipsec > > > >> config file on > > > >> /etc/pam.d ... I didn't find any sample on ipsec-tools 0.7 > > > >> source tree ... where > > > >> is it?? > > > >> > > > >> Ross S. W. Walker wrote: > > > >>> If you compiled ipsec tools yourself did you compile with > > > >> the pam option? > > > >>> If not then you can't tell it to use pam for authentication. > > > >>> > > > >>> If you did, did you setup the appropriate ipsec config file in > > > >>> /etc/pam.d? I believe there is an example one in the ipsec > > > >> source tree. > > > >>> -Ross > > > >>> > > > >>> > > > >>> -----Original Message----- > > > >>> From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> > > > >>> To: centos(a)centos.org <centos(a)centos.org> > > > >>> Sent: Fri Oct 12 18:38:38 2007 > > > >>> Subject: [CentOS] OT: a very big problem with > > ipsec-tools on CentOS5 > > > >>> > > > >>> Hi all, > > > >>> > > > >>> I am trying to establish a vpn tunnel between one CentOS5 > > > >> IPSec server > > > >>> and a > > > >>> roadwarrior client, CentOS5 too. Roadwarrior use > > > >> ipsec-tools version 0.6.5-8 > > > >>> (that comes with CentOS5) and server uses version 0.7 > > > >> (downloaded from > > > >>> ipsec-tools website). > > > >>> > > > >>> My server configuration is: > > > >>> > > > >>> path include "/etc/racoon"; > > > >>> path certificate "/etc/racoon/certs"; > > > >>> path pre_shared_key "/etc/racoon/psk.txt"; > > > >>> path pidfile "/var/run/racoon.pid"; > > > >>> #log debug; > > > >>> > > > >>> listen { > > > >>> adminsock "/var/racoon/racoon.sock" "root" > > "nobody" 0660; > > > >>> isakmp 172.28.45.4 [500]; > > > >>> isakmp_natt 172.28.45.4 [4500]; > > > >>> } > > > >>> > > > >>> remote anonymous { > > > >>> exchange_mode aggressive; > > > >>> certificate_type x509 "gwenc.crt" "gwenc.key"; > > > >>> my_identifier asn1dn; > > > >>> proposal_check claim; > > > >>> generate_policy on; > > > >>> nat_traversal on; > > > >>> dpd_delay 20; > > > >>> ike_frag on; > > > >>> passive on; > > > >>> proposal { > > > >>> encryption_algorithm aes; > > > >>> hash_algorithm sha256; > > > >>> authentication_method hybrid_rsa_server; > > > >>> dh_group 2; > > > >>> } > > > >>> } > > > >>> > > > >>> mode_cfg { > > > >>> network4 172.31.78.5; > > > >>> netmask4 255.255.255.240; > > > >>> pool_size 6; > > > >>> dns4 172.25.50.1; > > > >>> auth_source pam; > > > >>> auth_groups "users"; > > > >>> group_source system; > > > >>> auth_throttle 10; > > > >>> pfs_group 2; > > > >>> } > > > >>> > > > >>> sainfo anonymous > > > >>> { > > > >>> pfs_group 2; > > > >>> lifetime time 1 hour; > > > >>> encryption_algorithm rijndael; > > > >>> authentication_algorithm hmac_sha256; > > > >>> compression_algorithm deflate; > > > >>> } > > > >>> > > > >>> When I try to connect from roadwarrior client using > > xauth, server > > > >>> returns me > > > >>> this errors: > > > >>> > > > >>> 2007-10-13 00:21:52: INFO: ISAKMP-SA established > > > >>> 172.28.45.4[4500]-172.17.35.3[4500] > > > >> spi:e3ff2f5a0873ff54:ad9b13f8035ec2f2 > > > >>> 2007-10-13 00:21:52: INFO: Using port 0 > > > >>> 2007-10-13 00:21:52: ERROR: pam_authenticate failed: > > > >> Authentication failure > > > >>> 2007-10-13 00:21:52: INFO: Released port 0 > > > >>> 2007-10-13 00:21:52: INFO: login failed for user "charlie" > > > >>> 2007-10-13 00:21:52: ERROR: Attempt to release an > > > >> unallocated address > > > >>> (port 0) > > > >>> 2007-10-13 00:21:52: ERROR: mode config 6 from > > > >> 172.17.35.3[4500], but we > > > >>> have no > > > >>> ISAKMP-SA. > > > >>> 2007-10-13 00:21:52: ERROR: unknown Informational > > exchange received. > > > >>> > > > >>> why? I don't understand. Well, yes, I think that server > > > >> doesn't use > > > >>> really pam > > > >>> libraries or problem is that linux use shadow for > > passwords instead > > > >>> passwd file. > > > >>> > > > >>> > > > >>> I see a lot of webs on this configuration works out of > > > >> the box, but > > > >>> not for > > > >>> me.... I am really desperated. > > > >>> > > > >>> Many thanks. > > > >>> > > > >>> P.D: On ipsec-tools mailing list i don't receive any response. > > > >>> -- > > > >>> CL Martinez > > > >>> carlopmart {at} gmail {d0t} com > > > >>> _______________________________________________ > > > >>> CentOS mailing list > > > >>> CentOS(a)centos.org > > > >>> http://lists.centos.org/mailman/listinfo/centos > > > >>> > > > >>> > > > >> -------------------------------------------------------------- > > > >> ---------- > > > >>> This e-mail, and any attachments thereto, is intended only > > > >> for use by > > > >>> the addressee(s) named herein and may contain legally > > > >> privileged and/or > > > >>> confidential information. If you are not the intended > > > >> recipient of this > > > >>> e-mail, you are hereby notified that any dissemination, > > > >> distribution or > > > >>> copying of this e-mail, and any attachments thereto, is strictly > > > >>> prohibited. If you have received this e-mail in error, please > > > >>> immediately notify the sender and permanently delete the > > > >> original and > > > >>> any copy or printout thereof. > > > >> > > > >> -- > > > >> CL Martinez > > > >> carlopmart {at} gmail {d0t} com > > > >> > > > > > > > > > > ______________________________________________________________________ > > > > This e-mail, and any attachments thereto, is intended > > only for use by > > > > the addressee(s) named herein and may contain legally privileged > > > > and/or confidential information. If you are not the > > intended recipient > > > > of this e-mail, you are hereby notified that any dissemination, > > > > distribution or copying of this e-mail, and any > > attachments thereto, > > > > is strictly prohibited. If you have received this e-mail in error, > > > > please immediately notify the sender and permanently delete the > > > > original and any copy or printout thereof. > > > > > > > > > > > > > > > > > -- > > > CL Martinez > > > carlopmart {at} gmail {d0t} com > > > _______________________________________________ > > > CentOS mailing list > > > CentOS(a)centos.org > > > http://lists.centos.org/mailman/listinfo/centos > > > > > > > ______________________________________________________________________ > This e-mail, and any attachments thereto, is intended only for use by > the addressee(s) named herein and may contain legally privileged > and/or confidential information. If you are not the intended recipient > of this e-mail, you are hereby notified that any dissemination, > distribution or copying of this e-mail, and any attachments thereto, > is strictly prohibited. If you have received this e-mail in error, > please immediately notify the sender and permanently delete the > original and any copy or printout thereof. > >

18 years, 5 months

[CentOS-virt] Issues with exposing USB serial dongle to guest VM

by Philip Prindeville

Hi. I have Centos 7 (updated) running as my host, and I’m using Qemu and KVM, version 2.0.0 and 2.6.0. I have a Trendnet TU-S9 USB serial dongle attached to the host, which uses the Prolific 2303 chipset. I blacklisted the pl2303 driver so the host doesn’t grab the device, and want to expose it to the guest. On the client, I see 2 USB hubs (3.0 and 2.0), and I see 2 USB endpoints (even though 3 are configured). So the USB CF card readers are visible, but not the USB dongle, even though it’s plugged in. Here’s what I see on the host: [philipp@kvm1 ~]$ ps -f -p13468 UID PID PPID C STIME TTY TIME CMD qemu 13468 1 2 14:51 ? 00:02:39 /usr/libexec/qemu-kvm -name guest=ubuntu16.04-2,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-ubuntu16.04-2/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu Broadwell,+vme,+ds,+acpi,+ss,+ht,+tm,+pbe,+dtes64,+monitor,+ds_cpl,+vmx,+smx,+est,+tm2,+xtpr,+pdcm,+dca,+osxsave,+f16c,+rdrand,+arat,+tsc_adjust,+xsaveopt,+pdpe1gb,+abm,+rtm,+hle -m 8192 -realtime mlock=off -smp 8,maxcpus=12,sockets=12,cores=1,threads=1 -uuid a9590ac8-e532-4dce-b6ef-d3b35c0db865 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-ubuntu16.04-2/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device nec-usb-xhci,id=usb,bus=pci.0,addr=0x5 -device ich9-usb-ehci1,id=usb1,bus=pci.0,addr=0xa.0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/var/lib/libvirt/images/ubuntu16.04-2.img,format=raw,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=1 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=2 -device usb-host,hostbus=3,hostaddr=13,id=hostdev1,bus=usb.0,port=3 -device usb-host,hostbus=3,hostaddr=12,id=hostdev2,bus=usb.0,port=4 -device usb-host,hostbus=3,hostaddr=15,id=hostdev3,bus=usb1.0,port=1 -device vfio-pci,host=07:10.0,id=hostdev0,bus=pci.0,addr=0x3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on [philipp@kvm1 ~]$ sudo lsof -p 13468 -n -P COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME qemu-kvm 13468 qemu cwd DIR 253,0 242 64 / qemu-kvm 13468 qemu rtd DIR 253,0 242 64 / qemu-kvm 13468 qemu txt REG 253,0 8883768 100834619 /usr/libexec/qemu-kvm qemu-kvm 13468 qemu mem REG 253,0 19984 34091991 /usr/lib64/sasl2/libplain.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 19984 34091988 /usr/lib64/sasl2/liblogin.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 57888 33916680 /usr/lib64/sasl2/libdigestmd5.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 24160 33916677 /usr/lib64/sasl2/libcrammd5.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 1846280 100701718 /usr/lib64/libdb-5.3.so qemu-kvm 13468 qemu mem REG 253,0 28200 33627120 /usr/lib64/sasl2/libsasldb.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 19952 33627117 /usr/lib64/sasl2/libanonymous.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 62184 100664409 /usr/lib64/libnss_files-2.17.so qemu-kvm 13468 qemu mem REG 253,0 68192 100701681 /usr/lib64/libbz2.so.1.0.6 qemu-kvm 13468 qemu mem REG 253,0 99952 100701712 /usr/lib64/libelf-0.166.so qemu-kvm 13468 qemu mem REG 253,0 398264 100701630 /usr/lib64/libpcre.so.1.2.0 qemu-kvm 13468 qemu mem REG 253,0 28360 100702508 /usr/lib64/libogg.so.0.8.0 qemu-kvm 13468 qemu mem REG 253,0 189256 100882393 /usr/lib64/libvorbis.so.0.4.6 qemu-kvm 13468 qemu mem REG 253,0 2944120 100882395 /usr/lib64/libvorbisenc.so.2.0.9 qemu-kvm 13468 qemu mem REG 253,0 285608 100882391 /usr/lib64/libFLAC.so.8.3.0 qemu-kvm 13468 qemu mem REG 253,0 48848 100960245 /usr/lib64/libgsm.so.1.0.12 qemu-kvm 13468 qemu mem REG 253,0 113584 100664401 /usr/lib64/libnsl-2.17.so qemu-kvm 13468 qemu mem REG 253,0 157424 100701670 /usr/lib64/liblzma.so.5.2.2 qemu-kvm 13468 qemu mem REG 253,0 65648 101002376 /usr/lib64/libXi.so.6.1.0 qemu-kvm 13468 qemu mem REG 253,0 75848 101002374 /usr/lib64/libXext.so.6.4.0 qemu-kvm 13468 qemu mem REG 253,0 15512 100984172 /usr/lib64/libXau.so.6.0.0 qemu-kvm 13468 qemu mem REG 253,0 301576 100701829 /usr/lib64/libdw-0.166.so qemu-kvm 13468 qemu mem REG 253,0 155744 100701646 /usr/lib64/libselinux.so.1 qemu-kvm 13468 qemu mem REG 253,0 15624 100701842 /usr/lib64/libgmodule-2.0.so.0.4600.2 qemu-kvm 13468 qemu mem REG 253,0 32304 100701834 /usr/lib64/libffi.so.6.0.1 qemu-kvm 13468 qemu mem REG 253,0 11384 100667805 /usr/lib64/libfreebl3.so qemu-kvm 13468 qemu mem REG 253,0 23824 101229361 /usr/lib64/libasyncns.so.0.3.1 qemu-kvm 13468 qemu mem REG 253,0 378904 100960252 /usr/lib64/libsndfile.so.1.0.25 qemu-kvm 13468 qemu mem REG 253,0 42520 100702401 /usr/lib64/libwrap.so.0.7.6 qemu-kvm 13468 qemu mem REG 253,0 24104 101002378 /usr/lib64/libXtst.so.6.1.0 qemu-kvm 13468 qemu mem REG 253,0 32312 100826893 /usr/lib64/libSM.so.6.0.1 qemu-kvm 13468 qemu mem REG 253,0 100472 100826878 /usr/lib64/libICE.so.6.3.0 qemu-kvm 13468 qemu mem REG 253,0 141080 101002368 /usr/lib64/libxcb.so.1.1.0 qemu-kvm 13468 qemu mem REG 253,0 1318920 101002372 /usr/lib64/libX11.so.6.3.0 qemu-kvm 13468 qemu mem REG 253,0 6848 101002370 /usr/lib64/libX11-xcb.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 15688 100702424 /usr/lib64/libkeyutils.so.1.5 qemu-kvm 13468 qemu mem REG 253,0 62744 100667837 /usr/lib64/libkrb5support.so.0.1 qemu-kvm 13468 qemu mem REG 253,0 19384 100701739 /usr/lib64/libgpg-error.so.0.10.0 qemu-kvm 13468 qemu mem REG 253,0 48672 100984118 /usr/lib64/libunwind.so.8.0.1 qemu-kvm 13468 qemu mem REG 253,0 285296 100702506 /usr/lib64/libjpeg.so.62.1.0 qemu-kvm 13468 qemu mem REG 253,0 334904 100701844 /usr/lib64/libgobject-2.0.so.0.4600.2 qemu-kvm 13468 qemu mem REG 253,0 1595056 100701838 /usr/lib64/libgio-2.0.so.0.4600.2 qemu-kvm 13468 qemu mem REG 253,0 62688 100882399 /usr/lib64/libcelt051.so.0.0.0 qemu-kvm 13468 qemu mem REG 253,0 139008 100664438 /usr/lib64/libnl-3.so.200.23.0 qemu-kvm 13468 qemu mem REG 253,0 444832 100664446 /usr/lib64/libnl-route-3.so.200.23.0 qemu-kvm 13468 qemu mem REG 253,0 494440 100702458 /usr/lib64/libgmp.so.10.2.0 qemu-kvm 13468 qemu mem REG 253,0 160776 100702524 /usr/lib64/libhogweed.so.2.5 qemu-kvm 13468 qemu mem REG 253,0 82176 100702502 /usr/lib64/libtasn1.so.6.2.3 qemu-kvm 13468 qemu mem REG 253,0 465360 101027983 /usr/lib64/libtspi.so.1.2.0 qemu-kvm 13468 qemu mem REG 253,0 290864 100702407 /usr/lib64/libp11-kit.so.0.0.0 qemu-kvm 13468 qemu mem REG 253,0 41080 100664395 /usr/lib64/libcrypt-2.17.so qemu-kvm 13468 qemu mem REG 253,0 111080 100664419 /usr/lib64/libresolv-2.17.so qemu-kvm 13468 qemu mem REG 253,0 20024 100701747 /usr/lib64/libcap.so.2.22 qemu-kvm 13468 qemu mem REG 253,0 304576 100701679 /usr/lib64/libdbus-1.so.3.7.4 qemu-kvm 13468 qemu mem REG 253,0 502608 375140 /usr/lib64/pulseaudio/libpulsecommon-6.0.so qemu-kvm 13468 qemu mem REG 253,0 45456 100701728 /usr/lib64/libjson-c.so.2.0.1 qemu-kvm 13468 qemu mem REG 253,0 454008 100702586 /usr/lib64/libssl.so.1.0.1e qemu-kvm 13468 qemu mem REG 253,0 2025760 100702584 /usr/lib64/libcrypto.so.1.0.1e qemu-kvm 13468 qemu mem REG 253,0 19888 100701744 /usr/lib64/libattr.so.1.1.0 qemu-kvm 13468 qemu mem REG 253,0 15608 100702497 /usr/lib64/libboost_system-mt.so.1.53.0 qemu-kvm 13468 qemu mem REG 253,0 94320 100702518 /usr/lib64/libboost_thread-mt.so.1.53.0 qemu-kvm 13468 qemu mem REG 253,0 344280 100868642 /usr/lib64/libldap-2.4.so.2.10.3 qemu-kvm 13468 qemu mem REG 253,0 61872 100868640 /usr/lib64/liblber-2.4.so.2.10.3 qemu-kvm 13468 qemu mem REG 253,0 15848 100701657 /usr/lib64/libcom_err.so.2.1 qemu-kvm 13468 qemu mem REG 253,0 202568 100667824 /usr/lib64/libk5crypto.so.3.1 qemu-kvm 13468 qemu mem REG 253,0 959008 100667833 /usr/lib64/libkrb5.so.3.3 qemu-kvm 13468 qemu mem REG 253,0 324888 100667817 /usr/lib64/libgssapi_krb5.so.2.2 qemu-kvm 13468 qemu mem REG 253,0 19776 100664397 /usr/lib64/libdl-2.17.so qemu-kvm 13468 qemu mem REG 253,0 251784 101017300 /usr/lib64/libnspr4.so qemu-kvm 13468 qemu mem REG 253,0 20048 101017301 /usr/lib64/libplc4.so qemu-kvm 13468 qemu mem REG 253,0 15744 101017302 /usr/lib64/libplds4.so qemu-kvm 13468 qemu mem REG 253,0 186216 100706671 /usr/lib64/libnssutil3.so qemu-kvm 13468 qemu mem REG 253,0 1236840 100702603 /usr/lib64/libnss3.so qemu-kvm 13468 qemu mem REG 253,0 164040 100702605 /usr/lib64/libsmime3.so qemu-kvm 13468 qemu mem REG 253,0 315080 101072314 /usr/lib64/libssl3.so qemu-kvm 13468 qemu mem REG 253,0 208920 100701832 /usr/lib64/libidn.so.11.6.11 qemu-kvm 13468 qemu mem REG 253,0 534768 100667864 /usr/lib64/libgcrypt.so.11.8.2 qemu-kvm 13468 qemu mem REG 253,0 2118128 100664059 /usr/lib64/libc-2.17.so qemu-kvm 13468 qemu mem REG 253,0 143944 100664417 /usr/lib64/libpthread-2.17.so qemu-kvm 13468 qemu mem REG 253,0 88720 100663365 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 qemu-kvm 13468 qemu mem REG 253,0 1141928 100664399 /usr/lib64/libm-2.17.so qemu-kvm 13468 qemu mem REG 253,0 999944 100667871 /usr/lib64/libstdc++.so.6.0.19 qemu-kvm 13468 qemu mem REG 253,0 44448 100664421 /usr/lib64/librt-2.17.so qemu-kvm 13468 qemu mem REG 253,0 6944 100701846 /usr/lib64/libgthread-2.0.so.0.4600.2 qemu-kvm 13468 qemu mem REG 253,0 305168 100984122 /usr/lib64/libtcmalloc.so.4.2.6 qemu-kvm 13468 qemu mem REG 253,0 31904 100827014 /usr/lib64/libusbredirparser.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 99528 100826629 /usr/lib64/libusb-1.0.so.0.1.0 qemu-kvm 13468 qemu mem REG 253,0 1287896 100701840 /usr/lib64/libglib-2.0.so.0.4600.2 qemu-kvm 13468 qemu mem REG 253,0 49800 100702607 /usr/lib64/libcacard.so.0.0.0 qemu-kvm 13468 qemu mem REG 253,0 1230208 100749039 /usr/lib64/libspice-server.so.1.10.1 qemu-kvm 13468 qemu mem REG 253,0 80096 101153158 /usr/lib64/libibverbs.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 92032 101153164 /usr/lib64/librdmacm.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 266680 100984135 /usr/lib64/libseccomp.so.2.3.1 qemu-kvm 13468 qemu mem REG 253,0 23800 100826840 /usr/lib64/libsnappy.so.1.1.4 qemu-kvm 13468 qemu mem REG 253,0 135112 100702462 /usr/lib64/liblzo2.so.2.0.0 qemu-kvm 13468 qemu mem REG 253,0 1292416 101027989 /usr/lib64/libgnutls.so.28.41.16 qemu-kvm 13468 qemu mem REG 253,0 201296 100702526 /usr/lib64/libnettle.so.4.7 qemu-kvm 13468 qemu mem REG 253,0 121296 100701724 /usr/lib64/libsasl2.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 179296 100768842 /usr/lib64/libpng15.so.15.13.0 qemu-kvm 13468 qemu mem REG 253,0 320984 101017286 /usr/lib64/libpulse.so.0.18.0 qemu-kvm 13468 qemu mem REG 253,0 1033536 100826787 /usr/lib64/libasound.so.2.0.0 qemu-kvm 13468 qemu mem REG 253,0 50712 100702422 /usr/lib64/libnuma.so.1 qemu-kvm 13468 qemu mem REG 253,0 14872 100664425 /usr/lib64/libutil-2.17.so qemu-kvm 13468 qemu mem REG 253,0 698744 100826854 /usr/lib64/libpixman-1.so.0.34.0 qemu-kvm 13468 qemu mem REG 253,0 174088 100826406 /usr/lib64/libssh2.so.1.0.1 qemu-kvm 13468 qemu mem REG 253,0 20040 100706670 /usr/lib64/libuuid.so.1.3.0 qemu-kvm 13468 qemu mem REG 253,0 99304 100794835 /usr/lib64/libgfxdr.so.0.0.1 qemu-kvm 13468 qemu mem REG 253,0 115088 100794833 /usr/lib64/libgfrpc.so.0.0.1 qemu-kvm 13468 qemu mem REG 253,0 896344 100794837 /usr/lib64/libglusterfs.so.0.0.1 qemu-kvm 13468 qemu mem REG 253,0 150056 100826654 /usr/lib64/libgfapi.so.0.0.0 qemu-kvm 13468 qemu mem REG 253,0 37056 100701754 /usr/lib64/libacl.so.1.1.0 qemu-kvm 13468 qemu mem REG 253,0 5342808 100841989 /usr/lib64/librados.so.2.0.0 qemu-kvm 13468 qemu mem REG 253,0 5789632 100768762 /usr/lib64/librbd.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 435120 100842007 /usr/lib64/libcurl.so.4.3.0 qemu-kvm 13468 qemu mem REG 253,0 125336 33843740 /usr/lib64/iscsi/libiscsi.so.2.0.10900 qemu-kvm 13468 qemu mem REG 253,0 6264 100702465 /usr/lib64/libaio.so.1.0.1 qemu-kvm 13468 qemu mem REG 253,0 90664 100701649 /usr/lib64/libz.so.1.2.7 qemu-kvm 13468 qemu mem REG 253,0 155464 100664052 /usr/lib64/ld-2.17.so qemu-kvm 13468 qemu mem REG 0,9 6936 anon_inode:[vfio-device] (stat: No such file or directory) qemu-kvm 13468 qemu mem REG 253,0 162552 100706665 /usr/lib64/libsystemd.so.0.6.0 qemu-kvm 13468 qemu mem REG 253,0 83208 100706667 /usr/lib64/libudev.so.1.6.2 qemu-kvm 13468 qemu DEL REG 0,4 37202 /dev/zero qemu-kvm 13468 qemu DEL REG 0,4 37201 /dev/zero qemu-kvm 13468 qemu mem REG 0,18 4024 38290 /dev/shm/spice.13468 qemu-kvm 13468 qemu DEL REG 0,4 38287 /dev/zero qemu-kvm 13468 qemu 0u CHR 1,3 0t0 1028 /dev/null qemu-kvm 13468 qemu 1w FIFO 0,8 0t0 45255 pipe qemu-kvm 13468 qemu 2w FIFO 0,8 0t0 45255 pipe qemu-kvm 13468 qemu 3r CHR 1,9 0t0 1033 /dev/urandom qemu-kvm 13468 qemu 4u a_inode 0,9 0 6936 [signalfd] qemu-kvm 13468 qemu 5u a_inode 0,9 0 6936 [eventpoll] qemu-kvm 13468 qemu 6u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 7u a_inode 0,9 0 6936 [eventpoll] qemu-kvm 13468 qemu 8u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 9u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 10u unix 0xffff88102b7c1000 0t0 38284 /var/lib/libvirt/qemu/domain-2-ubuntu16.04-2/monitor.sock qemu-kvm 13468 qemu 11u CHR 5,2 0t0 1158 /dev/ptmx qemu-kvm 13468 qemu 12u CHR 10,232 0t0 12724 /dev/kvm qemu-kvm 13468 qemu 13u a_inode 0,9 0 6936 kvm-vm qemu-kvm 13468 qemu 14u unix 0xffff88102b7c3c00 0t0 38288 socket qemu-kvm 13468 qemu 15u unix 0xffff88102b7c2800 0t0 38289 socket qemu-kvm 13468 qemu 16u REG 0,18 4024 38290 /dev/shm/spice.13468 qemu-kvm 13468 qemu 17u IPv4 38293 0t0 TCP 127.0.0.1:5900 (LISTEN) qemu-kvm 13468 qemu 18u REG 253,1 171825168384 1074520646 /var/lib/libvirt/images/ubuntu16.04-2.img qemu-kvm 13468 qemu 19u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 20u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 21u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 22u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 23u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 24u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 25u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 26u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 27u unix 0xffff881026898000 0t0 40135 socket qemu-kvm 13468 qemu 28u unix 0xffff88102689f400 0t0 40136 socket qemu-kvm 13468 qemu 29u netlink 0t0 40137 KOBJECT_UEVENT qemu-kvm 13468 qemu 30r FIFO 0,8 0t0 40138 pipe qemu-kvm 13468 qemu 31w FIFO 0,8 0t0 40138 pipe qemu-kvm 13468 qemu 32r FIFO 0,8 0t0 40139 pipe qemu-kvm 13468 qemu 33w FIFO 0,8 0t0 40139 pipe qemu-kvm 13468 qemu 34u a_inode 0,9 0 6936 [timerfd] qemu-kvm 13468 qemu 35u CHR 245,0 0t0 22111 /dev/vfio/30 qemu-kvm 13468 qemu 36u CHR 10,196 0t0 11903 /dev/vfio/vfio qemu-kvm 13468 qemu 37u a_inode 0,9 0 6936 kvm-vfio qemu-kvm 13468 qemu 38u a_inode 0,9 0 6936 [vfio-device] qemu-kvm 13468 qemu 39u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 40u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 41u unix 0xffff88102de37000 0t0 40140 /var/lib/libvirt/qemu/domain-2-ubuntu16.04-2/monitor.sock qemu-kvm 13468 qemu 42u CHR 189,268 0t0 11444 /dev/bus/usb/003/013 qemu-kvm 13468 qemu 43u CHR 189,267 0t0 11441 /dev/bus/usb/003/012 qemu-kvm 13468 qemu 44u unix 0xffff88102d675c00 0t0 47483 socket qemu-kvm 13468 qemu 45u unix 0xffff88102689a400 0t0 40142 socket qemu-kvm 13468 qemu 46u unix 0xffff88102d674400 0t0 47488 socket qemu-kvm 13468 qemu 47u unix 0xffff880e32a7a400 0t0 44457 socket qemu-kvm 13468 qemu 48u unix 0xffff88102b200c00 0t0 45264 socket qemu-kvm 13468 qemu 49u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 50u unix 0xffff8810392a1000 0t0 22123 socket qemu-kvm 13468 qemu 51u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 52u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 53u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 54u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 55u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 56u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 57u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 58u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 59u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 60u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 61u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 62u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 63u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 64u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 65u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 66u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 67u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 68u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 69u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 70u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 71u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 72u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 73u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 74u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 75u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 76u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 77u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 78u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 79u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 80u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 81u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 82u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 83u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 84u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 85u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 86u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 87u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 88u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 89u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 90u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 91u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 92u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 93u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 94u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 95u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 96u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 97u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 98u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 99u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 100u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 101u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 102u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 103u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 104u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 105u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 106u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 107u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 108u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 109u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 110u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 111u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 112u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 113u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 114u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 115u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 116u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 117u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 118u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 119u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 120u a_inode 0,9 0 6936 [eventfd] [philipp@kvm1 ~]$ lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 003: ID 1058:25da Western Digital Technologies, Inc. Bus 004 Device 002: ID 2109:8110 VIA Labs, Inc. Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 007: ID 0557:2419 ATEN International Co., Ltd Bus 003 Device 004: ID 0557:7000 ATEN International Co., Ltd Hub Bus 003 Device 015: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 003 Device 013: ID 05dc:ba04 Lexar Media, Inc. Bus 003 Device 012: ID 0bda:0309 Realtek Semiconductor Corp. Bus 003 Device 009: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 003 Device 006: ID 1a40:0101 Terminus Technology Inc. Hub Bus 003 Device 011: ID 045e:000b Microsoft Corp. Natural Keyboard Elite Bus 003 Device 010: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 003 Device 008: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 003 Device 005: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 002: ID 2109:2811 VIA Labs, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [philipp@kvm1 ~]$ sudo cat /etc/libvirt/qemu/ubuntu16.04-2.xml  <domain type='kvm'> <name>ubuntu16.04-2</name> <uuid>a9590ac8-e532-4dce-b6ef-d3b35c0db865</uuid> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <vcpu placement='static' current='8'>12</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-rhel7.3.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-model'> <model fallback='allow'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/ubuntu16.04-2.img'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hda' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='usb' index='1' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x7'/> </controller> <interface type='network'> <mac address='52:54:00:fc:0f:5e'/> <source network='hostdev-net0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='spice' autoport='yes'> <listen type='address'/> <image compression='off'/> </graphics> <sound model='ich6'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x05dc'/> <product id='0xba04'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x0bda'/> <product id='0x0309'/> </source> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x067b'/> <product id='0x2303'/> </source> <address type='usb' bus='1' port='1'/> </hostdev> <redirdev bus='usb' type='spicevmc'> <address type='usb' bus='0' port='1'/> </redirdev> <redirdev bus='usb' type='spicevmc'> <address type='usb' bus='0' port='2'/> </redirdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> [philipp@kvm1 ~]$ and here’s what I see on the guest: philipp@ubuntu16:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0309 Realtek Semiconductor Corp. Bus 001 Device 002: ID 05dc:ba04 Lexar Media, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub philipp@ubuntu16:~$ I’m not sure what I’m missing. How do I verify that the parameters in the .xml domain definition are correct, and that they’re resulting in the correct args being passed to qemu-kvm when it gets exec’d? And why do the args: -device usb-host,hostbus=3,hostaddr=15,id=hostdev3,bus=usb1.0,port=1 seem to be silently ignored? I understand that USB is inherently pluggable and hence the device may or may not be present at the time that Qemu gets kicked off… Looking at https://github.com/esminc/qemu/blob/master/Source/device-qemu/android/andro… it claims that the PL2303 driver is supported. What am I missing? I need to access serial ports from several of my guest VMs, and my host doesn’t have built-in serial ports to USB dongles are my only option. Thanks, -Philip

8 years, 11 months

Re: [CentOS-es] [iptables] denegar rando dependiendo la IP de la fuenta ?

by angel jauregui

mmm es qye hay varios listillos que se lo podrian brincar :S... existe la problematica que en esa red todos tienen acceso admin a sus propios equipos. Generalmente siempre estan conectados con una cuenta de usuario dentro del dominio local, pero a veces se logean con la cuenta admin. Y como soy un prestador de servicios y no quieren invertir, la unica solucion es poner el proxy como GW. Para prevenir retardos coloque en el proxy 2 tarjetas de red 1Gb en virtual, y configure el switch cisco como VLAN en los 2 puertos donde conecto el proxy. Saludos ! El 5 de noviembre de 2013 08:52, Ramón Macías Zamora <rmacias(a)rks.ec>escribió: > Efectivamente el problema que tienes es porque está usando proxy > transparente. > > Si no usas proxy transparente si puedes controlarlo con las acl normales, > sin embargo para que funcione el proxy debes configurar manualmente el > proxy en los navegadores (En Firefox -> Preferencias -> Avanzado -> red -> > Conexión dar click en Configurar -> Configuración Manual del Proxy > > Saludos > > -- > > > > Ramón Macías Zamora > Tecnología, Investigación y Desarrollo > www.rks.ec - www.raykasolutions.com > Guayaquil - Ecuador > msn: ramon_macias(a)hotmail.com > skype: ramon_macias > UserLinux# 180926 (http://counter.li.org) > Cel: 593-8-0192238 > Tel: 593 4 6044566 > > <http://www.raykasolutions.com/> > > > WEB SITES, HOSTINGS, DOMINIOS, MANTENIMIENTO DE EQUIPOS, REDES, SERVIDORES > LINUX, SOPORTE. > > > 2013/11/5 angel jauregui <darkdiabliyo(a)gmail.com> > > > @Ramon no entiendo cuando mencionas "forzar a que los usuarios configuren > > el proxy" ??? > > > > Los usuarios no tienen que configurar nada, ya que por consecuencia el GW > > que se les asigna es el del proxy, el proxy en si actua como > > Proxy+Router+firewall. > > > > No entendi :S > > > > Saludos ! > > > > > > El 5 de noviembre de 2013 08:38, Ramón Macías Zamora <rmacias(a)rks.ec > > >escribió: > > > > > Yo creo que la solución ahí es forzar a que los usuarios configuren el > > > proxy en vez de usar proxy transparente que sólo funciona para http y > no > > > para https. > > > > > > Saludos > > > > > > -- > > > > > > > > > > > > Ramón Macías Zamora > > > Tecnología, Investigación y Desarrollo > > > www.rks.ec - www.raykasolutions.com > > > Guayaquil - Ecuador > > > msn: ramon_macias(a)hotmail.com > > > skype: ramon_macias > > > UserLinux# 180926 (http://counter.li.org) > > > Cel: 593-8-0192238 > > > Tel: 593 4 6044566 > > > > > > <http://www.raykasolutions.com/> > > > > > > > > > WEB SITES, HOSTINGS, DOMINIOS, MANTENIMIENTO DE EQUIPOS, REDES, > > SERVIDORES > > > LINUX, SOPORTE. > > > > > > > > > 2013/11/5 angel jauregui <darkdiabliyo(a)gmail.com> > > > > > > > @David asi tengo la denegacion tambien, pero si el usuario cambia a > > > "https" > > > > la pagina ya no es bloqueada, se brinca el filtro. > > > > > > > > Esto mas que nada porque en IPTables la regla indica que cualquier > cosa > > > que > > > > va al 80 se rediriga al 3128 (puerto squid), y al cambiar a HTTPS, ya > > no > > > se > > > > aplica la regla. > > > > > > > > Ahora no puedo quitar el puerto https y forzar solo http, ya que > > existen > > > > paginas de gobierno que requieren https, y se me vendria el mundo > > encima > > > > :S. > > > > > > > > Estoy intentando con estas reglas, ustedes que opinan: > > > > > > > > *# dar acceso a facebook para una ip fija* > > > > shell# iptables -A FORWARD -p tcp -s 10.1.0.10 -d IP_CIDR_DEFACEBOOK > > -j > > > > ACCEPT > > > > > > > > *# quitar acceso facebook para cualquiera del segmento* > > > > shell# iptables -A FORWARD -p tcp -s 10.1.0.0/24 -d > IP_CIDR_DEFACEBOOK > > > -j > > > > REJECT > > > > > > > > Saludos ! > > > > > > > > > > > > El 5 de noviembre de 2013 05:08, David González Romero > > > > <dgrvedado(a)gmail.com>escribió: > > > > > > > > > Tu has probado esta opción en Squid? > > > > > > > > > > acl denys url_regex "/etc/squid/denys" > > > > > Donde > > > > > /etc/squid/denys contiene: > > > > > facebook > > > > > twitter > > > > > ..... > > > > > Y luego > > > > > http_access deny restric > > > > > > > > > > Al menos así me funciona a mi. > > > > > > > > > > > > > > > Otra opcion sería comentar la línea "acl SSL_ports port 443" para > > > evitar > > > > > conexiones por el 443... > > > > > > > > > > > > > > > > > > > > > > > > > Saludos, > > > > > David > > > > > > > > > > > > > > > > > > > > El 4 de noviembre de 2013 18:47, angel jauregui > > > > > <darkdiabliyo(a)gmail.com>escribió: > > > > > > > > > > > Buenas. > > > > > > > > > > > > Estoy implementando limitaciones en la red, el objetivo es quitar > > > > acceso > > > > > a > > > > > > Redes Sociales, en primera instancia tengo SQUID que logra tapar > el > > > > > acceso > > > > > > a los sitios mediante http. > > > > > > > > > > > > El problema es que si los sitios tienes HTTPS, este es > > accesible.... > > > > > > > > > > > > En este caso http://facebook.com esta denegad por Squid. > > > > > > Pero al poner https://facebook.com entra exitosamente. > > > > > > > > > > > > La unica ocurrencia que tuve es usar IPTABLES, asi que puse esta > > > regla > > > > > que > > > > > > me esta haceindo cumplir el objetivo "En parte": > > > > > > > > > > > > iptables -I FORWARD -m tcp -p tcp -m iprange --dst-range > > > > > > 173.252.64.0-173.252.127.255 -j REJECT > > > > > > > > > > > > Donde: 173.252.64.0-173.252.127.255 ---> es el rando CIDr de > > > facebook. > > > > > > > > > > > > El problema *ahora radica* en que no logro hacer que ciertas IPs > > > > Locales > > > > > > (privilegiada - jefes) SI puedan acceder a redes sociales :S !. > > > > > > > > > > > > Intente ANTEponiendo esta regla: > > > > > > > > > > > > iptables -I FORWARD *-s ip_del_jefe *-m tcp -p tcp -m iprange > > > > --dst-range > > > > > > 173.252.64.0-173.252.127.255 -j ACCEPT > > > > > > > > > > > > Pero aun asi, se sigue bloqueando el sitio :S.... > > > > > > > > > > > > *shell# iptables -L -n* > > > > > > REJECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > > > > > > destination IP range 173.252.64.0-173.252.127.255 reject-with > > > > > > icmp-port-unreachable > > > > > > ACCEPT tcp -- 10.1.0.150 0.0.0.0/0 tcp > > > > > > destination IP range 173.252.64.0-173.252.127.255 > > > > > > > > > > > > -- > > > > > > M.S.I. Angel Haniel Cantu Jauregui. > > > > > > > > > > > > Celular: (011-52-1)-899-871-17-22 > > > > > > E-Mail: angel.cantu(a)sie-group.net > > > > > > Web: http://www.sie-group.net/ > > > > > > Cd. Reynosa Tamaulipas. > > > > > > _______________________________________________ > > > > > > CentOS-es mailing list > > > > > > CentOS-es(a)centos.org > > > > > > http://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > _______________________________________________ > > > > > CentOS-es mailing list > > > > > CentOS-es(a)centos.org > > > > > http://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > > > > > > > > > > > -- > > > > M.S.I. Angel Haniel Cantu Jauregui. > > > > > > > > Celular: (011-52-1)-899-871-17-22 > > > > E-Mail: angel.cantu(a)sie-group.net > > > > Web: http://www.sie-group.net/ > > > > Cd. Reynosa Tamaulipas. > > > > _______________________________________________ > > > > CentOS-es mailing list > > > > CentOS-es(a)centos.org > > > > http://lists.centos.org/mailman/listinfo/centos-es > > > > > > > _______________________________________________ > > > CentOS-es mailing list > > > CentOS-es(a)centos.org > > > http://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > -- > > M.S.I. Angel Haniel Cantu Jauregui. > > > > Celular: (011-52-1)-899-871-17-22 > > E-Mail: angel.cantu(a)sie-group.net > > Web: http://www.sie-group.net/ > > Cd. Reynosa Tamaulipas. > > _______________________________________________ > > CentOS-es mailing list > > CentOS-es(a)centos.org > > http://lists.centos.org/mailman/listinfo/centos-es > > > _______________________________________________ > CentOS-es mailing list > CentOS-es(a)centos.org > http://lists.centos.org/mailman/listinfo/centos-es > -- M.S.I. Angel Haniel Cantu Jauregui. Celular: (011-52-1)-899-871-17-22 E-Mail: angel.cantu(a)sie-group.net Web: http://www.sie-group.net/ Cd. Reynosa Tamaulipas.

12 years, 5 months

Re: [CentOS] Design changes are done in Fedora

by Les Mikesell

On Mon, Dec 29, 2014 at 8:04 PM, Warren Young <wyml(a)etr-usa.com> wrote: > >>> >>> the world where you design, build, and deploy The System is disappearing fast. >> >> Sure, if you don't care if you lose data, you can skip those steps. > > How did you jump from incremental feature roll-outs to data loss? There is no necessary connection there. No, it's not necessary for either code interfaces or data structures to change in backward-incompatible ways. But the people who push one kind of change aren't likely to care about the other either. > In fact, I’d say you have a bigger risk of data loss when moving between two systems released years apart than two systems released a month apart. That’s a huge software market in its own right: legacy data conversion. I'm not really arguing about the timing of changes, I'm concerned about the cost of unnecessary user interface changes, code interface breakage, and data incompatibility, regardless of when it happens. RHEL's reason for existence is that it mostly shields users from that within a major release. That doesn't make it better when it happens when you are forced to move to the next one. > If your software is DBMS-backed and a new feature changes the schema, you can use one of the many available systems for managing schema versions. Or, roll your own; it isn’t hard. Are you offering to do it for free? > You test before rolling something to production, and you run backups so that if all else fails, you can roll back to the prior version. That's fine if you have one machine and can afford to shut down while you make something work. Most businesses aren't like that. > None of this is revolutionary. It’s just what you do, every day. And it is time consuming and expensive. >> when it breaks it's not the developer answering >> the phones if anyone answers at all. > > Tech support calls shouldn’t go straight to the developers under any development model, short of sole proprietorship, and not even then, if you can get away with it. There needs to be at least one layer of buffering in there: train up the secretary to some basic level of cluefulness, do everything via email, or even hire some dedicated support staff. > > It simply costs too much to break a developer out of flow to allow a customer to ring a bell on a developer’s desk at will. Beg your pardon? How about not breaking the things that trigger the calls in the first place - or taking some responsibility for it. Do you think other people have nothing better to do? > Since we’re contrasting with waterfall development processes that may last many years, but not decades, I’d say the error has already been made if you’re still working with a waterfall-based methodology today. > We never change more than half of a load-balenced set of servers at once. So all changes have to be compatible when running concurrently, or worth rolling out a whole replacement farm. >> some stuff can't be. > > Very little software must be developed in waterfall fashion. If you run continuous services you either have to be able to run new/old concurrently or completely duplicate your server farm as you roll out incompatible clients. > Last time I checked, this sort of software only accounted for about ~5% of all software produced, and that fraction is likely dropping, with the moves toward cloud services, open source software, subscription software, and subsidized software. > > The vast majority of software developed is in-house stuff, where the developers and the users *can* enter into an agile delivery cycle. OK, but they have to not break existing interfaces when they do that. And that's not the case with OS upgrades. >> If you are, say, adding up dollars, how many times do you want that >> functionality to change? > > I’m not sure what you’re asking. I'm asking if computer science has advanced to the point where adding up a total needs new functionality, or if you would like the same total for the same numbers that you would have gotten last year. Or more to the point, if the same program ran correctly last year, wouldn't it be nice if it still ran the same way this year, in spite of the OS upgrade you need to do because of the security bugs that keep getting shipped while developers spend their time making arbitrary changes to user interfaces. > Compare a rolling release model like that of Cygwin or Ubuntu (not LTS). Something might break every few months, which sounds bad until you consider that the alternative is for *everything* to break at the same time, every 3-7 years. When your system requires extensive testing, the few times it breaks the better. Never would be nice... >>> I don’t mean that glibly. I mean you have made a fundamental mistake if your system breaks badly enough due to an OS change that you can’t fix it within an iteration or two of your normal development process. The most likely mistake is staffing your team entirely with people who have never been through a platform shift before. >> >> Please quantify that. How much should a business expect to spend per >> person to re-train their operations staff to keep their systems >> working across a required OS update? Not to add functionality. To >> keep something that was working running the way it was? > > If you hire competent people, you pay zero extra to do this, because this is the job they have been hired to do. That's nonsense for any complex system. There are always _many_ different OS versions in play and many different development groups that only understand a subset, and every new change they need to know about costs time and risks mistakes. > That's pretty much what IT/custom development is: coping with churn. And it is expensive. Unnecessarily so, in my opinion. >> How many customers for your service did you keep running non-stop >> across those transitions? > > Most of our customers are K-12 schools, so we’re not talking about a 24/7 system to begin with. K-12 runs maybe 9 hours a day (7am - 4pm), 5 days a week, 9 months out of the year. That gives us many upgrade windows. That's a very different scenario than a farm of data servers that have to be available 24/7. > We rarely change out hardware or the OS at a particular site. We generally run it until it falls over, dead. > > This means we’re still building binaries for EL3. I have a few of those, but I don't believe that is a sane thing to recommend. > This also means our software must *remain* broadly portable. When we talk about porting to EL7, we don’t mean that it stops working on EL6 and earlier. We might have some graceful feature degradation where the older OS simply can’t do something the newer one can, but we don’t just chop off an old OS because a new one came out. > You'd probably be better off in java if you aren't already. >>> Everyone’s moaning about systemd...at least it’s looking to be a real de facto standard going forward. >> >> What you expect to pay to re-train operations staff -just- for this >> change, -just- to keep things working the same.. > > You ask that as if you think you have a no-cost option in the question of how to address the churn. I ask it as if I think that software developers could make changes without breaking existing interfaces. And yes, I do think they could if they cared about anyone who built on those interfaces. >> We've got lots of stuff that will drop into Windows server versions >> spanning well over a 10 year range. > > Yes, well, Linux has always had a problem with ABI stability. Apparently the industry doesn’t really care about this, evidenced by the fizzling of LSB, and the current attacks on the work at freedesktop.org. Apparently we’d all rather be fractious than learn to get along well enough that we can nail down some real standards. Well, that has done a great job of keeping Microsoft in business. > I’ve never done much with Windows Server, but my sense is that they have plenty of churn over in their world, too. We’ve got SELinux and SystemD, they’ve got UAC, SxS DLLs, API deprecation, and tools that shuffle positions on every release. (Where did they move the IPv4 configuration dialog this time?!) > > We get worked up here about things like the loss of 32-bit support, but over in MS land, they get API-of-the-year. JET, ODBC, OLE DB, or ADO? Win32, .NET desktop, Silverlight, or Metro? GDI, WinG, DirectX, Windows Forms or XAML? On and on, and that’s just if you stay within the MSDN walls. Yes, there are changes - and sometimes mysterious breakage. But an outright abandonment of an existing interface that breaks previously working code s pretty rare (and I don't like it when they do it either...). >> Were you paying attention when Microsoft wanted to make XP obsolete? >> There is a lot of it still running. > > Were you paying attention when Target’s XP-based POS terminals all got pwned? > > Stability and compatibility are not universal goods. Well, some things you have to get right in the first place - and then stability is good. > Google already did that cost/benefit calculation: they tried staying on RH 7.1 indefinitely, and thereby built up 10 years of technical debt. Then when they did jump, it was a major undertaking, though one they apparently felt was worth doing. And conversely, they felt is was worth _not_ doing for a very very long time. So can the rest of us wait until we have google's resources? >> And why do you think it is a good thing >> for this to be a hard problem or for every individual user to be >> forced to solve it himself? > > I never said it was a good thing. I’m just reporting some observations from the field. Maybe I misunderstood - I thought you were defending the status quo - and the fedora developers that bring it to us. -- Les Mikesell lesmikesell(a)gmail.com

11 years, 3 months

Re: [CentOS-pt-br] Cluster no CentOS. Ajuda..

by CássioElias .

Umm..legal..tem como você me explicar o que são esses resources? Por exemplo...o resource home, resource pgsql, etc? O que esse resource faz? O que ele é? é porque parece que tenho que rodar um comando com esse resource, o comando: drbdadm create-md "resource" com esses vários resources, terei que rodar esse comando para cada um, certo? > Date: Wed, 4 Sep 2013 14:09:22 -0300 > From: asmartins(a)uem.br > To: centos-pt-br(a)centos.org > Subject: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda.. > > Olá Cássio, > > Bem, rodando com aquela configuração não, eu usei a tua como base :D > > Tenho DRBD em CentOS5, rodando, veja: > > [root@HUM-Srv2 ~]# rpm -qa |grep drbd > drbd83-8.3.8-1.el5.centos > kmod-drbd83-8.3.8-1.el5.centos > kmod-drbd83-8.3.2-6.el5_3 > > [root@HUM-Srv2 ~]# lvs > LV VG Attr LSize Origin Snap% Move Log Copy% Convert > home hum -wi-ao 5,00G > httpd hum -wi-ao 1,00G > pgsql hum -wi-ao 5,00G > root hum -wi-ao 4,00G > swap hum -wi-ao 8,00G > usr hum -wi-ao 5,00G > var hum -wi-ao 5,00G > > [root@HUM-Srv2 ~]# df -h > Sist. Arq. Tam Usad Disp Uso% Montado em > /dev/mapper/hum-root 3,9G 966M 2,8G 26% / > /dev/md0 99M 34M 60M 36% /boot > /dev/mapper/hum-usr 4,9G 1,8G 2,9G 38% /usr > /dev/mapper/hum-var 4,9G 2,4G 2,3G 52% /var > tmpfs 3,9G 0 3,9G 0% /dev/shm > /dev/drbd0 5,0G 139M 4,6G 3% /home > /dev/drbd1 5,0G 2,2G 2,6G 46% /var/lib/pgsql > /dev/drbd2 1008M 435M 523M 46% /var/www > > [root@HUM-Srv2 ~]# cat /etc/drbd.conf > # > global { > usage-count no; > } > common { > protocol C; > startup { > wfc-timeout 0; > degr-wfc-timeout 120; > } > disk { on-io-error detach; } > syncer { > rate 33M; > csums-alg md5; > } > net { > cram-hmac-alg sha1; > shared-secret "XXXXXXXXXX"; > sndbuf-size 0; > max-buffers 8000; > max-epoch-size 8000; > } > } > resource home { > device /dev/drbd0; > disk /dev/hum/home; > meta-disk internal; > on HUM-Srv1 { address 192.168.0.1:7790; } > on HUM-Srv2 { address 192.168.0.2:7790; } > } > resource pgsql { > device /dev/drbd1; > disk /dev/hum/pgsql; > meta-disk internal; > on HUM-Srv1 { address 192.168.0.1:7791; } > on HUM-Srv2 { address 192.168.0.2:7791; } > } > resource httpd { > device /dev/drbd2; > disk /dev/hum/httpd; > meta-disk internal; > on HUM-Srv1 { address 192.168.0.1:7792; } > on HUM-Srv2 { address 192.168.0.2:7792; } > } > > [root@HUM-Srv2 ~]# crm_mon > Defaulting to one-shot mode > You need to have curses available at compile time to enable console mode > > ============ > Last updated: Wed Sep 4 14:05:31 2013 > Current DC: hum-srv2 (1715e15d-2708-48a7-b0ff-4630267e95cd) > 2 Nodes configured. > 1 Resources configured. > ============ > > Node: hum-srv2 (1715e15d-2708-48a7-b0ff-4630267e95cd): online > Node: hum-srv1 (44725a77-39b0-4f44-b0e4-8e2d700df4fa): online > > Resource Group: HUM-SHI > IP-Addr (heartbeat::ocf:IPaddr2): Started hum-srv2 > DRDB_home (heartbeat:drbddisk): Started hum-srv2 > FS_home (heartbeat::ocf:Filesystem): Started hum-srv2 > DRBD_pgsql (heartbeat:drbddisk): Started hum-srv2 > FS_pgsql (heartbeat::ocf:Filesystem): Started hum-srv2 > DRBD_httpd (heartbeat:drbddisk): Started hum-srv2 > FS_httpd (heartbeat::ocf:Filesystem): Started hum-srv2 > PROG_pgsql (heartbeat::ocf:pgsql): Started hum-srv2 > PROG_apache (heartbeat::ocf:apache): Started hum-srv2 > > [root@HUM-Srv2 ~]# uptime > 14:06:26 up 572 days, 5:57, 1 user, load average: 0.04, 0.15, 0.13 > > Como você pode ver é um servidor LAPP (Linux/Apache/PHP/PostgreSQL) bem estável :D > > Att., > > Antonio. > > > ----- "CássioElias ." <cassioelias(a)hotmail.com> escreveu: > > > De: "CássioElias ." <cassioelias(a)hotmail.com> > > Para: "Lista de Discussão CentOS-BR" <centos-pt-br(a)centos.org> > > Enviadas: Quarta-feira, 4 de Setembro de 2013 11:27:23 (GMT-0300) Auto-Detected > > Assunto: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda.. > > > > Vichi...eu to ferrado. > > > > > > Acabei de formatar novamente os servidores CentOS e tentei fazer essa > > config que você passou... > > Deu kernel panic denovo...vou ter que formatar denovo... > > > > > > Outra coisa.. Essa config que você acabou de passar acredito que não > > deu certo não. > > Parece que deu conflito. Ele não aceitou as duas config mudando apenas > > algumas coisas. > > Tá certo essa config que você diz? Ela funciona ai com vocês? > > > > > > > Date: Wed, 4 Sep 2013 08:19:11 -0300 > > > From: asmartins(a)uem.br > > > To: centos-pt-br(a)centos.org > > > Subject: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda.. > > > > > > Olá Cássio, > > > > > > Não se preocupe em destruir tudo enquanto testa! É melhor fazer > > besteira agora do que > > > com as máquinas em produção! :D > > > > > > Sobre a histório do DRBD, vou te contar um segredo: no mundo unix > > (linux incluso) esqueça > > > que existem discos, partições, teclado, monitor, impressora... > > _tudo_ é _ARQUIVO_ ! Tá tudo lá > > > no /dev :D Podem ter formas de acesso diferentes, ser somente para > > escrita ou somente para > > > leitura (ou ambos), mas tudo é _ARQUIVO_. Então você vai usar como > > base para o DRBD um _ARQUIVO_, > > > que pode ser um disco (/dev/sda), uma partição (/dev/sda1), uma > > partição do LVM (/dev/vg_sys/lv_web), etc... > > > > > > No seu caso, se você particionou da forma como lhe disse vai ficar > > mais ou menos assim: > > > > > > > > > on centos-1.gnulinuxbr.com { > > > device /dev/drbd0; > > > disk /dev/vg_sys/lv_web; > > > address 10.0.20.1:7788; > > > meta-disk internal; > > > } > > > > > > on centos-2.gnulinuxbr.com { > > > device /dev/drbd0; > > > disk /dev/vg_sys/lv_web; > > > address 10.0.20.2:7788; > > > meta-disk internal; > > > } > > > > > > > > > on centos-1.gnulinuxbr.com { > > > device /dev/drbd1; > > > disk /dev/vg_sys/lv_mysql; > > > address 10.0.20.1:7789; > > > meta-disk internal; > > > } > > > > > > on centos-2.gnulinuxbr.com { > > > device /dev/drbd1; > > > disk /dev/vg_sys/lv_mysql; > > > address 10.0.20.2:7789; > > > meta-disk internal; > > > } > > > > > > Isso quer dizer, que você terá duas máquinas iguais, e usará as > > partições LVM (que são "arquivos" no /dev) > > > para servirem de base, uma em cada máquina, e o DRBD irá criar outro > > dispositivo (/dev/drbd0 ou outro nome, pode mudar) > > > que será usado para acesso a essa área, assim você irá montar p.ex. > > o /dev/drbd0 em /var/www e o /dev/drbd1 em /var/lib/mysql. > > > > > > Aqui tem mais sobre DRBD em LVM: > > http://www.drbd.org/users-guide/ch-lvm.html e no doc todo tem algumas > > coisas bem > > > interessantes para o futuro :D > > > > > > Att., > > > > > > Antonio. > > > > > > ----- "CássioElias ." <cassioelias(a)hotmail.com> escreveu: > > > > > > > De: "CássioElias ." <cassioelias(a)hotmail.com> > > > > Para: "Lista de Discussão CentOS-BR" <centos-pt-br(a)centos.org> > > > > Enviadas: Terça-feira, 3 de Setembro de 2013 23:51:20 (GMT-0300) > > Auto-Detected > > > > Assunto: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda.. > > > > > > > > Obrigado pela atenção Antônio. > > > > > > > > Devo dizer que entendi como funciona o DRBD, mas ainda não entendi > > > > como configura-lo. > > > > > > > > Ao que estou lendo parece que tenho que ter um HD separado para > > poder > > > > utiliza-lo? Isso procede? Não posso usa-lo apenas com 1 HD, o HD > > que > > > > está o S.O Linux? > > > > Outra coisa.. Tem como eu utilizar o DRBD apenas nas partições que > > eu > > > > quero? Por exemplo, fazer replica apenas do /var/lib/mysql e do > > > > /var/www ? Ou tenho especificamente que utilizar apenas o sda1 por > > > > exemplo? > > > > > > > > Veja esse arquivo de configuração de exemplo: > > > > > > > > # vim /etc/drbd.conf > > > > #!/bin/bash > > > > # You can find an example in > > /usr/share/doc/drbd.../drbd.conf.example > > > > > > > > #include "drbd.d/global_common.conf"; > > > > #include "drbd.d/*.res"; > > > > > > > > global { > > > > usage-count yes; > > > > } > > > > > > > > common { > > > > syncer { > > > > rate 100M; > > > > al-extents 257; > > > > } > > > > } > > > > > > > > resource mysql { > > > > protocol C; > > > > > > > > handlers { > > > > } > > > > > > > > startup { > > > > wfc-timeout 15; > > > > degr-wfc-timeout 20; # 2 minutes. > > > > become-primary-on both; > > > > } > > > > > > > > disk { > > > > on-io-error detach; > > > > } > > > > > > > > net { > > > > sndbuf-size 512k; > > > > timeout 60; # 6 seconds (unit = 0.1 > > > > seconds) > > > > connect-int 10; # 10 seconds (unit = 1 > > > > second) > > > > ping-int 10; # 10 seconds (unit = 1 > > > > second) > > > > ping-timeout 5; # 500 ms (unit = 0.1 > > > > seconds) > > > > max-buffers 2048; > > > > > > > > allow-two-primaries; > > > > after-sb-0pri discard-zero-changes; > > > > after-sb-0pri discard-least-changes; > > > > after-sb-1pri discard-secondary; > > > > after-sb-2pri disconnect; > > > > } > > > > > > > > syncer { > > > > rate 100M; > > > > al-extents 257; > > > > } > > > > > > > > on centos-1.gnulinuxbr.com { > > > > device /dev/drbd0; > > > > disk /dev/sda5; > > > > address 10.0.20.1:7788; > > > > meta-disk internal; > > > > } > > > > > > > > on centos-2.gnulinuxbr.com { > > > > device /dev/drbd0; > > > > disk /dev/sda5; > > > > address 10.0.20.2:7788; > > > > meta-disk internal; > > > > } > > > > } > > > > > > > > Em device foi utilizado o /dev/drbd0 como partição virtual para o > > > > drbd. Isso da certo? É correto? Posso usar isso? > > > > Em disk fou usado o /dev/sda5. Nele eu poderia usar o disco que > > está > > > > meu S.O? Por exemplo o sda1? > > > > Outra coisa, nesse disk eu poderia especificar qual ponto de > > montagem > > > > eu quero fazer backup? Por exemplo, poderia ficar assim? > > > > > > > > > > > > on centos-2.gnulinuxbr.com { > > > > device /dev/drbd0; > > > > disk /var/lib/mysql; > > > > disl /var/www; > > > > address 10.0.20.2:7788; > > > > meta-disk internal; > > > > } > > > > Pode ser assim, ou assim está errado? > > > > > > > > Hehehe....o cluster pelo corosync e pacemaker deu certinho. Os nós > > > > funcionaram perfeitamente. Fui tentar configurar o DRBD e fiz > > > > besteira, agora só aparece kernel panic. Vou ter que começar tudo > > > > denovo até ficar redondinho para produção. > > > > > > > > Obrigado, e agradeço a ajuda desde já! > > > > > > > > > > > > > Date: Tue, 3 Sep 2013 17:05:24 -0300 > > > > > From: asmartins(a)uem.br > > > > > To: centos-pt-br(a)centos.org > > > > > Subject: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda.. > > > > > > > > > > Olá Cássio! > > > > > > > > > > E o cluster? Agora esta funcionando? > > > > > > > > > > ----- "CássioElias ." <cassioelias(a)hotmail.com> escreveu: > > > > > > > > > > > > Entendi Antônio. Legal heim. Você deve trabalhar em > > universidade > > > > > > então, como você mesmo disse. > > > > > > Deve dar uma trabalho heim! Manter todos esses serviços e > > > > servidores > > > > > > online..hehe.. > > > > > > > > > > Sim, e além dos servidores também cuidamos da rede :D > > > > > > > > > > > > > > > > > Uma pergunta. Pela sua esperiência com DRDB, teria como você > > me > > > > > > explicar didaticamente para o que ele serve? > > > > > > O que ele faz eu sei, mas em teoria teria como você me > > explica-lo? > > > > > > > > > > > > > > > > O DRBD é básicamente um RAID1 (mirror) via rede, ou seja, um > > > > determinado > > > > > dispositivo (disco, partição, etc) é copiado e mantido em > > sincronia > > > > entre > > > > > dois computadores. A forma de acesso pode ser RW/RO ou RW/RW. > > Mas, a > > > > forma > > > > > mais básica é tudo que você escreve no disco do computador A é > > > > escrito > > > > > também no disco do computador B. Assim, se o computador A > > falhar, > > > > tem-se > > > > > uma cópia no computador B, que pode assumir o serviço. > > > > > > > > > > Basicamente é isso... mas dá para fazer algumas coisinhas a > > mais, > > > > que é > > > > > melhor não colocar aqui agora para não confundir. :D > > > > > > > > > > Att., > > > > > > > > > > Antonio. > > > > > > > > > > -- > > > > > Antonio da Silva Martins Jr. > > > > > Analista de Suporte > > > > > NPD - Núcleo de Processamento de Dados > > > > > UEM - Universidade Estadual de Maringá > > > > > email: asmartins(a)uem.br > > > > > fone: +55 (44) 3011-4015 / 3011-4411 > > > > > inoc-dba: 263076*100 > > > > > > > > > > "Real Programmers don’t need comments — the code is obvious." > > > > > > > > > > -- > > > > > Esta mensagem foi verificada pelo sistema de antivirus e > > > > > acredita-se estar livre de perigo. > > > > > > > > > > _______________________________________________ > > > > > CentOS-pt-br mailing list > > > > > CentOS-pt-br(a)centos.org > > > > > http://lists.centos.org/mailman/listinfo/centos-pt-br > > > > > > > > -- > > > > Esta mensagem foi verificada pelo sistema de antivírus e > > > > acredita-se estar livre de perigo. > > > > _______________________________________________ > > > > CentOS-pt-br mailing list > > > > CentOS-pt-br(a)centos.org > > > > http://lists.centos.org/mailman/listinfo/centos-pt-br > > > > > > -- > > > Antonio da Silva Martins Jr. > > > Analista de Suporte > > > NPD - Núcleo de Processamento de Dados > > > UEM - Universidade Estadual de Maringá > > > email: asmartins(a)uem.br > > > fone: +55 (44) 3011-4015 / 3011-4411 > > > inoc-dba: 263076*100 > > > > > > "Real Programmers don’t need comments — the code is obvious." > > > > > > -- > > > Esta mensagem foi verificada pelo sistema de antivirus e > > > acredita-se estar livre de perigo. > > > > > > _______________________________________________ > > > CentOS-pt-br mailing list > > > CentOS-pt-br(a)centos.org > > > http://lists.centos.org/mailman/listinfo/centos-pt-br > > > > -- > > Esta mensagem foi verificada pelo sistema de antivírus e > > acredita-se estar livre de perigo. > > _______________________________________________ > > CentOS-pt-br mailing list > > CentOS-pt-br(a)centos.org > > http://lists.centos.org/mailman/listinfo/centos-pt-br > > -- > Antonio da Silva Martins Jr. > Analista de Suporte > NPD - Núcleo de Processamento de Dados > UEM - Universidade Estadual de Maringá > email: asmartins(a)uem.br > fone: +55 (44) 3011-4015 / 3011-4411 > inoc-dba: 263076*100 > > "Real Programmers don’t need comments — the code is obvious." > > -- > Esta mensagem foi verificada pelo sistema de antivirus e > acredita-se estar livre de perigo. > > _______________________________________________ > CentOS-pt-br mailing list > CentOS-pt-br(a)centos.org > http://lists.centos.org/mailman/listinfo/centos-pt-br

12 years, 7 months

[CentOS-virt] xendomains not autostarting

by Ben M.

I have been scratching my head on this for days. Xendomains services just doesn't want to start at boot it seems, so I don't get my auto-domU's up without "service xendomains start" and the all start. chkconfig looks correct, I have checked xm dmesg, dmesg, turned off selinux and the only "clue" I have is that the xend.log startup looks different than a fairly similar machine and I don't quite understand what it might be saying. Is dom0 crashing and restarting at machine bootup? I have only one domU in ../auto to keep this simpler, its name is "v22c54" and I have one other anomaly: smartd is also not starting on services boot up but apparently runs fine with a manual command. === xend.log boot up === [2009-11-30 08:40:53 xend 3466] INFO (SrvDaemon:283) Xend Daemon started [2009-11-30 08:40:53 xend 3466] INFO (SrvDaemon:287) Xend changeset: unavailable. [2009-11-30 08:40:53 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:228) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 19493383087L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'mem_kb': 1048576L, 'domid': 0, 'max_vcpu_id': 3, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'online_vcpus': 4, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0}) [2009-11-30 08:40:53 xend.XendDomainInfo 3466] INFO (XendDomainInfo:240) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2009-11-30 08:40:53 xend.XendDomainInfo 3466] WARNING (XendDomainInfo:262) No vm path in store for existing domain 0 [2009-11-30 08:40:53 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:992) Storing VM details: {'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0', 'xend/restart_count': '0', 'vcpus': '4', 'vcpu_avail': '15', 'memory': '1024', 'on_crash': 'restart', 'maxmem': '1024'} [2009-11-30 08:40:53 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:1027) Storing domain details: {'cpu/1/availability': 'online', 'cpu/3/availability': 'online', 'name': 'Domain-0', 'console/limit': '4194304', 'cpu/2/availability': 'online', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'memory/target': '1048576'} [2009-11-30 08:40:53 xend 3466] DEBUG (XendDomain:163) number of vcpus to use is 2 [2009-11-30 08:40:53 xend 3466] INFO (SrvServer:116) unix path=/var/lib/xend/xend-socket [2009-11-30 08:40:53 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:1249) XendDomainInfo.handleShutdownWatch == after manual xendomains start == [root@localhost ~]# service xendomains start Restoring Xen domains: v22c54. Starting auto Xen domains: v22c54(skip)[done] [ OK ] ~~ xend.log cont'd from above point ~~ [2009-11-30 11:17:15 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:287) XendDomainInfo.restore(['domain', ['domid', '3'], ['uuid', 'a3199faf-edb4-42e5-bea1-01f2df77a47f'], ['vcpus', '1'], ['vcpu_avail', '1'], ['cpu_cap', '0'], ['cpu_weight', '256.0'], ['memory', '512'], ['shadow_memory', '0'], ['maxmem', '512'], ['bootloader', '/usr/bin/pygrub'], ['features'], ['name', 'v22c54'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['ramdisk', '/var/lib/xen/boot_ramdisk.yFE7zn'], ['kernel', '/var/lib/xen/boot_kernel.bnNF6O'], ['args', 'ro root=/dev/vgcentos00/root']]], ['cpus', []], ['device', ['vif', ['backend', '0'], ['script', 'vif-bridge'], ['bridge', 'xenbr1'], ['mac', '00:16:36:41:76:ae']]], ['device', ['tap', ['backend', '0'], ['dev', 'xvda:disk'], ['uname', 'tap:aio:/var/lib/xen/images/vms/v22c54'], ['mode', 'w']]], ['device', ['vkbd', ['backend', '0']]], ['device', ['vfb', ['backend', '0'], ['type', 'vnc'], ['vncunused', '1'], ['xauthority', '/root/.Xauthority'], ['keymap', 'en-us']]], ['state', '-b----'], ['shutdown_reason', 'poweroff'], ['cpu_time', '0.008262668'], ['online_vcpus', '1'], ['up_time', '305.694555044'], ['start_time', '1259414461.79'], ['store_mfn', '1875035'], ['console_mfn', '2193022']]) [2009-11-30 11:17:15 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:328) parseConfig: config is ['domain', ['domid', '3'], ['uuid', 'a3199faf-edb4-42e5-bea1-01f2df77a47f'], ['vcpus', '1'], ['vcpu_avail', '1'], ['cpu_cap', '0'], ['cpu_weight', '256.0'], ['memory', '512'], ['shadow_memory', '0'], ['maxmem', '512'], ['bootloader', '/usr/bin/pygrub'], ['features'], ['name', 'v22c54'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['ramdisk', '/var/lib/xen/boot_ramdisk.yFE7zn'], ['kernel', '/var/lib/xen/boot_kernel.bnNF6O'], ['args', 'ro root=/dev/vgcentos00/root']]], ['cpus', []], ['device', ['vif', ['backend', '0'], ['script', 'vif-bridge'], ['bridge', 'xenbr1'], ['mac', '00:16:36:41:76:ae']]], ['device', ['tap', ['backend', '0'], ['dev', 'xvda:disk'], ['uname', 'tap:aio:/var/lib/xen/images/vms/v22c54'], ['mode', 'w']]], ['device', ['vkbd', ['backend', '0']]], ['device', ['vfb', ['backend', '0'], ['type', 'vnc'], ['vncunused', '1'], ['xauthority', '/root/.Xauthority'], ['keymap', 'en-us']]], ['state', '-b----'], ['shutdown_reason', 'poweroff'], ['cpu_time', '0.008262668'], ['online_vcpus', '1'], ['up_time', '305.694555044'], ['start_time', '1259414461.79'], ['store_mfn', '1875035'], ['console_mfn', '2193022']] [2009-11-30 11:17:15 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:445) parseConfig: result is {'features': None, 'image': ['linux', ['ramdisk', '/var/lib/xen/boot_ramdisk.yFE7zn'], ['kernel', '/var/lib/xen/boot_kernel.bnNF6O'], ['args', 'ro root=/dev/vgcentos00/root']], 'cpus': [], 'vcpu_avail': 1, 'backend': [], 'uuid': 'a3199faf-edb4-42e5-bea1-01f2df77a47f', 'on_reboot': 'restart', 'cpu_weight': 256.0, 'memory': 512, 'cpu_cap': 0, 'localtime': None, 'timer_mode': None, 'start_time': 1259414461.79, 'on_poweroff': 'destroy', 'on_crash': 'restart', 'device': [('vif', ['vif', ['backend', '0'], ['script', 'vif-bridge'], ['bridge', 'xenbr1'], ['mac', '00:16:36:41:76:ae']]), ('tap', ['tap', ['backend', '0'], ['dev', 'xvda:disk'], ['uname', 'tap:aio:/var/lib/xen/images/vms/v22c54'], ['mode', 'w']]), ('vkbd', ['vkbd', ['backend', '0']]), ('vfb', ['vfb', ['backend', '0'], ['type', 'vnc'], ['vncunused', '1'], ['xauthority', '/root/.Xauthority'], ['keymap', 'en-us']])], 'bootloader': '/usr/bin/pygrub', 'maxmem': 512, 'shadow_memory': 0, 'name': 'v22c54', 'bootloader_args': None, 'vcpus': 1, 'cpu': None} [2009-11-30 11:17:15 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:1774) XendDomainInfo.construct: None [2009-11-30 11:17:15 xend 3466] DEBUG (balloon:145) Balloon: 7021072 KiB free; need 4096; done. [2009-11-30 11:17:15 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:992) Storing VM details: {'shadow_memory': '0', 'uuid': 'a3199faf-edb4-42e5-bea1-01f2df77a47f', 'on_crash': 'restart', 'on_reboot': 'restart', 'start_time': '1259414461.79', 'on_poweroff': 'destroy', 'name': 'v22c54', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '512', 'bootloader': '/usr/bin/pygrub', 'image': "(linux (ramdisk /var/lib/xen/boot_ramdisk.yFE7zn) (kernel /var/lib/xen/boot_kernel.bnNF6O) (args 'ro root=/dev/vgcentos00/root'))", 'maxmem': '512'} [2009-11-30 11:17:15 xend 3466] DEBUG (DevController:114) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vkbd/1/0'} to /local/domain/1/device/vkbd/0. [2009-11-30 11:17:15 xend 3466] DEBUG (DevController:116) DevController: writing {'frontend-id': '1', 'domain': 'v22c54', 'frontend': '/local/domain/1/device/vkbd/0', 'state': '1', 'online': '1'} to /local/domain/0/backend/vkbd/1/0. [2009-11-30 11:17:15 xend 3466] DEBUG (DevController:114) DevController: writing {'backend-id': '0', 'mac': '00:16:36:41:76:ae', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0. [2009-11-30 11:17:15 xend 3466] DEBUG (DevController:116) DevController: writing {'bridge': 'xenbr1', 'domain': 'v22c54', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/1/device/vif/0', 'mac': '00:16:36:41:76:ae', 'online': '1', 'frontend-id': '1'} to /local/domain/0/backend/vif/1/0. [2009-11-30 11:17:15 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:633) Checking for duplicate for uname: /var/lib/xen/images/vms/v22c54 [tap:aio:/var/lib/xen/images/vms/v22c54], dev: xvda:disk, mode: w [2009-11-30 11:17:15 xend 3466] DEBUG (blkif:27) exception looking up device number for xvda:disk: [Errno 2] No such file or directory: '/dev/xvda:disk' [2009-11-30 11:17:15 xend 3466] DEBUG (blkif:27) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2009-11-30 11:17:15 xend 3466] DEBUG (blkif:27) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2009-11-30 11:17:15 xend 3466] DEBUG (DevController:114) DevController: writing {'backend-id': '0', 'virtual-device': '51712', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/tap/1/51712'} to /local/domain/1/device/vbd/51712. [2009-11-30 11:17:15 xend 3466] DEBUG (DevController:116) DevController: writing {'domain': 'v22c54', 'frontend': '/local/domain/1/device/vbd/51712', 'format': 'raw', 'dev': 'xvda', 'state': '1', 'params': 'aio:/var/lib/xen/images/vms/v22c54', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'tap'} to /local/domain/0/backend/tap/1/51712. [2009-11-30 11:17:15 xend 3466] DEBUG (DevController:114) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vfb/1/0'} to /local/domain/1/device/vfb/0. [2009-11-30 11:17:15 xend 3466] DEBUG (DevController:116) DevController: writing {'vncunused': '1', 'domain': 'v22c54', 'frontend': '/local/domain/1/device/vfb/0', 'xauthority': '/root/.Xauthority', 'state': '1', 'keymap': 'en-us', 'online': '1', 'frontend-id': '1', 'type': 'vnc'} to /local/domain/0/backend/vfb/1/0. [2009-11-30 11:17:15 xend 3466] DEBUG (vfbif:70) No VNC passwd configured for vfb access [2009-11-30 11:17:15 xend 3466] DEBUG (vfbif:11) Spawn: ['/usr/lib64/xen/bin/qemu-dm', '-M', 'xenpv', '-d', '1', '-domain-name', 'v22c54', '-vnc', '127.0.0.1:0', '-vncunused', '-k', 'en-us'] [2009-11-30 11:17:15 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:1027) Storing domain details: {'console/port': '2', 'name': 'v22c54', 'console/limit': '4194304', 'vm': '/vm/a3199faf-edb4-42e5-bea1-01f2df77a47f', 'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/port': '1'} [2009-11-30 11:17:15 xend 3466] DEBUG (XendCheckpoint:200) restore:shadow=0x0, _static_max=0x200, _static_min=0x200, [2009-11-30 11:17:15 xend 3466] DEBUG (balloon:145) Balloon: 7021064 KiB free; need 524288; done. [2009-11-30 11:17:15 xend 3466] DEBUG (XendCheckpoint:217) [xc_restore]: /usr/lib64/xen/bin/xc_restore 20 1 1 2 0 0 0 [2009-11-30 11:17:15 xend 3466] INFO (XendCheckpoint:353) xc_domain_restore start: p2m_size = 20800 [2009-11-30 11:17:15 xend 3466] INFO (XendCheckpoint:353) Reloading memory pages: 0% [2009-11-30 11:17:21 xend 3466] INFO (XendCheckpoint:353) Received all pages (0 races) [2009-11-30 11:17:21 xend 3466] INFO (XendCheckpoint:3100% [2009-11-30 11:17:21 xend 3466] INFO (XendCheckpoint:353) Memory reloaded (35912 pages) [2009-11-30 11:17:21 xend 3466] INFO (XendCheckpoint:353) Domain ready to be built. [2009-11-30 11:17:21 xend 3466] DEBUG (XendCheckpoint:324) store-mfn 1842329 [2009-11-30 11:17:21 xend 3466] DEBUG (XendCheckpoint:324) console-mfn 2117145 [2009-11-30 11:17:21 xend 3466] INFO (XendCheckpoint:353) Restore exit with rc=0 [2009-11-30 11:17:21 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:927) XendDomainInfo.completeRestore [2009-11-30 11:17:21 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:1027) Storing domain details: {'console/ring-ref': '2117145', 'console/port': '2', 'name': 'v22c54', 'console/limit': '4194304', 'vm': '/vm/a3199faf-edb4-42e5-bea1-01f2df77a47f', 'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/ring-ref': '1842329', 'store/port': '1'} [2009-11-30 11:17:21 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:943) XendDomainInfo.completeRestore done [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:158) Waiting for devices vif. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:164) Waiting for 0. [2009-11-30 11:17:21 xend.XendDomainInfo 3466] DEBUG (XendDomainInfo:1249) XendDomainInfo.handleShutdownWatch [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:509) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:523) hotplugStatusCallback 1. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:158) Waiting for devices usb. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:158) Waiting for devices vbd. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:158) Waiting for devices irq. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:158) Waiting for devices vkbd. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:164) Waiting for 0. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:509) hotplugStatusCallback /local/domain/0/backend/vkbd/1/0/hotplug-status. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:523) hotplugStatusCallback 1. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:158) Waiting for devices vfb. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:164) Waiting for 0. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:509) hotplugStatusCallback /local/domain/0/backend/vfb/1/0/hotplug-status. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:523) hotplugStatusCallback 1. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:158) Waiting for devices pci. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:158) Waiting for devices ioports. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:158) Waiting for devices tap. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:164) Waiting for 51712. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:509) hotplugStatusCallback /local/domain/0/backend/tap/1/51712/hotplug-status. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:523) hotplugStatusCallback 1. [2009-11-30 11:17:21 xend 3466] DEBUG (DevController:158) Waiting for devices vtpm.

16 years, 4 months

Re: [CentOS] Raspberry PI3 - CentOS armv7hl gnome desktop

by dsavage＠peaknet.net

> Maybe there is a better place to post this message but as my question > was still CentOS related thought I would start here. Please advise if > there is a better forum of which to ask this question. > > I am playing around with making a "desktop" workstation out of a > Raspberry PI3. I have had no problems installing the OS and pretty much > have everything working except a Gnome desktop. > > I did: > > > yum groupinstall "GNOME Desktop" > > and from what I can tell everything necessary is installed. However when > I try to start X up I see it try and start, the display blinks as if > everything is good and then drops back down to the console. The log file > shown below shows a single error ([ 2665.952] (EE) AIGLX: reverting to > software rendering). > > [ 2665.710] > X.Org X Server 1.17.2 > Release Date: 2015-06-16 > [ 2665.725] X Protocol Version 11, Revision 0 > [ 2665.731] Build Operating System: 4.5.7-fedora-4 > [ 2665.736] Current Operating System: Linux centos-rpi3 4.4.33-v7.1.el7 > #1 SMP Mon Nov 21 18:48:06 UTC 2016 armv7l > [ 2665.736] Kernel command line: 8250.nr_uarts=0 dma.dmachans=0x7f35 > bcm2708_fb.fbwidth=1872 bcm2708_fb.fbheight=1168 > bcm2709.boardrev=0xa22082 bcm2709.serial=0x54bd9ed0 > smsc95xx.macaddr=B8:27:EB:BD:9E:D0 bcm2708_fb.fbswap=1 > bcm2709.uart_clock=48000000 vc_mem.mem_base=0x3dc00000 > vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 > console=tty1 root=/dev/mmcblk0p3 rootfstype=ext4 elevator=deadline > rootwait selinux=1 security=selinux enforcing=0 > [ 2665.756] Build Date: 09 November 2016 05:46:31PM > [ 2665.763] Build ID: xorg-x11-server 1.17.2-22.el7 > [ 2665.769] Current version of pixman: 0.34.0 > [ 2665.783] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 2665.783] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 2665.812] (==) Log file: "/var/log/Xorg.1.log", Time: Sat Dec 31 > 20:08:58 2016 > [ 2665.819] (==) Using config file: "/etc/X11/xorg.conf" > [ 2665.827] (==) Using system config directory > "/usr/share/X11/xorg.conf.d" > [ 2665.828] (==) ServerLayout "Default Layout" > [ 2665.828] (**) |-->Screen "Screen0" (0) > [ 2665.828] (**) | |-->Monitor "Monitor0" > [ 2665.829] (**) | |-->Device "VideocoreIV" > [ 2665.829] (**) |-->Input Device "Keyboard0" > [ 2665.829] (==) Automatically adding devices > [ 2665.829] (==) Automatically enabling devices > [ 2665.830] (==) Automatically adding GPU devices > [ 2665.830] (==) Max clients allowed: 256, resource mask: 0x1fffff > [ 2665.830] (==) FontPath set to: > catalogue:/etc/X11/fontpath.d, > built-ins > [ 2665.830] (==) ModulePath set to "/usr/lib/xorg/modules" > [ 2665.830] (II) The server relies on udev to provide the list of input > devices. > If no devices become available, reconfigure udev or disable > AutoAddDevices. > [ 2665.830] (WW) Hotplugging is on, devices using drivers 'kbd', > 'mouse' or 'vmmouse' will be disabled. > [ 2665.830] (WW) Disabling Keyboard0 > [ 2665.830] (II) Loader magic: 0x54cf7004 > [ 2665.830] (II) Module ABI versions: > [ 2665.830] X.Org ANSI C Emulation: 0.4 > [ 2665.830] X.Org Video Driver: 19.0 > [ 2665.830] X.Org XInput driver : 21.0 > [ 2665.830] X.Org Server Extension : 9.0 > [ 2665.831] (II) no primary bus or device found > [ 2665.831] (II) LoadModule: "glx" > [ 2665.832] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so > [ 2665.855] (II) Module glx: vendor="X.Org Foundation" > [ 2665.855] compiled for 1.17.2, module version = 1.0.0 > [ 2665.855] ABI class: X.Org Server Extension, version 9.0 > [ 2665.855] (==) AIGLX enabled > [ 2665.855] (II) LoadModule: "fbdev" > [ 2665.856] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so > [ 2665.857] (II) Module fbdev: vendor="X.Org Foundation" > [ 2665.857] compiled for 1.17.2, module version = 0.4.3 > [ 2665.857] Module class: X.Org Video Driver > [ 2665.857] ABI class: X.Org Video Driver, version 19.0 > [ 2665.857] (II) FBDEV: driver for framebuffer: fbdev > [ 2665.857] (++) using VT number 1 > > [ 2665.857] (WW) Falling back to old probe method for fbdev > [ 2665.857] (II) Loading sub module "fbdevhw" > [ 2665.857] (II) LoadModule: "fbdevhw" > [ 2665.858] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so > [ 2665.859] (II) Module fbdevhw: vendor="X.Org Foundation" > [ 2665.859] compiled for 1.17.2, module version = 0.0.2 > [ 2665.859] ABI class: X.Org Video Driver, version 19.0 > [ 2665.859] (II) FBDEV(0): using default device > [ 2665.859] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card > support > [ 2665.860] (**) FBDEV(0): Depth 24, (--) framebuffer bpp 32 > [ 2665.860] (==) FBDEV(0): RGB weight 888 > [ 2665.860] (==) FBDEV(0): Default visual is TrueColor > [ 2665.860] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) > [ 2665.860] (II) FBDEV(0): hardware: BCM2708 FB (video memory: 8541kB) > > [ 2665.860] (II) FBDEV(0): checking modes against framebuffer device... > [ 2665.860] (II) FBDEV(0): mode "1920x1200" not found > [ 2665.860] (II) FBDEV(0): mode "1600x1200" ok > [ 2665.860] (II) FBDEV(0): mode "1280x1024" ok > [ 2665.860] (II) FBDEV(0): mode "1152x864" ok > [ 2665.860] (II) FBDEV(0): mode "1024x768" ok > [ 2665.861] (II) FBDEV(0): mode "800x600" ok > [ 2665.861] (II) FBDEV(0): mode "720x400" ok > [ 2665.861] (II) FBDEV(0): mode "640x480" ok > [ 2665.861] (II) FBDEV(0): checking modes against monitor... > [ 2665.861] (--) FBDEV(0): Virtual size is 1600x1200 (pitch 1600) > [ 2665.861] (**) FBDEV(0): Default mode "1600x1200": 162.0 MHz (scaled > from 0.0 MHz), 75.0 kHz, 60.0 Hz > [ 2665.861] (II) FBDEV(0): Modeline "1600x1200"x0.0 162.00 1600 1664 > 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz d) > [ 2665.861] (**) FBDEV(0): Default mode "1280x1024": 108.0 MHz (scaled > from 0.0 MHz), 64.0 kHz, 60.0 Hz > [ 2665.861] (II) FBDEV(0): Modeline "1280x1024"x0.0 108.00 1280 1328 > 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz d) > [ 2665.861] (**) FBDEV(0): Default mode "1152x864": 108.0 MHz (scaled > from 0.0 MHz), 67.5 kHz, 75.0 Hz > [ 2665.861] (II) FBDEV(0): Modeline "1152x864"x0.0 108.00 1152 1216 > 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz d) > [ 2665.861] (**) FBDEV(0): Default mode "1024x768": 65.0 MHz (scaled > from 0.0 MHz), 48.4 kHz, 60.0 Hz > [ 2665.861] (II) FBDEV(0): Modeline "1024x768"x0.0 65.00 1024 1048 > 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d) > [ 2665.861] (**) FBDEV(0): Default mode "800x600": 36.0 MHz (scaled > from 0.0 MHz), 35.2 kHz, 56.2 Hz > [ 2665.861] (II) FBDEV(0): Modeline "800x600"x0.0 36.00 800 824 896 > 1024 600 601 603 625 +hsync +vsync (35.2 kHz d) > [ 2665.862] (**) FBDEV(0): Default mode "640x480": 25.2 MHz (scaled > from 0.0 MHz), 31.5 kHz, 59.9 Hz > [ 2665.862] (II) FBDEV(0): Modeline "640x480"x0.0 25.18 640 656 752 > 800 480 490 492 525 -hsync -vsync (31.5 kHz d) > [ 2665.862] (**) FBDEV(0): Display dimensions: (518, 324) mm > [ 2665.862] (**) FBDEV(0): DPI set to (78, 94) > [ 2665.862] (II) Loading sub module "fb" > [ 2665.862] (II) LoadModule: "fb" > [ 2665.863] (II) Loading /usr/lib/xorg/modules/libfb.so > [ 2665.864] (II) Module fb: vendor="X.Org Foundation" > [ 2665.864] compiled for 1.17.2, module version = 1.0.0 > [ 2665.865] ABI class: X.Org ANSI C Emulation, version 0.4 > [ 2665.865] (**) FBDEV(0): using shadow framebuffer > [ 2665.865] (II) Loading sub module "shadow" > [ 2665.865] (II) LoadModule: "shadow" > [ 2665.865] (II) Loading /usr/lib/xorg/modules/libshadow.so > [ 2665.865] (II) Module shadow: vendor="X.Org Foundation" > [ 2665.865] compiled for 1.17.2, module version = 1.1.0 > [ 2665.866] ABI class: X.Org ANSI C Emulation, version 0.4 > [ 2665.866] (==) Depth 24 pixmap format is 32 bpp > [ 2665.892] (==) FBDEV(0): Backing store enabled > [ 2665.894] (**) FBDEV(0): DPMS enabled > [ 2665.894] (==) RandR enabled > [ 2665.945] (II) SELinux: Disabled by boolean > [ 2665.952] (II) AIGLX: Screen 0 is not DRI2 capable > [ 2665.952] (EE) AIGLX: reverting to software rendering > [ 2665.998] (II) AIGLX: Loaded and initialized swrast > [ 2665.998] (II) GLX: Initialized DRISWRAST GL provider for screen 0 > [ 2666.260] (II) config/udev: Adding input device CM Storm QuickFire > Rapid keyboard (/dev/input/event0) > [ 2666.260] (**) CM Storm QuickFire Rapid keyboard: Applying InputClass > "evdev keyboard catchall" > [ 2666.260] (II) LoadModule: "evdev" > [ 2666.261] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so > [ 2666.263] (II) Module evdev: vendor="X.Org Foundation" > [ 2666.263] compiled for 1.17.2, module version = 2.9.2 > [ 2666.264] Module class: X.Org XInput Driver > [ 2666.264] ABI class: X.Org XInput driver, version 21.0 > [ 2666.264] (II) Using input driver 'evdev' for 'CM Storm QuickFire > Rapid keyboard' > [ 2666.264] (**) CM Storm QuickFire Rapid keyboard: always reports core > events > [ 2666.264] (**) evdev: CM Storm QuickFire Rapid keyboard: Device: > "/dev/input/event0" > [ 2666.264] (--) evdev: CM Storm QuickFire Rapid keyboard: Vendor > 0x2516 Product 0x4 > [ 2666.265] (--) evdev: CM Storm QuickFire Rapid keyboard: Found keys > [ 2666.265] (II) evdev: CM Storm QuickFire Rapid keyboard: Configuring > as keyboard > [ 2666.265] (**) Option "config_info" > "udev:/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/0003:2516:0004.000E/input/input13/event0" > [ 2666.265] (II) XINPUT: Adding extended input device "CM Storm > QuickFire Rapid keyboard" (type: KEYBOARD, id 6) > [ 2666.265] (**) Option "xkb_rules" "evdev" > [ 2666.270] (II) config/udev: Adding input device CM Storm QuickFire > Rapid keyboard (/dev/input/event1) > [ 2666.270] (**) CM Storm QuickFire Rapid keyboard: Applying InputClass > "evdev keyboard catchall" > [ 2666.270] (II) Using input driver 'evdev' for 'CM Storm QuickFire > Rapid keyboard' > [ 2666.270] (**) CM Storm QuickFire Rapid keyboard: always reports core > events > [ 2666.270] (**) evdev: CM Storm QuickFire Rapid keyboard: Device: > "/dev/input/event1" > [ 2666.271] (--) evdev: CM Storm QuickFire Rapid keyboard: Vendor > 0x2516 Product 0x4 > [ 2666.271] (--) evdev: CM Storm QuickFire Rapid keyboard: Found keys > [ 2666.271] (II) evdev: CM Storm QuickFire Rapid keyboard: Configuring > as keyboard > [ 2666.271] (**) Option "config_info" > "udev:/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.1/0003:2516:0004.000F/input/input14/event1" > [ 2666.271] (II) XINPUT: Adding extended input device "CM Storm > QuickFire Rapid keyboard" (type: KEYBOARD, id 7) > [ 2666.271] (**) Option "xkb_rules" "evdev" > [ 2666.623] (II) evdev: CM Storm QuickFire Rapid keyboard: Close > [ 2666.623] (II) UnloadModule: "evdev" > [ 2666.623] (II) evdev: CM Storm QuickFire Rapid keyboard: Close > [ 2666.623] (II) UnloadModule: "evdev" > [ 2666.703] (II) Server terminated successfully (0). Closing log file. > > I used this /etc.X11/xorg.conf: > > Section "ServerLayout" > Identifier "Default Layout" > Screen 0 "Screen0" 0 0 > InputDevice "Keyboard0" "CoreKeyboard" > EndSection > > Section "InputDevice" > Identifier "Keyboard0" > Driver "kbd" > Option "XkbModel" "pc105" > Option "XkbLayout" "us" > EndSection > > Section "Device" > Identifier "VideocoreIV" > VendorName "Broadcom" > BoardName "RPI3Graphics" > Driver "fbdev" > EndSection > > Section "Monitor" > Identifier "Monitor0" > VendorName "Dell" > ModelName "Ultrasharp U2410" > DisplaySize 518 324 > HorizSync 30.0 - 81.0 > VertRefresh 56.0 - 75.0 > Option "DPMS" > EndSection > > Section "Screen" > Identifier "Screen0" > Device "VideocoreIV" > Monitor "Monitor0" > DefaultDepth 24 > SubSection "Display" > Viewport 0 0 > Depth 24 > Modes "1920x1200" "1600x1200" "1280x1024" > "1152x864" "1024x768" "800x600" "720x400" "640x480" > EndSubSection > EndSection > > Does anybody see what I am doing wrong? Like I said it looks like the > desktop wants to startup but then just crshes. > > Thanks for your help. > > Paul (ganci(a)nurdog.com) > Cell: (303)257-5208 > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > > The only real problem I see is here: [ 2665.952] (EE) AIGLX: reverting to software rendering It appears that CentOS wants to use hardware acceleration that the Pi can't do. Video is definitely one of the Pi's weaker capabilities. Compared to the other desktops, GNOME is a resource hog. I'm a MATE guy, so I can't yet speak to the CentOS ARM build. I do know that the MATE Spin for Fedora 25 ARM installed perfectly on my Raspberry Pi3. --Doc Savage Fairview Heights, IL

9 years, 3 months

Re: [CentOS-es] Configurar Telefono Cisco 7940G !

by Andres Genovez

Estimado EPE pidiendote las disculpas necesarias, en realidad el compañero está subiendo su tftp y dhcp en CentOS, me imagino ;) Angel te paso la configuración SIPBLABLABLA.cnf ---code----------- image_version: P0S3-08-11-00 line1_name: "906" line1_authname: "906" line1_shortname: "DT" line1_password: "hackme" line1_displayname: "DT"; no utilizar nombres largos, caracteres especiales o sino sale como UNPROVISIONED proxy1_port: "5060" proxy1_address: "172.16.289.254" nat_enable: "1" outbound_proxy: "172.16.289.254" outbound_proxy_port: "5060" proxy_register: "1" timer_register_expires: "1" sntp_mode: "directedbroadcast" sntp_server: "133.300.400.1"; servidor de hora time_zone: "CST" time_format_24hr: "1" phone_label: "sietepingas.com " ; add a space at the end, looks neater phone_password: "cisco" ; Limited to 31 characters (Default - cisco) user_info: none telnet_level: 2 logo_url: "http://192.887.988.400/logo-pepito.bmp" ----code-------------- Obvio las ips son ficticias las tendrás que colocar de acuerdo a tus configuraciones. Saludos. El 12 de noviembre de 2013 10:42, angel jauregui <darkdiabliyo(a)gmail.com>escribió: > LEs confirmo que ya pude hacer que se descargara el firmware al telefono y > pusiera la vendita leyenda de "SIP". > > El problema estaba en mi DHCP, les dejo mi configuracion: > > *shell# cat /etc/dhcp/dhcpd.conf* > ddns-update-style interim; > ddns-updates on; > ddns-domainname "midominio.com"; > ddns-rev-domainname "in-addr.arpa."; > ignore client-updates; > authoritative; > default-lease-time 600; > max-lease-time 7200; > option ip-forwarding off; > option domain-name "midominio.com"; > option tftp-server-name "10.0.1.1"; > option boot-server code 66 = string; > option boot-server "10.0.1.1"; > option option-66 code 66 = text; > option option-67 code 67 = text; > option vlan-flag code 190 = unsigned integer 8; > option voice-vlan-id code 191 = unsigned integer 16; > option data-vlan-id code 192 = unsigned integer 16; > # option voip-tftp-servers 10.0.1.1; > # option voip-tftp-servers code 150 = ip-address; > option ntp-servers 0.pool.ntp.org, 1.poo.ntp.org, 2.pool.ntp.org, > 3.pool.ntp.org; > log-facility local7; > allow bootp; > allow booting; > > include "/etc/rndc.key"; > > zone 1.0.10.in-addr.arpa. { > primary 127.0.0.1; > key rndc-key; > } > > zone midominio.com. { > primary 127.0.0.1; > key rndc-key; > } > > shared-network midominiocom { > subnet 10.0.1.0 netmask 255.255.255.0 { > option routers 10.0.1.1; > option subnet-mask 255.255.255.0; > option broadcast-address 10.0.1.255; > option domain-name-servers ns1.midominio.com; > option netbios-name-servers 10.0.1.1; > range 10.0.1.100 10.0.1.150; > filename "pxelinux.0"; > } > host diabliyo { > option host-name "diabliyo.midominio.com"; > hardware ethernet 44:1E:A1:D7:B7:83; > fixed-address 10.0.1.10; > } > host diabliyo2 { > option host-name "diabliyo2.midominio.com"; > hardware ethernet AC:81:12:92:34:12; > fixed-address 10.0.1.11; > } > host ciscophone1 { > option host-name "ciscophone1.midominio.com"; > hardware ethernet 00:14:F2:AE:65:29; > fixed-address 10.0.1.201; > next-server 10.0.1.1; > # filename "XMLDefault.cnf.xml"; > } > host ciscophone2 { > option host-name "ciscophone2.midominio.com"; > hardware ethernet 00:15:63:4D:22:CE; > fixed-address 10.0.1.202; > next-server 10.0.1.1; > } > > > Y los archivos que mantengo en el /home/tftp son: > > *shell# ls -l /home/tftp* > XMLDefault.cnf.xml > SIPDefault.cnf > SEPAABBCCDDEEFF.cnf > SEPAABBCCDDEEFF.cnf.xml > P0S3-8-12-00.sb2 > P0S3-8-12-00.loads > P0S3-8-12-00.sbn > P0S3-8-12-00.bin > OS79XX.TXT > List.xml > dialplan.xml > cmterm-7940-7960-8.2.00-sip.cop > > Aun me falta configurar bien el SEPAABBCCDDEEFF.cnf y > SEPAABBCCDDEEFF.cnf.xml que es el que carga la configuración especifica > para el telefono con mac AA:BB:CC:DD:EE:FF. > > En cuanto quede les paso contenido de los archivos ya testeado y > funcionando :D > > *Quiero agregar* que uno de los 2 (dos) teléfonos continua teniendo > problemas, vaya después de resetearlo hace solo esto: > > - Configuring VLAN > - Configuring IP > - Protocol Application Invalid. > > En cambio el otro telefono, SI pasa a la parte de cargar el Firmware y lo > demas... > > Saludos ! > > > El 12 de noviembre de 2013 08:23, angel jauregui > <darkdiabliyo(a)gmail.com>escribió: > > > @Gerardo algo lei sobre el firmware SIP y que para identificarlo debe > > aparecer en laparte superior de la pantalla, pero *no veo nada* que diga > > SIP, es solo una bara negra... > > > > Aparte no logro se conecte al TFTP :S, ya que en las opciones donde dice > > "TFTP Server" esta vacio :'(. Se supone debe mencionar la direccion de mi > > TFTP, pero nada. > > > > Por esta misma razon puse la configuracion de mi TFTP (en la primer > > publicacion), ya que no consigo se baje el Firmaware que subi al TFTP > > (/home/tftp/) > > > > Saludos ! > > > > > > El 11 de noviembre de 2013 21:10, Gerardo Barajas < > > gerardo.barajas(a)gmail.com> escribió: > > > > Ya tienes el firmware para SIP? > >> On Nov 11, 2013 6:27 PM, "angel jauregui" <darkdiabliyo(a)gmail.com> > wrote: > >> > >> > Encontre este sitio donde hay un monton de Firmwares > >> > http://files.domoticaforum.eu/Cisco/Firmware/7960/ > >> > Pero aun no puedo cargarle nada :(... vaya me baje el archivo " > >> > P0S3-8-12-00.zip< > >> > http://files.domoticaforum.eu/Cisco/Firmware/7960/P0S3-8-12-00.zip>", > >> > despues cree el directorio del TFTP los archivos: > >> > > >> > shell# ls -l /home/tftp/ > >> > OS79XX.TXT > >> > P003-8-12-00.bin > >> > P003-8-12-00.sbin > >> > P003-8-12-00.loads > >> > P003-8-12-00.sb2 > >> > SEPaabbddcceeff.cnf.xml > >> > SEPaabbddcceeff.cnf > >> > > >> > El ZIP que les comente anteriormente me provee los archivo *.bin, > >> *.sbin, > >> > *.loas y *.sb2... > >> > El XML y CNF lo arme con este ejemplo: > >> > > >> > XML --> > >> > http://www.minded.ca/wp-content/uploads/2009/12/SEP7940.cnf_.xml_.txt > >> > CNF --> > >> http://www.minded.ca/wp-content/uploads/2009/12/SIP7940.cnf_.txt > >> > > >> > Pero dejo pendiente el resultado, ya que me sali d la ofi y no probe > >> > reiniciar el telefono. > >> > > >> > Hasta aqui, voy bien (teoricamente) ??? me falta algo ? > >> > > >> > Saludos ! > >> > > >> > > >> > > >> > > >> > El 11 de noviembre de 2013 15:50, Andres Genovez > >> > <andresgenovez(a)gmail.com>escribió: > >> > > >> > > Basicamente el proceso es similar, > >> > > > >> > > http://www.crice.org/?q=node/444 > >> > > > >> > > Solo que tendría que conseguir el Firmware del 7940, > >> > > > >> > > Saludos. > >> > > > >> > > > >> > > > >> > > > >> > > El 11 de noviembre de 2013 16:46, angel jauregui > >> > > <darkdiabliyo(a)gmail.com>escribió: > >> > > > >> > > > Buenas. > >> > > > > >> > > > Acabo de conseguir un par de teléfonos Cisco 7940G que quiero > >> echarlos > >> > > > andar con asterisk+freepbx. Antes de entrar a asterisk+freepbx > >> quisiera > >> > > por > >> > > > favor me orientaras sobe las configuraciones que tengo que hacer > con > >> > los > >> > > > teléfonos CISCO. > >> > > > > >> > > > Estuve buscando en Google y leyendo, pero al parecer muchos > >> ejemplos de > >> > > > basan en una version de firmware que es mayor a la que tienen mis > >> > > > teléfonos. > >> > > > > >> > > > En fin, todas son *suposiciones....* el manual que estoy siguiendo > >> es > >> > > este: > >> > > > > >> > > >> > http://www.minded.ca/2009-12-16/configure-cisco-ip-phones-with-asterisk/ > >> > > > > >> > > > Hasta ahorita tengo esto: > >> > > > > >> > > > 1- Montado mi servidor DNS y asignando IP's a mis equipos. En > >> > especifico > >> > > > para los teléfonos (son 2), por MAC les estoy dando un IP > >> especifico: > >> > > > 10.0.1.201 y 10.0.1.202. > >> > > > > >> > > > 2- El dns esta configurado asi: > >> > > > > >> > > > *shell# cat /etc/dhcp/dhcpd.conf* > >> > > > ddns-update-style interim; > >> > > > ddns-updates on; > >> > > > ddns-domainname "midominio.com"; > >> > > > ddns-rev-domainname "in-addr.arpa."; > >> > > > ignore client-updates; > >> > > > authoritative; > >> > > > default-lease-time 600; > >> > > > max-lease-time 7200; > >> > > > option ip-forwarding off; > >> > > > option domain-name "midominio.com"; > >> > > > option ntp-servers 0.pool.ntp.org, 1.poo.ntp.org, 2.pool.ntp.org, > >> > > > 3.pool.ntp.org; > >> > > > log-facility local7; > >> > > > allow bootp; > >> > > > allow booting; > >> > > > > >> > > > include "/etc/rndc.key"; > >> > > > > >> > > > zone 1.0.10.in-addr.arpa. { > >> > > > primary 127.0.0.1; > >> > > > key rndc-key; > >> > > > } > >> > > > > >> > > > zone midominio.com. { > >> > > > primary 127.0.0.1; > >> > > > key rndc-key; > >> > > > } > >> > > > > >> > > > shared-network midominio { > >> > > > subnet 10.0.1.0 netmask 255.255.255.0 { > >> > > > option routers 10.0.1.1; > >> > > > option subnet-mask 255.255.255.0; > >> > > > option broadcast-address 10.0.1.255; > >> > > > option domain-name-servers ns1.midominio.com; > >> > > > option netbios-name-servers 10.0.1.1; > >> > > > range 10.0.1.100 10.0.1.150; > >> > > > filename "pxelinux.0"; > >> > > > } > >> > > > > >> > > > host ciscophone1 { > >> > > > option host-name "ciscophone1.midominio.com"; > >> > > > hardware ethernet aa:bb:cc:dd:ee:ff; > >> > > > fixed-address 10.0.1.201; > >> > > > filename "XMLDefault.cnf.xml"; > >> > > > } > >> > > > > >> > > > host ciscophone2 { > >> > > > option host-name "ciscophone1.midominio.com"; > >> > > > hardware ethernet gg:hh:ii:jj:kk:ll; > >> > > > fixed-address 10.0.1.201; > >> > > > filename "XMLDefault.cnf.xml"; > >> > > > } > >> > > > > >> > > > Alguien puede orientarme ? > >> > > > Como ven tengo activalo el PXEBoot, ya que para equipos en red > puedo > >> > > > reinstalar linux o alguna ISO de respaldo en caliente. > >> > > > > >> > > > Por el lado de los telefonos, solo se les asigna el IP que le > >> > > corresponde, > >> > > > pero nadamas :S.... no sale el XML que se supone carge ni nada :S > >> > > > > >> > > > Saludos ! > >> > > > > >> > > > -- > >> > > > M.S.I. Angel Haniel Cantu Jauregui. > >> > > > > >> > > > Celular: (011-52-1)-899-871-17-22 > >> > > > E-Mail: angel.cantu(a)sie-group.net > >> > > > Web: http://www.sie-group.net/ > >> > > > Cd. Reynosa Tamaulipas. > >> > > > _______________________________________________ > >> > > > CentOS-es mailing list > >> > > > CentOS-es(a)centos.org > >> > > > http://lists.centos.org/mailman/listinfo/centos-es > >> > > > > >> > > > >> > > > >> > > > >> > > -- > >> > > Atentamente > >> > > > >> > > Andrés Genovez Tobar / DTIT > >> > > Tel: 842388 ext 177 > >> > > Perfil profesional http://lnkd.in/gcdhJE > >> > > _______________________________________________ > >> > > CentOS-es mailing list > >> > > CentOS-es(a)centos.org > >> > > http://lists.centos.org/mailman/listinfo/centos-es > >> > > > >> > > >> > > >> > > >> > -- > >> > M.S.I. Angel Haniel Cantu Jauregui. > >> > > >> > Celular: (011-52-1)-899-871-17-22 > >> > E-Mail: angel.cantu(a)sie-group.net > >> > Web: http://www.sie-group.net/ > >> > Cd. Reynosa Tamaulipas. > >> > _______________________________________________ > >> > CentOS-es mailing list > >> > CentOS-es(a)centos.org > >> > http://lists.centos.org/mailman/listinfo/centos-es > >> > > >> _______________________________________________ > >> CentOS-es mailing list > >> CentOS-es(a)centos.org > >> http://lists.centos.org/mailman/listinfo/centos-es > >> > > > > > > > > -- > > M.S.I. Angel Haniel Cantu Jauregui. > > > > Celular: (011-52-1)-899-871-17-22 > > E-Mail: angel.cantu(a)sie-group.net > > Web: http://www.sie-group.net/ > > Cd. Reynosa Tamaulipas. > > > > > > -- > M.S.I. Angel Haniel Cantu Jauregui. > > Celular: (011-52-1)-899-871-17-22 > E-Mail: angel.cantu(a)sie-group.net > Web: http://www.sie-group.net/ > Cd. Reynosa Tamaulipas. > _______________________________________________ > CentOS-es mailing list > CentOS-es(a)centos.org > http://lists.centos.org/mailman/listinfo/centos-es > -- Atentamente Andrés Genovez Tobar / DTIT Tel: 842388 ext 177 Perfil profesional http://lnkd.in/gcdhJE

12 years, 4 months

Search results for query "Linux ./configure"