Vista Forums - Virtual Server

BSOD 0x0000007e when backup starts

CourtK — Wed, 18 Nov 2009 18:39:47 GMT

Not every time, but when the backup starts on the host I geta a blue screen
with the following error code:
0x0000007e(0xffffffffc0000047,0xfffff80001e83e28,0xfffffa60010c4590,0xfffffa6001dc4630)

I found this Microsoft article http://support.microsoft.com/kb/960038/en-us
that resembles my issue. Any objections or concerns? My system is a Dell
PowerEdge 2950 running Windows 2008 with Hyper-V.

Hyper-V and access to storage

RW — Wed, 18 Nov 2009 17:33:01 GMT

I know my subject line is not real descriptive but I couldn't come up with
anything that would explain right away my issue. So I have HP iSCSI SAN which
is not tested or supported by HP on Windows 2008 server, which makes it
difficult to troubleshoot. Overall this iSCSI SAN works well with Win 2008 as
long Hyper-V is not enabled, what happens is that as soon as I enable Hyper-V
our HP iSCSI SAN starts getting iscsi login attempts from Hyper-V boxes
exactly every 30 minutes, this will continue for hours and at some point SAN
controllers running out of memory by cumulating those "iscsi login attempts"
from Hyper-V boxes and SAN crashes. Reboot and all starts over again.
HP support is refusing to help because we are in unsupported configuration,
they don't want or don't know how to answer question what are those "iscsi
login attempts" and why their piece of hardware is running out of memory over
the time.
in any case since this only happens when Hyper-V is enabled my best guess is
that Hyper-V is checking / verifying existence of storage every 30 minutes
but I cannot find any documentation confirming this or if this can be change
in registry.
Does someone who knows Hyper-V in and out is aware of such verification
process that runs every 30 minutes in Hyper-V?
I first was thinking this is Win 2008 iSCSI or MPIO issue but this is not
happening when Hyper-V is disabled.

DisableTaskOffload in my VM and HOST

SirBrand — Wed, 18 Nov 2009 09:33:02 GMT

>Can you confirm for �Update these value on PHISICAL HOST� only please?

No, I cannot, but hopefully someone else will answer.

--
Bob Comer

On Wed, 18 Nov 2009 04:55:02 -0800, SirBrand
wrote:

Quote:

>"Robert Comer" wrote:
>

Quote:

>> > - Update these value on PHISICAL HOST

>>
>> That's the one.
>>
>> --
>> Bob Comer

>
>Thanks for your reply but I found this post
>http://xpworld.spaces.live.com/blog/...CB31!354.entry were
>authors said:
>�I was handed the solution: Disable TCP Offloading in the VM in stead of on
>the host�
>
>Can you confirm for �Update these value on PHISICAL HOST� only please?
>
>Thank you enough

Hardware for Windows Server 2008 R2 Hyper-V

Henri Fournier — Tue, 17 Nov 2009 06:29:33 GMT

Are you taking about your HP ML350 G5 on your blog? Now that you've had it
for a while and i7 is out, what would you do differently? You mentioned the
G6...

I'm guessing you're not running Windows Server 2008 R2 Hyper-V on that box,
since it hasn't been available for that long. So what's your software setup,
if you don't mind? Thanks.

PS: Mine would be $ CAD too.

Henri

"Charlie Russel - MVP" wrote:

Quote:

> Well, you could certainly build a box to do this for a fairly reasonable
> price. I know I built one with 16 GB, a serious RAID card, 4x500 GB
> Enterprise SATA drives, a pair of backup USB drives, and 3 NICs for roughly
> $3k CAD, so you should be able to do it for under $2500 USD. Especially now
> that Core i7 is out and supports 12 GB without any problem or expensive 4GB
> DIMMs. (I had to build mine with 4GB DIMMs because it was pre-i7.)
>
> --
> Charlie.
> http://msmvps.com/blogs/russel
>
>
>
>
> "Henri Fournier" wrote in message
> news:0234E553-2485-4A13-B105-0D0E66DDB2F5@newsgroup

Quote:

> > OK, I just checked the System Rq. for SBS 2008 and see that the min is 4
> > GB,
> > which is usually not enough, so I see where your 6 comes in. I didn't
> > realize
> > how much higher the req. are over sbs 2003 (min 512 MB - rec 1 GB).
> >
> > Wow! Following all your recommendations just drove the price of the box up
> > by a factor of 3. Yikes. Not the bargain solution I was hoping for.
> >
> > Thanks for the info.
> >
> > Henri
> >
> > "Charlie Russel - MVP" wrote:
> >

Quote:

> >> You aren't even close at 8GB. SBS 2008 will require a minimum of 6GB to
> >> be
> >> useable, even in a small SOHO office. For the others, you can probably
> >> get
> >> away with 2GB each, though it's pretty tight if you're actually doing
> >> anything with the SQL Server box. 12 GB would be tight, but acceptable,
> >> and
> >> 16 GB would be a better choice. If you do go with 12, make sure you have
> >> an
> >> option to increase beyond that if you don't want to be boxed in.
> >>
> >> I'd give SBS it's own physical NIC, plus one for management, and one or
> >> two
> >> for sharing with other VMs.
> >>
> >> For a smallish office like this, you're probably all right with a SATA
> >> RAID
> >> (though SAS is always a better choice). But not ever RAID0 - you not only
> >> don't have redundancy, you've actually increased your risk of failure.
> >> But a
> >> decent PERC card in there, and a RAID 10 or 0+1 with 4 disks should give
> >> you
> >> acceptable throughput.
> >>
> >> One of the biggest problems with virtualizing workloads is providing
> >> adequate I/O to handle the load. It's easy to calculate what you need for
> >> processor or RAM, since those translate directly from what you're
> >> replacing.
> >> But keep in mind that you're now putting all the I/O load from all your
> >> VMs
> >> onto your disk and network subsystems and if you don't provide a good
> >> base
> >> here the entire workload will grind to a halt.
> >>
> >> --
> >> Charlie.
> >> http://msmvps.com/blogs/russel
> >>
> >>
> >>
> >>
> >> "Henri Fournier" wrote in
> >> message
> >> news:9BAF6D35-FF9E-4870-A2A9-807CD5A779B1@newsgroup
> >> > I'm new to this platform and haven't been able to find a great source
> >> > for
> >> > hardware recommendations, so hopefully someone here can shed some
> >> > light.
> >> >
> >> > I'm looking at replacing a few old whitebox PC (P3 dual proc and p4)
> >> > being
> >> > used as servers with one machine running VMs. The machines are old and
> >> > tired
> >> > and draw a lot of power. I'd like consolidate, get better performance
> >> > and
> >> > save energy. However, the budget is pretty tight, so I'm not looking
> >> > for
> >> > the
> >> > ideal server. I need something I can afford that'll get the job done
> >> > (software is through partner program, so I'm only concerned about
> >> > hardware
> >> > costs). I'm running a SOHO office, so the servers are not under a heavy
> >> > load.
> >> > I'd like to setup the following VMs:
> >> > * SBS 2008 (upgrading from SBS 2003)
> >> > * WS2008 Std with SQL Server 2008
> >> > * WS 2008 Web Edition
> >> > * W7 (for remote access through SBS 2008 RWW)
> >> >
> >> > I was looking at the new Dell PowerEdge T110 (bottom end), which comes
> >> > with
> >> > a quad-core Xeon processor and 8 GB of RAM. I thought I could assign a
> >> > core
> >> > to each VM (can you do this?), 1 GB to the host, 1 Gb to the Web and 2
> >> > GB
> >> > to
> >> > each of the others. Let me know if I'm already out-to-lunch.
> >> >
> >> > When it comes to drives, I'm kinda lost. Should I have 1 drive per VM?
> >> > If
> >> > so, which VM should share with the host? Am I OK with onboard SATA
> >> > controller
> >> > (no RAID) or should I go with RAID 0? Something else? Would prefer SATA
> >> > over
> >> > SCSI due to price, unless it's the wrong way to go.
> >> >
> >> > As for NICs, how many do I need? 1 for the host and 1 for the VMs, or 1
> >> > for
> >> > each of the VMs? Can they be any GB NIC, or do they need to be special
> >> > virtualization-ready NICs?
> >> >
> >> > Anything else I should know/do?
> >> >
> >> > Thanks.
> >>
> >> .
> >>

>
> .
>

Hyper-v server and patching

Mitch — Mon, 16 Nov 2009 16:10:02 GMT

Not strictly required, but if you don't, the chances are greater that you'll
have to reboot before your patch will be fully applied.

--
Charlie.
http://msmvps.com/blogs/russel

"Mitch" wrote in message
news:700CC136-44B7-4893-8BA6-3FCA46ABCF83@newsgroup

Quote:

> Is it necessary to shutdown the guests in order to patch the host? I read
> an
> article saying this step was necessary. Thanks

MS Virtual Server 2005 R2 service does not start after reboot

Ben — Mon, 16 Nov 2009 13:05:01 GMT

Hello everybody

My Virtual Server 2005 R2 service does not start after a reboot of the
computer. I did not found an option in the web interface to enable that.
The service is set to "Automatic" with "Network Service" account.

Don't I see the obvious?

Ben