> Same Virtual Machine running ok at Intel Centrino (Dell Inspiron 630m)
> when
> runs at AMD athlon X2 (Dell Latitude D531) causes host computer to crash
> and
> reboot.
> I have tried 2 identical computers and the result is the same.
> So looks like is something related to VPC 2007.
> Host windows xp pro sp2.
> VM windows xp pro sp2.
> VPC 2007 6.0.192.0
>
> Someone have a clue???
> Thanks

> Are your BIOS and mainboard drivers up to date?
>
> "Antonio" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Same Virtual Machine running ok at Intel Centrino (Dell Inspiron 630m)
> > when
> > runs at AMD athlon X2 (Dell Latitude D531) causes host computer to crash
> > and
> > reboot.
> > I have tried 2 identical computers and the result is the same.
> > So looks like is something related to VPC 2007.
> > Host windows xp pro sp2.
> > VM windows xp pro sp2.
> > VPC 2007 6.0.192.0
> >
> > Someone have a clue???
> > Thanks
>

> Colin,
>
> I am using 2 Brand new Dell laptops..I got them last week!!
> Host windows is up to date, But I will check BIOS and drivers.
> Thank you
>
> "Colin Barnhorst" wrote:
>
> > Are your BIOS and mainboard drivers up to date?
> >
> > "Antonio" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> > > Same Virtual Machine running ok at Intel Centrino (Dell Inspiron 630m)
> > > when
> > > runs at AMD athlon X2 (Dell Latitude D531) causes host computer to crash
> > > and
> > > reboot.
> > > I have tried 2 identical computers and the result is the same.
> > > So looks like is something related to VPC 2007.
> > > Host windows xp pro sp2.
> > > VM windows xp pro sp2.
> > > VPC 2007 6.0.192.0
> > >
> > > Someone have a clue???
> > > Thanks
> >

>I just updated my BIOS.
>I had D531 A04 bios, and now I have the latest D531 A05.
>Also updated all available AMD drivers from Dell website.
>
>I did that in my 2 machines, and... ...STILL NOT WORKING!!!
>

> On Thu, 12 Jun 2008 08:41:03 -0700, Antonio
> <(email address - cut out)> wrote:
>
> >I just updated my BIOS.
> >I had D531 A04 bios, and now I have the latest D531 A05.
> >Also updated all available AMD drivers from Dell website.
> >
> >I did that in my 2 machines, and... ...STILL NOT WORKING!!!
> >
> What happens if you disable hardware virtualization in the BIOS?
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
> I do not work for Microsoft.
>

> On Thu, 12 Jun 2008 10:51:03 -0700, Antonio
> <(email address - cut out)> wrote:
>
> >I have disabled VIRTUALIZATION in the BIOS in both machines.
> >Still not working...
> >
> >I have 3 diferent VM, and when I start any of them, it freezes the host.
> >The same VM files runs ok on a machine with Intel Centrino.
> >
>
> I would do as follows (don't know if that is what you did):
> - Create a *new* virtual machine on the new host PC
> - When it asks for the virtual disk point it to the one you have moved
> from the other PC
>
> This will at least make sure that the machine built on the new host is
> compatible hardware-wise with the host itself.
>
> Maybe it will run better now?
>
> --
>
> Bo Berglund (Sweden)
>

>I have disabled VIRTUALIZATION in the BIOS in both machines.
>Still not working...
>
>I have 3 diferent VM, and when I start any of them, it freezes the host.
>The same VM files runs ok on a machine with Intel Centrino.
>

> Bo, I did that already..still the same
> I have created a new VM and called " Test" ..and used the Virtual Hard Drive
> I had.
>
> I will try to build a whole new VM and VHD at the AMD computer.
> But then, imagine if we had to create a new VM on each computer because on
> incompatibility, why use VM so??
>
> Thank you anyways for your help!
>
>
>
> "Bo Berglund" wrote:
>
> > On Thu, 12 Jun 2008 10:51:03 -0700, Antonio
> > <(email address - cut out)> wrote:
> >
> > >I have disabled VIRTUALIZATION in the BIOS in both machines.
> > >Still not working...
> > >
> > >I have 3 diferent VM, and when I start any of them, it freezes the host.
> > >The same VM files runs ok on a machine with Intel Centrino.
> > >
> >
> > I would do as follows (don't know if that is what you did):
> > - Create a *new* virtual machine on the new host PC
> > - When it asks for the virtual disk point it to the one you have moved
> > from the other PC
> >
> > This will at least make sure that the machine built on the new host is
> > compatible hardware-wise with the host itself.
> >
> > Maybe it will run better now?
> >
> > --
> >
> > Bo Berglund (Sweden)
> >

>Bo, I did that already..still the same
>I have created a new VM and called " Test" ..and used the Virtual Hard Drive
>I had.
>
>I will try to build a whole new VM and VHD at the AMD computer.
>But then, imagine if we had to create a new VM on each computer because on
>incompatibility, why use VM so??
>

> On Thu, 12 Jun 2008 12:00:00 -0700, Antonio
> <(email address - cut out)> wrote:
>
> >Bo, I did that already..still the same
> >I have created a new VM and called " Test" ..and used the Virtual Hard Drive
> >I had.
> >
> >I will try to build a whole new VM and VHD at the AMD computer.
> >But then, imagine if we had to create a new VM on each computer because on
> >incompatibility, why use VM so??
> >
>
> Even in a VM, you're not emulating the CPU, there's way too much
> overhead for that, so in VPC/VMWare/etc the CPU is virtualized.
> So, on an AMD system the VMs have an AMD cpu, while on an Intel system
> they have a Intel CPU. If you're using images created on an Intel
> system some OSes install CPU specific kernels. Other issues can occur
> as well, i.e. the XP SP3 issue on AMD-based systems.
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
> I do not work for Microsoft.
>

> Same Virtual Machine running ok at Intel Centrino (Dell Inspiron 630m) when
> runs at AMD athlon X2 (Dell Latitude D531) causes host computer to crash and
> reboot.
> I have tried 2 identical computers and the result is the same.
> So looks like is something related to VPC 2007.
> Host windows xp pro sp2.
> VM windows xp pro sp2.
> VPC 2007 6.0.192.0
>
> Someone have a clue???
> Thanks

>
> > Same Virtual Machine running ok at Intel Centrino (Dell Inspiron 630m) when
> > runs at AMD athlon X2 (Dell Latitude D531) causes host computer to crash and
> > reboot.
> > I have tried 2 identical computers and the result is the same.
> > So looks like is something related to VPC 2007.
> > Host windows xp pro sp2.
> > VM windows xp pro sp2.
> > VPC 2007 6.0.192.0
> >
> > Someone have a clue???
> > Thanks
>
> I also have the Dell Latitude D531...same issue - anything in VPC just crashes the machine.
>
> I just use VMWare Converter and open everything in VMWare player, seems that works (not all the time though)
>
> Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com
>

> On Fri, 19 Dec 2008 02:09:01 -0800, Vilson
> <(email address - cut out)> wrote:
>
>>Hi, Im Vilson here.
>>
>>I am facing the same problem. I am running Window Vista Ultimate 32Bits
>>SP1,
>>AMD Turon 64x2 2.0GB (Acer Aspire 4530 721G16) and VPC 2007 SP1 with a
>>guest
>>OS Window XP SP3 causes host computer to crash and just stuck while
>>installation began in DOS mode for many tries.
>>
>>Anyone can tell me what can i do to solve this problem?
>>
> In almost 100% of the cases where the host PC has experienced BSOD or
> similar in connection to running a guest in VPC2007 it has been caused
> by faultu hardware virtualization.

>
>"Bo Berglund" <(email address - cut out)> wrote in message
>news:(email address - cut out)...
>> On Fri, 19 Dec 2008 02:09:01 -0800, Vilson
>> <(email address - cut out)> wrote:
>>
>>>Hi, Im Vilson here.
>>>
>>>I am facing the same problem. I am running Window Vista Ultimate 32Bits
>>>SP1,
>>>AMD Turon 64x2 2.0GB (Acer Aspire 4530 721G16) and VPC 2007 SP1 with a
>>>guest
>>>OS Window XP SP3 causes host computer to crash and just stuck while
>>>installation began in DOS mode for many tries.
>>>
>>>Anyone can tell me what can i do to solve this problem?
>>>
>> In almost 100% of the cases where the host PC has experienced BSOD or
>> similar in connection to running a guest in VPC2007 it has been caused
>> by faultu hardware virtualization.
>
>If this is so, why would other VMs work? I run VirtualBox all day long,
>every day, with hw virt enabled, and it has never once crashed. I used
>VMWare for a while, likewise worked fine. It is only VPC that will BSOD my
>machine, even with hardware virtualization disabled.
>
> With me, it's mostly when I close the VPC gui itself, not any of the VMs,
>that it will BSOD. That pretty much eliminates hardware virtualization as
>the cause.
>

> VPC, VMWare, and VirtualBox are all different apps, have different
> architecture and are coded different. They do the same thing but
> access the system's resources slightly differently.
>
> It could be a driver issue, have you updated your NIC driver from the
> manufacturer's site?
>
> Are you trying to run 2 different VMs programs at the same time? This
> will cause a crash, only one program can use HW Virt at a time.
>

>Hi, Im Vilson here.
>
>I am facing the same problem. I am running Window Vista Ultimate 32Bits SP1,
>AMD Turon 64x2 2.0GB (Acer Aspire 4530 721G16) and VPC 2007 SP1 with a guest
>OS Window XP SP3 causes host computer to crash and just stuck while
>installation began in DOS mode for many tries.
>
>Anyone can tell me what can i do to solve this problem?
>

> On Fri, 19 Dec 2008 02:09:01 -0800, Vilson
> <(email address - cut out)> wrote:
>
> >Hi, Im Vilson here.
> >
> >I am facing the same problem. I am running Window Vista Ultimate 32Bits SP1,
> >AMD Turon 64x2 2.0GB (Acer Aspire 4530 721G16) and VPC 2007 SP1 with a guest
> >OS Window XP SP3 causes host computer to crash and just stuck while
> >installation began in DOS mode for many tries.
> >
> >Anyone can tell me what can i do to solve this problem?
> >
> In almost 100% of the cases where the host PC has experienced BSOD or
> similar in connection to running a guest in VPC2007 it has been caused
> by faultu hardware virtualization.
>
> So at first:
> In the VPC Console go to File/Options and disable Hardware
> Virtualization.
> Then test if the operation you tried before works better now.
>
> Next if this does not work:
> In the BIOS setup of your host PC disable the hardware virtualization,
> then power down your PC completely and start it again (full power down
> needed for this change).
>
> Now after booting up again, try what you were doing before and see if
> it is now OK. Chances are that the host PC BIOS is not handling
> hardware virtualization correctly and then you need a BIOS update to
> make it work.
> --
>
> Bo Berglund (Sweden)
>