J-H's Posts

Thanks! The registry hacked solved the problem.
You can use a motherboard with a SATA controller that is recognized by ESX. It is not supported but it is a common lab setup. http://communities.vmware.com/message/822867
Do you have a S5000PAL or a S5000PSL ROMB motherboard?. I have a S5000PSLROMB and made similar bad experience when I tried to use it with ESX 3.0.x. http://communities.vmware.com/message/5905... See more...
Do you have a S5000PAL or a S5000PSL ROMB motherboard?. I have a S5000PSLROMB and made similar bad experience when I tried to use it with ESX 3.0.x. http://communities.vmware.com/message/590583 With ESX 3.0.x I had to purchase a RAID activation key (AXXRAK18E), memory for the RAID card, and I also purchased a battery backup unit (AXXRSBBU3). This was quite expensive. I assume you do not need the ROMB version with ESX 3.5 because I believe you now can use the onboard SATA controller. http://communities.vmware.com/message/820550#820550
I'm currently running a VM located on the disk connected to the SATA controller. What I haven't tried is to remove the ROMB card and only use the disk connected to the SATA controller to i... See more...
I'm currently running a VM located on the disk connected to the SATA controller. What I haven't tried is to remove the ROMB card and only use the disk connected to the SATA controller to install ESX and create a VMFS on a partition of that disk or another disk connected to the SATA controller. I'm currently too busy to perform this test.
I have an Intel S5000PSLROMB motherboard. With ESX 3.0.x I had to purchase a RAID activation key (AXXRAK18E), memory for the RAID card, and I also purchased a battery backup unit (AXXRSBBU3). T... See more...
I have an Intel S5000PSLROMB motherboard. With ESX 3.0.x I had to purchase a RAID activation key (AXXRAK18E), memory for the RAID card, and I also purchased a battery backup unit (AXXRSBBU3). This was quite expensive. http://communities.vmware.com/message/590583 ESX 3.0.x did not recognize the onboard SATA controller (6321ESB). The installation CD only showed the disks connected to the ROMB card and also after the installation I only could use disk connected to the ROMB card. The ESX 3.5 installation CD now recognizes the SATA controller and the ROMB card. I was able to create a VMFS on a disk connected to the SATA controller. It is likely that with ESX 3.5 I could have bought the S5000PSLSATA or S5000PSLSAS motherboard which is cheaper, and it would not be required to buy the RAID activation key and RAID memory. The only difference would be that the configuration would not be on the HCL and therefore is not supported. This is my test system at home so I could live with this disadvantage.
According to IE 7 is supported with Web Access. If you connect with IE 7 you get a warning that the browser is not supported. According to only IE 6 has been certified with web access. I... See more...
According to IE 7 is supported with Web Access. If you connect with IE 7 you get a warning that the browser is not supported. According to only IE 6 has been certified with web access. If I try to connect to the console of a guest then IE 7 crashes.
vi3_35_25_installation_guide.pdf page 69. You have to select the driver at the time you create the DSN.
I changed the configuration of the guest to use the ISO file on a batastore, but the installation stops at the same point. Vmware.log now contains the following entries: Nov 23 11:20:50.258: vc... See more...
I changed the configuration of the guest to use the ISO file on a batastore, but the installation stops at the same point. Vmware.log now contains the following entries: Nov 23 11:20:50.258: vcpu-0| CDROM: Mode Sense for Unsupported Page 0x1B Nov 23 11:20:50.267: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 0 ... Nov 23 11:20:50.270: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 1 start feature 0 ... Nov 23 11:20:50.271: vcpu-0| CDROM: Unknown command 0xAC. I thought that I should try to uninstall the patches of November 15, but according to http://www.vmware.com/pdf/esx3_esxupdate.pdf it is not possible to uninstall ESX patches. ## Can I remove patches from my ESX Server system once they have been installed? The esxupdate utility does not support rolling back or removing any type of updates. You cannot remove patches once they have been installed. ## Any tips are highly appreciated. The current situation is really annoying. In the beginning of the Windows Server 2008 / Longhorn beta program I had problems with the VMware tools related to the CDROM in the guest. Only the 32 bit version was working with the help of http://sti.epfl.ch/intranet/informatique/virtualisation/drivers-vista-rtm-esx.flp.zip (many thanks to Paul Giddens). Now I again have trouble with the x64 version…
Host: ESX 3.02 with all patches I try to install Windows Server 2008 November CTP but the installation process stops at “Completing installation”. It stays at this point and the only visible... See more...
Host: ESX 3.02 with all patches I try to install Windows Server 2008 November CTP but the installation process stops at “Completing installation”. It stays at this point and the only visible progress is the three points that the installer draws on the screen. The ISO image is mounted in Virtual CloneDrive and the virtual DVD drive letter is connected in the VI client. I have the same issue with the RC0 build of Windows Server 2008. Vmware.log contains the following entries: … Nov 22 18:38:10.524: vmx| VIDE CDROM: Emulating Inquiry response on raw drive Nov 22 18:38:10.524: vmx| VIDE CDROM: Emulating Inquiry response on raw drive Nov 22 18:38:10.525: vmx| VIDE CDROM: Emulating Inquiry response on raw drive … The client CD-ROM is configured as Pass through IDE. In the past I was able to install the RC0 build without any problems. The only change that I’m aware of is that I recently installed the ESX patches from November 15. Is anybody able to install the Windows Server 2008 November CTP build or the RC0 build and how do you assign the ISO to the guest?
Have you configured the disks in a hardware RAID set? I had this issue with a Intel S5000PSL based system.
Do you have the RAID activation key and the RAID memory? http://www.vmware.com/community/thread.jspa?messageID=590577 Message was edited by: J-H
I have several SCSI related messages in /var/log/vmkernel. Is my assumption correct that these error messages are VMkernel messages that are not specific to the SCSI commands issued on behalf of... See more...
I have several SCSI related messages in /var/log/vmkernel. Is my assumption correct that these error messages are VMkernel messages that are not specific to the SCSI commands issued on behalf of one VM guest? Where do I find a documentation about the SCSI error codes and the format of the VMKernel error messages? The configuration is an Intel S5000PSLROMB motherboard with the hardware RAID controller SROMBSAS18E and SATA disks, Samsung HD501LJ (SpinPoint T) , attached. I know that only my motherboard and the RAID controller is supported but it is not supported to host a VMFS on SATA disks. I tried to update the motherboard BIOS to version 79, but I had to go back to Version 74 because otherwise the megaraid_sas driver did not load during the server boot. Do you know if these error messages would very likely also appear with other SATA disks that are sold as “RAID edition” like Seagate ST3500630NS (Barracuda ES, RAID-Edition). ## Aug 13 14:42:02 pc3 vmkernel: 1:03:41:06.950 cpu5:1032)LinSCSI: 3616: Aborting cmds with world 1024, originHandle 0x52032d0, originSN 410281 from vmhba0:2:0 Aug 13 14:42:02 pc3 vmkernel: 1:03:41:06.950 cpu5:1032)LinSCSI: 3632: Abort failed for cmd with serial=410281, status=bad0001, retval=bad0001 Aug 13 14:42:56 pc3 vmkernel: 1:03:42:00.978 cpu5:1032)SCSI: 3731: AsyncIO timeout (5000); aborting cmd w/ sn 425475, handle 5639/0x52032d0 Aug 13 14:42:56 pc3 vmkernel: 1:03:42:00.978 cpu5:1032)LinSCSI: 3616: Aborting cmds with world 1024, originHandle 0x52032d0, originSN 425475 from vmhba0:2:0 Aug 13 14:42:56 pc3 vmkernel: 1:03:42:00.978 cpu5:1032)LinSCSI: 3632: Abort failed for cmd with serial=425475, status=bad0001, retval=bad0001 Aug 13 14:43:45 pc3 vmkernel: 1:03:42:50.096 cpu4:1113)VSCSI: 2604: Creating Virtual Device for world 1114 vscsi0:0 Aug 13 14:43:45 pc3 vmkernel: 1:03:42:50.096 cpu4:1113)SCSI: 1271: Set shares value for world 1114 to 0x3e8 Aug 13 14:43:54 pc3 vmkernel: 1:03:42:59.681 cpu3:1114)SCSI: 215: Invalid Opcode (0xa0) Aug 13 14:57:12 pc3 vmkernel: 1:03:56:16.917 cpu3:1114)SCSI: 169: STOP_UNIT cmd issued to virt dis Aug 13 14:57:22 pc3 vmkernel: 1:03:56:26.861 cpu2:1114)SCSI: 215: Invalid Opcode (0xa0) Aug 13 14:58:13 pc3 vmkernel: 1:03:57:17.922 cpu1:1081)SCSI: 215: Invalid Opcode (0xa0) ## Thanks.
What board do you exactly have? If you have the SL5000PSLROMB, then you need the hardware RAID activation key and additional memory for the controller. http://www.vmware.com/community/message.j... See more...
What board do you exactly have? If you have the SL5000PSLROMB, then you need the hardware RAID activation key and additional memory for the controller. http://www.vmware.com/community/message.jspa?messageID=590583
I'm currently running several 64 bit versions and the only problem that I have is the CDROM driver http://www.vmware.com/community/thread.jspa?messageID=637492&#637492
You have to differentiate between what works and what is supported. SATA is not supported according to the HCL to store VMDK files, but it works if your controller masks the SATA disk as a SCSI... See more...
You have to differentiate between what works and what is supported. SATA is not supported according to the HCL to store VMDK files, but it works if your controller masks the SATA disk as a SCSI disk. This is okay for testing purposes but not recommended for production use. One of my test systems is using for example the LSI Logic MegaRAID 150-4. You may want to read this web site for a list of controllers that mask SATA disks as SCSI. http://vmprofessional.com/index.php?content=sata_faq You might also run into issues that you select a supported controller, but this controller only works if you enable hardware RAID support. http://www.vmware.com/community/message.jspa?messageID=590583
I have tried the installation with and without passthrough. The only way I was successful previously was using Virtual CloneDrive as installation device. But this does not solve the issue that t... See more...
I have tried the installation with and without passthrough. The only way I was successful previously was using Virtual CloneDrive as installation device. But this does not solve the issue that the “DVD/CD-ROM NECVMWar VMware IDE CDR00 ATA Device” inside the VM fails. I would prefer a VM that has a DVD/CDROM drive.
The TimeOutValue was already decimal 60 and changing it to a higher value, for example, decimal 600 did not solve the problem.
I’m trying to do some self study with VCB. I do not have a SAN so I have to use iSCSI and the software initiator. I know it is not supported. There are a few posts that others have also tried it.... See more...
I’m trying to do some self study with VCB. I do not have a SAN so I have to use iSCSI and the software initiator. I know it is not supported. There are a few posts that others have also tried it. I have no problem to use vcbMounter to do a full VM backup using –t fullVM. If I try a file level mount using –t file then the snapshot is created of the VM but at the time vcbMounter tries to mount the disk the VCB proxy nearly freezes. In the event viewer of the VCB proxy several error messages are available “The device, \Device\Scsi\symmpi1, did not respond within the timeout period.” The VCB proxy is a VM on ESX 3.01 running W2K3 Sp2 x86 using the Microsoft Initiator 2.04. The iSCSI target is a VM on VMware Server running openSUSE 10.2 with IET 0.4.15. Any tips are appreciated how I can solve the problem, or the information that I’m not the only one that runs into this issue and it cannot be fixed. Thanks
Using the 32 bit version of vista and longhorn works fine with the cdrom driver provided by PaulVCP referenced in http://www.vmware.com/community/thread.jspa?messageID=633267. With the 64 bit ... See more...
Using the 32 bit version of vista and longhorn works fine with the cdrom driver provided by PaulVCP referenced in http://www.vmware.com/community/thread.jspa?messageID=633267. With the 64 bit version of vista and longhorn the cdrom driver issue is still more than annoying. I tried several approaches using a local dvd device on the ESX server, connecting to a ISO on the VI client, and connecting to a virtual CDROM provided by Daemon tools on a W2K3 server – all approaches failed. I finally managed to install longhorn beta 3 using the virtual CDROM provided by Virtual CloneDrive on my laptop running Vista. Does somebody have a cdrom driver for the x64 versions of longhorn and vista? It would be more than appreciated if VMware would make a 64 bit and 32 bit driver available. Okay, longhorn is not released yet, but vista is released since more than a few months and it should not be too difficult for VMware to create the necessary drivers. I know we can complain about Microsoft making these drivers necessary with the new operating systems. Maybe somebody will say this was done by intention. Anyhow, this does not solve the problem and the best VMware can do is providing the necessary drivers. The current situation that ESX customers face when they try to install a major operating system, like Vista and Longhorn, is an excellent argument for VMware’s competition to tell customers they should not use ESX. Therefore, I’m wondering why this situation is accepted since months. VMware please provide the 64 bit versions of these drivers – it is for your advantage!
I had a similar issue with a storage controller using a LSI chip. I could not create a vmfs until I bought a RAID activation key and setup the disk as a RAID 0 volume. http://www.vmware.com/comm... See more...
I had a similar issue with a storage controller using a LSI chip. I could not create a vmfs until I bought a RAID activation key and setup the disk as a RAID 0 volume. http://www.vmware.com/community/message.jspa?messageID=590583