Allgemein

Where are we with vGPU in #Horizon #View: Features and Limitations

lenzker

The Usage of Graphical Processing Unit (GPU)  within the Virtualization field is getting more and more important. Shaders of the GPU can be used for massive-parallel calculations at the same time and speed up applications tremendously. Within the End-User Computing (EUC) field the GPU plays an important role as well (depending on the use-case). Not just certain 3d applications require the acceleration through the GPU (eg. CAD applications, Quake 3), even daily applications can benefit from it (Browser, Microsoft Office, etc.).

Since vSphere 6 there is not need to hide behind XenServer (on this specific feature) since the hypervisor platform supports vGPU or as it is currently called: Shared Pass-Through graphics.

You assemble the graphics-card which must be compatible with the HCL, install its correct drivers on the ESXi and the virtual machine and voila. Here we go… End-user experience at its best. Combine it with Horizon 7 and voila… Desktop Virtualization is really getting serious.

Unfortunately there are still some limitations when you use the GPU.

Limitations:

  • no vMotion: Virtual Machines having a vGPU built in cannot be migrated away via vMotion. This will definitely have an impact on the operational processes (maintenance-mode, patching, etc.) Read more →

Why #VMworld (2016 US edition)

lenzker

When I started blogging I would have never believed that I would say this. This is a sponsored post. No no, I am not making money by writing this, but I was gifted with a VMworld blogger pass for Las Vegas. I’m really grateful for this opportunity and I can assure that this post would have been exactly the same if I didn’t received the ticket.

People knowing me better (and understanding what I am actually doing) know that I am very excited going to #VMworld. With the following post I try to give you some reasons why I love it & why VMworld is a great event and foundation to develop yourself a little further (it’s all about personal development, isn’t it?!)

If it’s your first time visiting VMware’s US event I think you will be able to extract some useful information to gain a maximum benefit out of it.

vmworld

Read more →

Why #vBeers (Munich edition)

lenzker

A few weeks ago I finally managed it to organize the first (kind of official) #vbeers event here in Munich. In the beginning I was afraid if anyone shows up.

Since the weather wasn’t as good as I was hoping I reserved a spot at the Augustiner beer-keller (‘We were going deeper-underground’) … 12 guys were showing up (where are the virtualization girls/women?!) and speaking for myself (and hopefully for the others attending as well)… it was a great evening…

Awesome talks about technologies, processes, problems, projects, highly skilled people (we had 2 VCDX and a few wannabe VCDX on the table) and of course… one or another beer (not the small ones you might think of…in Bavaria we drink our beer in 1 liter (= 0,264172 gallons) glasses)…

vbeers

Read more →

vSphere console: black screen on Windows 10 & Windows 2012 R2

lenzker

If you have a black-screen on the vSphere console (no matter if using .NET client, Web-Client, Remote-Console, etc.) typically the following things help you out:

  • Having the correct port opened between your client and the ESXi host where the virtual machine is running on (TCP: 903)
  • Correct working DNS: Your client must be able to lookup the ESXi FQDN
  • Permissions

For sure there are many more things… most of them are well documented nowadays… so check them out.

There might be another reason if you use Windows 10 or Windows 2012 R2 (Not sure how it is in the older versions) where the symptoms (a black screen) might be similiar, but the problem is not vSphere related (even though it seems to be).

Read more →

A server error occured [400] or vCenter Server ‘once upon a time’

lenzker

After fixing a failed SSD of one of my lab-hosts I had some minor issues with my vCenter. Whenever I logged on into it I received this error.

vCenter error 400

“[400] An error occured while sending an authentication request to the vCenter Single Sign-On server – An error occured when processing the metadate during vCenter Single Sign-On setup – null.”

fair enough I checked the :5480 VAMI of my PSC and vCenter and the vCenter showed me the SSO was not initialized.

Read more →

#topvblog 2016: Place your vote and see my recommendations

lenzker

As every year Eric Siebert started the collection for votes regarding the best blogs within the virtualization field.

Caused by the great blogging-landscape I don’t see any chance to come close to the top 100 area. But still I hope to gain one or the other vote within the new blogger category (vLenzker.net exists for around 6 months right now)

Screen Shot 2016-05-04 at 09.56.55

Here you can give your vote. Thanks VMturbo and Eric Siebert to sponsor and execute this event once again.

I am listed with two blogs this year: vLenzker (Fabian Lenz) & 

Read more →

UPDATE: #vBeers in Munich: 12th May 2016 – 06:00PM – Augustiner Keller

lenzker

###Update

WHEN? 12th May 2016 – 06:00PM

WHERE? Augustiner Keller (Arnulfstr. 52, 80335 München)

Sponsored? Nope ;-( (BYOW – Bring your own wallet)

Screen Shot 2016-05-06 at 10.14.24

I am impressed about the amount of people interested in such an event and Doodle has decided. We will have a Munich #vBeers meet-up on the 12th May 2016 – 06:00PM. If you are interested please don’t hesitate to sign-up here.

Read more →

How to do the ESXi VMkernel PING: Unknown interface: Invalid argument

lenzker

Over the years one of my favourite tool when troubleshooting network problems in the vSphere world was vmkping. It allows us to send an ICMP request based on a specified VMkernel port (perfect for troubleshooting vMotion/vXLAN problems).

With ESXCLI NETWORK DIAG PING a nice wrapper for the ping tool was implemented into the ESXCLI namespaces, so that we can use this command remote via vCLI oder even through the PowerCLI cmdlet.

Unfortunately in vSphere 6.0 the command doesn’t work anymore as it has been before (in case that you do NOT use the default networking stack). VXLAN, vMotion and Provisioning traffic can now be configured to use a seperate tcp/ip stack (dedicated routing/arp tables).

Once you use such a non-default-VMkernel port via ping or the according ESXCLI command you receive the following error:

Unknown interface ‘vmkX’: Invalid argument

Invalid Argument

To make it work again make sure to specify the networking stack.

esxcli network diag ping -I vmk2 –netstack=vmotion -H 192.168.119.63

VMkping suc

Take care since the stack parameter requires a case-sensitive input?

esxcli network diag ping -I vmk2 –netstack=vMotion -H 192.168.119.63

leads to

Got no data from process:
/bin/ping ++netstack=vMotion -S vMotion -I vmk2 -X 192.168.119.63

so better use the correct value out of the following command return:

esxcli network ip netstack list

netstack

–>

vxlan / vmotion or skip the entry for defaultTcpipStack

If you don’t like the ESXCLI method, just use the -S parameter in the good old vmkping

vmkping

 

#VMworld 2015 Barcelona in 187 seconds: A video for the memories

lenzker

VMworld 2015 is over and I still haven’t processed all the experiences, information, talks. Nevertheless I have processed all of the small videoclips I made during #VMworld with my iPhone.

VMworld header

Some people might know that I always like to create small videos (you find them on youtube as well) of the awesome trips,travels and journeys I am on. It is great to have a short summary of some experiences a few years later and therefore I did the same with the VMworld material I created during the last days.

I hope you enjoy it and hope to see a lot of the guys I met during this VMworld next year again (in Las Vegas & Barcelona).

Direct link