locked
Error starting Virtual Machine,using virtual Vista machine to "Hyper V" into a 2008 core server RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    I have a Core 2008 server setup on a Dell PowerEdge 2950, with the Virtualization Enabled in the BIOS.

    I installed Core 2008, ran the Hyper V update, set up remote access etc and am now able to RDP into the box.

    I then build Vista machine using Virtual PC, running on my XP workstation. I installed the Hyper V manager and updates on the Virtual Vista machine.

    I set the WMI access and modified all the permissions mentioned on the MS website documentation.

    I was able to connect and create a network and two new 2008 servers, in the midst of setting up the print server role on one of the virtual servers, it crashed never to come up again. I let it crash and put my attention to the other machine, soon after it too crahed never to come up again.

    When I am in the hyper v mgnt console i fire up the virtual server only to recive this error:


    [Window Title]
    Virtual Machine Connection

    [Main Instruction]
    The application encountered an error while attempting to change the state of 'SSIPrint'.

    [Content]
    'SSIPrint' failed to initialize.

    Failed to create memory contents file 'C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\1FC88166-6642-46D2-A545-E0CF3773DD60\1FC88166-6642-46D2-A545-E0CF3773DD60.bin' of size 2000 MB.

    [Expanded Information]
    'SSIPrint' failed to initialize. (Virtual machine 1FC88166-6642-46D2-A545-E0CF3773DD60)

    'SSIPrint' failed to create memory contents file 'C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\1FC88166-6642-46D2-A545-E0CF3773DD60\1FC88166-6642-46D2-A545-E0CF3773DD60.bin' of size 2000 MB. (Virtual machine 1FC88166-6642-46D2-A545-E0CF3773DD60)

    [V] See details  [Close]



    I have a feeling if i go ahead and create a new Virtual server it will do the same thing.


    My server has 4GB or RAM i have since given each Virtual server 1GB of RAM to no avail.Ive ran updates on the vista machine to no avail. Ive checked the updates on the server, it has the Hyper V update but would not take the language update (dont think i need it)

    Ive of course rebooted serveral times.


    I have theory's this is cause by the server not being activated,the fact that my vista machine is a virtual machine itself or that i am missing some update.At this point these theorys have no truth or proof based on them, they are all i really have left.

    I ve been searching the forums and documentation to no avail.

    Any suggestions would be greatly appreciated.

    -jf
    Friday, August 29, 2008 9:09 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm running a very similar setup myself, although with a genuine (not virtualised) vista-business system as my 'control' station (it's my desktop workstation)

    I ended up abandoning CORE because I would have been the only one here that knows how to adminster the box if there was an issue.   So I'm running full version of 2008 as the host OS at this point.

    First of all, the errors seem to be coming purely from the host system, so I'd not worry about the problem being in your vista virtual box.

    The errors are all related to creating files, so one of the first things I'd be checking is the health of the disks in that system, free-space, etc.    The memory contents file is used to hold a copy of the systems memory, and is I believe used when the machine is snapshotted or suspended in any way.

    I don't know if the system not being registered would cause that to happen, but the first thing I'd check is free-space on the C: drive,    That could be a problem in some setups where perhaps you intendeed c: to be just for host OS, and d: for app data..
    --Chuck
    • Proposed as answer by Chang Yin Monday, September 1, 2008 10:18 AM
    • Marked as answer by Chang Yin Friday, September 5, 2008 11:02 AM
    Friday, August 29, 2008 10:45 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm running a very similar setup myself, although with a genuine (not virtualised) vista-business system as my 'control' station (it's my desktop workstation)

    I ended up abandoning CORE because I would have been the only one here that knows how to adminster the box if there was an issue.   So I'm running full version of 2008 as the host OS at this point.

    First of all, the errors seem to be coming purely from the host system, so I'd not worry about the problem being in your vista virtual box.

    The errors are all related to creating files, so one of the first things I'd be checking is the health of the disks in that system, free-space, etc.    The memory contents file is used to hold a copy of the systems memory, and is I believe used when the machine is snapshotted or suspended in any way.

    I don't know if the system not being registered would cause that to happen, but the first thing I'd check is free-space on the C: drive,    That could be a problem in some setups where perhaps you intendeed c: to be just for host OS, and d: for app data..
    --Chuck
    • Proposed as answer by Chang Yin Monday, September 1, 2008 10:18 AM
    • Marked as answer by Chang Yin Friday, September 5, 2008 11:02 AM
    Friday, August 29, 2008 10:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    ok, thanks, that was one thing i was debating too, when i install core, the drives didnt seem right, so i am going to rebuild my RAID the right way then reinstall Core....

    Thanks for the tips, ill pos again if i get it all working. The whole concept seems pretty cool, ill probably end up storing the Vista virtual machine in my IT drive so everyone in IT can manage the servers via Hyper V.


    Thanks again
    -JF
    Tuesday, September 2, 2008 4:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    when you get many VM's running on one system, often the bottleneck can be the disk..  so you want to use the fastest disks possible for holding the VHD's

    When managing remotely via Hyper-V Manager I find that my ability to manage the VM's   really doesn't mattter too much where the VM's are located.  As long as I can 'see' them from HVM.   About the only time I get down and dirty with files is if I'm exporting or importing a VM..   I sometimes remote to the server itself to move those around 

    In general I think you'd want to keep most users away from the VHD and snapshot files, because if someone were to mess with them it might mess up your virtual machine, but a lot depends I guess on what you are using the VM's for, and what users will be doing with them.

    --Chuck
    Tuesday, September 2, 2008 5:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It was the hard disks....i set up the RAID 5 and formated it, created new machines and stored them there. They installed and have been working fine all day. Once is services as my print server right now, so all is well. Lets see if they work tomorrow :)

    Now on to backing these things up. I could go the route of just backing up data and configurations as if i were on a phyisical server, but do you think its better to just back up the VHD and the virtual servers themselves?
    Tuesday, September 2, 2008 11:02 PM