ahem, update 1 fixes the vga hang issue, but the performance is still pants
Performance of what? As a VM it's fine, the only slow part is the console, which is fine if you only use it to get far enough for RDP to work.Originally Posted by oxide54
I've got about 12 R2 VMs with no performance issues.
sorry yes that what i meant the performance of the console is slow.
rdp doesn't work very well over our vpn, vsphere is fine.
the performance was still quite rubbish over rdp, then i noticed I had only give it 1 VCPU.
with 1 VCPU cpu = 100% constant and 3.25gb memory in use all the time.
with 2 VCPU cpu = 0% constant and 711mb
weird.
sorry the reboot just seemed to fix it for a bit.
its eating cpu, and memory usage is back to 3.25gb but task manager isn't showing any app as using the memory. and the cpu is blamed on system process. weird.
found something about the intel nic driver that comes with 08 r2 not working very well, and updated it but it hasn't helped. would make sense though if a kernel driver is eating all the memory then no app would show as using it.
was the emulated intel nic,
I removed it and added a vmxnet and all seems well now, lets hope it stays that way.
it does seem sooo much more responsive.
I noticed the same with Windows XP Machines, assigned 1GB ram, and it would eat all its allocated RAM, reporting falsely. U1 fixed this.
even on update one i still had problems, but i wiped it and put a server core install on which is running nicely now.
We are not running esx4 u1 yet and have noticed that one of our 2008 R2 enterprise servers doesnt come back online for about 30 minutes after a reboot. Don't understand why it takes so long.
Is there a guide which can guide me to do the upgrade to esx4 u1?
Any tips and things to avoid when doing this upgrade? I have got 3 esx hosts to upgrade.
Thanks
All i did was shut down the VM's, pulled the fibre lead out, put the CD in and said install. Was really painless.
Are you sure this is Vsphere related ? I have seen this issue as well and it was due to wrong DNS configuring on the domain controllers. They should point to each other and the 127.0.0.1 ip should be configured as well.
PS : We migrated to U1 this week. and untill now everything runs smoothly
bio..
Is anybody's 2008 R2 in ESXi 4.0 U1 running sluggishly slow?
Like the mouse stutters etc.
Furthermore, would anyone think of having the 2008 R2 as the primary DC and the secondary DC sitting on a physical server? Anyone done such a thing?
Read the rest of the thread!!
Install VMware tools and enable remote desktop / open firewall for remote desktop. and then use remote desktop to connect to the VM. its the VM console that slow not the actual vm itself.
Thanks. I thought there was a fix considering the first post was made back in November.
update 1 is the fix, as you'll see when you select the operating system type it now says Windows 2008 R2 without experimental in brackets.
it does fix the "problem" but the console is still quite painfull to use, but kind of always has been with esx.
my 2003 vm's are always connected to with VNC, and the 2008 ones remote desktop.
with a sysprep'd ghost image / vm template you should only really need the console to setup the template.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote