[09:57] <macjl> Hello
[09:57] <macjl> I'm trying to install Unbuntu in LPAR
[09:57] <macjl> But facing problems with VLAN tagging
[09:58] <macjl> The installer don't ask me if I use VLAN, so the network does'nt work...
[09:59] <macjl> Anyone know how to net install ubuntu on s390x arch with VLAN tagging?
[10:07] <xnox> macjl, you have two options
[10:07] <xnox> macjl, return to main menu ("<")
[10:07] <xnox> change debconf priority to medium
[10:07] <xnox> then it should ask you to use vlan, but that may or may not work.
[10:08] <xnox> i typically "go through the motions up to ssh client password setup"
[10:08] <xnox> then return to main menu
[10:08] <xnox> drop to shell
[10:08] <xnox> and bring up vlan network by hand, e.g.
[10:08] <xnox> ip link set dev encc000 up
[10:08] <xnox> ip link add link encc000 name encc000.2654 type vlan id 2654
[10:08] <xnox> ip addr add 10.245.237.7/24 brd 10.245.237.255 dev encc000.2654
[10:08] <xnox> ip link set dev encc000.2654 up
[10:09] <xnox> ip route add default via 10.245.237.1
[10:09] <xnox> echo nameserver 10.245.237.1 >> /etc/resolv.conf
[10:09] <xnox> ..
[10:09] <xnox> adjust as needed.
[10:09] <xnox> you would then have to bring up network by hand again in the installed system, and adjust /etc/network/interfaces
[10:10] <xnox> work is in progress to improve vlan network support. Do let me know your experience with debconf medium priority that does ask for vlan network tag.
[10:13] <macjl> Thans, I'll try!
[10:13] <xnox> macjl, no problem. =)
[11:55] <Bercik> It's good to see people alive on s390* channels :)
[12:18] <xnox> Bercik, yeah =) slowly picking up.
[12:19] <Bercik> I remember idling +/- 9 months on hercules channel. Not even one word :)
[12:19] <xnox> hehe
[12:19] <xnox> honestly i have tried hercules, but did not manage to boot anything in it =(
[12:19] <Bercik> I did
[12:19] <Bercik> but not with ubuntu ;(
[12:20] <Bercik> nor modern distros (RHEL 7, SLES 12).
[12:20] <xnox> yeah, cause ubuntu needs transactional memory and like zEC12 or better cpu
[12:20] <xnox> i don't think hercules has emulation for that
[12:20] <Bercik> I tried newest 4.0
[12:20] <xnox> i wish qemu had system emulation on other platforms, but that's not in for same reasons arm64 foreign emulation is not there
[12:21] <xnox> hm, i did not try 4.0 from github, right?
[12:22] <Bercik> yup,
[12:22] <Bercik> It runs debian 8 with no problems. Same for my rusty z/OS 1.10
[12:23] <xnox> https://github.com/hercules-390/hyperion/issues/39
[12:23] <xnox> we need that for ubuntu
[12:24] <Bercik> Depends on my CPU config. After IPL it ends up with "you need more recent hardware" or Wait State
[12:35] <Bercik> xnox,   --enable-interlocked-access-facility-2=yes|no
[12:35] <Bercik>                           enable/disable Interlocked Access Facility 2
[12:35] <Bercik>                           (default yes)
[12:35] <Bercik> this is mentioned multiple times, when talking about Linux IPL, and this new version seems to has it.
[12:36] <xnox> no idea. i just know that both kernel and glibc use transactional memory on ubuntu (and other modern distros too)
[12:36] <xnox> and that needs transactiona-execution facility
[12:36] <xnox> i don't know what this interlocked access facility is, and/or if transactional memory/execution is implemented using above in hercules
[14:36] <macjl> For infomation, with debconf priority set to medium, I was able to choose a VLAN ID
[14:37] <macjl> But after installation, the configuration was not ste in /etc/network/interfaces
[14:37] <macjl> I had to set it up manually
[14:58] <xnox> macjl, ack. thanks.
[14:58] <xnox> will investigate and will try to fix that up.
[14:59] <xnox> macjl, if you wish you can open a bug report about that with $ ubuntu-bug debian-installer
[14:59] <xnox> or open one on launchpad manually against ubuntu project, debian-installer package, and attach logs from /var/log/installer
[14:59] <xnox> if you can/allowed to share those.
[15:04] <macjl> I'll see if I can
[15:04] <macjl> Now I'm trying to make bonding work with vlan....
[15:08] <xnox> macjl, =))))) it should work, i try to avoid fiddling with things like that, and just defer it to infrastructure team =)
[15:55] <macjl> It worked with VLAN + bonding. I've just moved a VM from IBM KVM to Ubuntu (offline) with no problems :)
[15:57] <macjl> It doesn't seem to work with live migration because of a SELinux problem :
[15:57] <macjl> error: unsupported configuration: Unable to find security driver for model selinux
[16:11] <xnox> macjl, right. in ubuntu we support live migration among our hypervisors (e.g. lxd to lxd, qemu to qemu)
[16:11] <xnox> i don't know if it's possible to move things form z/KVM to Ubuntu live.
[16:12] <xnox> macjl, could you open a bug report about that? because surely we should be able to translate selinux model to apparmor (which is what used to protect qemu on ubuntu) and/or give option to ignore selinux context for migration (sub-optimal, but better than failing outright)
[16:12] <xnox> maybe we can enable selinux in relevant parts of the stack to make migrations work too.
[16:13] <xnox> if you add tag "s390x" to the bug report, I will notice it and can route it appropriately to the right ubuntu teams