SQL Server 2008 on Hyper-V Virtual Machine with Multiple instances

Running SQL Server 2008 instance on a Virtual Machine (Hyper-V) on a Windows 2008 R2 OS. Currently has a few production DBs. The whole VM itself is on RAID 5 volume (so are the DB files etc).

We will be adding further development and production DBs onto this VM soon. The production DB's on average are 1.5Gig in size with the largest DB less than 20Gig.

My question is: would having multiple instances make much difference in my situation. i.e.
Data separation (dev, prod)
An instance fails the others still work (not sure if applicable in a shared disk situation)

Would multiple instances be worth the overhead? i.e. more services, memory used by services

Thanks.

PS. Our disk layout is on a single disk and I understand that is not the recommended but will leave as a separate issue as I want to nut down on the multiple instance question first.

If I understand, you have a single VM running under Win 2008 Host OS on a single box?

If so, there is no advantage is having multiple SQL Server instances.

Data separation of dev vs prod doesn't matter because you'd only end up using resources for dev that should be on prod. And with a single server you have a single point of failures (no matter how you configure disks).

If you have do it on the cheap, one big instance.
If you can buy more kit, get a proper physical production server.

StackExchange Database Administrators Q#2815, answer score: 2