Posts by cosmos

  • LE 12.0 added lvm2, luks (dm-crypt, veracrypt), mdraid, ext4 encryption

    No worries buddy!

    Your nightly runs just fine (the LE12 does not run due to the kernel version, whereas LE13 nightly also runs just fine). So there's no pressure really :)

    It's just strange the way virtio-lan works with the kernel; it does not "present" its features (unless it's a dummy driver). Same behaviour in LE13 nightly as well (see also Does the STANDARD LE (not the virtualized image) support the virtio devices (especially virtio net)? )

    And thank you for your build <3

  • Does the STANDARD LE (not the virtualized image) support the virtio devices (especially virtio net)?

    Adding output of ethtool corresponding to the virtio-net provided card:

    From the looks of it, the driver is correctly identified as virtio_net. For some reason though, there is a lot of information missing (like duplex or any wake-on-lan capabilities). IIRC, other VMs get this information just fine.

    Could it be a kernel build issue?

  • LE 12.0 added lvm2, luks (dm-crypt, veracrypt), mdraid, ext4 encryption

    Do the N150 builds include the virtio* devices (net/balloon etc)?

    I have network access in a VM with your latest generic image, but trying to set wake on lan on eth0 throws an error:

    I don;t especially like the unknown speed/duplex etc above... Also no reference to the virtio-net driver used, see

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

  • Does the STANDARD LE (not the virtualized image) support the virtio devices (especially virtio net)?

    I'm tinkering with sky42 's special image for Intel N150-based rigs, as a virtualized proxmox instance.

    The VM has internet access just fine, but when I'm yrying to enable WOL I receive an error.

    FYI, dmesg output:

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Regardless of the image I'm currently using, any idea if the standard image LE12 image includes virtio* devices?

    EDIT: Yes it does, see post #2.

    Addendum: the latest official LE12 nightly produces a black screen, LE works though (can SSH):

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    From kodi.log:

  • Howto: LE 12 as a Proxmox VM with GPU pass-through on Intel N150

    This is a work-in-progress thread, I'll try to document what works and what doesn't.

    Goal:

    I have a GMKtec G3 plus mini pc, with an Intel N150 CPU. I wanted to run Proxmox on it to host my home VMs/containers. The most crucial role that the system was bought for was serving as my bedroom LibreELEC to drive my TV.

    Intended audience:

    You should probably feel at home with the Proxmox Virtualization Environment (PVE). It's an excellent hypervisor with a very friendly community.

    Initial setup:

    Make sure that on the system UEFI is enabled as well as all virtualization options (Intel VT, VT-d, IO-SRV if present).

    I will not cover the Proxmox initial installation procedure. I followed the defaults and that was it.

    You'll need a copy of a specially created LE build by sky42, see RE: LE 12.0 added lvm2, luks (dm-crypt, veracrypt), mdraid, ext4 encryption (NOTE: As of July 7th, LE12 nightly does not run with the N150 GPU (prolly due to the kernel used). OTOH, LE13 nightly runs just fine, but I selected sky42 's build since all my addons are basically for LE12 (and they work flawlessly).

    From the link, download the img.gz version, and write it to a thumb drive using the LibreELEC USB Creator application.

    Create a VM say libreelec mostly with with the default settings. I configured it for 4 vCPUs, 4Gb of RAM and a 32 vHDD. Select the cpu type to be host. Do not change the GPU type. BIOS should be (by default) SeaBIOS, which is ok.

    Connect the thumb-drive to the system and from within proxmox add it as USB device, using pass-through. Boot from that and just do a LibreELEC install. Let it reboot after install, it will be stuck in the LE logo screen, that's ok. Power it down.

    The actual stuff:

    Now comes the hard part, to pass through the graphics adapter from proxmox to the LE VM. First add some modules to /etc/modules, so the file looks like this (see [1]):

    Code
    # /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
