In my opinion the only people who feel threatened by this tool are those which feel it would expose something they are not being transparent about. Might be worth noting for any future purchase decisions...Lol when I saw this earlier I just knew...tonight would be good. It doesn't matter but it won't stop the drama. Popcorn up people.
Of course it is; it's a neat technical question.Isn't the question "can you determine whether you are running in a hypervisor from within a restricted container" interesting enough without a drama angle? If not that, then is "can we determine as much information about the hypervisor from inside the container" interesting?
My whole point in downloading and running the test was that I wanted to create drama and publicly humiliate my provider, but alas, the server that Oles delivered to me today 1 minute and 53 seconds after ordering is not running under a hypervisor. Just think of the drama that would have ensued if the test had shown that Oles was trying to pass off slabs as E3 dedis.What's the point here but drama?
Isn't the question "can you determine whether you are running in a hypervisor from within a restricted container" interesting enough without a drama angle?
Interesting... I will pick one up and test with it.The OVH Classic and Low Latency VPS lines are OpenVZ running on VMWare
But you are a provider!tl;dr: I wouldn't do slabbing with VMware if I were a provider.
I meant in that context a provider that used a scheme that would benefit from slabbing (i.e. OpenVZ).But you are a provider!
can you teach me how did you get into that instead?version 0.2 of this tool has been tagged in GIT, downloadable here: https://github.com/kaniini/slabbed-or-not/archive/0.2.zip
This version is basically all about tickling VMware from inside an OpenVZ container. If that doesn't apply to your situation, it's probably pretty boring.
Interesting aspect: This version could be modified to do evil things to VMware from inside the OpenVZ container on some versions of VMware. For example, if you're running under VMware Workstation, some very trivial modifications to this tool would allow you to do things like disconnect the virtual HDD, from inside the OpenVZ container.
Good news: ESXi 5 appears to no longer allow device enumeration. Older versions -- no idea. If it lists devices, you can disconnect them by adding some code. The hypervisor's hypercall port assumes if you can access it that you have permission to do these things to the VM.
Bad news: It is not practical to block access to the VMware hypercall port. Even though ioperm() and iopl()/inl()/outl() syscalls are hidden behind the sys_rawio POSIX capability, you can just simply use some inline asm to make the hypercalls.
tl;dr: I wouldn't do slabbing with VMware if I were a provider.
Clearly you haven't been on LET lately.Wonder when the BlueVM does slabbing thread will pop up. They have actual service stability issues, and is likely related to their slabbing setup. Quite a bit of drama for a provider that's been solid.
is it IN the buyvm thread? I stopped reading it on like page 2.Clearly you haven't been on LET lately.
Johnston already said they do slab some of their smaller plans and gave the reason for doing itWonder when the BlueVM does slabbing thread will pop up. They have actual service stability issues, and is likely related to their slabbing setup. Quite a bit of drama for a provider that's been solid.
No-one is saying slabbing is bad..This forum is turning into LET.
Slabbing does not equal low quality. It has it's uses. Parts of AWS uses slabbing because it's efficient and stable.
^--- THIS.No-one is saying slabbing is bad..