As many of you are aware..I have two of these from 1and1..and are quite enjoying them..and may even add a third to the fleet today.
Aside from no update thing..many of you have had misadventures with these I would care not to have. Are there limitations to what you can install? I remember putting Oracle on one before..and that worked fine (surprised me) and I have put Tomcat on a linux vps before..worked fine...even after I started seriously using it (which is sometimes when fun really starts) and it was still fine.
I am more intersted in using these to test CGI scripts..learn ASP and .NET..and whatnot. I guess my primary question is this:
Can these be used to test applications before trying them on a real server? How close to the real thing are these vps's?
If experience is useful..it would say pretty darn close to the real thing. I do need a Vmware based one, though.
In order to increase the reliability of a audio streaming service I am thinking to take the action I describe below.
1. Buy two Windows VPSs with WMS installed.
2. Register a domain name (i.e audiostream.com) with 4 nameservers: ns1.ip1_vps1, ns2.ip2_vps1, ns3.ip1_vps2, ns4.ip2_vps2.
3. Create all publishing points (streams) on both servers.
Normaly VPS1 should serve all clients. In case VPS1 goes down, VPS2 should jump in and serve all clients-connections. As soon as VPS1 becomes available (ns1 & ns2 start responding again), VPS1 starts serving all new connections.
Load balancing or any other kind of advanced load, traffic, etc management is not important.
Then we have the following cases: 1. VPS1 is down , which means that VPS2 should take charge.
2. VPS1 is up (ns, http, ftp services), but WMS1 is down (crashed). Means that the playlist (asx) file should be built so that it also includes the IP, port & publishing points of VPS2. This should be done because ns1 & ns2 will answer without any problem, but WMS1 will be crashed and won't serve any media connections, thus ASX will look for the next available stream in the playlist.
Do you think that the above is possible. Is this gonna work?
Has the VZ bug where "doing a Windows Update on a node applies it to the whole server and then reboots the node" been fixed yet. We offer Linux VPS using VZ and was going to use it for Windows too but when I heard that I put the plan on hold.
What are the advantages/disadvantages of each solution? So far we have been using Virtuozzo Windows VPS and we would like to learn how it compares to MS Virtual Server 2005.
Does anyone know if running centOS 5.2 as a host OS on a dedicated server would be able to run both Linux and Windows VPS servers using virtuozzo? on their video it says you can however i cant find where/how to install a windows server 2003 template.
We use VS 2005 and are happy with the stability and performance etc but wanted to know if there are any great advantages to using virtuozzo? It seems that a higher ratio of VPS per box can be achieved with virtuozzo due to the ability to share RAM but is this worth it for the extra cost of licenses and possible security / stability risks?
Is there any windows software which will allow me to login to my Virtuozzo Power Panel instead of the web interface? I know that one exists for hypervm.
Without any fanfare, at the beginning of September, Parallels released Virtuozzo Containers (formerly Virtuozzo) 4.5.
Version 4, launched in January, unified for the first time the Windows and Linux branches, introducing major new features like virtual SMP masking and support for Microsoft and Red Hat cluster services.
Version 4.5, which is built on this new architecture, brings in a wire range of new capabilities:
Support for Windows Server 2008 (32/64bit, with or without Hyper-V, up to Service Pack 1) and its new Failover Clustering
Support for Hyper-V (it’s not exactly clear if this just means that the Hyper-V parent partition can be segmented in containers, or something else)
Support for TCP/IP Offload Engine (TOE) NICs inside the containers
Support for new 3rd party backup and anti-virus solutions (including the ones provided by AVG, CA, EMC, IBM, McAfee, Symantec and F-Secure)
Support for iSCSI inside the containers (a container can be an Initiator)
Support for IPv6 addresses inside the containers
It’s not entirely clear why Parallels didn’t promote in any way what is still considered its flagship product. It is true that the large majority of the attention is focused on hardware virtualization, but the company OS virtualization platform should still have a competitive advantage over VMware, Citrix and Microsoft hypervisors in the hosting industry, which is well worth some more marketing effort.
We are wondering why Parallels haven't been shouting from the rooftops. This is a game changer.
I currently have 2 VPSs that I'm monitoring and I noticed that on one of them the memory usage is much higher than the other which doesn't make sense to me. I tracked the high memory usage to the Apache processes.
Here's the overview of the VPSs:
LiquidWeb VPS- 512MB RAM, 10 Sites with minimal usage. Average httpd process (Owner Priority Cpu% Mem% Command): nobody 0 0.0 1.2 /usr/local/apache/bin/httpd -k start -DSSL
Virpus VPS- 384MB RAM, 61 sites with moderate usage. Average httpd process (Owner Priority Cpu% Mem% Command): nobody 0 0.0 0.3 /usr/local/apache/bin/httpd -k start -DSSL
Both Apache configurations are identical, the only difference besides the hardware is that LiquidWeb runs CentOS4.7 and Virpus runs CentOS5.2, any ideas? It's not to big of a deal since I'm not near my limit for either of them but I was just curious.
what's going inside my provider Powervps/Defender hosting, they are offering now 25% OFF of new customers + triply bandwidth.
Curent customers are not allowod to get this offer, until they order a new VPS and cancel the older.
I'm asking, because i feel, it's samething, why they don't go upgarading the account throughly with keeping IPs and data..? why do old customers need to cancel the old VPS then they go get a new VPS..?
are Old VPSs powerfully then the newest..? any informations...?
Last month I order 2 Xen VPSs from Xenvz.co.uk and use them for VPN proxy.
But a few days ago, xenvz stopped one vps and state "This is because it is spreading the Conficker virus.". I'm a little surprise because there's only 10+ users on this vps. Most of them use VPN for visting Youtube or P2P download or gaming. And Conficker virus can only run on Windows, but all my vps is running on Debian.
Maybe someone had download something that contain Conficker virus?
Anyway, I had to move a few users to another vps yesterday.
But xenvz stop my another vps today for the same reason!
I really do not know whether or not one of my user is spreading or other reason, but as I know, Conficker virus had affected thousands of hosts in the past. If someone download or being affect by conficker for any reason, provider then stop their host, I'm afraid thousands of sites would down.
Most VPS offerings have "burstable" memory allocations. I get how you can do this with most things -- letting a VPS access more CPU cycles can be done pretty easily, and a 10 Mbps line burstable to 100 Mbps makes sense.
But how does the guest OS handle all of a sudden having more memory? Since a lot of VPS guests run without modification, how does this work? Does the typical Linux system support dynamic changes in RAM? I can only imagine that dealing with "un-bursting" is even more complex: suppose I have 128MB, burst to 512, but then the host node tries to reclaim some of it. Is the system smart enough to seamlessly swap out to disk when RAM "disappears?" I'd fully expect a kernel panic when the system's RAM shrinks in size, particularly when the RAM was in use.
I'm curious about exactly how all of this is managed. Given that 95% of VPS hosts give a burstable range of RAM, what exactly manages this? Is the virtualization platform handling this and somehow "tricking" the kernel, or is the guest system able to deal with changing RAM allocations? And, if the latter, is this a standard feature of the Linux kernel, or are guest OS mods still necessary to deal with burstable RAM?
I was just curious as to how virtuozzo manages the cpu usage. Do all VPS's just use as much cpu as they can at one time or is there a min and max limit?
We're currently using virtuozzo and have been but we are thinking of starting a Xen server as our techs have the technical expertise to manage a Xen server. I'm just wondering whether we would be better off with this or not, compared to Virtuozzo.
I've noticed a lot of the recommended VPS' are using Virtuozzo (e.g. KickAssVPS and WiredTree). Can anyone recommend good Windows VPS that utilize other software (ESX, Xen, Hyper-V)?
I installed Apf on Virtuozzo VE, which went well until I enabled it. I could not access Plesk installed on the machine, then I realized it was listening to port 8880 from the Service VE as well as 8443. Enabling 8880 in the common ports solved the problem, but I only want it blocked for everything BUT the Service VE.
I looked in the manual and the section that discusses adding custom rules for aliases only has a header and does not have any description.
Anyone know how to block port 8880 to the world but allow 8880 to a particular IP?
We are having an issue when trying to cache Fedora Core 10.
Code:
vzpkg create cache fedora-core-10-x86_64 Creation OS template cache for fedora-core-10-x86_64 template Error: Python directory not found in /vz/pkgenv/rpm46x64 Error: Can't find environment directory /vz/pkgenv/rpm46x64: No such file or directory
The only recent changes that have been made is the Hostname. Before making this change, I was caching OS templates like it was christmas.
I've read that Virtuozzo 4.0 supported ipv6. I'm having problems finding anything to help setup the node for ipv6. I can't anything on the web except for some people talking about how to disable ipv6. So I was just wondering if anyone else has seen anything.
Edit: I don't think I posted in the correct section. Opps. Could a moderator move this to the right section?
