Custom Query (16363 matches)
Results (1747 - 1749 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9297 | obsolete | VM crashes after trying to play a video on Win7 guest | ||
| Description |
Host OS: Linux Mint 10 64-bit (Compiz on), nvidia drivers 260.19.06
Effect:
|
|||
| #9302 | obsolete | FreeDOS - uide (CD-ROM support) problems | ||
| Description |
Referring to Virtual Box error message #9191: As already mentioned in the message 9191, uide.sys, a driver in FreeDOS, which supports SATA HDs and CD-ROMs (=replacement for oakcdrom.sys in older Win9x systems) has the problem, that it "hangs" for in about 2 minutes and then exits with the message: EDD BIOS data ERROR, Disk 80h. It works fine from a real boot disk in a real machine - and it works fine from vmware. I talked with the programmer of uide.sys, Jack Ellis and got the following response: There seem to be 2 problems: First, they do not provide "EDD BIOS" data, which tells me the I-O device addresses for each hard disk. I need those addresses to "match" with the controller I-O addresses found during UIDE's PCI scan. Second, they appear not to support an "Identify ATA Device" command,
If UIDE gets no reply to that command, it will "time out" after a long time. You can check this bug report with one of my prepared small ISO images fdosboot_106.iso or fdosatwork_106.iso which can be downloaded from my website: www.bootablecd.de/downloads/bootablecd/fdosboot_106.iso or www.bootablecd.de/downloads/bootablecd/fdosatwork_106.iso (both are in about 1,5 MB in size). Please note that uide.sys requires 80 MB RAM without any set options, so the RAM settings of virtual box for DOS should be at least at 96 MB!!! A second thing I noticed with FreeDOS and virtual box: When you boot one of these ISO images and try to create a virtual HD with fdisk you have to run fdisk twice (instead of one time as usual). After the first time it reports an error message. First fdisk and then fdisk /mbr as fdisk seems to be not able to write the MBR at the first execution. Thanks. |
|||
| #9303 | obsolete | Cannot clone VM using VBox 4.1.0 because 'VBoxGuestAdditions.iso already exists' -> Fixed in SVN | ||
| Description |
Discussed in community here: http://forums.virtualbox.org/viewtopic.php?f=1&t=43313&p=195119#p195119 I have a problem when using VBox 4.1.0 to clone a VM. I chose to clone the current state of one of my VM's and left the check box 'Reinitialize the MAC address of all network cards' clear. I saw: "Failed to clone the virtual machine <name>.
Cannot register the image ‘C:\Proqram FiIes\OracIe\VirtuaIBox\VBoxGuestAdditionsiso'
with UUID { <number> } because a CD/DVD image ‘C:\Proqram FiIes\OracIeVirtuaIBox/VBoxGuestAdditions.iso’
with UUID { <number> } already exists.
I then removed the guest additions ISO from the IDE Controller Storage Tree in Settings > Storage but I still got the same error. I then tried to remove the guest additions ISO from Media Manager because it says that the iso is attached to snapshots 8 and 9 of my VM, but the 'Remove' button and menu options are disabled (greyed out). perryg suggested: Yes I have seen this very thing. You need to release the image from all of the snapshots as well. Usually this can be done in the media manager by selecting release for the guest additions . If however this does not work you need to start the snapshot and then use the device tab to remove it in each snapshot that still has it mounted. This has been reported before and AFAIK it was resolved, but now it appears that it has returned. I have not succeeded in doing this yet. So, in summary, the GUI clone tool does not work for my VM. |
|||

