virtualbox.org

It doesn't look like any of us can tell you why it doesn't work.

I would strongly suggest you create a bug ticket, and _attach_ a machine log file to the ticket.

http://www.virtualbox.org/wiki/Bugtracker

Only one problem, even though I am logged it it still says that I need ticket create priviliges. How do I get that?

MCP

The forum and bug tracking system do not share usernames/passwords.

You need to create a new username to create a bug ticket.

http://www.virtualbox.org/register

Stéphane

The BSOD on your Windows Guest could be due to the PIIX setting. Change it from PIIX4 to PIIX3 and see how that goes.

mcp:
Please post what kind of error you get. Did you try to run '/etc/init.d/vboxdrv setup' as root? It's possible that the kernel module was not build properly.

Sasquatch wrote:The BSOD on your Windows Guest could be due to the PIIX setting. Change it from PIIX4 to PIIX3 and see how that goes.

mcp:
Please post what kind of error you get. Did you try to run '/etc/init.d/vboxdrv setup' as root? It's possible that the kernel module was not build properly.

Since I had ver. 2.06 setup and working properly I just installed 2.1 over it. It seems to install just fine. I then open the application and click to start my vm. That is where I have a problem. The window opens but I don't get the vbox splash screen it just closes and either reports aborted for one of my vm's or running for the other. Either way nothing else happens.

I did try changing the vm from PIIX4 to PIIX3 and it did not make any difference. I've never tried running 'etc/init.d/vboxdrv setup'. What would that do different? How would you suggest I proceed?

MCP

mcp wrote:I've never tried running 'etc/init.d/vboxdrv setup'. What would that do different? How would you suggest I proceed?

It would not make a difference. The error would show up before that if the kernel driver had not been setup yet.

My suggestion to proceed: create a ticket, and _attach_ to the ticket some example .log files from when the guest has shut down and is in the "aborted" state. From within the VB GUI, CTRL+L should bring up the last 4 logs.

Stéphane

Sasquatch wrote:The BSOD on your Windows Guest could be due to the PIIX setting. Change it from PIIX4 to PIIX3 and see how that goes.

Yes! Thank you my friend. I had the exact same problem as Prognatus and changing to PIIX3 got my XP guest to boot correctly.

What are these PIIX thingies anyway?!?

Frank Mehnert wrote:Actually I cannot access these log files. Could you just open a bug report and append (NOT cut'n'paste) these log files?

I'd be only happy to oblige, but I can't seem to find the log files anywhere on disk.

stephanecharette wrote:My suggestion to proceed: create a ticket, and _attach_ to the ticket some example .log files from when the guest has shut down and is in the "aborted" state. From within the VB GUI, CTRL+L should bring up the last 4 logs.

Yes, I see them there, but since I'm not going to cut & paste from there, and don't know where to find the logs, how do I attach these files?

Sasquatch wrote:The BSOD on your Windows Guest could be due to the PIIX setting. Change it from PIIX4 to PIIX3 and see how that goes.

I tried that before posting here. No change.

Prognatus wrote:I'd be only happy to oblige, but I can't seem to find the log files anywhere on disk.
...
Yes, I see them there, but since I'm not going to cut & paste from there, and don't know where to find the logs, how do I attach these files?

On linux-based systems, look at /home/username/.VirtualBox/Windows XP/Logs/VBox.log*

Stéphane

Maybe my observations relate to the same root cause:

I was able to install my Warp 4.5 under VBox 2.1.0 from scratch. However there seem to be some problems with the harddisk emulation:

Without prior installing the boot manager, booting hangs on a black screen.

With having the boot manager installed I get a warning message - before boot manager menu shows up:

"Drive 1 is not ready. Press any key."

After just pressing 'Enter' boot manager menu shows up and booting proceeds normally.
(I have tried all: PIIX3 and PIIX4, with/without IO-APIC, with/without ACPI, ...)

Ingo

Anybody know if this issue is fixed in version 2.4? I tried to install 1.66, but it crashes in the same way. Will now try to install v1.64 and restore my backup.vdi from using that version. If nothing works after that, I have to look for alternatives to VirtualBox and install the Windows client from scratch again.

Hmm... I just read in another thread that someone said it's important to turn on hardware virtualization (vt) in the BIOS. One of the reasons I chose VirtualBox in the first place is that my PC doesn't have a processor that supports vt in hardware. Is it true that support for non-vt processors are removed from the product? If so, in which version was it removed?

Prognatus wrote:Hmm... I just read in another thread that someone said it's important to turn on hardware virtualization (vt) in the BIOS. One of the reasons I chose VirtualBox in the first place is that my PC doesn't have a processor that supports vt in hardware. Is it true that support for non-vt processors are removed from the product? If so, in which version was it removed?

If they would remove it, they would shoot themselves in the foot. There are tons of users who don't have hardware virtualization in their CPU, myself included. Or the CPU does it, but the mainboard doesn't (my laptop for example). It's only needed if you want to run 64 bit Guests.