He/Him. Formerly sgibson5150@kbin.social.

Alt account: sgibson5150@lemmy.dbzer0.com

  • 2 posts
  • 12 comments
Joined 2 years ago
Cake day: March 7th, 2024
  • sgibson5150@slrpnk.nettoLinux@programming.dev•virtio-win question
    2 years

    Agreed on your assessment. I’m beginning to suspect I did all the Linux stuff right but screwed up on the Windows side. Copying over a new vhdx right now. ⏳

    No grub involved in this scenario. Machine being virtualized is Windows only.

  • sgibson5150@slrpnk.nettoLinux@programming.dev•virtio-win question
    2 years

    Ty for response! Error is BdsDxe: failed to load Boot0001 etc. I do have TPM hardware on the host. See pic below.

    Good suggestion on repair. Had to do that one time when virtualizing a Win8.1 box back in the day, though I recall I at least got a Windows logo at boot on that occasion.

Linux@programming.devbysgibson5150@slrpnk.net
2 years

virtio-win question

Final edit: I got all the Linux stuff right but made a dumb mistake generating the image on the Windows side. Watching the VM boot right now. Thanks to all for your support!

Contemplating Fedora Kinoite for work daily driver. Need to prove that I can virtualize an existing physical Windows 11 machine. Using Bazzite on a personal laptop as a host test bed.

Test host seems to be set up correctly. I layered the packages in the virtualization group, layered virtio-win (from downloaded rpm package), added my user to the libvert group, and enabled libvirtd. After a reboot or two, I can connect with the Virtual Machine Manager and define my VM.

On physical machine I used Disk2vhd to generate a vhdx. Moved that file to the test host and converted to qcow2. Copied disk image to /var/lib/libvert/images and added it as my drive image when I defined the VM.

VM starts but will not boot. Stupid question: Should I have installed virt-win-gt-x64.msi from the virtio-win ISO on the source Windows install before I created the vhdx?

Edit: Since I posted, I installed a Debian guest from scratch in this environment and it runs like a champ. 👍

4
    Linux@programming.devbysgibson5150@slrpnk.net
    2 years

    Rootless docker breaks Hyper-V dynamic memory

    Guest OS is Debian 12.7, no desktop environment. VM was created with Powershell so that I could specify the Configuration Version (9.0). This VM is intended to be migrated to a Server 2019 host.

    I have a series of checkpoints so I can observe the behavior at each. After installing (rootfull) docker, VM memory demand idles around 526 MB. Starting a session and running top doesn’t change the memory demand at all.

    When I start with the checkpoint where I’ve made docker rootless, memory demand idles slightly higher before login, maybe 870 MB. When I start a session and run top, though, memory demand skyrockets and assigned memory quickly reaches max dynamic memory, 4096 MB. The output in top barely changes. For giggles I bumped the max to 6 GB and demand still continued to rise.

    There are no containers defined in either case. Any ideas about what I’m seeing?

    0
      • sgibson5150@slrpnk.nettoProgrammer Humor@programming.dev•rm -rf /
        2 years

        Hey, sometimes you need to hose out the cruft.

        Why yes, I do maintain a legacy application that still stores user files in Program Files in blatent violation of 15 years of Windows best practices and continues to be done contrary to my repeated advice, why do you ask?