similar to: CentOS-7 x86_64 AMIs and consistent network device naming

On 04/11/16 11:18, Jinesh Choksi wrote: > Hello, > > Re: > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/7.3_Release_Notes/bug_fixes_general_updates.html > > Are there any upcoming plans for turning off the use of legacy interface > names in the next official CentOS 7.x AMI? > > Currently, both the official RHEL 7.3 GA AMI and the

On 01/30/2017 03:18 AM, Jinesh Choksi wrote: >>Are there other kernel options that might be useful to try? > > pci=nomsi > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/13 Incidentally, already found that one and I'm trying it currently on one of the boxes. So far there's been no issues, but it's only been since Friday. Also, I found

As a heads up RHEL 7.3 is released: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.3_Release_Notes/index.html Pay careful attention when the CR repo starts churning out RPMs (if you have CR enabled) as there have been a few rebases in this - notably firewalld, NetworkManager, freeIPA, libreoffice, samba, amongst others If you have an ipv6 environment ping is now

On 28/01/17 05:21, Kevin Stange wrote: > On 01/27/2017 06:08 AM, Karel Hendrych wrote: >> Have you tried to eliminate all power management features all over? > > I've been trying to find and disable all power management features but > having relatively little luck with that solving the problems. Stabbing > the the dark I've tried different ACPI settings, including

Hai, I am using dell insprion 580 machine for xen installation and dom0 configuation. I compiled xen source code and configured the kernal. Grub entry given below menuentry ''Xen 4.0.0-rc8 / Ubuntu 10.4 kernel 2.6.32.25 pvops'' { insmod ext2 set root=''(hd0,3)'' multiboot (hd0,3)/boot/xen-4.0.0-rc8.gz module (hd0,3)/boot/vmlinuz-2.6.32.25 dummy=dummy

Hai, I am using dell insprion 580 machine for xen installation and dom0 configuation. I compiled xen source code and configured the kernal. Grub entry given below menuentry ''Xen 4.0.0-rc8 / Ubuntu 10.4 kernel 2.6.32.25 pvops'' { insmod ext2 set root=''(hd0,3)'' multiboot (hd0,3)/boot/xen-4.0.0-rc8.gz module (hd0,3)/boot/vmlinuz-2.6.32.25 dummy=dummy

Hai, I use following steps for LV backup. * lvcreate -L 5G -s -n lv_snapshot /dev/VG_XenStorage-7b010600-3920-5526-b3ec-6f7b0f610f3c/VHD-a2db885c-9ad0-46c3-b2c3-a30cb71d83f8 lv_snapshot created* This command worked properly Then issue kpartx command kpartx -av

Hai, I use following steps for LV backup. * lvcreate -L 5G -s -n lv_snapshot /dev/VG_XenStorage-7b010600-3920-5526-b3ec-6f7b0f610f3c/VHD-a2db885c-9ad0-46c3-b2c3-a30cb71d83f8 lv_snapshot created* This command worked properly Then issue kpartx command kpartx -av

Chris Mauritz wrote: > > The 32bit PPC release is for the older G3/G4 macs, no? I've got a > pile of unused G4 400-800mhz powermacs just sitting around The ppc32 distro will work on any NewWorld G3, G4 based machine ( and 32bit ibm power, like the older rs6k's ) - it _also_ works fine on the MacMini and G4 Xserve's. With some common sense tweaks, a G4 450Mhz is a very

Hello- Does anyone one this list maintain the official CentOS 6 + 7 AMIs in AWS? If so, could you please enable those images for use with the new g3.* instance types? If this list is the wrong place for this request, please point me in the right direction. Thanks! -Stephan

Hi list, I've noticed that instance-backed AMIs are not available in AWS MP (only the EBS ones are there). Still though, also the instance-backed AMIs are listed as published and available on your wiki: http://wiki.centos.org/Cloud/AWS I've seen that the same question was asked already before but I'm not sure the answer given actually covered the whole question:

Some additional info... AFAIK, the AMIs I'm referring to are owned/maintained by the CentOS team, not by AWS. Details and suggestions to contact this list for assistance are published at both https://wiki.centos.org/Cloud/AWS and https://wiki.centos.org/Cloud/AWS Basically, the maintainer of the Centos.org AWS account just needs to add/approve the current AMIs for the g3.* instance

Hi list, I've noticed that instance-backed AMIs no longer seem to exist for the 'official' CentOS images, though the EBS ones are fine.. Looking at the wiki (http://wiki.centos.org/Cloud/AWS), the AMIs listed on marketplace are slightly newer than what's listed on the wiki, so just wondering if something got overlooked after the last build? Cheers, -- Richard Clark richard at

Hi, I am trying to copy the latest CentOS image to my own AWS account so that I can enable EBS volume encryption. It currently looks like the option when sharing the image is not enabled to allow direct copying of the snapshots, and I am wondering if this could be looked at? I can start an instance with this AMI, then create a new snapshot for the purpose of enabling EBS volume encryption, but

I know this list is meant for discussion of compiz specifically, but .... 1) I sometimes see compiz spit out "Could not bind pixmap to texture" messages, even though it _appears_ to be working fine. I randomly guess that this is due to me running out of video memory (iirc I have 64mb of vram). Is that possibly a problem? I think Vista and OS X manually manage video

Hello all, and thank you very much for the Centos 7 HVM AMI [1], greatly appreciated! This AMI does not work on the newly launched AWS Frankfurt region (eu-central-1). Any plans for fixing that? According to the AWS announcement [2], "The Region supports all sizes of T2, M3, C3, R3, and I2 instances". (We'll be running the CentOS 7 HVM AMI going forward, but looks like none of

On 01/27/2017 06:08 AM, Karel Hendrych wrote: > Have you tried to eliminate all power management features all over? I've been trying to find and disable all power management features but having relatively little luck with that solving the problems. Stabbing the the dark I've tried different ACPI settings, including completely disabling it, disabling CPU frequency scaling, and setting

Hi Folks, A recent exchange on the 'octave' list led to the following paper being cited, which I had not met before: What Every Computer Scientist Should Know About Floating-Point Arithmetic, by David Goldberg, originally published in the March, 1991 issue of Computing Surveys. PDF and HTML versions are widely available on the web (see Google), e.g. at

Hi All, Now that this thread has accumulated some feedback, I thought I'd try to summarize my thoughts on error handling in LLVM, and why I think this proposal is worth adopting: (1) Failure to check an error *is* a programmatic error, and our error system should reflect this. This makes it easy to spot mistakes in our error handling and correct them. (2) Error returns should describe all

On 01/30/2017 12:59 PM, Kevin Stange wrote: > On 01/30/2017 03:18 AM, Jinesh Choksi wrote: >>> Are there other kernel options that might be useful to try? >> >> pci=nomsi >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/13 > > Incidentally, already found that one and I'm trying it currently on one > of the boxes. So far