Prev: Windows 7 joining SBS 2003 R2 domain
Next: Say goodbye to this news group...
From: Leythos on 8 May 2010 15:11
In article <#Uexyrt7KHA.5412(a)TK2MSFTNGP06.phx.gbl>, sbradcpa(a)pacbell.net
says...
>
> Leythos wrote:
> > In article <#lQxdos7KHA.2292(a)TK2MSFTNGP04.phx.gbl>, kerry(a)kdbNOSPAMsys-
> > tems.c*a*m says...
> >
> >> I've seen similar problems when installing SBS 2008 to a Hyper-V virtual
> >> machine. The problem was caused by poor I/O of the of the disk system. Make
> >> sure you are not using a dynamic vhd. If you are using SATA disks make sure
> >> no other virtual machines are running that are using the same disk that the
> >> SBS vhd is on. What are the hardware specs of the server and how is the
> >> virtual machine configured?
> >>
> >>
> >
> > There has to be more to it than just SATA performance. I have a single
> > Quad Core x64 server class motherboard with a single 1TB RAID 1 and run
> > SBS 2008, Win 2008, Win 2003, XP SP3 and Vista as children all at the
> > same time on that single hardware 1TB RAID-1.
> >
> >
> Yeah but did you install SBS with all those other things running?

Yes

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free(a)rrohio.com (remove 999 for proper email address)
From: Susan Bradley on 8 May 2010 16:36
Leythos wrote:
> In article <#Uexyrt7KHA.5412(a)TK2MSFTNGP06.phx.gbl>, sbradcpa(a)pacbell.net
> says...
>
>> Leythos wrote:
>>
>>> In article <#lQxdos7KHA.2292(a)TK2MSFTNGP04.phx.gbl>, kerry(a)kdbNOSPAMsys-
>>> tems.c*a*m says...
>>>
>>>
>>>> I've seen similar problems when installing SBS 2008 to a Hyper-V virtual
>>>> machine. The problem was caused by poor I/O of the of the disk system. Make
>>>> sure you are not using a dynamic vhd. If you are using SATA disks make sure
>>>> no other virtual machines are running that are using the same disk that the
>>>> SBS vhd is on. What are the hardware specs of the server and how is the
>>>> virtual machine configured?
>>>>
>>>>
>>>>
>>> There has to be more to it than just SATA performance. I have a single
>>> Quad Core x64 server class motherboard with a single 1TB RAID 1 and run
>>> SBS 2008, Win 2008, Win 2003, XP SP3 and Vista as children all at the
>>> same time on that single hardware 1TB RAID-1.
>>>
>>>
>>>
>> Yeah but did you install SBS with all those other things running?
>>
>
> Yes
>
>
You live on the edge :-)
From: Kerry Brown on 8 May 2010 17:43

"Leythos" <spam999free(a)rrohio.com> wrote in message
news:MPG.264f63eb673cdeb098a337(a)us.news.astraweb.com...
> In article <#lQxdos7KHA.2292(a)TK2MSFTNGP04.phx.gbl>, kerry(a)kdbNOSPAMsys-
> tems.c*a*m says...
>>
>> I've seen similar problems when installing SBS 2008 to a Hyper-V virtual
>> machine. The problem was caused by poor I/O of the of the disk system.
>> Make
>> sure you are not using a dynamic vhd. If you are using SATA disks make
>> sure
>> no other virtual machines are running that are using the same disk that
>> the
>> SBS vhd is on. What are the hardware specs of the server and how is the
>> virtual machine configured?
>>
>
> There has to be more to it than just SATA performance. I have a single
> Quad Core x64 server class motherboard with a single 1TB RAID 1 and run
> SBS 2008, Win 2008, Win 2003, XP SP3 and Vista as children all at the
> same time on that single hardware 1TB RAID-1.
>

There probably is more to it but that was the advice I got back from MS. I
could replicate the problem about 50% of the time. The server was dual quad
core Opteron with 16GB RAM, 10GB allocated to the SBS 2008 vm during the
install. I had one other vm running, a server 2003 vm with 1GB RAM for use
as a router for the SBS test install. Stopping the other vm allowed SBS 2008
to install every time. I was doing multiple installs testing various
migration scenarios. MS indicated it wasn't a RAM or CPU problem but most
likely disk I/O. Once SBS 2008 was installed I was able to run other vhd's
off of the same disk no problem.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/




From: Leythos on 9 May 2010 09:48
In article <#uIMh4u7KHA.5848(a)TK2MSFTNGP06.phx.gbl>, sbradcpa(a)pacbell.net
says...
>
> Leythos wrote:
> > In article <#Uexyrt7KHA.5412(a)TK2MSFTNGP06.phx.gbl>, sbradcpa(a)pacbell.net
> > says...
> >
> >> Leythos wrote:
> >>
> >>> In article <#lQxdos7KHA.2292(a)TK2MSFTNGP04.phx.gbl>, kerry(a)kdbNOSPAMsys-
> >>> tems.c*a*m says...
> >>>
> >>>
> >>>> I've seen similar problems when installing SBS 2008 to a Hyper-V virtual
> >>>> machine. The problem was caused by poor I/O of the of the disk system. Make
> >>>> sure you are not using a dynamic vhd. If you are using SATA disks make sure
> >>>> no other virtual machines are running that are using the same disk that the
> >>>> SBS vhd is on. What are the hardware specs of the server and how is the
> >>>> virtual machine configured?
> >>>>
> >>>>
> >>>>
> >>> There has to be more to it than just SATA performance. I have a single
> >>> Quad Core x64 server class motherboard with a single 1TB RAID 1 and run
> >>> SBS 2008, Win 2008, Win 2003, XP SP3 and Vista as children all at the
> >>> same time on that single hardware 1TB RAID-1.
> >>>
> >>>
> >>>
> >> Yeah but did you install SBS with all those other things running?
> >>
> >
> > Yes
> >
> >
> You live on the edge :-)

It was just a test machine to see how VM worked when stressed. The SV
2008 was a DC with XP as a child, the 2003 was an active web server
(small though) and the SBS had one client (Vista).

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free(a)rrohio.com (remove 999 for proper email address)
From: Leythos on 9 May 2010 09:49
In article <#U9RRev7KHA.720(a)TK2MSFTNGP05.phx.gbl>, kerry(a)kdbNOSPAMsys-
tems.c*a*m says...
> > There has to be more to it than just SATA performance. I have a single
> > Quad Core x64 server class motherboard with a single 1TB RAID 1 and run
> > SBS 2008, Win 2008, Win 2003, XP SP3 and Vista as children all at the
> > same time on that single hardware 1TB RAID-1.
> >
>
> There probably is more to it but that was the advice I got back from MS. I
> could replicate the problem about 50% of the time. The server was dual quad
> core Opteron with 16GB RAM, 10GB allocated to the SBS 2008 vm during the
> install. I had one other vm running, a server 2003 vm with 1GB RAM for use
> as a router for the SBS test install. Stopping the other vm allowed SBS 2008
> to install every time. I was doing multiple installs testing various
> migration scenarios. MS indicated it wasn't a RAM or CPU problem but most
> likely disk I/O. Once SBS 2008 was installed I was able to run other vhd's
> off of the same disk no problem.
>

I was using an Asus Server motherboard with 8GB ram on it, so I had less
ram then your test. I used the on-board RAID controller...

What vendors motherboard were you testing with?

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free(a)rrohio.com (remove 999 for proper email address)
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Windows 7 joining SBS 2003 R2 domain
Next: Say goodbye to this news group...