Hello, Is it the Kernel who makes problems for Ubuntu 20.05 LTS servers, ive installed them 30-40 times. But at this new company I get /etc/network/somethng.yaml as network file ifconfig looks like esp50, no DHCP so I can see rest of my ip adresses. Ip up or ip add dont work.
This happened I think when I use the new hosting company of my new dedicated servers rescue system cause it boot up with Debian kernel, with the wrong commands in the grub.cfg I found it online that it was going to be change along with Debian to ubuntu and they have a list of distres old but they have 20.04 its but all is netinstallers. So I dont think when I run that it get rids of the .yaml netwrork system or kernel. I need to run regular Netplan with eth0 eth0:1 eth0:3 and so on and with DHCP like ive done now for 10 years. So, do any of you know what does this ? Is it the boot up of Debians kernel and grub that is the issue or is it the kernel itself. And thi kernek you talk about now, does it support the regular Netplan eth0, eth0:1 with DHCP and without that .YAML file, I like to have t like Ive lve always had it Sorry, my question my sound stupid to you profesionals but im learning and learning each day. Not much I can do than to learn! My server has been down for over a month now because I got convid19 while being in for testing of my terminal liver disease. Thought I would be safe in the hospital but no. So no emails for my coworkers, family and no website for all my customers so I need to ge this up snd running. Thank you! P.s. Whch kernel can the Ubuntu 20.04.1 LTS handle at the moment, which version, I dont care if its early stage as long as it works, supports all mu needs like the network (Netplan) and so on. And where I can find this version for download. All regards, David > 14. sep. 2020 kl. 11:45 skrev Christian Ehrhardt > <1895...@bugs.launchpad.net>: > > Hi Woodrow, > thanks for your report - you made me think, but I think this isn't valid to > add to Focal. > Let me outline why and please don't feel rejected but discuss if you disagree. > > > First of all I need to stop expectations a bit "... need to backport newer > usptream (5.0 based) to focal ..." => No, that won't happen as it would > violate [1] SRU Policy > But OTOH you can get the newer qemu (and others) backportes outside of the > main archive as part of the Ubuntu Cloud Archive [2] > > > Furthermore I picked up the fix you mean in 1:5.0-5ubuntu3 but cross arch > execution of arm required more and was already brought up in bug 1890881 (and > handled for groovy there). Unfortunately the changes eventually required for > it no more qualify for an SRU [1] as the cross arch execution also isn't a > very common use case and the regression risk would be high. > > Therefore while I agree to the issue existing in Focal, I think due to: > a) a fix being available in Groovy > b) follow on fixes turned out to be needed for many sub-usecases and non > SRUable > c) qemu backports of Groovy to Focal will be availble via cloud archive > > You might say that (c) is complex, which is true - but the use case > brought up here is developer centric as well which are smart and easily > able to run with a supported PPA on top. > > > If you think there really is a major gain in just backporting this single fix > without the others that at the same time can't be done by just upgrading or > using the UCA please outline the case and I'll reconsider an SRU for it (if > it applies without a swarm of dependent commits to qemu 4.2). > > [1]: https://wiki.ubuntu.com/StableReleaseUpdates > [2]: https://wiki.ubuntu.com/OpenStack/CloudArchive > > ** Also affects: qemu (Ubuntu Focal) > Importance: Undecided > Status: New > > ** Changed in: qemu (Ubuntu Focal) > Status: New => Won't Fix > > ** Changed in: qemu (Ubuntu) > Status: New => Fix Released > > -- > You received this bug notification because you are subscribed to Focal. > Matching subscriptions: i...@lie.as > https://bugs.launchpad.net/bugs/1895456 > > Title: > [Focal] qemu can't support semtimedop syscall > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1895456/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895456 Title: [Focal] qemu can't support semtimedop syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1895456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
