VMware ESX 4 expanding an IDE Drive
I found an article on how to do this, but one of the steps is to edit the vmdk file and tell it that it is a lsilogic drive instead of an ide drive, and when I find the vmdk file and try to edit it with vi I get a "Permission Denied" error. I am trying to edit the right vmdk file, not the large flat file with the data, but the vmdk file with the information about the disk. The article I am following is this one.
http://claykinney.blogspot.com/2010/06/vmware-esxi-4-increase-ide-drive-size.html
http://claykinney.blogspot.com/2010/06/vmware-esxi-4-increase-ide-drive-size.html
ploftin
Did you stop the VM before attempting this process? The VM must be stopped to edit the VMDK. In fact, if ANY VM has that VMDK mapped, they must all be stopped before you can edit the VMDK file.
ASKER
I cloned the machine that I want to do this to, and I'm using the cloned vm to test this process on first. It is shut down yes. The vmdk file should only belong to the clone vm.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, I have done that before when I originally did a p2v with this machine, but after it is converted it breaks the licensing for the application that that is a pain to get re-done. Maybe it wouldn't happen just going from a virtual machine to a virtual machine though.
Hmm...that sucks. I don't recall hearing about that happening, but good to know that can happen when doing P2Vs. Well, it won't hurt to try it I guess...let me know how it goes. :)
~coolsport00
~coolsport00
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I got impatient and just used the standalone converter, and as expected the application broke and I had to re-license it. Not a huge deal, but a pain. The disk is resized though so that issue is out of the way.
Afterwards out of curiousity I double checked to see if I could edit the vmdk file again, but made sure I was logged in as root. That was the issue as far as not being able to edit the file. I was logged in with another user and didn't su - first.
Thanks guys.
Afterwards out of curiousity I double checked to see if I could edit the vmdk file again, but made sure I was logged in as root. That was the issue as far as not being able to edit the file. I was logged in with another user and didn't su - first.
Thanks guys.