[CentOS] Failed to get to installer for CentOS 7 VM under CentOS 6...

[Robert Heller]

I just tried to create a CentOS 7 VM on a CentOS 6 host, but it crashes to the 
dracut prompt.  I am using the PXEBoot installer.  I *think* it is unhappy 
with the (virtual) graphics controller, but I am not sure.  

The rdsosreport.txt file is available here:
https://www.deepsoft.com/wp-content/uploads/2018/09/rdsosreport.txt

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
   
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] C7 and NVIDIA driver

[Yan Li]

On 09/20/2018 10:51 AM, James Pearson wrote:

What is more puzzling, is that we have probably over a thousand workstations 
running CentOS 7.5 with Nvidia cards using the proprietary driver and haven't 
seen any of the 'issues' listed - which are:

*  Nvidia proprietary module doesn't work after upgrading to RHEL7.5
*  No graphics after updating to RHEL7.5
*  Desktop does not start after upgrading to RHEL7.5 with Nvidia graphics driver
*  Black screen after installing Nvidia proprietary graphics module in RHEL7.5

We're using gdm which launches Mate


I am using the latest CentOS 7.5 gdm/GNOME with 390.30-2.el7 driver from 
cuda repo. Haven't seen any problem either. Chip is Quadro M2000M.


--
Yan Li
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] C7 and NVIDIA driver

[Yan Li]

On 09/20/2018 10:49 AM, Yan Li wrote:
NVIDIA actually releases their drivers in official RPM format for 
RHEL/CentOS. Much easier/faster to use and update than their shell 
script driver. They are in NVIDIA's cuda repo. You can install the repo 
files from here:


https://developer.nvidia.com/cuda-downloads

Choose "rpm (network)" for the last step to get to the yum repo. I use 
cuda but I think you can just install nvidia-kmod to get the driver only.


Just checked. The latest repo changed the package name from nvidia-kmod 
to dkms-nvidia.


A minor problem is that one cuda version and repo are only maintained 
for about half a year, then NVIDIA moves to next version. If you always 
want the latest NVIDIA driver, you might need to change the cuda repo 
URL to point to the latest every year. I only upgrade when TensorFlow 
supports a new version of CUDA.


I was wrong on this. NVIDIA now actively updates the repo to always 
point to the latest driver. No manual update needed.


--
Yan Li
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] C7 and NVIDIA driver

[James Pearson]

Alessandro Baggi:
>
> I found this https://access.redhat.com/solutions/3438891 but I've not
> access to this content. In this content seems that the workaround is
> using lightdm and mask gdm.

That page is not exactly helpful ... virtually no details

Strangely, it has 'Solution Verified' at the top of the page, but the listed 
'Resolution' is:

> At this time there is no guaranteed resolution of this issue. Using the
> Nvidia Beta graphics module sometimes works, but is not guaranteed
> or supported

What is more puzzling, is that we have probably over a thousand workstations 
running CentOS 7.5 with Nvidia cards using the proprietary driver and haven't 
seen any of the 'issues' listed - which are:

*  Nvidia proprietary module doesn't work after upgrading to RHEL7.5
*  No graphics after updating to RHEL7.5
*  Desktop does not start after upgrading to RHEL7.5 with Nvidia graphics driver
*  Black screen after installing Nvidia proprietary graphics module in RHEL7.5

We're using gdm which launches Mate

James Pearson
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] C7 and NVIDIA driver

[Yan Li]

On 09/20/2018 07:04 AM, Alessandro Baggi wrote:

Hi all,
I'm running C7 on i7 8700k/asus z370-a with an GTX1050.
I noticed that there are several problems installing Nvidia proprietary 
driver. After one week of troubleshooting I got my solution. Hope that 
can help other user.
... 
I tried using proprietary driver from nvidia site and from elrepo.


NVIDIA actually releases their drivers in official RPM format for 
RHEL/CentOS. Much easier/faster to use and update than their shell 
script driver. They are in NVIDIA's cuda repo. You can install the repo 
files from here:


https://developer.nvidia.com/cuda-downloads

Choose "rpm (network)" for the last step to get to the yum repo. I use 
cuda but I think you can just install nvidia-kmod to get the driver only.


A minor problem is that one cuda version and repo are only maintained 
for about half a year, then NVIDIA moves to next version. If you always 
want the latest NVIDIA driver, you might need to change the cuda repo 
URL to point to the latest every year. I only upgrade when TensorFlow 
supports a new version of CUDA.


This may not solve your specific problem. I just think that there's no 
reason to going back to use NVIDIA's clumsy .run driver or any 3rd party 
driver when the official RPMs are easy to use/update.


--
Yan Li
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IPv6 fixed address using ip token

[Mark Milhollan]

On Thu, 20 Sep 2018, Kenneth Porter wrote:

> I'm about to publish a fixed IPv6 address and I understand I can use the ip
> token command to lock the host part of the RA-assigned address to a fixed
> value. But I can't see an obvious place to configure this. 

It looks like there is no support for IPv6 tokenized identifiers in the 
existing ifcfg scripting (report an upstream bug?) so you would have to 
wait for Red Hat to produce a solution, patch the scripts yourself (set 
the interface's token just before bringing the interface up in 
ifup-ipv6) or remove their use and write your own systemd.network(5) 
unit for all the interfaces -- perhaps one of the two latter things 
while waiting for the former.


/mark
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Install qemu packages from ovirt instead of original.

[--N-- via CentOS]

Hi,
I have a KVM server running on Centos 7.5.
[root@kvm2 ~]# cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)


