XenServer Memory Management
-
-
That was half a decade ago, does that still apply?
-
-
Well that sucks. Is the limitation in the XS APIs or in XenCenter? Do you get it with XO as well? I know that Xen doesn't have the limitation, it has to be coming from a higher layer.
-
@scottalanmiller Well you can do it, you just have to edit the VM files. Seems silly to have to do that
I have half a mind to just use KVM, but it doesn't seem as nice as XenServer
-
I ran the command, and it worked well.
-
@anonymous said:
@scottalanmiller Well you can do it, you just have to edit the VM files. Seems silly to have to do that
I have half a mind to just use KVM, but it doesn't seem as nice as XenServer
That wouldn't be the logical response. If you are unhappy with the XenServer limitations put on top of Xen, just move to Xen. It isn't Xen that you are unhappy with.
-
I think these are just limitations of the templates. If you use the Other install media, I don't think you have these limitations. You can also create your own templates.
-
The other thing to watch is if you make a ton of VMs from your VM templates, they are linked to the VHD of the template. This is usually only an issue in large environments where you would have a large linkage and could cause performance issues. To get around that you would actually copy the VM instead of cloning from a template.
This is only referring to the templates that you create that have a VHD attached, not the templates that come with XenServer.
-
@johnhooks said:
I think these are just limitations of the templates. If you use the Other install media, I don't think you have these limitations. You can also create your own templates.
That would explain why I was not aware of them. I nearly always use other media.
