(xen) I use it in production and haven't had any problems. Granted I don't have hardware redundancy, but its not critical either.
Can you elaborate on that (if you don't mind) ? I'm curious - what kind of non-critical production are you running? I've worked on/with virtual systems for about 20 years, but production was almost always (I hesitate saying "virtually" here ) on the "real thing". The one exception being IBMs PR/SM, which is/was "hardware virtualisation", I suppose.
Its a web/dns server in my closet :) and no one on it pays for it. Granted if the hardware went down I'd panic a little, but I wouldn't owe anyone anything. So fingers crossed :) My main servers (VMs) are allocated an actual partition so I'm not worried about getting the data if needed. Maybe a bit naive there though.
You can add things like heartbeat and have your vms stored on iscsi or some nas. The bootup time is amazingly fast too. The base is small as long as you aren't using it for anything other than VMs.
I've got a couple of quad-core boxes, and running a few virtual servers sounds like a cool thing to do - I'm just looking for the killer app :-)
Then definitely give xen a try. I had fun testing it. Try out the live migration too! roughly a 60 ms downtime. ( you have to have the vm on a central center to all host machines).
As for the list, anything to do with virtualization. I was pushing for a xen list, but well they said I have to play nice with others :)
I think "virtualisation" is the right theme - the issues that crop up have got to be roughly the same, albeit with vm-specific solutions etc.
yes no. and I say that because there is some bad blood between kvm and xen. Also different implementations. Though one list pools a lot more knowledge. Stephen -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org