[CentOS-docs] Weekly meetings for the Docs SIG
In last week's meeting, the CentOS board voted to formalize the Documentation SIG, with Amy and me as co-chairs. I'd like to start weekly meetings, like we do for the Promo SIG. I don't expect that everybody will make it every week. I've opened a poll to find a good time for everybody. Please fill it out if you're interested in participating: https://whenisgood.net/pfywzpz The poll is for the week of Nov 27 (I'll be out next week), but you should fill it in based on when you regularly (not necessarily always) have time each week. Make sure to select your location to see the times in your time zone. Thanks, Shaun ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] CentOS web+docs working day
Planning page is up. Add yourself if you're coming. https://gitlab.com/CentOS/promo/centos-events/-/issues/2 On Thu, 2022-12-08 at 16:20 -0500, Shaun McCance wrote: > Hi all, > > We're going to have a web+docs working day in Brussels on February 6, > the day after FOSDEM. I'll get a planning page up soon where you can > add your name if you're coming. In the meantime, if you want to come, > plan your travel accordingly. > > Also, don't forget that we're hosting CentOS Connect on February 3, > the > day before FOSDEM. It's free, but please register. > > https://connect.centos.org/ > > Thanks, > Shaun McCance > CentOS Community Architect > Red Hat Open Source Program Office > ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] CentOS web+docs working day
Hi all, We're going to have a web+docs working day in Brussels on February 6, the day after FOSDEM. I'll get a planning page up soon where you can add your name if you're coming. In the meantime, if you want to come, plan your travel accordingly. Also, don't forget that we're hosting CentOS Connect on February 3, the day before FOSDEM. It's free, but please register. https://connect.centos.org/ Thanks, Shaun McCance CentOS Community Architect Red Hat Open Source Program Office ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Status of RHEL docs for CentOS, questions
Yeah, my issue with Option 2 was that it doesn't reflow. We could get the same side-by-side effect while allowing reflow on smaller screens using CSS flexbox or grid, but I don't know how to do that in asciidoc. Sometimes sites just hand-craft the HTML of the landing page, but I don't want to make work for people. Also, we should consider how well these designs will work with three concurrent streams. On Mon, 2022-03-28 at 18:45 +0200, Tomas Capek wrote: > Hi all, > > while Option 2 was my favorite as well and it looks great on wide > screens, one concern is that it might not look as good on mobile > devices. > > Since we had a sync-up call with Shaun last week, we added Option 4 > which shows collapsible docs lists and categories under each major > version. > > Hope that helps, > Tomas > > On Fri, Mar 25, 2022 at 7:52 PM Amy Marrich wrote: > > I've only started looking through but I like Option 2. As you said > > the list will get longer and this will ultimately have less > > scrolling then having everything listed vertically/ > > > > Amy > > Amy Marrich > > She/Her/Hers > > Principal Technical Marketing Manager - Cloud Platforms > > Red Hat, Inc > > a...@redhat.com > > Mobile: 954-818-0514 > > Slack: amarrich > > IRC: spotz > > > > > > > > On Fri, Mar 25, 2022 at 10:02 AM Shaun McCance > > wrote: > > > Hi folks, > > > > > > A team inside Red Hat has been working on upstreaming the RHEL > > > docs to > > > CentOS Stream. I'd like to share the progress and gather some > > > feedback. > > > You can see a preview rendering here: > > > > > > https://redhat.gitlab.io/centos-stream/docs/enterprise-docs/ > > > > > > Sources here: > > > > > > https://gitlab.com/redhat/centos-stream/docs/enterprise-docs > > > > > > Currently, there are three documents being built for each of > > > Stream 8 > > > and Stream 9. There are a LOT more to come, but it will take > > > time. > > > > > > Questions: > > > > > > * That front page rendering has three options for how to link off > > > to > > > all the documents. Bearing in mind that the list will grow, how > > > would > > > you prefer it presented? > > > > > > * Opinions on the overall look and feel? Using some common > > > centos.org > > > design elements would be nice, but I don't want to block on that. > > > > > > * I've asked in the past what documents people would like Red Hat > > > to > > > prioritize, and gotten some responses. Feel free to keep > > > requesting. > > > > > > Thanks, > > > Shaun > > > > > > ___ > > > CentOS-docs mailing list > > > CentOS-docs@centos.org > > > https://lists.centos.org/mailman/listinfo/centos-docs > > > > > ___ > > CentOS-docs mailing list > > CentOS-docs@centos.org > > https://lists.centos.org/mailman/listinfo/centos-docs > > > ___ > CentOS-docs mailing list > CentOS-docs@centos.org > https://lists.centos.org/mailman/listinfo/centos-docs ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] Status of RHEL docs for CentOS, questions
Hi folks, A team inside Red Hat has been working on upstreaming the RHEL docs to CentOS Stream. I'd like to share the progress and gather some feedback. You can see a preview rendering here: https://redhat.gitlab.io/centos-stream/docs/enterprise-docs/ Sources here: https://gitlab.com/redhat/centos-stream/docs/enterprise-docs Currently, there are three documents being built for each of Stream 8 and Stream 9. There are a LOT more to come, but it will take time. Questions: * That front page rendering has three options for how to link off to all the documents. Bearing in mind that the list will grow, how would you prefer it presented? * Opinions on the overall look and feel? Using some common centos.org design elements would be nice, but I don't want to block on that. * I've asked in the past what documents people would like Red Hat to prioritize, and gotten some responses. Feel free to keep requesting. Thanks, Shaun ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] CentOS/Fedora docs meeting
Hi folks, Docs meetings tomorrow March 16, 2022 18:30 UTC in #fedora-meeting-1 on Matrix. https://discussion.fedoraproject.org/t/docs-meeting-agenda-2022-03-16/37489 Thanks, Shaun ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] CentOS/Fedora docs meeting
Hi all, We're doing another one of those shared CentOS/Fedora docs meetings today, in an hour, at 18:30 UTC #fedora-meeting-1 on Matrix. https://discussion.fedoraproject.org/t/meeting-schedule/36706 Sorry for the late notice. I had a todo item to ping this list yesterday, and I just plain slipped. -- Shaun ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] Docs meeting with Fedora
Hi folks, Ben Cotton has been working on revamping the Fedora docs team. I've been working with him to see where we can share resources. We're doing weekly meetings. Please join if you can. https://discussion.fedoraproject.org/t/meeting-schedule/36706 Wednesdays (starting tomorrow) at 18:30 UTC in #fedora-meeting-1 on Matrix. Let me know if you have questions, or if you can't make it but want me to bring things to the table. Thanks, Shaun ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] Interest in office hours?
Hi all, Is there any interest in having bi-weekly office hours to discuss stuff going on around CentOS docs? We could get onto this list, along with other (actual) SIGs: https://www.centos.org/community/calendar/ I've done docs office hours for other projects. Sometimes they're very boring. Sometimes real work gets done. Sometimes you end up onboarding a great new community member. I think they're useful, but they require patience. This is a no-commitment meeting. Can't make it? No problem. I can commit to showing up and running them for a while, as long as it's at a time that's not awful in the US Eastern timezone. -- Shaun ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Documentation SIG responsibilities
On Thu, 2021-11-04 at 16:15 -0400, Rich Bowen wrote: > > > On 11/4/21 15:15, Shaun McCance wrote: > > Hi all, > > > > I'm working on revamping the Documentation SIG wiki page, and > > hoping to > > present where we stand to the CentOS board at some point. > > > > https://wiki.centos.org/SpecialInterestGroup/Documentation > > > > I'd like to have a set of core responsibilities. Proposal: > > > > * Working with the Red Hat documentation folks on publishing > > material > > upstreamed from RHEL. > > > > * Identifying, writing, and maintaining content aside from stuff > > that > > is intended for RHEL, whether that's in manuals or shorter form > > wiki > > material. > > > > * Periodically auditing and pruning old and outdated documentation. > > > > * Promoting CentOS documentation as a reliable source of > > information > > for CentOS and enterprise Linux in general. > > > > * Working with translators to make documentation available in > > languages > > other than English. > > > > * Working with other special interest groups on their documentation > > needs and helping them create, maintain, and integrate their own > > content. > > I think this is covered under "reliable" and "pruning old and > outdated", > but I'd love to see someone take charge of doing a complete audit of > the > wiki and making it correct and authoritative. It has become a bit of > a > pile of "might be right, sometimes" over the past decade, and it's > challenging to find anything in it. Yeah, in my mind it's covered under that, but I think it's worth calling that out specifically. Wikis inevitably accumulate cruft if nobody is tending to them. -- Shaun ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] Documentation SIG responsibilities
Hi all, I'm working on revamping the Documentation SIG wiki page, and hoping to present where we stand to the CentOS board at some point. https://wiki.centos.org/SpecialInterestGroup/Documentation I'd like to have a set of core responsibilities. Proposal: * Working with the Red Hat documentation folks on publishing material upstreamed from RHEL. * Identifying, writing, and maintaining content aside from stuff that is intended for RHEL, whether that's in manuals or shorter form wiki material. * Periodically auditing and pruning old and outdated documentation. * Promoting CentOS documentation as a reliable source of information for CentOS and enterprise Linux in general. * Working with translators to make documentation available in languages other than English. * Working with other special interest groups on their documentation needs and helping them create, maintain, and integrate their own content. Thoughts? -- Shaun ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] Wiki editing privs
Hi folks, I'd like to get permission to edit wiki.centos.org. The Contribute page says I should email here. My username is ShaunMcCance. I intend to edit the Documentation SIG proposal page with input from the community, and from there edit pages under Documentation, TipsAndTricks, and HowTos. Thanks, Shaun McCance Documentation Community Architect Red Hat Open Source Program Office ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] Centos 7 Kernel 3.10.0-693.11.6.el7.x86_64 does not boot PV
Weird, Just did a new PV deploy of CentOS 7 and upgraded the kernel and it worked fine this time. -- Shaun Reitan NDCHost.com -- Original Message -- From: "Johnny Hughes" <joh...@centos.org> To: centos-virt@centos.org Sent: 2018-01-09 07:33:26 AM Subject: Re: [CentOS-virt] Centos 7 Kernel 3.10.0-693.11.6.el7.x86_64 does not boot PV On 01/08/2018 02:10 PM, Shaun Reitan wrote: While installing the experemental kernel on a CentOS 7 PV the following happened. After a reboot of the PV the kernel looks to be installed but there is no option for booting it in grub. I attempted to run yum reinstall kernel-4.9.75-204.el7.centos.x86_64 and it installed fine but still no entry in grub. No initramfs existed and I found kernel-modules did not install properly so I then ran yum reinstall kernel-modules and received a ton of errors that looked like the following.. depmod: ERROR: failed to load symbols from /lib/modules/4.9.75-204.el7.centos.x86_64/kernel/drivers/misc/sgi-xp/xpc.ko.xz: Exec format error after which a initramfs does exist however on reboot still no option for the new kernel. Installed and works fine for me. Very odd. from my Dom0 machine: [root@xendom0 ~]# uname -a Linux xendom0 4.9.75-29.el7.x86_64 #1 SMP Fri Jan 5 19:42:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux From my DomU CentOS-7 PV VM: Linux x7-x8664-pv 4.9.75-204.el7.centos.x86_64 #1 SMP Fri Jan 5 17:51:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux My CentOS-7 PV config: [root@xendom0 ~]# cat /etc/xen/config.d/c7-x8664.pv.cfg bootloader= "/usr/lib/xen/bin/pygrub" name = "c7-x8664.pv" memory = 4096 vcpus = 2 vif = [ 'mac=00:16:3E:29:00:02,bridge=xenbr0' ] disk = [ 'phy:/dev/cl/c7-x8664-pv,xvda,rw' ] vfb = [ 'type=vnc,vncdisplay=1,vncpasswd=supersecret' ] [root@CC0A2543 ~]# [ 587.145018] [ cut here ] [ 587.145018] kernel BUG at arch/x86/kernel/paravirt.c:244! [ 587.145018] invalid opcode: [#1] SMP [ 587.145018] Modules linked in: xen_netfront coretemp pcspkr ip_tables ext4 mbcache jbd2 xen_blkfront [ 587.145018] CPU: 0 PID: 2126 Comm: dracut Not tainted 3.10.0-123.4.4.el7.x86_64 #1 [ 587.145018] task: 880002da5b00 ti: 8800f6088000 task.ti: 8800f6088000 [ 587.145018] RIP: e030:[] [] enter_lazy.part.0+0x4/0x6 [ 587.145018] RSP: e02b:8800ff403ab0 EFLAGS: 00010002 [ 587.145018] RAX: 0001 RBX: 8800f8ad4040 RCX: 3000 [ 587.145018] RDX: 8840 RSI: 8800 RDI: 0005a52cc067 [ 587.145018] RBP: 8800ff403ab0 R08: 8800ff403b78 R09: 81362409 [ 587.145018] R10: 8800fa001e00 R11: 8800 R12: c9609000 [ 587.145018] R13: c9608000 R14: R15: 8100a6b0 [ 587.145018] FS: 7f14b0680740() GS:8800ff40() knlGS: [ 587.145018] CS: e033 DS: ES: CR0: 8005003b [ 587.145018] CR2: 7f14b0473000 CR3: f6099000 CR4: 2660 [ 587.145018] DR0: DR1: DR2: [ 587.145018] DR3: DR6: 0ff0 DR7: 0400 [ 587.145018] Stack: [ 587.145018] 8800ff403ac0 81046bc7 8800ff403b60 8116d8d6 [ 587.145018] c9608fff c9609000 818cec90 c9608fff [ 587.145018] c9609000 8800fa04d000 0004 c9608fff [ 587.145018] Call Trace: [ 587.145018] [ 587.145018] [] paravirt_enter_lazy_mmu+0x27/0x30 [ 587.145018] [] apply_to_page_range+0x266/0x440 [ 587.145018] [] arch_gnttab_map_status+0x3b/0x70 [ 587.145018] [] gnttab_map_frames_v2+0xd6/0x150 [ 587.145018] [] gnttab_map+0xa1/0x140 [ 587.145018] [] get_free_entries+0x100/0x2e0 [ 587.145018] [] gnttab_alloc_grant_references+0x15/0x30 [ 587.145018] [] do_blkif_request+0x683/0x850 [xen_blkfront] [ 587.145018] [] __blk_run_queue+0x33/0x40 [ 587.145018] [] blk_start_queue+0x29/0x40 [ 587.145018] [] kick_pending_request_queues+0x21/0x30 [xen_blkfront] [ 587.145018] [] blkif_interrupt+0x5c7/0x670 [xen_blkfront] [ 587.145018] [] handle_irq_event_percpu+0x3e/0x1e0 [ 587.145018] [] handle_irq_event+0x3d/0x60 [ 587.145018] [] handle_edge_irq+0x77/0x130 [ 587.145018] [] __xen_evtchn_do_upcall+0x227/0x350 [ 587.145018] [] xen_evtchn_do_upcall+0x2b/0x50 [ 587.145018] [] xen_do_hypervisor_callback+0x1e/0x30 [ 587.145018] [ 587.145018] [] ? free_cpumask_var+0x9/0x10 [ 587.145018] [] ? unmap_page_range+0x5f8/0x860 [ 587.145018] [] ? unmap_single_vma+0x81/0xf0 [ 587.145018] [] ? unmap_vmas+0x49/0x90 [ 587.145018] [] ? exit_mmap+0xac/0x1a0 [ 587.145018] [] ? mmput+0x67/0xf0 [ 587.145018] [] ? flush_old_exec+0x422/0x880 [ 587.145018] [] ? load_elf_binary+0x33c/0xde0 [ 587.145018] [] ? ima_get_action+0x23/0x30 [ 587.145018] [] ? process_measurement+0x8e/0x250 [ 587.145018] [] ? ima_bprm_check+0x49/0x50 [ 587.
Re: [CentOS-virt] Centos 7 Kernel 3.10.0-693.11.6.el7.x86_64 does not boot PV
While installing the experemental kernel on a CentOS 7 PV the following happened. After a reboot of the PV the kernel looks to be installed but there is no option for booting it in grub. I attempted to run yum reinstall kernel-4.9.75-204.el7.centos.x86_64 and it installed fine but still no entry in grub. No initramfs existed and I found kernel-modules did not install properly so I then ran yum reinstall kernel-modules and received a ton of errors that looked like the following.. depmod: ERROR: failed to load symbols from /lib/modules/4.9.75-204.el7.centos.x86_64/kernel/drivers/misc/sgi-xp/xpc.ko.xz: Exec format error after which a initramfs does exist however on reboot still no option for the new kernel. [root@CC0A2543 ~]# [ 587.145018] [ cut here ] [ 587.145018] kernel BUG at arch/x86/kernel/paravirt.c:244! [ 587.145018] invalid opcode: [#1] SMP [ 587.145018] Modules linked in: xen_netfront coretemp pcspkr ip_tables ext4 mbcache jbd2 xen_blkfront [ 587.145018] CPU: 0 PID: 2126 Comm: dracut Not tainted 3.10.0-123.4.4.el7.x86_64 #1 [ 587.145018] task: 880002da5b00 ti: 8800f6088000 task.ti: 8800f6088000 [ 587.145018] RIP: e030:[] [] enter_lazy.part.0+0x4/0x6 [ 587.145018] RSP: e02b:8800ff403ab0 EFLAGS: 00010002 [ 587.145018] RAX: 0001 RBX: 8800f8ad4040 RCX: 3000 [ 587.145018] RDX: 8840 RSI: 8800 RDI: 0005a52cc067 [ 587.145018] RBP: 8800ff403ab0 R08: 8800ff403b78 R09: 81362409 [ 587.145018] R10: 8800fa001e00 R11: 8800 R12: c9609000 [ 587.145018] R13: c9608000 R14: R15: 8100a6b0 [ 587.145018] FS: 7f14b0680740() GS:8800ff40() knlGS: [ 587.145018] CS: e033 DS: ES: CR0: 8005003b [ 587.145018] CR2: 7f14b0473000 CR3: f6099000 CR4: 2660 [ 587.145018] DR0: DR1: DR2: [ 587.145018] DR3: DR6: 0ff0 DR7: 0400 [ 587.145018] Stack: [ 587.145018] 8800ff403ac0 81046bc7 8800ff403b60 8116d8d6 [ 587.145018] c9608fff c9609000 818cec90 c9608fff [ 587.145018] c9609000 8800fa04d000 0004 c9608fff [ 587.145018] Call Trace: [ 587.145018] [ 587.145018] [] paravirt_enter_lazy_mmu+0x27/0x30 [ 587.145018] [] apply_to_page_range+0x266/0x440 [ 587.145018] [] arch_gnttab_map_status+0x3b/0x70 [ 587.145018] [] gnttab_map_frames_v2+0xd6/0x150 [ 587.145018] [] gnttab_map+0xa1/0x140 [ 587.145018] [] get_free_entries+0x100/0x2e0 [ 587.145018] [] gnttab_alloc_grant_references+0x15/0x30 [ 587.145018] [] do_blkif_request+0x683/0x850 [xen_blkfront] [ 587.145018] [] __blk_run_queue+0x33/0x40 [ 587.145018] [] blk_start_queue+0x29/0x40 [ 587.145018] [] kick_pending_request_queues+0x21/0x30 [xen_blkfront] [ 587.145018] [] blkif_interrupt+0x5c7/0x670 [xen_blkfront] [ 587.145018] [] handle_irq_event_percpu+0x3e/0x1e0 [ 587.145018] [] handle_irq_event+0x3d/0x60 [ 587.145018] [] handle_edge_irq+0x77/0x130 [ 587.145018] [] __xen_evtchn_do_upcall+0x227/0x350 [ 587.145018] [] xen_evtchn_do_upcall+0x2b/0x50 [ 587.145018] [] xen_do_hypervisor_callback+0x1e/0x30 [ 587.145018] [ 587.145018] [] ? free_cpumask_var+0x9/0x10 [ 587.145018] [] ? unmap_page_range+0x5f8/0x860 [ 587.145018] [] ? unmap_single_vma+0x81/0xf0 [ 587.145018] [] ? unmap_vmas+0x49/0x90 [ 587.145018] [] ? exit_mmap+0xac/0x1a0 [ 587.145018] [] ? mmput+0x67/0xf0 [ 587.145018] [] ? flush_old_exec+0x422/0x880 [ 587.145018] [] ? load_elf_binary+0x33c/0xde0 [ 587.145018] [] ? ima_get_action+0x23/0x30 [ 587.145018] [] ? process_measurement+0x8e/0x250 [ 587.145018] [] ? ima_bprm_check+0x49/0x50 [ 587.145018] [] ? load_elf_library+0x230/0x230 [ 587.145018] [] ? search_binary_handler+0xf5/0x310 [ 587.145018] [] ? do_execve_common.isra.22+0x559/0x650 [ 587.145018] [] ? SyS_execve+0x36/0x50 [ 587.145018] [] ? stub_execve+0x69/0xa0 [ 587.145018] Code: 8d 55 f0 48 8d 4d f4 e8 b4 8e a2 ff 66 90 48 8b 55 f8 65 48 33 14 25 28 00 00 00 8b 45 e8 74 05 e8 ab 3a a8 ff c9 c3 55 48 89 e5 <0f> 0b 66 66 66 66 90 55 48 89 e5 0f 0b 55 48 89 e5 0f 0b 66 66 [ 587.145018] RIP [] enter_lazy.part.0+0x4/0x6 [ 587.145018] RSP [ 587.145018] ---[ end trace 8566ed161f106c20 ]--- [ 587.145018] Kernel panic - not syncing: Fatal exception in interrupt -- Shaun Reitan NDCHost.com -- Original Message -- From: "Johnny Hughes" <joh...@centos.org> To: centos-virt@centos.org Sent: 2018-01-06 05:34:22 AM Subject: Re: [CentOS-virt] Centos 7 Kernel 3.10.0-693.11.6.el7.x86_64 does not boot PV On 01/06/2018 03:16 AM, Dmitry Melekhov wrote: The same problem with latest centos 6 kernel,i.e. with meltdown fix. I can't see console
Re: [CentOS-virt] CentOS-virt - Kernel Side-Channel Attacks
4.9.75-30 works in my dev environment for CentOS 6. [root@devhost1 ~]# uname -a Linux devhost1.servers.provps.com 4.9.75-30.el6.x86_64 #1 SMP Fri Jan 5 20:58:49 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- Shaun Reitan NDCHost.com -- Original Message -- From: "Johnny Hughes" <joh...@centos.org> To: centos-virt@centos.org Sent: 2018-01-06 02:09:12 AM Subject: Re: [CentOS-virt] CentOS-virt - Kernel Side-Channel Attacks On 01/05/2018 06:33 AM, George Dunlap wrote: On Thu, Jan 4, 2018 at 7:12 PM, Sarah Newman <s...@prgmr.com> wrote: On 01/04/2018 10:49 AM, Akemi Yagi wrote: On Thu, Jan 4, 2018 at 9:51 AM, <rik...@deds.nl> wrote: Please patch the CentOS-virt Kernel to fix the Kernel Side-Channel Attacks vulnerabilities. The latest CentOS-virt kernel was released in November, as seen below. kernel-4.9.63-29.el7.x86_64.rpm 2017-11-21 13:30 https://access.redhat.com/security/vulnerabilities/speculativeexecution http://mirror.centos.org/centos/7/virt/x86_64/xen/ As far as I can see, the patches for KAISER (Kernel Address Isolation to have Side-channels Efficiently Removed) will appear in kernel 4.9.75. Looks like it will be released soon upstream (kernel.org). To my best knowledge KAISER doesn't matter for Xen Dom0's given they run in PV mode, and KAISER isn't enabled for PV guests. But it will be important if anyone is running the CentOS kernel in their HVM domUs (as guest kernels can be attacked using SP3 by guest user space without the KPTI patches). I'm sure Johnny will get to it as soon as he has the opportunity. I have just pushed the 4.9.75-29.el7 and 4.9.75-30.el6 kernels to the testing repositories. https://buildlogs.centos.org/centos/7/virt/x86_64/xen/ and https://buildlogs.centos.org/centos/6/virt/x86_64/xen/ xen, xen-44, xen-46, xen-48 repos should all get the rpms (not just xen) .. el6 has yet to post there, but it is tagged and should show up in a couple hours. The kernel is already there in the el7 trees. We need lots of testing .. the configuration name is now: CONFIG_PAGE_TABLE_ISOLATION=y (instead of CONFIG_KAISER) Please test these kernels so we can release them .. it boots for me as a Dom0 kernel and I can start PVHVM and HVM CentOS DomU machines .. which is how I test before I move the kernels to the testing repos. ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Centos 6 2.6.32-696.18.7.el6.x86_64 does not boot in Xen PV mode
I can confirm the issue with 2.6.32-696.18.7.el6.x86_64, but mine looks alittle different... Maybe because i'm using pvgrub. = Init TPM Front Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront initialization! error = ENOENT Tpmfront:Info Shutting down tpmfront close blk: backend=/local/domain/0/backend/vbd/14/51712 node=device/vbd/51712 close blk: backend=/local/domain/0/backend/vbd/14/51728 node=device/vbd/51728 [root@devhost1]# -- Shaun Reitan NDCHost.com -- Original Message -- From: "Sarah Newman" <s...@prgmr.com> To: "Discussion about the virtualization on CentOS" <centos-virt@centos.org> Sent: 2018-01-05 12:39:21 AM Subject: [CentOS-virt] Centos 6 2.6.32-696.18.7.el6.x86_64 does not boot in Xen PV mode Problems start before any of the kaiser code executes, though it could still be related to CONFIG_KAISER since that has effects beyond kaiser.c. --- (early) Initializing cgroup subsys cpuset (early) Initializing cgroup subsys cpu (early) Linux version 2.6.32-696.18.7.el6.x86_64 (mockbu...@c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Thu Jan 4 17:31:22 UTC 2018 (early) Command line: ro console=hvc0 rootflags=barrier=0 crashkernel=auto SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us earlyprintk=xen (early) KERNEL supported cpus: (early) Intel GenuineIntel (early) AMD AuthenticAMD (early) Centaur CentaurHauls (early) 1 multicall(s) failed: cpu 0 (early) Pid: 0, comm: swapper Not tainted 2.6.32-696.18.7.el6.x86_64 #1 (early) Call Trace: (early) [] ? xen_mc_flush+0x1c3/0x250 (early) [] ? xen_extend_mmu_update+0xde/0x1b0 (early) [] ? xen_set_pmd_hyper+0x9d/0xc0 (early) [] ? early_ioremap_init+0x98/0x133 (early) [] ? setup_arch+0x40/0xca6 (early) [] ? vprintk_default+0xe/0x10 (early) [] ? printk+0x4f/0x52 (early) [] ? start_kernel+0xdc/0x43b (early) [] ? reserve_early+0x30/0x39 (early) [] ? x86_64_start_reservations+0x125/0x129 (early) [] ? xen_start_kernel+0x4fe/0x505 (early) [ cut here ] (early) WARNING: at arch/x86/xen/multicalls.c:182 xen_mc_flush+0x21f/0x250() (Not tainted) (early) Modules linked in: (early) Pid: 0, comm: swapper Not tainted 2.6.32-696.18.7.el6.x86_64 #1 (early) Call Trace: (early) [] ? warn_slowpath_common+0x91/0xe0 (early) [] ? __raw_callee_save_xen_restore_fl+0x11/0x1e (early) [] ? warn_slowpath_null+0x1a/0x20 (early) [] ? xen_mc_flush+0x21f/0x250 (early) [] ? xen_extend_mmu_update+0xde/0x1b0 (early) [] ? xen_extend_mmu_update+0xde/0x1b0 (early) [] ? xen_set_pmd_hyper+0x9d/0xc0 (early) [] ? early_ioremap_init+0x98/0x133 (early) [] ? setup_arch+0x40/0xca6 (early) [] ? vprintk_default+0xe/0x10 (early) [] ? printk+0x4f/0x52 (early) [] ? start_kernel+0xdc/0x43b (early) [] ? reserve_early+0x30/0x39 (early) [] ? x86_64_start_reservations+0x125/0x129 (early) [] ? xen_start_kernel+0x4fe/0x505 (early) ---[ end trace a7919e7f17c0a725 ]--- (early) ACPI in unprivileged domain disabled (early) released 0 pages of unused memory (early) BIOS-provided physical RAM map: (early) Xen: - 000a (usable) (early) Xen: 000a - 0010 (reserved) (early) Xen: 0010 - 2000 (usable) (early) bootconsole [xenboot0] enabled ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Centos 7 Kernel 3.10.0-693.11.6.el7.x86_64 does not boot PV
registered [0.464189] libphy: Fixed MDIO Bus: probed [0.464329] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [0.464345] ehci-pci: EHCI PCI platform driver [0.464366] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [0.464379] ohci-pci: OHCI PCI platform driver [0.464396] uhci_hcd: USB Universal Host Controller Interface driver [0.464474] usbcore: registered new interface driver usbserial [0.464494] usbcore: registered new interface driver usbserial_generic [0.464510] usbserial: USB Serial support registered for generic [0.464544] i8042: PNP: No PS/2 controller found. Probing ports directly. [1.495394] i8042: No controller found [1.495593] mousedev: PS/2 mouse device common for all mice [1.556097] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [1.556211] rtc_cmos: probe of rtc_cmos failed with error -38 [1.556300] dmi-sysfs: dmi entry is absent. [1.556343] hidraw: raw HID events driver (C) Jiri Kosina [1.556508] usbcore: registered new interface driver usbhid [1.556520] usbhid: USB HID core driver [1.556575] drop_monitor: Initializing network drop monitor service [1.556688] TCP: cubic registered [1.556703] Initializing XFRM netlink socket [1.556865] NET: Registered protocol family 10 [1.557258] NET: Registered protocol family 17 [1.557280] mce: Unable to init device /dev/mcelog (rc: -5) [1.557403] microcode: CPU0 sig=0x6f6, pf=0x4, revision=0xcd [1.557421] microcode: CPU1 sig=0x6f6, pf=0x4, revision=0xcd [1.557453] microcode: CPU2 sig=0x6f6, pf=0x4, revision=0xcd [1.557484] microcode: CPU3 sig=0x6f6, pf=0x4, revision=0xcd [1.557635] microcode: Microcode Update Driver: v2.01 <tig...@aivazian.fsnet.co.uk>, Peter Oruba [1.558075] Loading compiled-in X.509 certificates [1.558128] Loaded X.509 cert 'CentOS Linux kpatch signing key: ea0413152cde1d98ebdca3fe6f0230904c9ef717' [1.558159] Loaded X.509 cert 'CentOS Linux Driver update signing key: 7f421ee0ab69461574bb358861dbe77762a4201b' [1.559033] Loaded X.509 cert 'CentOS Linux kernel signing key: 2cbc9870546343ca3ae120c2bceb984401955962' [1.559080] registered taskstats version 1 [1.561924] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 816ab65d [1.561924] [1.561953] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.10.0-693.11.6.el7.x86_64 #1 [1.561966] Call Trace: [1.561982] [] dump_stack+0x19/0x1b [1.561996] [] panic+0xe8/0x20d [1.562009] [] ? __schedule+0x95d/0x9b0 [1.562009] [] ? switched_to_idle+0x10/0x10 [1.562009] [] __stack_chk_fail+0x1b/0x20 [1.562009] [] __schedule+0x95d/0x9b0 [1.562009] [] ? __do_page_fault+0x171/0x450 [1.562009] [] ? do_page_fault+0x35/0x90 [1.562009] [] ? page_fault+0x28/0x30 [1.562009] [] ? error_exit+0x2a/0x60 [1.562009] [] ? retint_swapgs+0x5/0x6 -- Shaun Reitan NDCHost.com ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Cannot allocate Memory
We are planing on moving to xl but have not done so yet. Our xend configs are untouched so they should match what they were when the xen-* packages were installed. We force dom0 to 1024MB of memory via grub. On a couple servers were we've seen this issue we've had 16+ GB of memory free and the domU was requesting something small like 2GB. -- Shaun -- Original Message -- From: "George Dunlap" <dunl...@umich.edu> To: "Shaun Reitan" <shaun.rei...@ndchost.com>; "Discussion about the virtualization on CentOS" <centos-virt@centos.org> Sent: 6/24/2016 4:28:53 AM Subject: Re: [CentOS-virt] Cannot allocate Memory On Wed, Jun 22, 2016 at 6:45 PM, Shaun Reitan <shaun.rei...@ndchost.com> wrote: Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a guest because of what looks like an issue allocating memory even though xm info shows like 5x the amount of free memory needed? We are still unfortunately still using xm... it's on my list, i know.. We've had this happen on a couple hosts now. Only way to resolve seams to be rebooting the host. I'm going to update the host to latest Xen 4.4 now hoping this is a old bug. xend hasn't had much love in years, so it's fairly unlikely that this has been fixed. Here's from xen logs [2016-06-22 09:13:50 1958] DEBUG (XendDomainInfo:105) XendDomainInfo.create(['vm', ['name', 'xxx'], ['memory', 2048], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', 2], ['oos', 1], ['image', ['linux', ['kernel', '/kernels/vmlinux-2.6.18.8-4'], ['videoram', 4], ['args', 'root=/dev/xvda ro xencons=tty console=tty1 '], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:vg/fs_6818'], ['dev', 'xvda'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:vg/fs_6819'], ['dev', 'xvdb'], ['mode', 'w']]], ['device', ['vif', ['rate', '40mb/s'], ['mac', 'FE:FD:48:01:F1:E7') [2016-06-22 09:13:50 1958] DEBUG (XendDomainInfo:2504) XendDomainInfo.constructDomain [2016-06-22 09:13:50 1958] DEBUG (balloon:187) Balloon: 7602632 KiB free; need 16384; done. [2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:2566) (12, 'Cannot allocate memory') Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2561, in _constructDomain target = self.info.target()) Error: (12, 'Cannot allocate memory') [2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:490) VM start failed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 475, in start XendTask.log_progress(0, 30, self._constructDomain) File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2572, in _constructDomain raise VmError(failmsg) VmError: Creating domain failed: name=xxx [2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:110) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 108, in create vm.start() File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 475, in start XendTask.log_progress(0, 30, self._constructDomain) File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2572, in _constructDomain raise VmError(failmsg) VmError: Creating domain failed: name=xxx If you haven't decided to switch to xl, would you mind reposting this question to xen-users? If you do, please also include the output of "xl info" after the failure. The logs tell us that xend is asking dom0 to free up some memory to use to create the guest. My guess is that there's a slight mismatch between how much memory xend things needs to be freed and how much memory actually needs freeing. Thanks, -George ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Cannot allocate Memory
Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a guest because of what looks like an issue allocating memory even though xm info shows like 5x the amount of free memory needed? We are still unfortunately still using xm... it's on my list, i know.. We've had this happen on a couple hosts now. Only way to resolve seams to be rebooting the host. I'm going to update the host to latest Xen 4.4 now hoping this is a old bug. Here's from xen logs [2016-06-22 09:13:50 1958] DEBUG (XendDomainInfo:105) XendDomainInfo.create(['vm', ['name', 'xxx'], ['memory', 2048], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', 2], ['oos', 1], ['image', ['linux', ['kernel', '/kernels/vmlinux-2.6.18.8-4'], ['videoram', 4], ['args', 'root=/dev/xvda ro xencons=tty console=tty1 '], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:vg/fs_6818'], ['dev', 'xvda'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:vg/fs_6819'], ['dev', 'xvdb'], ['mode', 'w']]], ['device', ['vif', ['rate', '40mb/s'], ['mac', 'FE:FD:48:01:F1:E7') [2016-06-22 09:13:50 1958] DEBUG (XendDomainInfo:2504) XendDomainInfo.constructDomain [2016-06-22 09:13:50 1958] DEBUG (balloon:187) Balloon: 7602632 KiB free; need 16384; done. [2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:2566) (12, 'Cannot allocate memory') Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2561, in _constructDomain target = self.info.target()) Error: (12, 'Cannot allocate memory') [2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:490) VM start failed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 475, in start XendTask.log_progress(0, 30, self._constructDomain) File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2572, in _constructDomain raise VmError(failmsg) VmError: Creating domain failed: name=xxx [2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:110) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 108, in create vm.start() File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 475, in start XendTask.log_progress(0, 30, self._constructDomain) File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2572, in _constructDomain raise VmError(failmsg) VmError: Creating domain failed: name=xxx -- Shaun___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Kernel 3.18.21-17 and 3.18.21-18 kernel panics
I've seen this issue on about 15 different servers now. Anybody else seeing this? Screenshot: http://imgur.com/cBcwr8l I also have a video of the boot process if that will be helpful. -- Shaun Reitan___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-docs] Open Help Conference
Hi all, I'm the main organizer of the Open Help Conference Sprints. Open Help is taking place September 26-30 this year, its fifth year. Open Help features a combination of talks and open discussion on topics related to open source documentation. The conference portion is September 26-27. After the conference, we host three days of multiple team doc sprints, September 28-30. We have room for six teams to host sprints this year. Open Help has hosted sprints for teams like GNOME, Mozilla, Wikipedia, and WordPress in the past. There's some background on the sprints and tips for holding a doc sprint in my opensource.com article: http://opensource.com/community/15/7/five-lessons-open-help-doc-sprints I'd love to have some folks from CentOS out this year. You can attend with or without a team sprint, though we like having entire teams out for sprints. We also have room for more talks. More information is available on the web site: https://conf.openhelp.cc/ Let me know if you have any questions. Thanks, Shaun McCance ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Docs strategy and tactics [RFC]
On Tue, 2015-03-17 at 01:54 +0530, kunaal jain wrote: On Mon, Mar 16, 2015 at 10:48 PM, Shaun McCance sha...@redhat.com wrote: I like putting focus on this. It provides people a resource for things they actually want to do. Nobody wants just an operating system. I also think it's a great avenue for getting community contributions. It's easy to make a one-time contribution on a topic you know well without digging into how it affects everything. An anecdote: I pay Linode for a VPS. I run a few things on there that I'm only barely qualified to run. The Linode docs have some of the best guides I've seen for things like setting up Postfix and Mailman to run a mailing list. It's not docs for Linode per se, but it is docs for what you actually want to do once you've paid for that shiny VPS. I think there's a lot of potential here for CentOS to be the source for setup guides and the like for stuff people actually do once they've installed an enterprise OS. This is one of the main motivation about this. Curating content from contributors which write about how to do things on CentOS. When I get a new shiny OS, I need to know how powerful it is, what I can do with it. I have a VPS on digitalocean. The reason I got convinced of using a VPS was their documentation. How awesome a VPS is, what I can do with it. Their docs is selling their product! Just to throw another wrench in: I don't know what DigitalOcean's docs are like, but Linode generally provides their guides for Ubuntu, Debian, and CentOS. However, for whatever reason, they tend to do Ubuntu first. So there are bunches of guides without CentOS versions. They do allow people outside Linode to submit guides. So outside of normal CentOS docs, a useful exercise would be for people to port non-CentOS guides on Linode (and other places) to CentOS. It would increase mindshare for CentOS. It sounds like you want to set up content pools that multiple projects and upstreams can pull from. That's a very hard problem, and even harder if you need to support multiple formats. The technical details of such a system could easily take up another email thread. That's the goal. Start a new project on this. A new toolchain. It will take time to develop it fully. There is interest of me taking this as Google Summer of Code Project with Karsten as mentor. Sure. I've dealt with quite a bit of this while working on GNOME docs. It's challenging, but mostly enjoyably so. I mentioned to Karsten off-list that, if you want a usable system at the end, it's important to really define the workflow and what tools are needed. I've had quite a few GSoC projects that just ended up as interesting experiments, but never got used. Interesting experiments can be fine, but not if your documentation strategy depends on them. -- Shaun ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Docs strategy and tactics [RFC]
If the doc fits perfectly within an upstream as an example of how to deploy or use the upstream software on the CentOS platform, we push doc to the appropriate upstream(s). Link or copy is carried at centos.org/docs and appropriate wiki pages. 3.3 Unclear where doc fits, so author and SIG members engage with upstream project(s) to find out best way forward. One of the reasons this might be the case is that the doc deals with integration, so there are multiple upstreams involved. And I think that's an area where CentOS docs can provide real value, and drive traffic to CentOS. I want a Google search for How to deploy X with Y to give a CentOS result. 3.3.1 Write down each upstream preference as we learn. 4. Content is prepared for target location and delivered. 4.1 Document is edited for style, grammar, punctuation, etc. 4.2 Document is edited for ease of translation. 4.3 Conversion to a standard format, if required. 4.4 Check-in to version controlled system. 5. Publicity around document being available -- @centos, proper links across CentOS wiki and at /docs, possibly a blog post highlighting a new series of content, etc. 5.1 Potential interaction with Promo SIG here. == Tooling There are a few levels to think about here where it comes to thinking about a chunk of content: A. The markup used, standards around how it's written (avoid idioms, use the Oxford comma, etc.) Don't make contributors work too hard at this. Nitpicky review processes are a huge barrier to contribution, and not just for newcomers. I've tried a few times over the last few years to kickstart an open source style guide that projects could share, so we don't all have to keep writing our own. What I think I've learned is that you do want a style guide, but you really ought to have a tl;dr version. Sort of like codes of conducts often have short forms and long forms. Nobody wants to read the long form before making their first contribution. B. Tools for editing that don't drive people crazy. C. Tools to convert the source to one or more document formats. This includes converting to an upstream project's preferred format. Without getting too far ahead here, there are clearly a handful of solutions that will work well. For example, we could author using whatever preferred editor in a markup such as AsciiDoc or MarkDown, then use e.g. AsciiDoctor to do the conversions (to Mallard, XML, HTML, PDF, ePub, etc.), all with sources stored in Git. That would allow for us to mirror content to github.com/CentOS and people could use Prose.io for editing and pull requests to submit content. We would sync all that back to git.centos.org. That sort of workflow and tooling would allow us to take advantage of the 'social coding' aspect of GitHub, which is essentially a very low barrier to writing that is missing in tools such as DocBook XML. For editing, the GitHub workflow is nice in that it allows me to use my preferred editor and other tools, but also allows super-easy editing on the web. Prose.io is a nice idea, but I haven't found it very compelling in practice. You need tools for maintenance of very large sets of docs. For smaller sets, you can deal with a lot more person work. It sounds like you want to set up content pools that multiple projects and upstreams can pull from. That's a very hard problem, and even harder if you need to support multiple formats. The technical details of such a system could easily take up another email thread. == Notes [1] We have to write up a secondary proposal for the CentOS Board to make the Docs group a SIG. Part of the SIG idea is to have 'functional SIGs', meaning groups whose purpose is to get things done /for/ the Project itself. Examples are Infrastructure, Documentation, Design, Promotions (Marketing), CBS/Build System, and so forth. These are different from 'upstream or variant SIGs' that focus on doing things /on/ the Project's artifacts, for example the Cloud Instance SIG, Virt SIG, and Cloud SIG. +1 -- Shaun ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-virt] messages logs flooded with xen_balloon: reserve_additional_memory: add_memory() failed
My /var/log/messages log is being flooded with kernel messages showing the following messages Aug 1 11:22:52 host43 kernel: System RAM resource 4800 - 4fff cannot be added Aug 1 11:22:52 host43 kernel: xen_balloon: reserve_additional_memory: add_memory() failed: –17 Doing a search I found a thread from xen-devel that talks a bit about it. I’m not sure if this is related to the same issue or if that issue was ever fixed. When I cat current_kb and target_kb the values don’t match, they are just barely off. I have not tried setting them to match yet. http://marc.info/?t=13560150894r=1w=3 [root@host ~]# cat /sys/devices/system/xen_memory/xen_memory0/info/current_kb 1048532 [root@host ~]# cat /sys/devices/system/xen_memory/xen_memory0/target_kb 1048576 Any ideas? -- Shaun Reitan___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS] Openswan or Ipsec-tools?
On 14/05/2012 19:15, Steve Clark wrote: Yes the fc12 version loads just fine. ipsec-tools-0.7.3-4.fc12.i686 So it's not in CentOS 6. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Openswan or Ipsec-tools?
I didn't think ipsec-tools were in CentOS 6? Just openswan. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum yum or not?
On 30/04/2012 02:20, Spiro Harvey wrote: Shaun cen...@stinkfish.org wrote: I just need to be really careful about the remove command in future. I've found that breaking things is always the fastest path to a great education. I'd certainly agree with that :) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum yum or not?
On 26/04/2012 22:08, Ljubomir Ljubojevic wrote: (snip) yum history list yum history info number given transaction and yum history undo yum history redo, ... ... Well this is it. I've used both 'remove' and 'history undo' and had better success (system not having something important removed) with the latter. .. and so I was wondering whether it's advised to use this form rather than yum remove, and to find out why 'remove' is less successful (or if it's just me!). Another example I had recently was when I installed Networkmanager-openswan and then after installing realised that it didn't support L2TP/IPSec VPNs so I uninstalled it, again with 'yum remove'. It removed the WiFi applet from the Gnome panel, which wasn't what I was expecting. I had to reinstall networkmanager to get it back. It just seems I should probably be more cautious of inspecting proposed system changes when doing 'yum remove' but just wanted to make sure that I wasn't doing something wrong. There is a nice sheet on the differences between apt and yum on distrowatch's website which I've RTFM'd obviously :) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] High load averages copying USB
On 27/04/2012 02:18, Lists wrote: Problem isn't so much actual speed but causing network monitors to freak out due to high load average when performing backups. I can make exceptions for servers doing backups, but then I don't get notifications when the load is legitimately high. I can make exceptions only during backup times, but that increases complexity. When using nagios or zabbix you're better off working out what the average load is over a large period of time (say, day, or week) and then comparing the load over the last 15 miuntes, say, to the average load. This should even out spikes, and also be comparing to a good base level load. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] High load
On 25/04/2012 07:09, Kaushal Shriyan wrote: Hi Is there a way to nail down the issue of high load on a server basically trying to understand the reason behind high load at a specific time period. I use top command but it does not have history. Nagios reports saying *[04-25-2012 10:11:00] SERVICE ALERT: dev;LOAD;WARNING;HARD;3;WARNING - load average: 6.88, 6.36, 5.71* When this happens and you get an alert login to the box and take a look. vmstat, top, iostat, iotop ... all good commands to see what's going on. Of course if you can't or don't want to login then you can always get nagios to email you what's currently going on by writing your own custom plugin via nrpe. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum yum or not?
On 27/04/2012 12:24, Jason Pyeron wrote: Are you saying that you had the applet in the gnome panel prior to installing the network manager rpm and then when you removed the network manager rpm (via yum) it yanked the applet too? If so which version of Centos and which version of network manager was it? This is precisely what I'm saying. And this to me is unexpected behaviour. Centos 6.2 and the networkmanager package that's in base. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum yum or not?
On 27/04/2012 14:05, Les Mikesell wrote: What did you expect: Removing for dependencies: NetworkManager-gnome meant before you confirmed the yum action? Well if that was what was presented to me as an action then I obviously need to be more vigilant! :) In fact I had similar issues in Fedora and weird things happening adding/removing packages. But then the reason why I didn't pay as much attention in the first place is because I *assumed that only that removed-pacakage and dependencies brought in by it at the install-time would be removed via a yum remove. Maybe there are differences in the dependency management that I need to go read about..? Thanks. * assumption being the mother of .. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum yum or not?
On 27/04/2012 14:56, Markku Kolkka wrote: So the real problem is that you don't understand the directionality of dependencies. Almost certainly :) yum install packagename installs packagename + anything that packagename requires. yum remove packagename removes packagename + anything that requires packagename. The set of packages required by packagename and the set of packages that require packagename are two entirely different things. Yes, I thought yum remove packagename would remove the packagename plus any dependencies that were INSTALLED by the yum install packagename action. That is, I expected it to NOT remove dependency packages that were already present when yum install packagename was performed. So a misunderstanding on my part. I just need to be really careful about the remove command in future. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] yum yum or not?
Hi all, I'm a bit of a newbie to CentOS though not Linux in general. I come from an apt-get package management mentality and I've had a few issues where package management actions haven't quite done what I'd expect. So I'm guessing it's user error! :) I installed GNOME and then decided that I wanted to install Xfce to try it out. I decided to then remove it with just 'yum remove' after playing with it a bit. It seemed to uninstall a lot of GNOME stuff (presumably that they had in common) and so the next time I tried to use GNOME it looked different and was missing a few components. Should I have just reverted the install of Xfce to undo it so that those dependencies would've have been touched or is this just how yum works? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum yum or not?
On 26/04/2012 15:58, Les Mikesell wrote: You can't really generalize about that. Yum just does what the dependencies of the rpm packages you install or remove tell it to do. A yum groupinstall 'GNOME Desktop Environment' might bring back anything that is missing. Well I was kinda expecting it to not remove the shared dependencies leaving GNOME fairly broken. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] how to get dev/dsp and oss modules back
Hello I have some older programs that require OSS and /dev/dsp I have tried the pulseaudio trick with padsp but some work and some don't. I have also edited the /etc/modprobe/dist-oss-conf and uncommented the line that says install snd-pcm /sbin/modprobe --ignore-install snd-pcm /sbin/modprobe snd-pcm-oss /sbin/modprobe snd-seq-device /sbin/modprobe snd-seq-oss This was supposed to work at least from what I have read to get the modules back but unfortunately it has not. I have no /dev/dsp at all or any oss modules when doing a lsmod. As you can see here snd_emu10k1_synth 4968 0 snd_emux_synth 30789 1 snd_emu10k1_synth snd_seq_virmidi 4176 1 snd_emux_synth snd_seq_midi_event 5815 1 snd_seq_virmidi snd_seq_midi_emul 5187 1 snd_emux_synth snd_seq46091 4 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_event,snd_seq_midi_emul snd_emu10k1 128854 5 snd_emu10k1_synth snd_rawmidi18705 2 snd_seq_virmidi,snd_emu10k1 snd_ac97_codec 95710 1 snd_emu10k1 ac97_bus 942 1 snd_ac97_codec snd_pcm66969 3 snd_emu10k1,snd_ac97_codec snd_seq_device 5354 5 snd_emu10k1_synth,snd_emux_synth,snd_seq,snd_emu10k1,snd_rawmidi snd_timer 18308 3 snd_seq,snd_emu10k1,snd_pcm snd_page_alloc 7080 2 snd_emu10k1,snd_pcm snd_util_mem2950 2 snd_emux_synth,snd_emu10k1 snd_hwdep 5320 2 snd_emux_synth,snd_emu10k1 snd52754 17 snd_emux_synth,snd_seq_virmidi,snd_seq,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_seq_device,snd_timer,snd_hwdep soundcore 6460 1 snd I have tried it with both pulseaudio installed and pulseaudio not installed and no go either way. So my question is this, have the OSS modules and support been removed from the kernel like many other distros have done? If so I will have to rebuild the kernel to get this functionality back which really is no big deal, but was hoping someone would know something I do not, thanks in advance. -- Mister Jones ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] recommended way to install source rpms?
On Sun, Oct 10, 2010 at 8:23 PM, JohnS jse...@gmail.com wrote: On Sun, 2010-10-10 at 17:36 -0600, Frank Cox wrote: On Sun, 2010-10-10 at 18:58 -0400, Robert P. J. Day wrote: but it's a little high-handed to not explain how to do something because you've decided it's not something you want *others* to know. There is very little to explain, if all you want to do is examine the source. Install rpmdevtools. Run rpmdev-setuptree Really? ]$ yum search rpmdevtools Loaded plugins: fastestmirror addons | 951 B 00:00 base | 2.1 kB 00:00 extras | 2.1 kB 00:00 updates | 1.9 kB 00:00 Excluding Packages in global exclude list Finished Warning: No matches found for: rpmdevtools No Matches found John ___ rpmdevtools is in the epel repo so if you dont have epel installed and setup you wont see it with a yum search -- Shaun http://lostonsvault.org twitter - http://twitter.com/lostson identi - http://identi.ca/lostson ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Status of tracker for 64bit?
On Fri, July 4, 2008 10:22 am, Kwan Lowe wrote: Good morning to you all: I've been trying for a few hours to connect to the tracker for the 5.2 x64 DVD. It has been giving a connection refused error. A few days ago the 5.2 i386 downloaded succesfully. Is the tracker down?? Or is something odd happening on my side?? thanks, Kwan Hi, I just tried the torrent, it is giving me the same error. It can't have been offline very long as I just downloaded the x64 version yesterday. Shaun ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
