..@gmail.com>>
>> > Reply-To:
>>"dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
>> <
>> > dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
>> > Date: Wednesday, April 23, 2014 at 2:50 PM
>>
Mackey mailto:tmac...@gmail.com>>
> > Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
> <
> > dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> > Date: Wednesday, April 23, 2014 at 2:50 PM
> > To: "dev@cloudst
:dev@cloudstack.apache.org>" <
> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> Subject: Hypervisor version and XenServer
>
> I'm running through some bugs with my Xen->XenServer work and just ran
> across the HYPERVISOR_VERSION being the Xen ver
@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>>
Subject: Hypervisor version and XenServer
I'm running through some bugs with my Xen->XenServer work and just ran
across the HYPERVISOR_VERSION being the Xen version and not the XenServer
v
I'm running through some bugs with my Xen->XenServer work and just ran
across the HYPERVISOR_VERSION being the Xen version and not the XenServer
version. Does anyone know why that is? Given that feature/function in
XenServer is tied to the XenServer version, I see using the Xen version as
a bug w