intelvfio
vfio_iommu_type1
vfio_pci

    Immediately afterwards run:

    Code
    update-initramfs -u -k all

    The kernel should also be started with an iommu=pt option (see also [1], plus how to do it in [2]). Basically, edit /etc/default/grub and
    set variable GRUB_CMDLINE_LINUX_DEFAULT to be "quiet iommu=pt" instead of "quiet".
    Save and do a:

    Code
    grub-update

    Reboot.

    Now you'll have to locate which is the PCI id of your graphics card. You do that by running a (sample output included):

    Code
    root@pve:~# lspci -nnv |grep -i vga
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-N [Intel Graphics] [8086:46d4] (prog-if 00 [VGA controller])

    So the id is the one ending in 00:02.0. Now go to the LE VM configuration and add a PCI device. Select Raw device and from the pull down menu select the device ending in the code corresponding to your VGA. Check the Primary GPU box. Do not touch anything else!

    At this point, being optimists we'll expect that everything will work, so this is the type to connect a USB keyboard to the box (if you have disconnected it before) and pass through the USB device that corresponds to your keyboard (Add USB device -> Use USB Vendor/Device ID).

    Start your VM. If everything went fine, the console display of proxmox will be replaced with the librelec boot screen and, finally, with the LE configuration wizard.

    For the record this is how my vm.conf file looks like:

    Final thoughts:

    As this is WIP, I have not tested audio (currently connected to a computer monitor with no audio, but expect that it will work over HDMI). If not, the guide will be modified to reflect any changes.

    Additionally, I do want to have some smart hibernation of the VM. If I find anything, I'll update the howto as well.


    References:

    [1]: Proxmox PCI(e) Passthrough

    [2]: Proxmox Editing the Kernel Commandline

  • [x86-64] Running LE as a VM in proxmox?

    I've managed to pass-through the N150 GPU on my GMKtec G3 plus successfully, so Kodi is displayed to my monitor!

    The process had some obstacles, e.g. stable 12.0.2 was stuck after install, I was trying to use a VM display adapter instead of the passed-through etc.

    Guide will follow.

  • [x86-64] Running LE as a VM in proxmox?

    Glad to hear that!

    Basically I do not have a home lab, even though I do have a very old NAS, APs and a multitude of systems. I never had an always on system with low wattage and horsepower to spare. That's why I was thinking virtualizing the LE instance. I'm not really sure whether I'll follow the VM route TBH though, perhaps I'll follow a minimal energy-footprint approach instead. But atm I'm considering all options ;)

    One question: was hypervisor overhead significant in your case? That is, was the host (proxmox perhaps) load significant when idle and on playback?

  • [x86-64] Running LE as a VM in proxmox?

    chewitt thanks for the info. I did recall seeing back at the time that virtualized environment (full or para) were not supported, that's why I've abstained. Been using PVE and ESXi at work for years now, but never using pass-through, albeit from the occasional USB drive.

    Never used docker and I'm tempted to do so, but I think that it would be better to go full VM to pass through the entire GPU to LE.

    Still, once more thank you buddy for addressing my questions all these years :)

    Grasshopper thanks! I've seen a couple of posts earlier, plus some written in the proxmox forum. For example: https://forum.proxmox.com/threads/igpu-p…ics-530.138810/

  • Feature request: Allow for manual IPv6 DNS

    The current IPv6 connection configuration allows for full auto settings or fully manual.

    It might be helpful if one could allow manual config of IP/router/prefix, but provide the user with the option of specifying the DNS servers to use, for anti-blocking reasons.

    A very low priority request, hope it's worthwhile and doable, considering your limited time 🙂

  • [x86-64] Waking up an Intel-based PC plus IR wisdom needed

    Got an odroid C2 that will be replaced with a mini PC (a gmktek N150 El cheapo build). Also got an IR Creative remote that used to operate my always on C2.

    My TV is solely for LE use. Whenever I pressed something on the remote, it happily turned on the TV.

    The Intel build has a fan and I was wondering:

    1) would/could you recommend a cheap (say AliExpress) USB IR adapter that would play happily with the box?

    2) which way would be best to "hibernate" the device and have it start up with the minimum number of key presses? I know yatse offers a wake on lan function, but I'm wondering if there's something faster/less clumsy.

    TIA for any info provided.

  • [Odroid-C2] H264 Playback

    This is baffling to say the least. And apologies again for jumping OT, but I really needed the feedback of the OP in the other thread, since he is in the same boat and might be able to confirm (or not) my own experiences.

    It's funny: I honestly can't recall any issues at all on LE11 with H264 playback. Something has definitely changed, but from what you're saying it seems hard to track and, judging from the size of C2 installations, IMO not worth the hussle.

    But again, thank you for taking the time to address my issues :)