Custom Query (16363 matches)
Results (1438 - 1440 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8648 | duplicate | Restore snapshot produces inconsistent uuids across VirtualBox.xml / MyMachine.xml | ||
| Description |
After restoring a snapshot from the GUI (where Current State is not identical to the snapshot), MyMachine.xml contains an <Image uuid="{}"> tag but the uuid it references does not occur in VirtualBox.xml. (A vmdk file with the corresponding name is created in the Snapshots directory.) This produces the error reported in ticket 8595, when VirtualBox next starts up. (In fact the VirtualBox.xml file is not changed at all; I don't know whether the correct behaviour would be to write the new uuid through to the media registry or to not change it in the machine's own config file, but they certainly shouldn't be getting out of synch.) Attached files: {VirtualBox,BasicUbuntuInstall}.shutdown.xml are the files after I've shut the machine down and exited VirtualBox; .shutdown-restore.xml are from starting the GUI again, restoring the previous snapshot, and exiting the GUI. (Also a logfile is attached, perhaps you'll make more of it than I did.) My details: Host Ubuntu 10.04.2 64-bit, Debian package virtualbox-4.0 (4.0.4-70112~Ubuntu~lucid); guest Ubuntu server. (Not setting properties because I doubt it's relevant -- I've seen forum posts from windows users with apparently the same issue.) |
|||
| #10640 | obsolete | NAT relies on /etc/resolv.conf | ||
| Description |
I'm not filing this a major issue as it was just a deficiency I guess that I found when debugging something. Basically, VirtualBox on a Linux host takes the nameservers from /etc/resolv.conf to pass onto the guest when using NAT. I assume it does some magic when one of those nameservers is 127.0.0.1, and it all works hunky dory, excellent job on that. However, when using the resolvconf package, it is not required to have an /etc/resolv.conf file. You can setup resolvconf in a way that it creates a symlink for you, which AFAIK most distros will do this by default, but the host OS will still lookup DNS just fine without one. For example, the latest release of Linux Mint (maya / 13) on a default install does not have this symlink. This in turn means VMs booted with NAT will not have DNS, since there was no /etc/resolv.conf file for VirtualBox to grok and offer that info to the guest via DHCP. I'm unsure how you are supposed to grok the DNS if it's not in a static file somewhere. There is some talk on the Mint forums that putting the symlink back in place would be a nice thing to do, but it had me wondering if maybe VirtualBox shouldn't rely on it being there if it's not a mandatory file. Perhaps at a minimum, some kind of help/tooltip message when selecting NAT from the options if there is no /etc/resolv.conf file? |
|||
| #4568 | fixed | Crash virtualbox in host when i run second life in GNU/Linux guest -> Fixed in SVN. | ||
| Description |
When i run secondlife native program for linux in a guest machine virtualbox crashed with this message: Sorry but my operating system is in spanish Excepción no controlada en 0x7c920a73 en VirtualBox.exe: 0xC0000005: Infracción de acceso al escribir en la ubicación 0x08ce826a. |
|||

