NS with KVM and libvirt or proxmox?


Gehe ich recht, dass du Deutschprachig bist? Ralph entspricht eher deutsche schreibweise.
Deutsch, falls es für dich einfacher geht ist ohne weiteres möglich.

Right, you can take a template container (There’s plenty available) for a standard Centos 7 container
That takes a few secs (!)
Fire that up and install NethServer according to your requirements. There’s a howto on that on their site…
Use Containers for NethServer App or direct Apps on any Linux of your choice. I’m running a FOG-Project based Imaging solution on a base Centos Container.

The MAIN NethServer installation, the one with the AD, I’d definetely put that in a KVM based box, due to the fact that the AD itself is a further virtualisation in a container inside NethServer. As a KVM, the AD works very well.

Depending on the anticipated load… It’s easier to troubleshoot if seperated, and users can take it easier if just One service is down, not the whole network!

ProxMox doesn’t really support software raid, but if you keep your VMs on a NAS, that is in itself redundant (raided) then that’s ok. Software RAID does work on Proxmox, your mileage may very in setting it up…
I wouldn’t bother. Hook up the second disk from time to time and make a dd image to the second disk, hooked up via USB…

The NAS is the primary focal point for your VMs. They “live” and exist in there. So obviously you NEED somewhere else to keep Backups of these important files - a Backup on the same physical Disk is not really reasonable. If that disk crashes, your data and backups are gone…

So you need a second NAS. Get a bit a better one and use the present NAS as Backup. Later. For now you can use the NAS for both, but make saves manually on an external disk or whatever!

ProxMox out of the displays two containers, which are basically folders on the local disk. These can be used for anything, but you get no redundancy or Live migration. You CAN use Live Backup to migrate these VMs or Containers any time in the future, as soon as your Storage (NAS) suits your plans.
Here are the Storage options in ProxMox. The two lowest, with local in the name, are just that, local storage.
This is what you can add on for storage:

Proxmox specifies 5 different items which can be in a storage, here’s my setup:

Hope that clarifies things!


Ja, bin ich. Wobei “ph” eher die amerikanische Schreibweise ist. :wink: Wenn es die anderen nicht nervt, lass uns gern auf Deutsch weitermachen.

Die ganze Sache mit dem NAS hab ich schon vorher nicht verstanden. Die “Icy Box” macht RAID selbst, die Daten werden dort also redundant gespeichert. Außerdem ist noch eine weitere USB-Platte angeschlossen, die bisher für nightly Backups verwendet wird (mit “backuppc” auf dem Server).
Software-Raid läuft wohl nur auf dem Server, wobei das Board nötigenfalls auch Hardware-Raid kann.
md0 ist die Boot- und md1 die Root-Partition.

Die LVM-Volume Group sieht aktuell so aus:
PV VG Fmt Attr PSize PFree
/dev/md2 vg lvm2 a-- 582,17g 32,33g
/dev/pvusb vg lvm2 a-- 1,82t 30,00g
Pvusb ist die Icy Box.
So habe ich schon vor etlichen Jahren mal mit Xen angefangen, und der Umstieg auf KVM war problemlos möglich.
Am liebsten wäre mir, wenn ich Proxmox so installieren könnte, dass nur md0 und md1 neu formatiert würden für das Betriebssystem und den Hypervisor, und das LVM-Sytem bliebe, wie es ist - wenn nötig umgewandelt in LVM Thin.
Will sagen, ich verstehe die Dinge am besten, wenn sie so nah wie möglich am Bisherigen bleiben. Sonst säge ich womöglich den Ast ab, auf dem ich sitze, und die Installation dauert keine 20 Minuten, sondern eine Woche. Versuch es mal von dem Ende her zu denken.
Aber jedenfalls herzlichen Dank für die viele Mühe, die du dir machst!


Kannst du durchaus so machen, wobei ich selber noch nie mit md (nutze ich sonst überall) oder software raid gearbeitet hab im Bereich ProxMox. LVM kannst du quasi direkt einbinden, wie andere HW auch. Gewisse Freaks haben sogar die Grafikkarte mit Passthru weitergegeben.

Lass mal den NAS weg, und eine der MD disks. So kannst du gefahrlos testen!
Oder noch besser: eine andere Platte zum testen und herumspielen anhängen, der Software RAID mal komplett abgehängt.

ProxMox installlieren, Look & Feel drangewöhnen, also z.B. eine Windows Client oder Ubuntu zum testen installieren, und dann erst deinen NAS anstöpseln und einbinden. Ubuntu z.B. ist aus den Templates (Er füllt diese selber nach ein wenig Zeit) innert Minuten installiert. Eher 2-3 als 5!

ProxMox ist sehr flexible und kann mit dir mitwachsen, auch nach Bedarf. Nur der Cluster: Der sollte in Stein gemeisselt sein! Also als Ganzes sehr stabil sein, auch wenn mal ein Knoten im Cluster ausfällt…

So ist - für dich - ausser der GUI - fast alles beim alten, sogar die NAS Anbindung verbleibt.

Viel Spass!

Nerven ist sicher der falsche Ausdruck, aber viele verstehen es halt auf Deutsch nicht und können sich in keiner Art beteiligen, das ist eher das Problem. Ich tue mir selber oft schwer mit Englisch, aber jeder Beitrag kann für andere interessant sein, sofern sie ihn verstehen können, darum glaube ich, dass es besser ist, bei Englisch zu bleiben, es gibt ja einen deutschen Chat, wo man sich zu diversen Themen auf Deutsch austauschen kann:





You’re quite right here. In future we’ll use the german plattform for such stuff. I just had a feeling using german might assist in confidence to try out ProxMox.

Did you get to try it out yet?


In this case, it is fully ok. :smiley:

I fetched a hard disk today to setup an old pc as NAS box for Proxmox and will hopefully migrate my ESXi today/tonight. Backups are already made. I’ll give you a report asap…

Like I mentionned above - Proxmox will work quite well stand alone for starters. Add in your NAS as it gets ready!

You anyway can’t integrate it during setup, only After setup, reboot and using the web interface!

So do things side by side, while the cd installs on NAS-PC and Proxmox, enjoy a nice Wiener Melange or whatever beverage of your preference…

I still have two things running on my home VM ESXi, I’ll also attempt to migrate them later this evening or night. They’re not important. One is my last Win98SE and the other is OpenBSD - might go for a reinstallation rather than migration, seeing that OpenBSD also works with VirtIO.

Enjoy it!


1 Like

I still have an old Windows NT 4.0 VM. Do you think I can migrate it to Proxmox? Would be just for fun…

Windows I’ve done until Win2000 (Server and Workstation). I also have an archived WinNT40 Workstation running in ESXi.

VirtIO isn’t available, those only support back to Win2000.


Things look good, those confirmations are for older KVM versions. You can use Intel e1000 for NT, finden the right driver may be an issue (There were so many sub-versions of an Intel EE Pro 1000 Network Card).
Grafik can be cirrus based according to this:

Can’t use my old NT4 any more, the disk containing that image died a while ago. Remember those clicking noises, in the days before ssds? ;-(

Maybe later in the forum…


1 Like


I am using proxmox, it does support zfs and snapshots.
But i had to manually do a lot of stuff to get it working how i wanted.
Any idea if zfs would be supported soon on Nethserver ?

You could try to run the VM disk image from memory tmpfs :slight_smile:
Just as a test of course and see how fast it could get
I think it would be superfast


The fastest I have done: WinNT with the whole C-Disk in a RAM-Disk on my Mac.
Never seen NT boot up soooo fast!



Not what I want, especially since updates work so well in ProxMox. On a major update, a hand done ZFS is bound to screw up.


I dont think we should go offtopic, but you could message me about what you think it could go wrong ?


The thing is, ProxMox is sooo stable, and so are their updates. So I get into the habit of updating the hosts…
As long as everything is “out of the box”, nothing will screw up, ProxMox handles even major upgrades well.
However, I’m quite aware I might have to redo the UPS (NUT) configuration, also the SNMP stuff I made to allow remote monitoring.

Easy as it is, I don’t want even the Zabbix Agent running in my ProxMox. As close to the standard as possible.

There a quite a few things which can screw up, like a change in basic function of a ZFS library…
As long as you’ve got backups, and basically know what you’re doing, things should go fine.
But don’t give Murphy a chance to screw things up.

A good friend of mine asked me three years ago to help him set up a Windows2012 server, with SQL-Server and Exchange 2010. I stipulated that at least every three Months he should shut down the VMs and copy the Image over to the NAS (All was running on the Server, NAS only for Backup). That besides the usual Windows / Exchange Backups containing current data.

He never did that, the last image “off” the server is from December 2014…
And last week the whole thing crashed, Windows would boot up VERY slowly, the AD seemed f*cked and Exchange wouldn’t start up.
Even worse, despite a reboot of the VMWare ESXi Host, he couldn’t copy the files over to the NAS…
It’s running - for now - but we can’t make a save or backup of that sucker!
So we’ve got the data, but no system which can use that other than what’s running now on the ESXi.
–> We’ll know more on Monday… ;-(

That’s also the reason this particular client will be moving to ProxMox, so that doesn’t happen again.

My 2 cents…


I installed Proxmox now and I am impressed. I used my Nethserver VMWare VM as NAS, installed Proxmox on an old PC and it’s working like a charm. I online-cloned a Nethserver VM from my Nethserver NAS VM to local PVE machine. I just shared one NFS share for all items now for fast testing. Thanks for your manual, it helped me find my way through Proxmox.

Just some ideas:
If you can connect to this Windows system, you may use a tool like Drive Snapshot to push a system image to an external Windows share. Then you may setup new VM, boot with a PE system and restore from image. Downtime is minimal, as halt system A and boot system B.

Maybe an ubuntu live CD/USB may help to copy vms/data from vmfs filesystem to where you want:

If ESXi and VMs have to stay online you may take a snapshot of the VM, copy the original disk to NFS share and delete the snapshot. You may then setup a new VM with same settings and the copied disk.

Really cool!

Thx for the ideas, we’ll try out a few…

Had a look at the container-templates in proxmox and tried one out? Centos7 or Ubuntu… Its soooo fast!
My first Proxmox test was also an old PC - without even NAS.
It had only 4 GB RAM… I then installed Win7 Ultimate - and was really impressed, at how fast that went - on really old, crappy hardware…

Didn’t take long, and I flattened the first ESXi…

I must say, I also like the proxmox community and wiki. Lots of info out there…


One stupid question: should the Proxmox node ip belong to the Lan ip pool or should the server stand alone outside the lan?

Hi @rasi,

there are no stupid questions. Usually the Proxmox node ip has a LAN IP to be reachable from LAN and to let the VMs communicate with the rest of the network. But there are other configurations possible, like having WAN and LAN interfaces on Proxmox…

Looks that the title doesn’t reflect the content anymore. How can I reword it? :slight_smile:

1 Like