Re: [Vol-users] Windows Server 2008

Hi guys! most of the work i've done is using ESXi IIRC. I could check exactly when I get back to work but unfortunately it wont be until Sunday. I also saw it happen using VMware Workstation 8 (and there's also a tool attached that converts vmss to vmem files starting at that version. that was up until now the only way i knew of to read memory out of vmss/n files) so I guess ESX versions close to or above the VMWare 8 release date(which is, I guess, relatively new). i could also try it on a vmware workstation 8 when i get to work, if we won't figure it out by then. While searching for the vmss thingy I think I noticed VMware saying it's the new format they're going to use from now on (tho they could change their mind). AAron - actually it was quite rare, but the first vmss I used to test the patch had two or three, which made my patch break when i first tested it on other VMs. I could try to pinpoint it, but i guess it would be easier for me to reverse the vmware code than try it manually :) A thing to note is that that vmss also had two virtual CPUs, which might have caused having more than one region. it also had ~4G of RAM. most of the other VMs i used only had about 512M. did you try to run it on other vmss files that resemble the one i described? i used to have a contact at vmware a while back, but i don't think it would be legit to ask him. maybe we could post at the vmware support site? any of you ever done that? are they responsive to this kind of questions? - Nir On Fri, Jul 6, 2012 at 2:32 AM, AAron Walters <awalters(a)4tphi.net> wrote: