Support for FreeNas on ESXi

Status
Not open for further replies.

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215
Anyone else notice that a lot more people are delving into FreeNas on ESXi (even including me to some extent)? I know it is not precisely a "new" trend, but there seems to be a large influx of threads regarding it...

Most of the regulars obviously know about the other threads and warnings. But just seeing what everyone's take is on being more "supportive" towards it?
 
Last edited:

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
Anyone else notice that a lot more people are delving into FreeNas on ESXi (even including me to some extent)? I know it is not precisely a "new" trend, but there seems to be a large influx of threads regarding it...

Most of the regulars obviously know about the other threads and warnings. But just seeing what everyone's take is on being more "supportive" towards it?

The problem's the same as it was years ago when I wrote the anti-virtualization warning sticky. In general there's nothing wrong with a sufficiently clued individual virtualizing FreeNAS, but that probably includes needing some expertise with both FreeNAS and ESXi, and following a reasonable formula, rather than just pulling some random garbage out of your butt and making it up as you go along.

I didn't write the anti-virtualization stickies because I thought it couldn't be done... most of the FreeNAS instances here are virtualized and had been for quite some time by the time I wrote the warning.

The problem is that virtualization is every bit as twitchy and demanding as FreeNAS is. Sure, you can run FreeNAS on your repurposed old laptop and get it to share out some files, but do you really think that's going to be a good idea long term? I was seeing all sorts of people come in with the virtualization equivalent of that janky setup and then saying "but my hardware doesn't support VT-d, and RDM was working fine... but my disks no longer seem to have data on them, bad FreeNAS, and how dare you tell me the data might not be recoverable, those were my kids baby pix on there."

How many people do we see coming here with poor hardware selections for FreeNAS? Failing to set up things like SMART? Not burning in their systems? Not being willing to do the research to do things right? That's right... lots of them.

Virtualization adds another layer of butthurt on top of that, because the guys like @joeschmuck who actually have the patience and discipline to work through things one step at a time, carefully researching and learning along the way, are in the minority.

The people who come to this forum, quietly read the virtualization warning, then go off and read the linked articles on how to virtualize, and then have success with that, there's a lot of them... and we never hear from them, because it just works. When you're doing it right, it's all good. The ones I'm afraid of are the ones who come into the forums, can't be arsed to read the resources that are available, or worse, don't *understand* the resources that are available, and then start asking questions. There is a point at which you probably just shouldn't try.

If I sound bitter and cynical, it's because I've been through too many cycles of explaining to people why their half-arsed setups won't work right, then having people try to do it anyways and continue to explain to me how I'm wrong despite things obviously not working right for them, as evidenced by continued questions. Or, worse, the data losses of those who liked to argue RDM was the way to go, until they lost their data and it became unrecoverable.

The simple fact is that virtualization offers the opportunity for lots of additional complexity, which is in turn room for lots of additional things to go wrong, especially when you have people who are doing "creative" things to get a little home lab box to "work right." "I can't afford more memory." "My box doesn't support VT-d." "I don't have room for a PCIe card." etc.

The people who know ESXi and are sufficiently versed in it to look at my virtualization stickies and to understand all the things I said? They have no problems virtualizing. But they also typically don't participate heavily in the forum. And the ones who do, hey, I love talking about the ins and outs of this stuff with them.
 

Dice

Wizard
Joined
Dec 11, 2015
Messages
1,410
I've seen the uprising trend too, from close distance ;)

The stickies by @jgreco really served their purpose of rejecting noobs from getting "too deep" before having internalized the most basic aspects of FreeNAS setup and what it needs to work.
Admittedly, at first I got frustrated. The stickies were far from 'bullet point clear' on every step required to virtualize FreeNAS. Indeed a lot of information is presented but "under cover". Somehow masterfully hidden in full daylight, just enough to slow down a "follow bullet point list blindly" -approach. Instead they are vague enough to force additional research. Now in retrospect, it is clear how this was done rather intentionally... well executed too!

To me @joeschmuck's thread pulled me into daring taking "the plunge" which, in his patience rather translated to steady walk to deeper waters out from a shallow beach...
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
I've seen the uprising trend too, from close distance ;)

The stickies by @jgreco really served their purpose of rejecting noobs from getting "too deep" before having internalized the most basic aspects of FreeNAS setup and what it needs to work.
Admittedly, at first I got frustrated. The stickies were far from 'bullet point clear' on every step required to virtualize FreeNAS. Indeed a lot of information is presented but "under cover". Somehow masterfully hidden in full daylight, just enough to slow down a "follow bullet point list blindly" -approach. Instead they are vague enough to force additional research. Now in retrospect, it is clear how this was done rather intentionally... well executed too!

Well, thanks :smile:

At the point I had written those, I had already been virtualizing FreeNAS for a very long time, but the forum kept having this stream of new users arriving who were absolutely convinced that their crappy old eBay-bought NAS must be able to run ESXi and then FreeNAS as a guest. Problem is, around that era, we were seeing a lot of those system be Nehalem or earlier, and the high end Nehalems were the first CPU's to offer VT-d, and even then a lot of times it didn't seem to work well or work right. So most of them were doing craptacular stunts like running FreeNAS on hacked up RDM mappings or other tricks that """work""" for the weakest possible definition of the word.

I totally believe that someone who is reasonably familiar with both platforms and has the right setup can virtualize FreeNAS without a problem if it's done right, but I'm not up to the task of teaching hundreds of users individually how ESXi works and how FreeNAS works. I absolutely wanted anyone who wandered on in with a VMware certification under their belt and some FreeNAS experience to have the information they needed to make an informed decision. Unlike most virtualization tasks, FreeNAS isn't a simple VM. But for anyone who can wander on in and read what I've written and they mostly go "oh well that's obvious" and then maybe a "oh that's really good to know" or two, there ya go. And for some people there'll even be specific reasons you can disregard specific things I've said, but if you're smart enough to know why you can disregard something I've said, I don't need to explain that to the general audience.

Enjoy your virtualization. :smile:
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215
Agreed, having FreeNas on ESXi does bring in a whole lot of other nuisances that basically are outside of the normal FreeNas advice/troubleshooting. I have found the experience very rewarding and will be doing much more with it going forward.

While I would never call myself an expert at it or believe that I know all the answers, I was just considering sharing my knowledge (for what it is worth) and not just my normal knee-jerk reaction of saying "no" or "forget about it".

P.S. I too am thankful for your various virtualization threads and SLOG advice. Read and still re-read them a lot.
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
Agreed, having FreeNas on ESXi does bring in a whole lot of other nuisances that basically are outside of the normal FreeNas advice/troubleshooting. I have found the experience very rewarding and will be doing much more with it going forward.

While I would never call myself an expert at it or believe that I know all the answers, I was just considering sharing my knowledge (for what it is worth) and not just my normal knee-jerk reaction of saying "no" or "forget about it".

P.S. I too am thankful for your various virtualization threads and SLOG advice. Read and still re-read them a lot.

I think.... what is that... am I having a heart attack? Chest... tightening...

4929493759_db5c84e402_m.jpg


Oh crap, that's only supposed to happen at Christmas. Stop warming my heart, it's ticking me off.
 

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,478
I think.... what is that... am I having a heart attack? Chest... tightening...

4929493759_db5c84e402_m.jpg


Oh crap, that's only supposed to happen at Christmas. Stop warming my heart, it's ticking me off.
Who say's a leopard can't change his spots! :)

Seriously, though. The dire warnings on this site sure made a deep impression on me. I built my FreeNAS-on-ESXi all-in-one last May-June. But I didn't actually put it into 'production' use until just a few months ago. And I went to the trouble of building a second, inexpensive testbed system to experiment with before installing any updates or modifications to my main server.

But the fact is -- virtualized FreeNAS works great! (As always, with the caveat that it's done correctly.)

I wish I'd had one of these AIO systems 15-20 years ago, when I had 4 or 5 servers running in my office: a Novell Netware fileserver, OS/2 & Windows workstations, an Oracle database server, etc. It was expensive, and noisy. The systems I have now are a developer's dream.
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
Who say's a leopard can't change his spots! :)

Seriously, though. The dire warnings on this site sure made a deep impression on me. I built my FreeNAS-on-ESXi all-in-one last May-June. But I didn't actually put it into 'production' use until just a few months ago. And I went to the trouble of building a second, inexpensive testbed system to experiment with before installing any updates or modifications to my main server.

That's approximately the level you need to be at to be assured of having success. Test, test, experiment, break things, figure out how to recover. Putting something into production isn't the hour some people take to throw everything into the chassis and get it all connected. It's the entire process of becoming confident in a computing system, which includes carefully building it, then burning it in, then putting it into a lab environment and playing with it to understand it, then even staging a "beta" test time. It isn't just about the computing system, it's also about the guy who runs it, and whether or not he's going to have what it takes to fix problems, keep it up to date, and handle the inevitable emergency. Because at some point you're GOING to do something dumb that sends shivers down your spine, because you didn't think it through all the way, and then you're going to be so thankful that you took a very conservative approach to the whole thing.

But the fact is -- virtualized FreeNAS works great! (As always, with the caveat that it's done correctly.)

I wish I'd had one of these AIO systems 15-20 years ago, when I had 4 or 5 servers running in my office: a Novell Netware fileserver, OS/2 & Windows workstations, an Oracle database server, etc. It was expensive, and noisy. The systems I have now are a developer's dream.

Indeed. We live in a world of fantastic resources.
 
Status
Not open for further replies.
Top