infinitiguy's Posts

scp was really the key here. I forgot about it. All i knew is I couldnt use a unix command like cp to copy it off somewhere else, and that I could corrupt the disk so I was just being ex... See more...
scp was really the key here. I forgot about it. All i knew is I couldnt use a unix command like cp to copy it off somewhere else, and that I could corrupt the disk so I was just being extra obsessive careful Cheers to all that responded
I guess that was also one of my other questions. I use Veeam FastSCP and I didn't know if that would take care of the proper conversions between filesystems or not. i.e. download via scp to n... See more...
I guess that was also one of my other questions. I use Veeam FastSCP and I didn't know if that would take care of the proper conversions between filesystems or not. i.e. download via scp to ntfs, and then from ntfs copy straight back to vmfs without any need for vmkfstools.
I think I found my answer.. can anyone confirm? #1 vmkfstools -i diskonvmfs.vmdk -d 2gbsparse /vmimages/diskonext3 #2 ftp new ext3 disks across #3 vmkfstools -i diskonext3.vmdk... See more...
I think I found my answer.. can anyone confirm? #1 vmkfstools -i diskonvmfs.vmdk -d 2gbsparse /vmimages/diskonext3 #2 ftp new ext3 disks across #3 vmkfstools -i diskonext3.vmdk /vmfs/production/newvmfsdisk.vmdk does that sound right?
Here's the situation. I have two sets of ESX servers, in different cities. I need to get one VM from one cluster, to the 2nd cluster. My thought was move the vm from vmfs, to ext3(/vmimages)... See more...
Here's the situation. I have two sets of ESX servers, in different cities. I need to get one VM from one cluster, to the 2nd cluster. My thought was move the vm from vmfs, to ext3(/vmimages) then ftp it over to a ext3 partition on the other esx server, then use vmkfstools -i to import it back in.. Now I thought I had used this process before in the past, and I do this type of thing very rarely, so I can't remember exactly what I did to get it to work, but when I just tried # vmkfstools -i license3.vmdk /vmimages/machines/license3test.vmdk Destination disk format: VMFS thick Cloning disk 'license3.vmdk'... Failed to clone disk : File system isn't VMFS (35). Which I guess makes sense. What needs to change? Or is this not the proper way to do it and should I be doing something different? Running vc2.5 and esx 3.5U1 (u2 i think in the other location..)
I worked around this. I think this just has to do with buggy behavior in this whole process. I don't know if vmware doesn't support redhat linux 8.0 anymore.. or if somehow the conversion mes... See more...
I worked around this. I think this just has to do with buggy behavior in this whole process. I don't know if vmware doesn't support redhat linux 8.0 anymore.. or if somehow the conversion messed up the cd-rom in linux. What I ended up doing was just mounting the tools on another system and copying over the rpm.. then I installed vmware-tools and it seems to be working
followed this kind gents instructions here.. http://virtualaleph.blogspot.com/2007/05/virtualize-linux-server-with-vmware.html Unfortunately, when I rightclick in VI to instal... See more...
followed this kind gents instructions here.. http://virtualaleph.blogspot.com/2007/05/virtualize-linux-server-with-vmware.html Unfortunately, when I rightclick in VI to install vmware tools(to get the CD mounted) I get this error and the "cd" doesn't mount. Now what's interesting is... I don't seem to have a /dev/cdrom or a /mnt/cdrom anymore... which is a bit curious..
I just converted a redhat linux 8.0 physical server into a VM by using a workaround I found on a blog using vmware converter, and then making some modifications. The linux vm boots ... See more...
I just converted a redhat linux 8.0 physical server into a VM by using a workaround I found on a blog using vmware converter, and then making some modifications. The linux vm boots great now, and I want to get vmware tools installed, but when I try to install, I get "A general system error occurred: Internal error" anyone have any thoughts? VI 2.5 U1 and ESX 3.5 U1.
is there any danger in doing so? Will removing my host from the cluster cause any effect on my virtual machines? Will running service mgmt-vmware restart cause my virtual machines to reboot? S... See more...
is there any danger in doing so? Will removing my host from the cluster cause any effect on my virtual machines? Will running service mgmt-vmware restart cause my virtual machines to reboot? Should I treat this as a software upgrade and migrate all my machines off.. follow this procedure on one box.. move all machines back to that box.. and then repeat?
I'll start by saying.. HA used to work What I have is two hosts. Each runs about half its load and the plan is if one were to fail the other takes on the load. Simple. ... See more...
I'll start by saying.. HA used to work What I have is two hosts. Each runs about half its load and the plan is if one were to fail the other takes on the load. Simple. Problem is somewhere along my upgrade path, something got screwed and now HA will not re-configure. I constantly get the "HA agent on amer-esx1.fqdn.com in cluster Production in Waltham(datacenter) has an error. I get this on both hosts. I can ping from each host to the other host, I made entries in the /etc/hosts just to make sure although pinging back and forth was working before. I then started to think it may have been a 3.0.1/3.5 issue because I tried it again after upgrading one of my hosts but it still happens. I enabled HA again after everything was upgraded and I got the same error as well as a insufficient resources error. Are there any HA logs in 3.5.1 that may tell me exactly what is going on? Nothing else has really changed in terms of netowrking etc and I sure am running out of ideas
yep, both are right I was actually on the phone with vmware when the first reply came back and I let him tell me the same thing. Thanks all!
I'm a slight bit concerned.. my CPU's were compatible under 3.0.1, and now that I have a 3.0.1 and a 3.5.1 host they are no longer compatible? That's scary I attempt to move a machine and... See more...
I'm a slight bit concerned.. my CPU's were compatible under 3.0.1, and now that I have a 3.0.1 and a 3.5.1 host they are no longer compatible? That's scary I attempt to move a machine and I get the following warning. Migration from amer-esx2 to amer-esx1: Migration will cause the virtual machine's configuration to be modified, to preserve the cpu feature requirements for its guest OS. Amer-esx2 is my 3.0.1 node and Amer-esx1 is my newly upgraded 3.5.1 node.. Esx1 has a 3.2ghz xeon and Esx2 has a 2.8ghz Xeon, but they are from the same family, and like I said earlier... had worked fine over vMotion for months before this upgrade. Now... I really don't care if the configuration has to change, or anything like that... just as long as it wont destroy the virtual machine/vmdk.. or bring down the machine. I have domain controllers, and websites running on esx2 that I really don't want to have to bring offline. Any help is appreciated. I read a bunch of other posts about this subject but they don't exactly have to do with my circumstances.
I have 3 esx servers.. two are vmware enterprise running at 3.0.1(vmotion, ha, drs etc..) and a third standard license(no ha.. etc..) that I just upgraded to 3.5. I also have a single virtua... See more...
I have 3 esx servers.. two are vmware enterprise running at 3.0.1(vmotion, ha, drs etc..) and a third standard license(no ha.. etc..) that I just upgraded to 3.5. I also have a single virtual center license that I manage my two enterprise VMware ESX servers under. Two questions.. the 3.5 machine was my dev machine.. I just moved all my dev machines to it.. including some templates I had played around with, and now I've discovered I seem to have lost the ability to provision machines from templates.. after some quick reading I think this is because you need the machine to be managed under Virtual Center to be able to do that.. which is fine if that's the case.. more importantly, and this is a licensing question... can I add my esx standard license to my VC server so I can manage all 3 vm servers under virtual center? I just bought a 4th server with vmware foundation for the eng lab.. and it'd be great if I could manage that under my VC server as well, but I'm not sure if thats the way it works.
tried a firmware downgrade and its still not working.. about to call vmware support now.. any thoughts are most appreciated
config: HP ML 350 G5 - vmfs on a netapp san using qlogic hbas. running ESX 3.0.1 I think I know what the problem is, but I'm posting anyways just for thoughts. So I h... See more...
config: HP ML 350 G5 - vmfs on a netapp san using qlogic hbas. running ESX 3.0.1 I think I know what the problem is, but I'm posting anyways just for thoughts. So I had my systemboard replaced because I put some new memory in and all of a sudden I couldn't see the logical drives. Funny enough, after leaving the machine powered off and unplugged all weekend, it was able to see the drives again but the tech replaced the board since he had it anyways. The tech left aafter showing me that the logical drive appeared.. and I was happy. So I hooked everything back up, and start getting errors during the boot.. one had to do with loading the vmkernel qla4022 drivers and then complaining that it couldn't load that in the service console.. then a ton more scrolled by that I couldn't see, and finally ended with "failed to mount root" and dropped me into a busybox 0.60.5 shell. I searched around the forums real quick and saw other people had similar issues on esx 3.5 after a firmware upgrade on dells hardware. I have to suspect that something similar happened here, as it all worked fine for 8 months before, and im pretty sure the system board has the latest firmware from HP on it. I'm on to HP already to tell me what I need to do, but I forsee a fight ahead of me. I asked them how I can get a copy of older firmware so I can downgrade but we'll see what they have to say. Thoughts? Does the above seem to be the most plausible cause? Disgruntled and esxless...
just out of curiousity.. is there a link to the recommended way to back up a virtual center server? I just realized that I don't think I have my VC database backing up. Is it just a standard sq... See more...
just out of curiousity.. is there a link to the recommended way to back up a virtual center server? I just realized that I don't think I have my VC database backing up. Is it just a standard sql dump? Will that capture all my configs?
Part of my concern with VC2.5 is the posts I read about 3.0.1 machines managed under VC2.5 that weren't patched.. their VM's could randomly reboot. I'm running domain controllers, web servers... See more...
Part of my concern with VC2.5 is the posts I read about 3.0.1 machines managed under VC2.5 that weren't patched.. their VM's could randomly reboot. I'm running domain controllers, web servers and other services that I don't want to have randomly reboot which is why I'm so tied to patching 3.0.1 if I have to have it managed under vc2.5 You've given me some good info though. Cheers,
that's what I figured. What I was trying to avoid was having to patch my esx3.0.1 servers at all. I don't think I can really avoid that though... I can't migrate my machines without VC..... See more...
that's what I figured. What I was trying to avoid was having to patch my esx3.0.1 servers at all. I don't think I can really avoid that though... I can't migrate my machines without VC.. and I can't upgrade my machines without VC since I need to migrate between them... What a mess So I think what I'll have to do is... move my dev machines to my new unmanaged 3.5 box(lun re-point.. not a migrate).. then patch my empty ESX server to allow for 3.0.1 under 2.5.. Migrate my production machines to 3.0.1 (patched) then patch the 2nd production machine. Then I can upgrade virtual center to 2.5.. then I can upgrade both my ESX servers to 3.5(one... migrate.. do the 2nd..) does that all sound logical?
I have 2(soon to be 3 esx servers) 2 are at 3.0.1 w/ vc2.0.1 and the third I will build straight to esx 3.5. Now, I've read that esx 3.0.1 can work with vc 2.5 without some patches.. which I'... See more...
I have 2(soon to be 3 esx servers) 2 are at 3.0.1 w/ vc2.0.1 and the third I will build straight to esx 3.5. Now, I've read that esx 3.0.1 can work with vc 2.5 without some patches.. which I'm not that keen on installing... I'd rather just upgrade my hosts completely. My question is.. can I run two virtual center environments(even if I just have a license for one) for an interim until I get all my stuff upgraded? Or will that not work?
I haven't looked into any VMware certifications... what's out there? Anyone have good links regarding the certs? Is there only a VCP? How many tests do you have to take and how much? What are... See more...
I haven't looked into any VMware certifications... what's out there? Anyone have good links regarding the certs? Is there only a VCP? How many tests do you have to take and how much? What are the best study materials(other than real world playing/experience).
This is what I've done(on my HP's) but plan on doing the same on my dell's.. The only reason mine is 20GB used is because of /vmimages.. I have a bunch of iso's there. If you're using a SAN f... See more...
This is what I've done(on my HP's) but plan on doing the same on my dell's.. The only reason mine is 20GB used is because of /vmimages.. I have a bunch of iso's there. If you're using a SAN for your VMFS... just throw everything at root and split off /var and /opt to smaller sizes so they can be contained.. I like having it all in / because then I can use vmimages as the rest of my disk and not really have to worry about how "big" my / is # vdf -h Filesystem Size Used Avail Use% Mounted on /dev/cciss/c0d0p6 124G 20G 97G 18% / /dev/cciss/c0d0p1 244M 30M 201M 13% /boot /dev/cciss/c0d0p3 3.9G 75M 3.6G 2% /opt none 391M 0 391M 0% /dev/shm /dev/cciss/c0d0p2 5.8G 224M 5.3G 4% /var /vmfs/devices 814G 0 814G 0% /vmfs/devices /vmfs/volumes/4643eb73-018e4270-72ed-001b782f773a 304G 238G 65G 78% /vmfs/volumes/esx1_1 /vmfs/volumes/464d5cd5-682ab27c-ab60-001b782f773a 9.8G 8.6G 1.1G 88% /vmfs/volumes/esx1_2 /vmfs/volumes/47c8c330-cdf71dc0-70ae-001b782f773a 29G 8.6G 21G 28% /vmfs/volumes/esx1_3 #