Qemu packages are from Centos repository.
[root@kvm2 ~]# rpm -qa|grep qemu
libvirt-daemon-driver-qemu-3.9.0-14.el7_5.7.x86_64
qemu-img-1.5.3-156.el7_5.5.x86_64
qemu-kvm-common-1.5.3-156.el7_5.5.x86_64
ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch
qemu-guest-agent-2.8.0-2.el7_5.1.x86_64
qemu-kvm-1.5.3-156.el7_5.5.x86_64

But, I want to install a new version of qemu from ovirt repositories. (This 
because I need live disk snapshots). 

So I installed ovirt yum repository, run yum update and I see qemu will be 
updated (as you can see below in red)

Resolving Dependencies
--> Running transaction check
---> Package glusterfs.x86_64 0:3.8.4-54.15.el7.centos will be updated
---> Package glusterfs.x86_64 0:3.12.14-1.el7 will be an update
---> Package glusterfs-api.x86_64 0:3.8.4-54.15.el7.centos will be updated
---> Package glusterfs-api.x86_64 0:3.12.14-1.el7 will be an update
---> Package glusterfs-cli.x86_64 0:3.8.4-54.15.el7.centos will be updated
---> Package glusterfs-cli.x86_64 0:3.12.14-1.el7 will be an update
---> Package glusterfs-client-xlators.x86_64 0:3.8.4-54.15.el7.centos will be 
updated
---> Package glusterfs-client-xlators.x86_64 0:3.12.14-1.el7 will be an update
---> Package glusterfs-fuse.x86_64 0:3.8.4-54.15.el7.centos will be updated
---> Package glusterfs-fuse.x86_64 0:3.12.14-1.el7 will be an update
---> Package glusterfs-libs.x86_64 0:3.8.4-54.15.el7.centos will be updated
---> Package glusterfs-libs.x86_64 0:3.12.14-1.el7 will be an update
---> Package google-chrome-stable.x86_64 0:69.0.3497.92-1 will be updated
---> Package google-chrome-stable.x86_64 0:69.0.3497.100-1 will be an update
---> Package kexec-tools.x86_64 0:2.0.15-13.el7 will be updated
---> Package kexec-tools.x86_64 0:2.0.15-13.el7_5.1 will be an update
---> Package libcacard.x86_64 40:2.5.2-2.el7 will be updated
---> Package libcacard.x86_64 40:2.5.2-2.1.el7 will be an update
---> Package pyOpenSSL.x86_64 0:0.13.1-3.el7 will be obsoleted
---> Package python-coverage.x86_64 0:3.6-0.5.b3.el7 will be obsoleted
---> Package python-dateutil.noarch 0:1.5-7.el7 will be updated
---> Package python-dateutil.noarch 1:2.4.2-1.el7 will be an update
---> Package python-netaddr.noarch 0:0.7.5-9.el7 will be updated
---> Package python-netaddr.noarch 0:0.7.18-1.el7 will be an update
---> Package python-six.noarch 0:1.9.0-2.el7 will be obsoleted
---> Package python2-coverage.x86_64 0:4.4.1-1.el7 will be obsoleting
---> Package python2-pyOpenSSL.noarch 0:16.2.0-3.el7 will be obsoleting
---> Package python2-six.noarch 0:1.10.0-9.el7 will be obsoleting
---> Package qemu-img.x86_64 10:1.5.3-156.el7_5.5 will be obsoleted
---> Package qemu-img-ev.x86_64 10:2.10.0-21.el7_5.4.1 will be obsoleting
---> Package qemu-kvm.x86_64 10:1.5.3-156.el7_5.5 will be obsoleted
---> Package qemu-kvm-common.x86_64 10:1.5.3-156.el7_5.5 will be obsoleted
---> Package qemu-kvm-common-ev.x86_64 10:2.10.0-21.el7_5.4.1 will be obsoleting
---> Package qemu-kvm-ev.x86_64 10:2.10.0-21.el7_5.4.1 will be obsoleting
--> Finished Dependency Resolution

Finally I did not update qemu because this KVM server has multiples VMs running 
and I was not sure if it could impact VMs working.
My question, how can this qemu  update can imapct my already running VMs?
Appreciate your help.
Thanks in advance.
Regards

Israel.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] C7 and NVIDIA driver

[Alessandro Baggi]

Hi all,
I'm running C7 on i7 8700k/asus z370-a with an GTX1050.
I noticed that there are several problems installing Nvidia proprietary 
driver. After one week of troubleshooting I got my solution. Hope that 
can help other user.


I found this https://access.redhat.com/solutions/3438891 but I've not 
access to this content. In this content seems that the workaround is 
using lightdm and mask gdm.


The case:

I tried using proprietary driver from nvidia site and from elrepo.
In all the case I got system that hungs during boot. In a first time I 
got message about a device probing (and some kernel trace about i915) 
and running systemd-analyze blame seems that udev-settle hungs for 
several minutes. Some suggested to disable udev-settle if you does not 
have LVM but this is not my case.
After this error I got error with GDM (infinite hungs) so I tried 
lightdm that works blinking.


So I switched to multi-user level, I got always udev-settle hung but 
running startx system works but with some strange behaviuour.


Now I tried another solution. I installed kernel-lt, kernel-lt-devel and 
reinstalled NVIDIA driver. All works very well also reenabling graphical 
runlevel.


best regards
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] IPv6 fixed address using ip token

[Kenneth Porter]

I'm about to publish a fixed IPv6 address and I understand I can use the ip 
token command to lock the host part of the RA-assigned address to a fixed 
value. But I can't see an obvious place to configure this. The logical 
place would be in the ifcfg- file. Is there someplace else I 
should set this? NetworkManager? It looks like the new systemd-networkd has 
support for this but my interfaces seem to be configured from the old 
initscripts and the new systemd-networkd isn't installed.




___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos