>I think I have had every error in the book. If the following sounds like
>it is from a frustrated individule, it is !!!
>
> I have tried, for the last week, to migrate several vhd files from Virtual
> Server 2005, but just end up with error after error, so I have pretty much
> given up. As a last resort I thought I would try to just establish a
> simple, fresh, virtual server. Sounds easy, Ha !
>
> I tried to create a simple virtual server and it failed, and then I tried
> to delete it.
>
> Cannot access the settings for the selected machine
> The computer 'localhost' failed to perform the requested operation.
>
> An error occurred when atempting to delete the selected virtual machine.
> The computer 'localhost' failed ...................
>
> So I tried again:
>
> New Virtual Machine
> 512 MB
> Not Connect to Network
> 20 GB
> Install later
>
> All pretty simple !!!!!!
>
> The server encountered an error when configuring memory on New Virtual
> Machine. Wizard failed in rolling back the created virtual machine.
> Please delete manually.....
> Failed to add device 'Microsoft Synthetic Ethernet Port'
>
> And on it goes
>
> Is there something, somewhere, that details all these errors and how to
> handle them ?? Or, is the beta too far from completion to expect most
> users to have a
> satisfactory experience ? If I was working on a crummy piece of hardware
> I might expect mixed results. But this is a 2 processor, dual core, 16 GB
> of RAM, Enterprise Server 2008 with latest hyper-v refresh from last week,
> 950049.
>
> I would appreciate anyone's comments, good, bad, or indifferent.
>
> Disappointed Brian.
>
> \
>
>
>
>

> It sounds like your host is either having problems with the install of
> Win2008 or it has some kind of driver incompatibility. If you're just
> using in the box drivers, it's probably not the drivers. You can try
> removing the hyper-v role and then adding it again, maybe the hyper-v
> setup didn't complete correctly.
>
> When you do get a stable Hyper-V (Can at least start an install in a
> partition), the trick to migrating Virtual Server guests is to
> uninstall the Virtual Server additions, and I think the boot disk has
> to be IDE.
>
> --
> Bob Comer
>
>
>
> On Sun, 25 May 2008 21:00:05 -0700, "Brian" <(email address - cut out)>
> wrote:
>
>>I think I have had every error in the book. If the following sounds like
>>it
>>is from a frustrated individule, it is !!!
>>
>>I have tried, for the last week, to migrate several vhd files from Virtual
>>Server 2005, but just end up with error after error, so I have pretty much
>>given up. As a last resort I thought I would try to just establish a
>>simple, fresh, virtual server. Sounds easy, Ha !
>>
>>I tried to create a simple virtual server and it failed, and then I tried
>>to
>>delete it.
>>
>>Cannot access the settings for the selected machine
>>The computer 'localhost' failed to perform the requested operation.
>>
>>An error occurred when atempting to delete the selected virtual machine.
>>The computer 'localhost' failed ...................
>>
>>So I tried again:
>>
>>New Virtual Machine
>>512 MB
>>Not Connect to Network
>>20 GB
>>Install later
>>
>>All pretty simple !!!!!!
>>
>>The server encountered an error when configuring memory on New Virtual
>>Machine. Wizard failed in rolling back the created virtual machine.
>>Please
>>delete manually.....
>>Failed to add device 'Microsoft Synthetic Ethernet Port'
>>
>>And on it goes
>>
>>Is there something, somewhere, that details all these errors and how to
>>handle them ?? Or, is the beta too far from completion to expect most
>>users
>>to have a
>>satisfactory experience ? If I was working on a crummy piece of hardware
>>I
>>might expect mixed results. But this is a 2 processor, dual core, 16 GB
>>of
>>RAM, Enterprise Server 2008 with latest hyper-v refresh from last week,
>>950049.
>>
>>I would appreciate anyone's comments, good, bad, or indifferent.
>>
>>Disappointed Brian.
>>
>>\
>>
>>
>>

