From: "Geo" 

"Robert Comer"  wrote in message
news:4557c2f2$1{at}w3.nls.net...

> I don't think you understand just how isolated those drivers in the VM are
> from the actual hardware. (they don't actually touch the hardware at all,
> they only touch an emulated device.)  The CPU is a possible attack point
as
> that's only virtualized, but even it is enough so I haven't seen it crash
> the host.  Sure, an errant driver for say the sound card can be crashed by
a
> VM running, but I don't see an actual attack vector from the VM.

Wasn't talking about the drivers in the vm, was talking about the drivers
under the vm, they are still being used and so are still exposed although
the exposure may be reduced.

Reduced example: Remember that little NTFS issue with millions of tiny
files expanding the MFT, well if the VM uses a simulated partition then
that doesn't affect the drive since it will take place inside a file that
is the simulated partition.

Not reduced example: If you connect to the internet via a modem, I can
still ping you with an ATH ping and cause your modem to hangup.

Geo.

--- BBBS/NT v4.01 Flag-5