dustymabe changed the topic of #fedora-coreos to: Fedora CoreOS :: Find out more at https://getfedora.org/coreos/ :: Logs at https://libera.irclog.whitequark.org/fedora-coreos
ravanelli has joined #fedora-coreos
daMaestro has joined #fedora-coreos
ravanelli has quit [Ping timeout: 252 seconds]
jtgreene has quit [Quit: fBNC - https://bnc4free.com]
jtgreene has joined #fedora-coreos
jtgreene has quit [Changing host]
jtgreene has joined #fedora-coreos
ravanelli has joined #fedora-coreos
ravanelli has quit [Ping timeout: 248 seconds]
ravanelli has joined #fedora-coreos
ravanelli has quit [Ping timeout: 260 seconds]
rsalveti has quit [Quit: Connection closed for inactivity]
ravanelli has joined #fedora-coreos
ravanelli has quit [Ping timeout: 240 seconds]
paragan has joined #fedora-coreos
daMaestro has quit [Quit: Leaving]
jcajka has joined #fedora-coreos
ravanelli has joined #fedora-coreos
ravanelli has quit [Ping timeout: 248 seconds]
Betal has quit [Quit: WeeChat 3.5]
plarsen has quit [Remote host closed the connection]
bgilbert has quit [Ping timeout: 276 seconds]
bgilbert has joined #fedora-coreos
shanduur[m] has joined #fedora-coreos
<shanduur[m]> Hi! Am I able to set `GRUB_CMDLINE_LINUX` anyhow in CoreOS? I want to be able to do PCIe pass through in the KubeVirt 🙂
<stephanepoq> are you looking for "--append-karg " ? https://coreos.github.io/coreos-installer/cmd/install/
ravanelli has joined #fedora-coreos
<bgilbert> --append-karg only helps when running coreos-installer. it doesn't help with image-based use cases like kubevirt
<bgilbert> shanduur[m]: if you're using Fedora CoreOS and not with OKD, you can add kernel arguments with the kernel_arguments section in your Butane config
<bgilbert> shanduur[m]: if you're using OpenShift or OKD, there's a different mechanism you can use to add kernel arguments
<lucab> (depending on the kernel argument, there is also a good chance that it has a sysctl equivalent entry)
ravanelli has quit [Ping timeout: 260 seconds]
<bgilbert> dustymabe: add-override workflow fix in https://github.com/coreos/fedora-coreos-config/pull/1739
<shanduur[m]> I need to add `intel_iommu=on`
<lucab> shanduur: is FCOS the k8s host or the kubevirt guest?
<shanduur[m]> Host
<lucab> shanduur: and on which platform is it, or how do you provision the FCOS host?
<lucab> shanduur: generally speaking you are looking for https://docs.fedoraproject.org/en-US/fedora-coreos/kernel-args/#_modifying_kernel_arguments_via_ignition but there are there other options too depending on your specific/preferred flow
<shanduur[m]> Generally speaking, I will be migrating my home lab from PVE to FCOS (so bare metal deployment), as most of my workflow is on K8S. I am gathering knowledge about it now, as even I am running mostly containers, I want to add single Windows virtual machine, preferably with GPU passthrough.
jpn has joined #fedora-coreos
bgilbert has quit [Ping timeout: 248 seconds]
ravanelli has joined #fedora-coreos
ravanelli has quit [Ping timeout: 240 seconds]
crobinso has joined #fedora-coreos
ravanelli has joined #fedora-coreos
thomasfedb has joined #fedora-coreos
ravanelli has quit [Ping timeout: 252 seconds]
crobinso has quit [Ping timeout: 240 seconds]
ravanelli has joined #fedora-coreos
<mgrundmann> how long will i be able to build with cosa v.0.13.0?
<mgrundmann> or asked another way are there features in v0.14.0 that are required for building current stable versions?
ravanelli has quit [Ping timeout: 260 seconds]
<dustymabe> ICYMI there is a fedora 36 release party going on now: https://hopin.com/events/fedora-linux-36-release-party/registration
<walters> mgrundmann: Have you considered *deriving* from FCOS rather than doing custom builds? See https://github.com/coreos/coreos-layering-examples
<dustymabe> mgrundmann: probably fine with v0.13.0 - but generally follow latest works best
<dustymabe> we'll be switching over to a Fedora 36 base soon
<mgrundmann> i will just stay on 0.13 as long as i still need the ostree tar
<mgrundmann> i will definetly check if i can do all customization using layering
mheon has joined #fedora-coreos
ravanelli has joined #fedora-coreos
cyberpear has joined #fedora-coreos
nalind has joined #fedora-coreos
plarsen has joined #fedora-coreos
crobinso has joined #fedora-coreos
jcajka has quit [Quit: Leaving]
trikorasolns has joined #fedora-coreos
jlebon has joined #fedora-coreos
nalind has quit [Ping timeout: 240 seconds]
nalind has joined #fedora-coreos
<jlebon> could someone add an /approve to https://github.com/openshift/release/pull/28537 ?
<jlebon> otherwise the openshift cosa tests will keep using f35
<jlebon> dustymabe: thanks! i think i need someone from dptp now
cmagina has joined #fedora-coreos
cmagina has quit [Changing host]
trikorasolns has quit [Remote host closed the connection]
hjst has quit [Quit: Bye.]
hjst has joined #fedora-coreos
paragan has quit [Quit: Leaving]
<jlebon> dustymabe: ahhh nice. your comment rendered only after I added mine (https://github.com/coreos/fedora-coreos-tracker/issues/1175#issuecomment-1126259147)
<jlebon> should we mark them both as offtopic?
<jlebon> marked mine at least
<dustymabe> :)
<nemric> o/
<nemric> hi team :)
bittin has joined #fedora-coreos
bgilbert has joined #fedora-coreos
jpn has quit [Remote host closed the connection]
jpn has joined #fedora-coreos
<dustymabe> coreos-ci seems down - and I can't get to the OCP4 cluster
<dustymabe> i can get to the pipeline.. just FYI ^^
<jlebon> hmm, seems fine here
<dustymabe> ok now it's working
<jlebon> test failed on ext.config.kdump.crash also in rerun
<dustymabe> weird
<jlebon> glitch in the matrix :)
<dustymabe> interesting
jlebon has quit [Quit: leaving]
jpn has quit [Ping timeout: 260 seconds]
jpn has joined #fedora-coreos
jpn has quit [Client Quit]
bagasse has quit [Remote host closed the connection]
mindbender has quit [Ping timeout: 246 seconds]
mheon has quit [Ping timeout: 260 seconds]
nalind has quit [Quit: bye]
Betal has joined #fedora-coreos
mhbauer has joined #fedora-coreos
crobinso has quit [Ping timeout: 240 seconds]
mhbauer has quit [Ping timeout: 252 seconds]