WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: CorePure64 v17 networking issues  (Read 653 times)

Offline tzx17077

  • Newbie
  • *
  • Posts: 6
CorePure64 v17 networking issues
« on: March 02, 2026, 05:10:18 PM »
Hi all,

I am running TinyCore guest VMs in different hypervisors, such as VMW, Virtualbox, Hyper-V.
All of those use the 64bit port w/o graphical desktop (CorePure64).
With the latest version I face issues with my virtual network switches for Hyper-V supervisor: TinyCore does not detect them as network cards and thus refuses to go „online“.
VMWare and Virtualbox on the other hand work fine.

Anyone else facing similiar issues with Hyper-V? Does the kernel lack the capability to support Hyper-V networking? It so, why was this not the case with the previous versions?

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12645
Re: CorePure64 v17 networking issues
« Reply #1 on: March 02, 2026, 08:16:38 PM »
Hi tzx17077
I just took a look at the TC16 and 17 x86_64 config files and noticed a
bunch of  HYPERV  options visible in TC16 but missing in TC17.

This one stood out. Does this look like what's missing:
http://tinycorelinux.net/16.x/x86_64/release/src/kernel/config-6.12.11-tinycore64
Code: [Select]
#
# Microsoft Hyper-V guest support
#
CONFIG_HYPERV=m
# CONFIG_HYPERV_VTL_MODE is not set
CONFIG_HYPERV_TIMER=y
CONFIG_HYPERV_UTILS=m
CONFIG_HYPERV_BALLOON=m
# end of Microsoft Hyper-V guest support

http://tinycorelinux.net/17.x/x86_64/release/src/kernel/config-6.18.2-tinycore64
Code: [Select]
#
# Microsoft Hyper-V guest support
#
# CONFIG_HYPERV is not set
# end of Microsoft Hyper-V guest support

Here are all of the  HYPERV  entries for both config files.
TC16:
Code: [Select]
tc@E310:~/Desktop$ grep HYPERV config-6.12.11-tinycore64
CONFIG_HYPERVISOR_GUEST=y
# CONFIG_KVM_HYPERV is not set
CONFIG_HYPERV_VSOCKETS=m
CONFIG_PCI_HYPERV=m
CONFIG_PCI_HYPERV_INTERFACE=m
CONFIG_SYS_HYPERVISOR=y
CONFIG_HYPERV_STORAGE=m
CONFIG_HYPERV_NET=m
CONFIG_HYPERV_KEYBOARD=m
# CONFIG_DRM_HYPERV is not set
CONFIG_FB_HYPERV=m
CONFIG_HID_HYPERV_MOUSE=m
CONFIG_HYPERV=m
# CONFIG_HYPERV_VTL_MODE is not set
CONFIG_HYPERV_TIMER=y
CONFIG_HYPERV_UTILS=m
CONFIG_HYPERV_BALLOON=m
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_HYPERV_IOMMU=y
# CONFIG_HYPERV_TESTING is not set

TC17:
Code: [Select]
tc@E310:~/Desktop$ grep HYPERV config-6.18.2-tinycore64
CONFIG_HYPERVISOR_GUEST=y
# CONFIG_KVM_HYPERV is not set
CONFIG_SYS_HYPERVISOR=y
# CONFIG_HYPERV is not set
CONFIG_XEN_SYS_HYPERVISOR=y

Offline bdesro

  • Newbie
  • *
  • Posts: 2
HyperV Synthetic NIC Driver/Compatibility
« Reply #2 on: March 03, 2026, 12:53:15 PM »
Tinycore wont recognize HyperV synthetic NIC and is apparently missing modules to recognize HyperV synthetic NICs. we highly use TCL has a router but being only able to use legacy NIC is quite problematic.

Any help or suggestion to easily manage HyperV NIC without recompiling the kernel constantly would be appreciated :)

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12645
Re: CorePure64 v17 networking issues
« Reply #3 on: March 03, 2026, 01:04:57 PM »
Hi bdesro
Welcome to the forum.

I merged your topic with this one because they appear to be related.

Offline bdesro

  • Newbie
  • *
  • Posts: 2
Re: CorePure64 v17 networking issues
« Reply #4 on: March 03, 2026, 02:15:12 PM »
Hi, I too am facing the same issue. it seems that only legacy HyperV adapter are recognized because they dont require any drivers from the OS perspective. I tried with both version 16 and 17 and they both didnt have the proper kernel module for HyperV nor the packages available for installation.... I'm trying to figure a proper alternative to recompiling the kernel because legacy NIC in hyperV are limited to 100mbps....

Offline tzx17077

  • Newbie
  • *
  • Posts: 6
Re: CorePure64 v17 networking issues
« Reply #5 on: March 03, 2026, 04:04:11 PM »
So can anyone recompile kernel with all Hyper-V modules? If not, where can I find instructions on how to do it myself and compile a custom kernel?

