Custom Query (16363 matches)
Results (2146 - 2148 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2198 | fixed | Error in UG sec 1.2 -> fixed in 2.0.2 | ||
| Description |
UG Section 1.2 states "if you want to run 64-bit guest operating systems (a feature added with VirtualBox 2.0), since all 64-bit CPUs ship with hardware virtualization anyway." This is not correct. Some low end 64-bit chips (e.g. the Celeron E1200) and many older 64bit CPUs do not support VT-x. Also the motherboard BIOS must enable VT-x/AMD-V for it to be recognised. As a result we're getting forum members who have read this and therefore assume that they can use 64bit guests because they have a 64bit chip. |
|||
| #2199 | fixed | vboxmanage registervm ... does not look in current directory | ||
| Description |
When I attempt to import/register an xml file by executing vboxmanage registervm vb-xpp-sp2.xml, it does not look in the current directory for vb-xpp-sp2.xml. It looks for it in my user directory instead. Note pathes from command line and error below. D:\virtual.machines\virtual.box\hosts\vb-xpp-sp2>vboxmanage registervm vb-xpp-sp2.xml VirtualBox Command Line Management Interface Version 2.0.0 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. [!] FAILED calling virtualBox->OpenMachine(Bstr(argv[0]), machine.asOutParam()) at line 3089! [!] Primary RC = E_FAIL (0x80004005) - Unspecified error [!] Full error info present: true , basic error info present: true [!] Result Code = E_FAIL (0x80004005) - Unspecified error [!] Text = Could not lock the settings file 'E:\Documents and Settings\psmith\.VirtualBox\vb-xpp-sp2.xml' (VERR_FILE_NOT_FOUND) [!] Component = Machine, Interface: IMachine, {1e509de4-d96c-4f44-8b94-860194f710ac} [!] Callee = IVirtualBox, {557a07bc-e6ae-4520-a361-4a8493199137} |
|||
| #2200 | obsolete | Altiris Imaging of Windows Guest through PXE disconnects after a short time | ||
| Description |
Using Virtualbox 2.0.0 on Windows XP SP3 host, attempting to image a Windows XP SP3 Guest (Though no OS yet installed) using an Altiris PXE Server. PXE server is on the local network. I created a virtual network interface through VirtualBox, and bridged it with my existing LAN connection. Booting the VM from network successfully finds the PXE server. It successfully loads the DOS PXE OS, and begins imaging. Network speed is very slow, and eventually the imaging fails due to 'corrupt image or partition'. I have tried the following steps: (Altiris KB articles: https://kb.altiris.com/display/1n/kb/article.asp?aid=17448&n=9&s=) Unfortunately they make no difference. Thought the VM will boot successfully to PXE through the bridged network connection, it seems that the speed is too slow or that the connection gets too many errors to successfully download the image file. |
|||

