Has someone tried to install Slackware on MS Hyper-V (Windows 2008 R2)? If so, can you share your experience, were there any special requirements? Thanks for shareing.

I remember trying a few years back, and I can't remember anything specific that caused any problems. Then again, I don't think I attempted to use Slackware as a Virtual Server. I was attempting to figure out Hyper-V. I would say test it out - it probably will work just fine.

I haven't tried Hyper-V but I have tried Linux in Virtual PC 2007. The problem was that the Microsoft Guest Additions only supported SUSE Linux and weren't much use for any other Linux or 2.6 kernels. Hopefully Microsoft has better Linux support for guest operating systems now. If not, you may lose features such as the mouse integration, clipboard integration and automatic screen resizing.

Check out the Guest OS support software provided by the Virtual Machine software. What guest operating systems are fully supported? For example Virtual PC 2007 is great for running Windows 95, 98, ME and earlier. VirtualBox is great for running NT versions of Windows from NT 4.0 through Windows 7. VirtualBox also has great guest support for Linux, including specific packages for some distros and a generic package that works with Slackware.

I just loaded Slackware 14 into a windows server 2012 hyper-v guest. The kernel modules for hyperv loaded automatically. I have what appears to be a fully functional install.

I just finished a Slackware 14.0 install on Win 8 Hyper-V. It's my understanding its very similar if not the same as Win Serv 2012 Hyper-V client. Would you mind telling me if you have a dedicated physical NIC for the Slackware VM? I do not. Instead I have a Virtual Switch bridged to my physical lan of my VM Host machine, but Slackware isn't seeing the NIC when I run an ifconfig. Only sees lo and not eth0.

Forgive my newbness, but could you provide some insight into how your network is setup on the VM in relation to the host machine?

@Seasonal vegetables,
I have the Intel 82579 attached to a virtual switch and it is recognized as eth0 on my system. Run lsmod to see what hv modules are loading.

I did find this too: http://www.linuxquestions.org/questi...on-4175438908/

@poucket I'm not sure I understood your response. I didn't see anything in the search list that was related to the question. Did you find something?

gmartin, I'm sorry that my response was unclear.

I meant that Seasonal Vegetables might find more help in the
virtualization forum, since your first post in this thread was made last November.
I haven't used Hyper-V, and did not know what to say about it. It seemed to me
that if a NIC did not appear in the output of ifconfig after installing the guest then
the answer may have more to do with Hyper-V than Slackware, but that could be wrong.
I'd be interested in any additional help you could provide.

My Linux students are also following a course in Windows administration, and they're double-booting Windows 2008 server and Slackware 14.0. I don't know any details about MS Hyper-V, but recently, they've all proudly shown me their Slackware installs in Hyper-V. So I guess it must be more or less easily doable.

1 members found this post helpful.

When I installed qemu on Slackware 13.37 I wanted to test an image of FreeBSD 8.2 that I had
made. The image booted and the VM worked well, but I did not think I had a network connection.
I tried shutting down and rebooting with many different qemu command lines. The NIC did not
work for me. I might have given up if I had not seen Alien's tutorial.
I was using ping to test the network connection, and the ICMP packets were getting nowhere.

To add some clarity to my response - I have Slackware 14.0 installed under Hyper-V with the 3.2.29 kernel and eth0 is available and working on my system. I know the Hyper-V modules were compiled in from 3.2.27 staging during Slackware 14.0/rc2. If you are running earlier than that, you may need to compile your own kernel or upgrade to a newer one.

Good idea - thanks

Any one getting this message on boot after installation?
"Kernel panic – not syncing: VFS: Unable to mout root fs on unkown-block"

For those who have difficulties with Slackware Linux 14.1's post installation on hyper-v and after the system perform the first boot and screen hangs at the following message "Kernel panic – not syncing: VFS: Unable to mout root fs on unkown-block". I made a step by step guide on how to fix this:
http://egoncalves.com.br/slackware/i...em-windows-10/

I hope I have contributed

1 members found this post helpful.