Hello,
Thank you for your answer, Ivan. Yes, I think it will work, but it is very
unstable variant. I hope it can be done in other way.
2017-10-02 17:46 GMT+03:00 Ivan Kudryavtsev :
> Hi, I believe that if you change os type to linux, you'll get it. But it
> could lead to problems with storage dr
As I found - it is hardcoded here -
libvirtComputingResource.isGuestPVEnabled
So, there are two ways or I change it in code, or I set OS Type for
template "Windows PV" or "Other PV". What is the difference between this
two types?
2017-10-04 14:36 GMT+03:00 Dmitriy Kaluzhniy :
> Hello,
> Thank you
Also note that as of 4.10 there is new support for Virtio-Scsi on KVM
Check out this PR note for an example of how to set it up on a template:
https://github.com/apache/cloudstack/pull/1955#issuecomment-284440859
- Si
From: Dmitriy Kaluzhniy
Sent: Wednesd
ps aux | grep VMNAME and you can see differences I guess :) probably next
to none (but I didn't check really)
We run all Windows VMs as "windows PV", but have also implemented
additional "Hyper-V Enlightments flags for KVM" in XML definition for all
"OS types" that have word "Windows" in it (
http
Anyone? I know I'm trying to squeeze some free paid consulting here :),
but trying to understand if PODs makes sense in this situation
Thx
On 2 October 2017 at 10:21, Andrija Panic wrote:
> Hi guys,
>
> Sorry for long post below...
>
> I was wondering if someone could bring some light for
I think this can cause problems, if not properly managed. Unless you
concentrate Domains/Users in Pods. Otherwise, you might end up with some
VMs of the same user/domain/project in different pods, and if they are
all in the same VPC for instance, we would expect them to be in the same
broadcast
