Page 1 of 1
Windows Server 2003 Guest
Posted: 26. Jun 2014, 16:14
by Gekkotypezero
This is my first time trying to load a Guest OS (Windows Server 2003) on Virtual Box. I'm using Shadow Protect on Server 2, running Windows Server 2003, which created a full backup. On Server 1, I'm using Virtual boot to basically upload the full backup into Virtual Box. When Virtual Box comes up, I see Windows Server 2003 loading screen. So I can tell that it's trying to load. Except that after a one minute wait time, a critical error message appears and shuts down the VM. I've attached the log file and png. I'm wondering if anyone can tell me what I'm doing wrong and how to solve this issue. Thank you.
Re: Windows Server 2003 Guest
Posted: 26. Jun 2014, 16:17
by mpack
VBox.log wrote:
00:00:01.544567 Host RAM: 4095MB total, 2104MB available
...
00:00:01.869609 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 GB)
...
00:02:28.523495 Console: VM runtime error: fatal=false, errorID=HostMemoryLow message="Unable to allocate and lock memory. The virtual machine will be paused. Please
Your host does not have enough RAM to allow you to dedicate 4GB to the guest, in fact that's more than your hosts total RAM. It's only a 32bit VM, I suggest you try giving it 512MB. OTOH I would also increase the graphics RAM to something reasonable, e.g. 32MB.
Re: Windows Server 2003 Guest
Posted: 26. Jun 2014, 17:42
by Gekkotypezero
Following your advice, I was able to get passed the Windows Server 2003 Loading screen, but received a BSOD. "Unmountable Boot Volume"
Re: Windows Server 2003 Guest
Posted: 26. Jun 2014, 17:58
by mpack
VBox.log wrote:
00:00:01.424864 File system of 'G:\ShadowProtect\SERVER2x_Disk_0_VM_{86839926-06cc-427e-88ea-5b0e20103490}_HD_{b7cf477f-a3a4-45b7-bc7f-877dd9afb92b}.XSP' is ntfs
I'm not familiar with an "XSP" file. What is it really?
VBox.log wrote:
00:00:17.332998 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_ERROR iSector=0x37e8f cSectors=0x1)
00:00:22.332219 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_ERROR iSector=0x37e8f cSectors=0x1)
etc
A Windows boot volume can't be located on a read-only host partition, and you need write permission.
Re: Windows Server 2003 Guest
Posted: 26. Jun 2014, 18:19
by Gekkotypezero
XSP files are those files which contain information about your ShadowProtect backups. That I know of, Virtual Boot by Shadow Protect takes the backup and turns it into a XSP file then with an addon, throws it into Virtual Box to be loaded into a Virtual Environment. You stated that I need write permissions, exactly how do I do that in Virtual Box?
Re: Windows Server 2003 Guest
Posted: 26. Jun 2014, 18:39
by mpack
Gekkotypezero wrote:You stated that I need write permissions, exactly how do I do that in Virtual Box?
You don't. File and folder permissions are managed by the host OS.
Re: Windows Server 2003 Guest
Posted: 27. Jun 2014, 06:28
by BillG
Gekkotypezero wrote:XSP files are those files which contain information about your ShadowProtect backups. That I know of, Virtual Boot by Shadow Protect takes the backup and turns it into a XSP file then with an addon, throws it into Virtual Box to be loaded into a Virtual Environment. You stated that I need write permissions, exactly how do I do that in Virtual Box?
For a proprietary solution like that I would contact them. It sounds like a Storagecraft problem rather than a VirtualBox one to me.
Re: Windows Server 2003 Guest
Posted: 27. Jun 2014, 16:43
by Gekkotypezero
Thank you mpack and Bill for the assist. It was a proprietary issue. Apparently Shadow Protect is not compatible with the latest version of Virtual Box. The most current version that they support is version 4.3.2 r90405. After uninstalling the latest version of VB and installing the older version, I was able to properly boot into the image that Shadow Protect created.