>I think I have had every error in the book. If the following sounds like it
>is from a frustrated individule, it is !!!
>
>I have tried, for the last week, to migrate several vhd files from Virtual
>Server 2005, but just end up with error after error, so I have pretty much
>given up. As a last resort I thought I would try to just establish a
>simple, fresh, virtual server. Sounds easy, Ha !
>
>I tried to create a simple virtual server and it failed, and then I tried to
>delete it.
>
>Cannot access the settings for the selected machine
>The computer 'localhost' failed to perform the requested operation.
>
>An error occurred when atempting to delete the selected virtual machine.
>The computer 'localhost' failed ...................
>
>So I tried again:
>
>New Virtual Machine
>512 MB
>Not Connect to Network
>20 GB
>Install later
>
>All pretty simple !!!!!!
>
>The server encountered an error when configuring memory on New Virtual
>Machine. Wizard failed in rolling back the created virtual machine. Please
>delete manually.....
>Failed to add device 'Microsoft Synthetic Ethernet Port'
>
>And on it goes
>
>Is there something, somewhere, that details all these errors and how to
>handle them ?? Or, is the beta too far from completion to expect most users
>to have a
>satisfactory experience ? If I was working on a crummy piece of hardware I
>might expect mixed results. But this is a 2 processor, dual core, 16 GB of
>RAM, Enterprise Server 2008 with latest hyper-v refresh from last week,
>950049.
>
>I would appreciate anyone's comments, good, bad, or indifferent.
>
>Disappointed Brian.
>
>\
>
>
>

> >The boot disk definitely must be IDE. You can change that before you
> >bring
>>it over, ideally. It's a royal PITA for those of us who have gotten used
>>to
>>creating SCSI drives for everything because of the speed on VS.
>
> That's what I thought, thanks for clarifying it. I've always used IDE
> boot disks to have the VM's remain compatible with VPC.
>
>>One caveat - you need to remove AV from the parent partition - it will
>>cause
>>all kinds of problems. You can have it running if you can control which
>>file
>>types it doesn't scan. There's a sort of workaround for Forefront Client
>>Security, but I know Trend has the problem as well.
>>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17
>
> Interesting! I haven't even run AV on my Win2008 test installs. It
> kind of sounds like this might be what the OP's problem is.
>
> --
> Bob Comer
>
>
>
>
> On Mon, 26 May 2008 07:44:16 -0700, "Charlie Russel - MVP"
> <(email address - cut out)> wrote:
>
>>The boot disk definitely must be IDE. You can change that before you bring
>>it over, ideally. It's a royal PITA for those of us who have gotten used
>>to
>>creating SCSI drives for everything because of the speed on VS.
>>
>>One caveat - you need to remove AV from the parent partition - it will
>>cause
>>all kinds of problems. You can have it running if you can control which
>>file
>>types it doesn't scan. There's a sort of workaround for Forefront Client
>>Security, but I know Trend has the problem as well.
>>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17

>it over, ideally. It's a royal PITA for those of us who have gotten used to
>creating SCSI drives for everything because of the speed on VS.
>One caveat - you need to remove AV from the parent partition - it will cause
>all kinds of problems. You can have it running if you can control which file
>types it doesn't scan. There's a sort of workaround for Forefront Client
>Security, but I know Trend has the problem as well.
>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17
>The boot disk definitely must be IDE. You can change that before you bring
>it over, ideally. It's a royal PITA for those of us who have gotten used to
>creating SCSI drives for everything because of the speed on VS.
>
>One caveat - you need to remove AV from the parent partition - it will cause
>all kinds of problems. You can have it running if you can control which file
>types it doesn't scan. There's a sort of workaround for Forefront Client
>Security, but I know Trend has the problem as well.
>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17

> Yes, it does sound like it could be the problem. I can tell you, I was
> totally frustrated and lost a lot of time trying to find the problem until
> we realized that it was FCS causing the issue. Needless to say, I pulled
> FCS off completely. I don't really need it scanning my parent partitions
> anyway. But another MVP I was working with on a project had the same
> issues, and it turns out he was running Trend. When I told him to disable
> Trend, the problems went away.
>
> (and I've never much used VPC, being a hard core server guy. So quickly
> figured out the install time on SCSI was half that of IDE and made the
> switch. Now I have to bring all those back over to Hyper-V. Sigh.)
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "Robert Comer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> >The boot disk definitely must be IDE. You can change that before you
>> >bring
>>>it over, ideally. It's a royal PITA for those of us who have gotten used
>>>to
>>>creating SCSI drives for everything because of the speed on VS.
>>
>> That's what I thought, thanks for clarifying it. I've always used IDE
>> boot disks to have the VM's remain compatible with VPC.
>>
>>>One caveat - you need to remove AV from the parent partition - it will
>>>cause
>>>all kinds of problems. You can have it running if you can control which
>>>file
>>>types it doesn't scan. There's a sort of workaround for Forefront Client
>>>Security, but I know Trend has the problem as well.
>>>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17
>>
>> Interesting! I haven't even run AV on my Win2008 test installs. It
>> kind of sounds like this might be what the OP's problem is.
>>
>> --
>> Bob Comer
>>
>>
>>
>>
>> On Mon, 26 May 2008 07:44:16 -0700, "Charlie Russel - MVP"
>> <(email address - cut out)> wrote:
>>
>>>The boot disk definitely must be IDE. You can change that before you
>>>bring
>>>it over, ideally. It's a royal PITA for those of us who have gotten used
>>>to
>>>creating SCSI drives for everything because of the speed on VS.
>>>
>>>One caveat - you need to remove AV from the parent partition - it will
>>>cause
>>>all kinds of problems. You can have it running if you can control which
>>>file
>>>types it doesn't scan. There's a sort of workaround for Forefront Client
>>>Security, but I know Trend has the problem as well.
>>>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17
>

> Thanks guys for the constructive ideas, and thanks for not crashing on me
> too hard.
>
> I do have Trend OfficeScan running on this computer that is giving me all
> the errors. Only things I have running are the OS with the only role,
> Hyper-v, and Trend OfficeScan. I will shut down Trend and re-install
> Hyper-v. With all the fooling around I have been doing there is a
> possibilty I have upset the Hyper-v installation.
>
> All my Virtual Server files are IDE so I don't have to worry about that.
> And the files I am trying to migrate all have had the Additions deleted.
> But now I am betting on the AV is the root cause of my problems. We'll
> soon see.
>
> Thanks
>
> Brian
>
> "Charlie Russel - MVP" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Yes, it does sound like it could be the problem. I can tell you, I was
>> totally frustrated and lost a lot of time trying to find the problem
>> until we realized that it was FCS causing the issue. Needless to say, I
>> pulled FCS off completely. I don't really need it scanning my parent
>> partitions anyway. But another MVP I was working with on a project had
>> the same issues, and it turns out he was running Trend. When I told him
>> to disable Trend, the problems went away.
>>
>> (and I've never much used VPC, being a hard core server guy. So quickly
>> figured out the install time on SCSI was half that of IDE and made the
>> switch. Now I have to bring all those back over to Hyper-V. Sigh.)
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>>
>> "Robert Comer" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> >The boot disk definitely must be IDE. You can change that before you
>>> >bring
>>>>it over, ideally. It's a royal PITA for those of us who have gotten used
>>>>to
>>>>creating SCSI drives for everything because of the speed on VS.
>>>
>>> That's what I thought, thanks for clarifying it. I've always used IDE
>>> boot disks to have the VM's remain compatible with VPC.
>>>
>>>>One caveat - you need to remove AV from the parent partition - it will
>>>>cause
>>>>all kinds of problems. You can have it running if you can control which
>>>>file
>>>>types it doesn't scan. There's a sort of workaround for Forefront Client
>>>>Security, but I know Trend has the problem as well.
>>>>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17
>>>
>>> Interesting! I haven't even run AV on my Win2008 test installs. It
>>> kind of sounds like this might be what the OP's problem is.
>>>
>>> --
>>> Bob Comer
>>>
>>>
>>>
>>>
>>> On Mon, 26 May 2008 07:44:16 -0700, "Charlie Russel - MVP"
>>> <(email address - cut out)> wrote:
>>>
>>>>The boot disk definitely must be IDE. You can change that before you
>>>>bring
>>>>it over, ideally. It's a royal PITA for those of us who have gotten used
>>>>to
>>>>creating SCSI drives for everything because of the speed on VS.
>>>>
>>>>One caveat - you need to remove AV from the parent partition - it will
>>>>cause
>>>>all kinds of problems. You can have it running if you can control which
>>>>file
>>>>types it doesn't scan. There's a sort of workaround for Forefront Client
>>>>Security, but I know Trend has the problem as well.
>>>>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17
>>
>

