Vista - Errors, errors, errors

05-26-2008

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.

\

05-26-2008

Forgot to mention, since I am so upset, all this rant pertains to Hyper-v

Thanks for reading, Disappointed Brian

"Brian" <briano@xxxxxx> wrote in message
news:eO%23r$TuvIHA.4848@xxxxxx

Quote:

>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.
>
> \
>
>
>
>

05-26-2008

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" <briano@xxxxxx>
wrote:

Quote:

>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.
>
>\
>
>
>

05-26-2008

>The boot disk definitely must be IDE. You can change that before you bring

Quote:

>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.

Quote:

>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/...0290&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"
<charlie@xxxxxx> wrote:

Quote:

>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/...0290&SiteID=17

05-26-2008

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" <charlie@xxxxxx> wrote in message
news:1043B987-FE97-406F-BE75-615BEA42BABD@xxxxxx

Quote:

> 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" <bobcomer-removeme-@xxxxxx> wrote in message
> news:hill349sjbpmuvobg4ab1p8a675rumb967@xxxxxx

Quote:

>> >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.
>>

Quote:

>>>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/...0290&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"
>> <charlie@xxxxxx> wrote:
>>

Quote:

>>>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/...0290&SiteID=17

>

05-28-2008

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" <charlie@xxxxxx> wrote in message
news:06FF0F6D-DF57-47DB-BA10-9F5987E3626A@xxxxxx

Quote:

> 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" <briano@xxxxxx> wrote in message
> news:uW$su12vIHA.1772@xxxxxx

Quote:

>> 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" <charlie@xxxxxx> wrote in message
>> news:1043B987-FE97-406F-BE75-615BEA42BABD@xxxxxx

Quote:

>>> 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" <bobcomer-removeme-@xxxxxx> wrote in message
>>> news:hill349sjbpmuvobg4ab1p8a675rumb967@xxxxxx
>>>> >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/...0290&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"
>>>> <charlie@xxxxxx> 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/...0290&SiteID=17
>>>

>>

>

06-21-2008

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

06-21-2008

What OS is running in the guest? Not all of them support the synthetic
ethernet adapters.

Are you trying to use iSCSI?

"mark" wrote in message news:200862105641markeboyle@xxxxxx

Quote:

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

05-26-2008	#1 (permalink)
Brian n/a posts	Errors, errors, errors 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. \
My System Specs

05-26-2008	#2 (permalink)
Brian n/a posts	Re: Errors, errors, errors Forgot to mention, since I am so upset, all this rant pertains to Hyper-v Thanks for reading, Disappointed Brian "Brian" <briano@xxxxxx> wrote in message news:eO%23r$TuvIHA.4848@xxxxxx Quote: >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. > > \ > > > >
My System Specs

05-26-2008	#3 (permalink)
Robert Comer n/a posts	Re: Errors, errors, errors 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" <briano@xxxxxx> wrote: Quote: >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. > >\ > > >
My System Specs

05-26-2008	#4 (permalink)
Robert Comer n/a posts	Re: Errors, errors, errors >The boot disk definitely must be IDE. You can change that before you bring Quote: >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. Quote: >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/...0290&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" <charlie@xxxxxx> wrote: Quote: >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/...0290&SiteID=17
My System Specs

05-26-2008	#5 (permalink)
Brian n/a posts	Re: Errors, errors, errors 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" <charlie@xxxxxx> wrote in message news:1043B987-FE97-406F-BE75-615BEA42BABD@xxxxxx Quote: > 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" <bobcomer-removeme-@xxxxxx> wrote in message > news:hill349sjbpmuvobg4ab1p8a675rumb967@xxxxxx Quote: Quote: >> >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. >> Quote: >>>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/...0290&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" >> <charlie@xxxxxx> wrote: >> Quote: >>>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/...0290&SiteID=17 >
My System Specs

05-28-2008	#6 (permalink)
Brian n/a posts	Re: Errors, errors, errors (FIXED) 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" <charlie@xxxxxx> wrote in message news:06FF0F6D-DF57-47DB-BA10-9F5987E3626A@xxxxxx Quote: > 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" <briano@xxxxxx> wrote in message > news:uW$su12vIHA.1772@xxxxxx Quote: >> 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" <charlie@xxxxxx> wrote in message >> news:1043B987-FE97-406F-BE75-615BEA42BABD@xxxxxx Quote: >>> 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" <bobcomer-removeme-@xxxxxx> wrote in message >>> news:hill349sjbpmuvobg4ab1p8a675rumb967@xxxxxx >>>> >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/...0290&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" >>>> <charlie@xxxxxx> 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/...0290&SiteID=17 >>> >> >
My System Specs

06-21-2008	#7 (permalink)
mark n/a posts	Failed to add device 'Microsoft Synthetic Ethernet Port' I get that error when trying to move an existing drive to SCSI. Put it back to IDE and it works fine
My System Specs

06-21-2008	#8 (permalink)
Bill Grant n/a posts	Re: Failed to add device 'Microsoft Synthetic Ethernet Port' What OS is running in the guest? Not all of them support the synthetic ethernet adapters. Are you trying to use iSCSI? "mark" wrote in message news:200862105641markeboyle@xxxxxx Quote: > I get that error when trying to move an existing drive to SCSI. Put it > back to IDE and it works fine
My System Specs

Similar Threads
Thread	Forum
Stop Errors - Troubleshooting Specific Stop Errors	Tutorials
Errors	Vista performance & maintenance
Errors, errors and more errors - I have Issues!	Vista performance & maintenance
SP1 - new errors?	Vista General
explorer errors, program errors, no task manager	Vista performance & maintenance