19:02:00 <wilcal> #startmeeting
19:02:00 <Inigo_Montoya> Meeting started Thu May  6 19:02:00 2021 UTC.  The chair is wilcal. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:02:00 <Inigo_Montoya> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:02:13 <wilcal> Hello everyone and welcome to this weeks QA meeting
19:02:24 <MageiaTJ> First sunny day this week. I ought to be out working, but I decided to take a break.
19:02:32 <wilcal> #topic Who's new?
19:02:38 <wilcal> ANyone new here today
19:03:28 <wilcal> Nope
19:03:40 <wilcal> #topic Mageia 7 to 8 using and testing
19:03:52 <wilcal> So how's it going. Seems very quiet
19:04:13 <wilcal> Latest Kernal and vbox updates went through without a hitch
19:05:57 <wilcal> Anything??
19:06:03 <MageiaTJ> I have something to check with the xscreensaver update later this evening, but It'll probably go through OK.
19:06:21 <wilcal> I do have something to post
19:06:32 <benmc_> only issue i have been aware of is system upgrde 7-8, kernel upgrade cannot proceed  due to conflict. i586 system, stays on mga7 kernel
19:06:57 <wilcal> Gracious
19:08:21 <wilcal> I have an issue that I want to post. Feel free to look it over and coment. It's a little lengthly
19:08:38 <wilcal> Here goes
19:08:40 <wilcal> I'm chasing an issue I'm seeing with M8 x86_64 Plasma Vbox Clients. Note that the clients I was seeing the issue in were all created before the final M8 isos were released. Vbox on creating a new client automatically sets the default Virtual Drive size to 20GB. Changing that virtual drive size later to something higher is difficult on already created clients. Not so if you are using real hardware. What happens is that the Vbox client uses up almost all
19:08:41 <wilcal> of the available virtual drive space to the point where the last Kernel update refused to install due to lack of available virtual drive space. The used space was over 16GB leaqving only a couple hundred MB of drive space left. The only way out of this was to create the client from new and start with a 30GB virtual drive. Once re-created the client the used space falls under 10GB and updates are possible. Was there log and tracing applications in M8
19:08:42 <wilcal> Cauldron just before it got released and then taken away at release? Note to self when creating a new Vbox Plasma client set the virtual drive space to 30GB not leaving at the default 20GB.
19:08:56 <wilcal> That's it
19:09:57 <wilcal> The 20GB M8 Plasma Vbox client becomes un-updateable
19:11:13 <benmc_> how does VB behave on other linux systems?
19:11:25 <MageiaTJ> There is a way to increase the size that's fairly easy. I did it a few months ago, but I don't remember how now.
19:11:31 <wilcal> That I can't tell you.
19:11:36 <benmc_> is it a Mageia issue or VB issue?
19:12:11 <MageiaTJ> Something I saw on Youtube that's not the "sanctioned" Vbox way.
19:12:23 <wilcal> Increasing the size of a partition is fairly simple on real hardware but I couldn't find a way that would work on a Vbox Client
19:12:30 <wilcal> That was usig Gparted
19:12:48 <wilcal> But you have to boot from a Gparted bootable iso
19:13:03 <wilcal> not the install your trying ti increae the partitions on
19:14:17 <wilcal> Also if you have an exisiting Vbox vdi file that was created with 30GB of virtual drive space if you create a new client from that it defaults to 20GB and that can't be changed
19:14:27 <wilcal> anyway it's kinda complex
19:15:00 <wilcal> does anyone here know if there were some logging and debugging applications in Cauldron up until the very end then release?
19:15:19 <wilcal> Those may take up a lot of space
19:15:33 <wilcal> I seem to rmember somehing like that years ago
19:16:36 <wilcal> Not a big deal. I just had to re-install the client starting with a 30GB virtual drive
19:17:22 <MageiaTJ> Is this with a fixed-size virtual disk, or dynamically allocated?
19:17:36 <wilcal> dynamically allocated
19:17:38 <MageiaTJ> The procedures are different.
19:17:59 <MageiaTJ> I believe that's the easier of the two.
19:18:12 <wilcal> It was the last set of kernel updates that pushed M8 over the top and ran out of space
19:18:34 <wilcal> M7 was low on space also but did update
19:19:14 <wilcal> It was complaining that it needed about 250MB more space to do the kernel update
19:19:26 <Bequimao> wilcal: You may a 2nd disk. I did it with Virt.manager.
19:19:57 <wilcal> I tried lots of tricks with Virt Mgr but that didn't work.
19:20:13 <Bequimao> *add*
19:21:18 <wilcal> If you do that and give the client anothher 10GB  you can see the unallocated space in the client with Gparted but I tried to but that space in the short partition and Gparted woulndt let me do that
19:21:29 <wilcal> and that because it was a mounted partition
19:22:03 <wilcal> tried add/resizee in Gparted
19:22:06 <MageiaTJ> You can "insert" a gparted iso into your virtual optical drive before you start the client.
19:22:36 <wilcal> That sounds like fun. I'll try that
19:22:58 <MageiaTJ> Do it from "Settings."
19:23:15 <wilcal> Yes make the opticai drive the first boot drive
19:24:00 <wilcal> optical drive being the Gparted iso
19:24:51 <wilcal> I don't think too many people are going to run into this
19:25:17 <wilcal> Note to self all plasma Vbox clients need 30GB virtual drives
19:25:55 <wilcal> Lets move on
19:25:56 <wilcal> #topic Anything else?
19:26:03 <wilcal> Anything else
19:26:43 <wilcal> Nothing?
19:27:02 <wilcal> Quiet week again
19:27:11 <wilcal> So countdown time thanks all for being here
19:27:16 <wilcal> T-5
19:27:18 <MageiaTJ> The Governor of New York thinks the state will be "fully" opened by July 1.
19:28:23 <wilcal> NV Gov Sisolak, a devoute Catholic, gave the NV Brothels the go effecitive Jun1
19:28:45 <wilcal> on that T-4
19:28:58 <wilcal> T-3
19:29:01 <MageiaTJ> Broadway started selling tickets again today.
19:29:06 <wilcal> Kool
19:29:09 <wilcal> T-2
19:29:20 <wilcal> T-1
19:29:23 <wilcal> bye all
19:29:26 <wilcal> #endmeeting