Offline CNK

  • Wiki Author
  • Sr. Member
  • *****
  • Posts: 425
Re: CorePure64 v17 networking issues
« Reply #6 on: March 03, 2026, 09:26:15 PM »
There are instructions for building a custom kernel on the Wiki.

Offline tzx17077

  • Newbie
  • *
  • Posts: 6
Re: CorePure64 v17 networking issues
« Reply #7 on: March 04, 2026, 03:21:22 PM »
I keep getting errors when following the steps mentioned inside the wiki. Can someone build a custom kernel with all Hyper-V configuration settings enabled (or at least set to m).

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 15531
Re: CorePure64 v17 networking issues
« Reply #8 on: March 04, 2026, 04:25:30 PM »
It would help if you could show the steps you took and the errors you got

Offline tzx17077

  • Newbie
  • *
  • Posts: 6
Re: CorePure64 v17 networking issues
« Reply #9 on: March 15, 2026, 05:10:44 AM »
Hello Juanito,

would you be so nice and share with us a new kernel with all HyperV modules enabled?
I am not that experienced in building a custom kernel and it would definitely help more people besides me.

Thanks,
Christian

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 15531
Re: CorePure64 v17 networking issues
« Reply #10 on: March 15, 2026, 07:15:24 AM »
It's not that difficult - maybe you could give it a go  :)

Code: [Select]
tce-load -i compiletc ncursesw-dev elfutils-dev perl5 bc
wget http://tinycorelinux.net/17.x/x86_64/release/src/kernel/linux-6.18.2-patched.tar.xz
wget http://tinycorelinux.net/17.x/x86_64/release/src/kernel/config-6.18.2-tinycore64
tar xf linux-6.18.2-patched.tar.xz
cd linux-6.18.2
make mrproper
cp ../config-6.18.2-tinycore64 .config
make oldconfig
make menuconfig [set the HyperV modules you require to enabled ("m")]
make bzImage
make modules

Once done you would need to boot from the bzImage produced and copy the new HyperV modules and make an extension of them.
« Last Edit: March 15, 2026, 07:41:53 AM by Juanito »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 15531
Re: CorePure64 v17 networking issues
« Reply #11 on: March 16, 2026, 05:53:03 AM »
I gave it a go, see: http://tinycorelinux.net/17.x/x86_64/tcz/src/hypervisor/

Boot bzImage rather than vmlinuz64 and load hypervisor-6.18.2-tinycore64.tcz

This is not tested and might not work..

Code: [Select]
grep HYPERV /usr/src/linux-6.18.2/.config
CONFIG_HYPERVISOR_GUEST=y
# CONFIG_KVM_HYPERV is not set
CONFIG_HYPERV_VSOCKETS=m
CONFIG_PCI_HYPERV=m
CONFIG_PCI_HYPERV_INTERFACE=m
CONFIG_SYS_HYPERVISOR=y
CONFIG_HYPERV_STORAGE=m
CONFIG_HYPERV_NET=m
CONFIG_HYPERV_KEYBOARD=m
# CONFIG_DRM_HYPERV is not set
CONFIG_FB_HYPERV=m
CONFIG_HID_HYPERV_MOUSE=m
CONFIG_HYPERV=y
# CONFIG_HYPERV_VTL_MODE is not set
CONFIG_HYPERV_TIMER=y
CONFIG_HYPERV_UTILS=m
CONFIG_HYPERV_BALLOON=m
CONFIG_HYPERV_VMBUS=m
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_HYPERV_IOMMU=y
# CONFIG_HYPERV_TESTING is not set

Offline neonix

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 583
Re: CorePure64 v17 networking issues
« Reply #12 on: March 16, 2026, 04:35:57 PM »
I tried microcore and tinycore 17.x86_64 run in qemu-system-x86_64 and network doesn't works. I tried 5 times with pendrive or iso file. I also noticed that udev shows weird errors.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 15531
Re: CorePure64 v17 networking issues
« Reply #13 on: March 17, 2026, 07:05:17 AM »
I just tried this:
Code: [Select]
sudo modprobe kvm-intel
qemu-img create -f qcow2 vdisk.img 2G
Formatting 'vdisk.img', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=2147483648 lazy_refcounts=off refcount_bits=16
qemu-system-x86_64 -enable-kvm -hda vdisk.img -m 2G -cdrom /home/tc/Downloads/*.iso -boot d

..and from inside the vm "wget repo.tinycorelinux.net/17.x/x86_64/release/CorePure64-17.0.iso" works.

Offline neonix

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 583
Re: CorePure64 v17 networking issues
« Reply #14 on: March 17, 2026, 11:59:42 AM »
I don't tried with kvm acceleration becouse when I install qemu in TC17.x86-64 the default extension is kvm-6.1.2-tinycore.tcz not kvm-6.1.2-tinycore64.tcz.

I recommend remove kvm-6.1.2-tinycore.tcz from qemu.tcz.dep file in TC17.x86-64.