> Trend is definitely one of those that will cause issues.
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "Brian" <(email address - cut out)> wrote in message
> news:uW$(email address - cut out)...
>> Thanks guys for the constructive ideas, and thanks for not crashing on me
>> too hard.
>>
>> I do have Trend OfficeScan running on this computer that is giving me all
>> the errors. Only things I have running are the OS with the only role,
>> Hyper-v, and Trend OfficeScan. I will shut down Trend and re-install
>> Hyper-v. With all the fooling around I have been doing there is a
>> possibilty I have upset the Hyper-v installation.
>>
>> All my Virtual Server files are IDE so I don't have to worry about that.
>> And the files I am trying to migrate all have had the Additions deleted.
>> But now I am betting on the AV is the root cause of my problems. We'll
>> soon see.
>>
>> Thanks
>>
>> Brian
>>
>> "Charlie Russel - MVP" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Yes, it does sound like it could be the problem. I can tell you, I was
>>> totally frustrated and lost a lot of time trying to find the problem
>>> until we realized that it was FCS causing the issue. Needless to say, I
>>> pulled FCS off completely. I don't really need it scanning my parent
>>> partitions anyway. But another MVP I was working with on a project had
>>> the same issues, and it turns out he was running Trend. When I told him
>>> to disable Trend, the problems went away.
>>>
>>> (and I've never much used VPC, being a hard core server guy. So quickly
>>> figured out the install time on SCSI was half that of IDE and made the
>>> switch. Now I have to bring all those back over to Hyper-V. Sigh.)
>>>
>>> --
>>> Charlie.
>>> http://msmvps.com/blogs/xperts64
>>> http://mvp.support.microsoft.com/profile/charlie.russel
>>>
>>>
>>> "Robert Comer" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>>> >The boot disk definitely must be IDE. You can change that before you
>>>> >bring
>>>>>it over, ideally. It's a royal PITA for those of us who have gotten
>>>>>used to
>>>>>creating SCSI drives for everything because of the speed on VS.
>>>>
>>>> That's what I thought, thanks for clarifying it. I've always used IDE
>>>> boot disks to have the VM's remain compatible with VPC.
>>>>
>>>>>One caveat - you need to remove AV from the parent partition - it will
>>>>>cause
>>>>>all kinds of problems. You can have it running if you can control which
>>>>>file
>>>>>types it doesn't scan. There's a sort of workaround for Forefront
>>>>>Client
>>>>>Security, but I know Trend has the problem as well.
>>>>>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17
>>>>
>>>> Interesting! I haven't even run AV on my Win2008 test installs. It
>>>> kind of sounds like this might be what the OP's problem is.
>>>>
>>>> --
>>>> Bob Comer
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, 26 May 2008 07:44:16 -0700, "Charlie Russel - MVP"
>>>> <(email address - cut out)> wrote:
>>>>
>>>>>The boot disk definitely must be IDE. You can change that before you
>>>>>bring
>>>>>it over, ideally. It's a royal PITA for those of us who have gotten
>>>>>used to
>>>>>creating SCSI drives for everything because of the speed on VS.
>>>>>
>>>>>One caveat - you need to remove AV from the parent partition - it will
>>>>>cause
>>>>>all kinds of problems. You can have it running if you can control which
>>>>>file
>>>>>types it doesn't scan. There's a sort of workaround for Forefront
>>>>>Client
>>>>>Security, but I know Trend has the problem as well.
>>>>>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17
>>>
>>
>

