VirtualBox VM-- Almost No Disk Space After Installing MX  [Solved]

Message
Author
User avatar
operadude
Posts: 1072
Joined: Tue Nov 05, 2019 12:08 am

VirtualBox VM-- Almost No Disk Space After Installing MX

#1 Post by operadude »

Having trouble when installing VirtualBox-- No matter what size I allocate, I have almost no disk space left after running the MX Installer. Weird. I've never had this problem before. Anyway...

Code: Select all

Snapshot created on: 20231013_1622
System:
  Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 info: plank wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.1_x64
    Libretto October 13 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: H270-HD3 v: N/A serial: <superuser required>
  Mobo: Gigabyte model: H270-HD3-CF v: x.x serial: <superuser required> UEFI: American Megatrends
    v: F5 date: 04/24/2017
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:0080 serial: N/A
    charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake gen: core 7 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
    microcode: 0xF4
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 800 min/max: 800/3900 scaling: driver: intel_pstate governor: powersave
    cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 31199
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: Micro-Star MSI driver: radeon
    v: kernel alternate: amdgpu arch: GCN-1 code: Southern Islands process: TSMC 28nm built: 2011-20
    pcie: gen: 3 speed: 8 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DVI-D-1,VGA-1
    bus-ID: 01:00.0 chip-ID: 1002:6613 class-ID: 0300 temp: 35.0 C
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 model: Samsung built: 2007 res: 1920x1080 hz: 60 dpi: 305
    gamma: 1.2 size: 160x90mm (6.3x3.54") diag: 184mm (7.2") ratio: 16:9 modes: max: 1920x1080
    min: 640x480
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: OLAND ( LLVM 15.0.6 DRM 2.50 6.1.0-10-amd64)
    direct-render: Yes
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
  Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 1002:aab0 class-ID: 0403
  API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:
  Local Storage: total: 8.44 TiB used: 5.73 TiB (67.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 1B2QEXE7 temp: 26.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 model: SATA SSD size: 111.79 GiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37120G size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61K1 scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: CC25 scheme: GPT
  ID-5: /dev/sdd maj-min: 8:48 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750
    scheme: GPT
  ID-6: /dev/sde maj-min: 8:64 vendor: Western Digital model: WD5000AADS-00S9B0 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A01
    scheme: GPT
  ID-7: /dev/sdf maj-min: 8:80 type: USB vendor: Seagate model: Expansion Desk size: 3.64 TiB
    block-size: physical: 4096 B logical: 4096 B type: N/A serial: <filter> rev: 0739 scheme: MBR
  ID-8: /dev/sdl maj-min: 8:176 type: USB model: Storage Device size: 7.42 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: N/A rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-9: /dev/sdm maj-min: 8:192 type: USB model: Storage Device size: 14.84 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: N/A rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-10: /dev/sdn maj-min: 8:208 type: USB model: Storage Device size: 3.69 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: N/A rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-11: /dev/sdo maj-min: 8:224 type: USB model: Mass Storage Device size: 7.4 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-12: /dev/sdp maj-min: 8:240 type: USB vendor: Sabrent model: SABRENT size: 698.64 GiB
    block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0104 scheme: MBR
Partition:
  ID-1: / raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 10.73 GiB (43.9%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 1.6 MiB (0.7%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 9.44 GiB (38.6%) fs: ext4
    dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 32 GiB used: 2.2 MiB (0.0%) priority: -2
    dev: /dev/nvme0n1p10 maj-min: 259:10
Sensors:
  System Temperatures: cpu: 30.0 C mobo: N/A gpu: radeon temp: 35.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2676 libs: 1438 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
    1: deb [arch=amd64] https://repo.skype.com/deb stable main
Info:
  Processes: 283 Uptime: 5h 48m wakeups: 3 Memory: 31.3 GiB used: 4.1 GiB (13.1%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
To clarify: no matter what size I allocate for the VDI (10GB, 20GB), even checking the "pre-allocate size" option, when the machine starts (tried with "Minimal", Xfce & Fluxbox images), I see that I have 12GB or more disk space. Ok, good.

However, when running the installer, and when I choose the whole "disk" (combined root and home), installation completes fine. However, after rebooting, when the installed system starts on Vbox, Thunar shows me that there are only MB of space available (ranging anywhere between 30MB (first try) to 877MB). When I hover over the "file system", it shows that it is taking-up almost all of the disk space.

I tried installing (in Vbox) with the option to use a custom layout, but I can't change the size of the disk space.

I even tried installing the "Minimal" respin (which is what I really want for this VM), allocating something like 8GB for the machine, 16GB of RAM, and the whole Minimal image is only 1GB.

I got the same results: something like 30MB of space left.

I know that the Minimal respin cannot take-up 8GB!

Not sure what's going on!

I have installed VMs with VirtualBox in the past, and never had this issue.

:confused:

User avatar
dolphin_oracle
Developer
Posts: 22733
Joined: Sun Dec 16, 2007 12:17 pm

Re: VirtualBox VM-- Almost No Disk Space After Installing MX

#2 Post by dolphin_oracle »

if you are using the automatic installer, its very likely that much space is being taken up by the swapfile.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/

User avatar
operadude
Posts: 1072
Joined: Tue Nov 05, 2019 12:08 am

Re: VirtualBox VM-- Almost No Disk Space After Installing MX

#3 Post by operadude »

dolphin_oracle wrote: Thu Jan 04, 2024 12:54 pm if you are using the automatic installer, its very likely that much space is being taken up by the swapfile.
Aha!

How can I mitigate that?
--Use a custom install layout?
--Not sure I can do that in a VM

I'll look into it and get back to you.

Thanks D.O. :exclamation:

User avatar
dolphin_oracle
Developer
Posts: 22733
Joined: Sun Dec 16, 2007 12:17 pm

Re: VirtualBox VM-- Almost No Disk Space After Installing MX  [Solved]

#4 Post by dolphin_oracle »

you can do custom partitioning in a vm.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/

User avatar
operadude
Posts: 1072
Joined: Tue Nov 05, 2019 12:08 am

Re: VirtualBox VM-- Almost No Disk Space After Installing MX

#5 Post by operadude »

dolphin_oracle wrote: Thu Jan 04, 2024 1:04 pm you can do custom partitioning in a vm.
OK, will get on it, and let you know!

I tried with one of those installs I mentioned, and it wouldn't let me change the size of root/home.
Not sure why.
Anyway, will continue to try.

Thanks again :exclamation:

User avatar
operadude
Posts: 1072
Joined: Tue Nov 05, 2019 12:08 am

Re: VirtualBox VM-- Almost No Disk Space After Installing MX

#6 Post by operadude »

@dolphin_oracle :number1:

Yes, custom partitioning DOES WORK! :happy:

I will just have to play with the sizes a bit, since I used the minimum 4.4GB for root, but after install only have 197MB left on root, so can't get all of the updates (99 of them). Oh, this is all on the MX Respin "Minimal".

Since the "Minimal" ISO is just about 1GB, I didn't think I would need over 4GB for root, but that's OK, since I have over 20GB to play with on my VM partition.

Thanks for the response, and living large (well, not on the "minimal" install ;) )

As per usual, Loving MX :exclamation:

:thumbsup: :thumbsup: :thumbsup:

User avatar
operadude
Posts: 1072
Joined: Tue Nov 05, 2019 12:08 am

Re: VirtualBox VM-- Almost No Disk Space After Installing MX

#7 Post by operadude »

Re-adjusted partition sizes, and after install have over 3GB for Root.
I left only 2GB for Home, since I'm not planning on keeping many files there.
All is good!

Post Reply

Return to “Software / Configuration”