For the past year I've been using a WinXP-Pro SP3 image on my Ubuntu 8.10 (now 9.04) host without any issues. Ever since upgrading VB from 2.2 to 3.0, however, the XP guest keeps hard-locking at random intervals. I don't think it's lasted more than 24 hours? The only change I made was to include the DX acceleration. Is there some way to troubleshoot this?
For instance, is it possible to remove the DX support?
After 3.0 upgrade, XP guest hard-locks
-
ashyanbhog
- Posts: 2
- Joined: 20. May 2008, 18:47
Re: After 3.0 upgrade, XP guest hard-locks
DirectX cam be enabled or disabled for each VM in settings through Virtualbox GUI
-
nbi
- Posts: 19
- Joined: 6. Jul 2009, 07:24
- Primary OS: Debian other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows XP32, XP64, WIN7-64
Re: After 3.0 upgrade, XP guest hard-locks
You aren't making use of SMP?
I'm getting these hard-locks with more than one CPU. If I configure only 1 CPU for XP then everything is ok again. Other than installing the guest additions I did nothing else such as enabling 3D support. In addition to the hard-locks I'm also noticing very bad warbling with the audio. Just like the hard-locks this goes away when configured for one CPU.
I'm getting these hard-locks with more than one CPU. If I configure only 1 CPU for XP then everything is ok again. Other than installing the guest additions I did nothing else such as enabling 3D support. In addition to the hard-locks I'm also noticing very bad warbling with the audio. Just like the hard-locks this goes away when configured for one CPU.
-
bsmith1051
- Posts: 17
- Joined: 15. May 2007, 23:04
Re: After 3.0 upgrade, XP guest hard-locks
This was initially a 'v2' image so it's never had dual-cpu enabled. Also, even though I selected DX support during the VB 3.0 install it's not enabled in this image.
-
steppnav
- Posts: 6
- Joined: 19. Jul 2009, 05:22
- Primary OS: Ubuntu other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows XP Professional
Re: After 3.0 upgrade, XP guest hard-locks
i might be having just the same behaviour:
Ubuntu 9, Lenovo 3000 N200 laptop, 1 gig of memory, Windows XP Pro as the guest O/S.
I fought like bloody heck to get it to boot in more than just safe mode. In regular Windows mode, It now works ok for a few minutes (sans networking) and then just freezes. I turned on task manager performance graphing just to watch and sure enough, it freezes. The cpu (via top) is pegged for the vm, so it's working hard to do nothing.
I still have all the NIC's disabled in this windows image, but that isn't related. After I get past the freeze up behaviour, I'll address getting networking to work without preventing the bootup.
Any Windoze/virtualbox gurus out there have a magic bullet?
Ubuntu 9, Lenovo 3000 N200 laptop, 1 gig of memory, Windows XP Pro as the guest O/S.
I fought like bloody heck to get it to boot in more than just safe mode. In regular Windows mode, It now works ok for a few minutes (sans networking) and then just freezes. I turned on task manager performance graphing just to watch and sure enough, it freezes. The cpu (via top) is pegged for the vm, so it's working hard to do nothing.
I still have all the NIC's disabled in this windows image, but that isn't related. After I get past the freeze up behaviour, I'll address getting networking to work without preventing the bootup.
Any Windoze/virtualbox gurus out there have a magic bullet?
-
bsmith1051
- Posts: 17
- Joined: 15. May 2007, 23:04
Re: After 3.0 upgrade, XP guest hard-locks
so far the 3.0.1 upgrade has been stable so hopefully they fixed a bug that was causing my lock-ups
stepnav,
Are you saying that your laptop only has 1 GB of physical memory, or does your WinXP VM have 1 GB of virtual memory? If the former then I'd check the Ubuntu System Monitor because the Linux host-OS might be freaking-out for lack of available physical memory.
stepnav,
Are you saying that your laptop only has 1 GB of physical memory, or does your WinXP VM have 1 GB of virtual memory? If the former then I'd check the Ubuntu System Monitor because the Linux host-OS might be freaking-out for lack of available physical memory.