Thursday, May 18, 2017

Trying to spend more time sharing the stuff I did.

Gitlab

On GitLab, projects are private by default. So I imported tons of projects from GitHub, but they are all marked Private by default. I did not find a good way to batch-mark projects as public. So today, I went ahead and marked them public one by one. It's quite tedious, and the interface takes a couple of seconds per project.xx

Spice macOS enablement

Yet another iteration on this one. I'm spending more time on this than I thought I would, but that's part of the learning process I guess.

Old machines repair

Since I can't connect with virt-manager from Muse for whatever reason (it keeps asking for software), I thought I'd try to reinstall Shuttle. Since I moved its primary disk to Turbo, I needed to add an old disk in it. Hopefully, one of my old disks will be good enough

Turbo enablement

The reason for trying to bring up one other machine is to get virt-manager to connect to Turbo and create my new VM. But I keep running into another problem, that virt-manager seems to be crashing.

Filed it as rhzb1452211.

I rebooted the f25-turbo guest several times, and after changing the grub command line to make it more verbose (I added console=ttyS0 to GRUB_CMDLINE_LINUX in my /etc/sysconfig/grub then ran grub2-mkconfig -o /etc/grub2.cfg), I finally got the capability to type in the login window. I don't think the two were related. I was attempting multiple things. One of them probably worked.

With the console=ttyS0 option, I can now virsh console f25-turbo and get my console output. Easier for copy-paste.

The verbose output from my guest is interesting:

[   49.972137] nouveau 0000:00:0a.0: fifo: SCHED_ERROR 08 []
[   49.973820] nouveau 0000:00:0a.0: fifo: SCHED_ERROR 08 []
[   49.975501] nouveau 0000:00:0a.0: fifo: SCHED_ERROR 08 []

So maybe I should disable nouveau in the guest too. Right now I suspect this may be the root cause of my issues with that guest. I need to install the NVIDIA driver anyway, so I might as well do that.