MS logic

... as in "most stoopid"!

So, here is the situation :

Client was just delivered with an Hyper-V cluster for his web services; once he tries to setup Apache & Co on his CentOS instances, figures that 50GB originally requested is not enough, wants to change it to 120GB...

So, virtual machines running linux with LVM partition, should be easy right? We might even be able to do it live, no need to shutdown the instance... let's check it out!

I found this little procedure, quite straight-forward, about manipulating LVM partition in a virtual environment :

https://www.rootusers.com/how-to-increase-the-size-of-a-linux-lvm-by-expanding-the-virtual-machine-disk/

But then I found out that you can only do so if the virtual disk was attached to a SCSI controller; I had a problem here, because the VM was already configured, installed and running via a IDE controller in Hyper-V. Oh well, the client didn't have any issue with us stopping the VMs in the beginning, we could address this issue later.

• VHDX - the ability to expand and shrink virtual hard disks is exclusive to virtual hard disks that are using the .vhdx file format. Online resizing is supported for VHDX disk types, including fixed, differencing, and dynamic disks. Virtual hard disks that use the .vhd file format are not supported for resizing operations.
• SCSI controller - the ability to expand or shrink the capacity of a virtual hard disk is exclusive to .vhdx files that are attached to a SCSI controller. VHDX files that are attached to an IDE controller are not supported.

[ https://technet.microsoft.com/en-us/library/dn282286(v=ws.11).aspx ]

So I followed the procedure and expended the VHDX file from 50GB to 128 (I always prefer to do things at the power of 2 in the binary realm).

This morning I decided to do a test run on an Hyper-V cluster we use for testing; created a VM, change from IDE controller to SCSI, installed CentOS without a fuss. Then, when I tried to boot the VM by itself :

WTS?

Again, a little search and I find the answer :

https://blogs.msdn.microsoft.com/virtual_pc_guy/2009/12/01/why-hyper-v-cannot-boot-off-of-scsi-disks-and-why-you-should-not-care/

Sorry Ben, but I do care : the TechNet link states that "Starting in Windows Server® 2012 R2, Hyper-V delivers the ability to expand or shrink the size of a virtual hard disk while the virtual machine is still running." but a VM on Hyper-V cannot boot off of a SCSI disks?

As we say in French, Je ne sais plus sur quel pied danser...

Don't make a sound...

[ code ]

procyon:~ ionreflex$ brew search sshpass
We won't add sshpass because it makes it too easy for novice SSH users to
ruin SSH's security.

[ / code ]

Can't argue with that...

... KILL!

nul@wormhole:~$ ssh root@supernova
VMcrap vCrapper Server Appliance
Password: yeah... right!
Password change requested. Choose a new password.
Old Password:  yeah... right!
New password: C0rr3ctH0rs3B4tt3r7St4pl3
BAD PASSWORD: is too simple

... WTF? X_x

[expletive/deleted]

nul@wormhole:~$ apt-get install htop
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
nul@wormhole:~$ fuck
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  htop
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 65.3 kB of archives.
After this operation, 203 kB of additional disk space will be used.
Get:1 http://ca.archive.ubuntu.com/ubuntu/ utopic/universe htop amd64 1.0.3-1 [65.3 kB]
Fetched 65.3 kB in 0s (536 kB/s)
Selecting previously unselected package htop.
(Reading database ... 201749 files and directories currently installed.)
Preparing to unpack .../htop_1.0.3-1_amd64.deb ...
Unpacking htop (1.0.3-1) ...
Processing triggers for man-db (2.7.0.2-2) ...
Processing triggers for mime-support (3.55ubuntu1.1) ...
Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu2) ...
Processing triggers for bamfdaemon (0.5.1+14.10.20140925-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
nul@wormhole:~$ cat .bashrc |grep fuck
alias fuck='sudo $(history -p \!\!)'

Tire la chevillette, la bobinette cherra...

... first you need to find the warlock, because only thee knows the warped holes of the void, from where you gain access to the gates of Nockmaar.

Count Zero

QWHAT ?

How come that, in order to reset the network error counts given by the netstat tool, you have to reboot ?

I'm talking about a firewall here! Talk about an interrupt...

Lord of the Ping / Pause / Play

Just found out that you could actually pause a "ping" command on Windoze (XP Pro and Vista64 Biz) : hit CTRL-S once to stop it, another time to restart it...

Kinda useless, but looked like undocumented! Well, was, as in not anymore! :o)

The Wizard of Ordz / Wordz

It was a long time ago, in a memory far, far away... okay, lets cut the crap : I've found out that the translation for FIRMWARE was MICROLOGICIEL... You may think I'm crazy - you're probably right but who isn't ? - but IMHO, MICROGICIEL sound so much better (I guess it doesn't make sense for the ink/glitch masses...) so paleez remove the LO part somebody ? :o)

Since it doesn't fit the Urban Dictionary - because it's a French word - I'm putting it on my blog! If I get enough commentaries approving it, the "Grand Dictionnaire Terminologique" might change it...

Yeah... Right!

X_x

More than meets the eye / High-Speed Video of Lightning

http://ztresearch.com/

The Case of the Multi-Faceted Full-Blown Google solution... or so I hoped!

Let's call it my M2FBG project...

If you took the time to read the "main function" on the right, then you'll know what to expect browsing throught the archives; then again, not being your typical one man tech army guy - and not doing everything as it's supposed to be done! - I like to put a special flavour to everything I do...

So this being a Blogger blog, my intentions were and still are to build this virtual space out of everything Google! The idea first originate when, using the Google Documents, I saw it was possible to publish from GDocs to Blogger... little I knew about I was getting into...

The fact is that it's been more than 6 months now! At first, GSupport seems available to troubleshoot and fix the problem, but then it won't reply to my follow-up... how typical! Don't get me wrong : I'm pretty sure people at GSupport have plenty to be busy, but does that excuse them for poor assistance to users ? I do hope they don't take for granted offering free services makes up for bad support... from my point of view, the feedback vibes feel even nastier!

Wow : I don't even tell what this is all about do I ? :o|

So here we go, fast-forward style : GDocs has a function to publish a text to a blog of your choice (you can choose from Blogger, Wordpress, Livejournal and others); that way you can work with others on a document and have it automatically published everytime a modification has occured. In the vast infinity of the web, I've always liked the approach of Google solutions, so I thought the idea of publishing a GDoc to one of my GBlog (or Blogger if you prefer, and yes, I have many!) was cool; so the GDoc was rapidly created, the publish options set and tested, then applied...

WTH ? Refresh = NULL!

Little troubleshooting, to find out that the GDoc hasn't been published to my desired blog, but to one I used before to troubleshoot another issue (which I'll probably summarize in another post soon enough!)... then the fun started!

My first report of the bug was more than 7 months ago! At First, GSupport was giving me an impression of interest in the issue, as I replied rapidly after trying out several tips they gave out, they replied again stating the feedback I gave would likely help them solve the issue... over the next three months, I gave other infos, after renaming the blog, trying the GBlog english interface instead of the french one - yeah btw, I'm french and that probably explain the funny turn my writhing takes from time to time! ;o) - but GSupport never wrote back, and as I wrote this, the problem is still there!

Being in the field this is something I really resent, not being able to know where things stand : a good practice would be a freely accessible webpage showing how bug/case file are being handle! But like I said, the big G is, well, so BIG it probably is overwhelmed with the infinity (!) of projects it is trying to deliver/debug/support/develop...

Anyhow, I'm still faithful that my M2FBG solution (!) will eventually be functional, but for now it will rest in peace...