Ok, so I do have some problem with windows 7... I've created two windows XP machines and they work just fine but when trying windows 7, it never acknowledges the IP, I just get the following in /var/log/messages...and when I open the image up on vmware it seems just fine, looks like it's using lsi logic and just sits at the login screen...:
Apr 20 00:29:43 vcl /usr/lib/vmware/bin/vmware-hostd[15093]: Accepted password for user root from 127.0.0.1 Apr 20 00:30:15 vcl last message repeated 12 times Apr 20 00:30:22 vcl last message repeated 3 times Apr 20 00:30:22 vcl kernel: device eth0 entered promiscuous mode Apr 20 00:30:22 vcl kernel: bridge-eth0: enabled promiscuous mode Apr 20 00:30:24 vcl /usr/lib/vmware/bin/vmware-hostd[15093]: Accepted password for user root from 127.0.0.1 Apr 20 00:30:29 vcl last message repeated 2 times Apr 20 00:30:55 vcl dhcpd: DHCPDISCOVER from 00:50:56:1a:01:03 via vmnet1 Apr 20 00:30:55 vcl dhcpd: DHCPOFFER on 192.168.1.2 to 00:50:56:1a:01:03 via vmnet1 Apr 20 00:31:00 vcl dhcpd: DHCPDISCOVER from 00:50:56:1a:01:03 via vmnet1 Apr 20 00:31:00 vcl dhcpd: DHCPOFFER on 192.168.1.2 to 00:50:56:1a:01:03 via vmnet1 Apr 20 00:31:08 vcl dhcpd: DHCPDISCOVER from 00:50:56:1a:01:03 via vmnet1 Apr 20 00:31:08 vcl dhcpd: DHCPOFFER on 192.168.1.2 to 00:50:56:1a:01:03 via vmnet1 Apr 20 00:31:24 vcl dhcpd: DHCPDISCOVER from 00:50:56:1a:01:03 via vmnet1 Apr 20 00:31:24 vcl dhcpd: DHCPOFFER on 192.168.1.2 to 00:50:56:1a:01:03 via vmnet1 Apr 20 00:31:56 vcl dhcpd: DHCPDISCOVER from 00:50:56:1a:01:03 via vmnet1 Apr 20 00:31:56 vcl dhcpd: DHCPOFFER on 192.168.1.2 to 00:50:56:1a:01:03 via vmnet1 Apr 20 00:32:00 vcl dhcpd: DHCPDISCOVER from 00:50:56:1a:01:03 via vmnet1 Apr 20 00:32:00 vcl dhcpd: DHCPOFFER on 192.168.1.2 to 00:50:56:1a:01:03 via vmnet1 Apr 20 00:32:09 vcl dhcpd: DHCPDISCOVER from 00:50:56:1a:01:03 via vmnet1 Apr 20 00:32:09 vcl dhcpd: DHCPOFFER on 192.168.1.2 to 00:50:56:1a:01:03 via vmnet1 Apr 20 00:32:26 vcl dhcpd: DHCPDISCOVER from 00:50:56:1a:01:03 via vmnet1 Apr 20 00:32:26 vcl dhcpd: DHCPOFFER on 192.168.1.2 to 00:50:56:1a:01:03 via vmnet1 On Tue, Apr 19, 2011 at 12:48 AM, Tyler Hardesty <tharde...@gmail.com>wrote: > Man, sorry to take up space but I actually found it here in the month of > April. I changed the logic type in vmware to lsi logic SAS and it powered up > just fine... so tomorrow I'll try and create a new image and double check to > make sure its set to lsi logic and not lsi logic sas. If that still doesn't > work I'll let you know. > > > On Tue, Apr 19, 2011 at 12:23 AM, Tyler Hardesty <tharde...@gmail.com>wrote: > >> Oh, follow-up, I didn't even bother checking the machine on vmware before. >> So I just did now and when windows 7 tries to boot it goes into start up >> repair. When going through the archive I think I remember seeing someone >> else with the problem and I think it got resolved?! But I just can't find it >> now, if anyone knows which month it's under (if it even exists) just let me >> know and I'll be happy to try some more trouble shooting and researching on >> my own. >> >> >> On Tue, Apr 19, 2011 at 12:09 AM, Tyler Hardesty <tharde...@gmail.com>wrote: >> >>> Is there anything different between windows xp and windows7 that would >>> cause windows 7 not to respond to dhcp? I have my windows XP image and >>> everything works fine so I decided to set up a Win7 machine to test it >>> out... the image captures fine but when trying to reserve it, it gives me >>> the same not responding to ssh message I had before. I checked the >>> /var/log/messages and it never shows a offer/request/ack message for the IP >>> like it does when I reserve the windows XP image. >> >> >> >
