Comments on: ESX Server 3.0.1 Patch Needed for VC 2.5 http://blog.scottlowe.org/2008/01/10/esx-server-301-patch-needed-for-vc-25/ The weblog of an IT pro specializing in virtualization, storage, and servers Mon, 01 Dec 2008 20:32:26 +0000 http://wordpress.org/?v=2.6 By: vijaysys http://blog.scottlowe.org/2008/01/10/esx-server-301-patch-needed-for-vc-25/#comment-35290 vijaysys Sun, 03 Feb 2008 15:14:19 +0000 http://blog.scottlowe.org/2008/01/10/esx-server-301-patch-needed-for-vc-25/#comment-35290 Hi Scott some inputs need for the following scenario: I have added additional 20 GB of disk space to one of my virtual machine(which has linux os). Do i need to reboot the Virtual machine, to configure new file system for the extra space added.... Thanks regards vijay Hi Scott

some inputs need for the following scenario: I have added additional 20 GB of disk space to one of my virtual machine(which has linux os). Do i need to reboot the Virtual machine, to configure new file system for the extra space added….

Thanks

regards
vijay

]]> By: slowe http://blog.scottlowe.org/2008/01/10/esx-server-301-patch-needed-for-vc-25/#comment-35155 slowe Tue, 22 Jan 2008 11:52:54 +0000 http://blog.scottlowe.org/2008/01/10/esx-server-301-patch-needed-for-vc-25/#comment-35155 Rich, I wish I had posted this sooner! I could have saved you some trouble. :) Rich,

I wish I had posted this sooner! I could have saved you some trouble. :)

]]> By: Rich http://blog.scottlowe.org/2008/01/10/esx-server-301-patch-needed-for-vc-25/#comment-35112 Rich Sat, 19 Jan 2008 03:22:04 +0000 http://blog.scottlowe.org/2008/01/10/esx-server-301-patch-needed-for-vc-25/#comment-35112 I think your post (and this problem) explains what happened to me at a client that I was helping upgrade to VI3.5 this week. We upgraded VC. Then we connected several ESX 3.0.2 hosts without any issues. We started connecting ESX 3.0.1 hosts and all of a sudden my client's phone start ringing because a file server VM is no longer available. Sure enough it had rebooted, but not only did it reboot the properties of the virtual nic no longer had the "connected box" checked. I wish I would have read this post on Monday .... I think your post (and this problem) explains what happened to me at a client that I was helping upgrade to VI3.5 this week. We upgraded VC. Then we connected several ESX 3.0.2 hosts without any issues. We started connecting ESX 3.0.1 hosts and all of a sudden my client’s phone start ringing because a file server VM is no longer available. Sure enough it had rebooted, but not only did it reboot the properties of the virtual nic no longer had the “connected box” checked. I wish I would have read this post on Monday ….

]]>