> The problem was Trend OfficeScan. Once it was stopped, all the errors
> went away. I sure wish I had seen some documentation pertaining to that
> problem before I invested a week to 10 days trying to get a system up and
> running. You would think, with all the searching I have done, I would have
> tripped on that solution long ago. I am my own worst ememy, I really
> should have thought that OfficeScan might contribute to some of my
> problems, but for some reason, I just missed it. I think I just forgot it
> was actually running.
>
> Many, many thanks to Charlie and Robert for leading me in the right
> direction. Also I waited too long before asking for help, that's my ego.
>
> Brian
>
> "Charlie Russel - MVP" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Trend is definitely one of those that will cause issues.
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>>
>> "Brian" <(email address - cut out)> wrote in message
>> news:uW$(email address - cut out)...
>>> Thanks guys for the constructive ideas, and thanks for not crashing on
>>> me too hard.
>>>
>>> I do have Trend OfficeScan running on this computer that is giving me
>>> all the errors. Only things I have running are the OS with the only
>>> role, Hyper-v, and Trend OfficeScan. I will shut down Trend and
>>> re-install Hyper-v. With all the fooling around I have been doing there
>>> is a possibilty I have upset the Hyper-v installation.
>>>
>>> All my Virtual Server files are IDE so I don't have to worry about that.
>>> And the files I am trying to migrate all have had the Additions deleted.
>>> But now I am betting on the AV is the root cause of my problems. We'll
>>> soon see.
>>>
>>> Thanks
>>>
>>> Brian
>>>
>>> "Charlie Russel - MVP" <(email address - cut out)> wrote in
>>> message news:(email address - cut out)...
>>>> Yes, it does sound like it could be the problem. I can tell you, I was
>>>> totally frustrated and lost a lot of time trying to find the problem
>>>> until we realized that it was FCS causing the issue. Needless to say, I
>>>> pulled FCS off completely. I don't really need it scanning my parent
>>>> partitions anyway. But another MVP I was working with on a project had
>>>> the same issues, and it turns out he was running Trend. When I told him
>>>> to disable Trend, the problems went away.
>>>>
>>>> (and I've never much used VPC, being a hard core server guy. So quickly
>>>> figured out the install time on SCSI was half that of IDE and made the
>>>> switch. Now I have to bring all those back over to Hyper-V. Sigh.)
>>>>
>>>> --
>>>> Charlie.
>>>> http://msmvps.com/blogs/xperts64
>>>> http://mvp.support.microsoft.com/profile/charlie.russel
>>>>
>>>>
>>>> "Robert Comer" <(email address - cut out)> wrote in message
>>>> news:(email address - cut out)...
>>>>> >The boot disk definitely must be IDE. You can change that before you
>>>>> >bring
>>>>>>it over, ideally. It's a royal PITA for those of us who have gotten
>>>>>>used to
>>>>>>creating SCSI drives for everything because of the speed on VS.
>>>>>
>>>>> That's what I thought, thanks for clarifying it. I've always used IDE
>>>>> boot disks to have the VM's remain compatible with VPC.
>>>>>
>>>>>>One caveat - you need to remove AV from the parent partition - it will
>>>>>>cause
>>>>>>all kinds of problems. You can have it running if you can control
>>>>>>which file
>>>>>>types it doesn't scan. There's a sort of workaround for Forefront
>>>>>>Client
>>>>>>Security, but I know Trend has the problem as well.
>>>>>>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17
>>>>>
>>>>> Interesting! I haven't even run AV on my Win2008 test installs. It
>>>>> kind of sounds like this might be what the OP's problem is.
>>>>>
>>>>> --
>>>>> Bob Comer
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, 26 May 2008 07:44:16 -0700, "Charlie Russel - MVP"
>>>>> <(email address - cut out)> wrote:
>>>>>
>>>>>>The boot disk definitely must be IDE. You can change that before you
>>>>>>bring
>>>>>>it over, ideally. It's a royal PITA for those of us who have gotten
>>>>>>used to
>>>>>>creating SCSI drives for everything because of the speed on VS.
>>>>>>
>>>>>>One caveat - you need to remove AV from the parent partition - it will
>>>>>>cause
>>>>>>all kinds of problems. You can have it running if you can control
>>>>>>which file
>>>>>>types it doesn't scan. There's a sort of workaround for Forefront
>>>>>>Client
>>>>>>Security, but I know Trend has the problem as well.
>>>>>>http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3140290&SiteID=17
>>>>
>>>
>>
>

> I get that error when trying to move an existing drive to SCSI. Put it
> back to IDE and it works fine