On 22.04.24 09:12, Jan Beulich wrote:
On 19.04.2024 17:29, George Dunlap wrote:
On Fri, Jul 7, 2023 at 3:56 PM George Dunlap wrote:
Xen's public interface offers access to the featuresets known / found /
used by the hypervisor. See XEN_SYSCTL_get_cpu_featureset, accessible
via xc_get_cpu_featu
On Mon, 22 Apr 2024, Jan Beulich wrote:
> On 19.04.2024 17:29, George Dunlap wrote:
> > On Fri, Jul 7, 2023 at 3:56 PM George Dunlap
> > wrote:
> >> Xen's public interface offers access to the featuresets known / found /
> >> used by the hypervisor. See XEN_SYSCTL_get_cpu_featureset, acce
On 19.04.2024 17:29, George Dunlap wrote:
> On Fri, Jul 7, 2023 at 3:56 PM George Dunlap wrote:
>> Xen's public interface offers access to the featuresets known / found /
>> used by the hypervisor. See XEN_SYSCTL_get_cpu_featureset, accessible
>> via xc_get_cpu_featureset().
>>
>>>
On 19.04.2024 17:51, George Dunlap wrote:
> On Fri, Apr 19, 2024 at 4:29 PM George Dunlap wrote:
>>
>> On Fri, Jul 7, 2023 at 3:56 PM George Dunlap wrote:
>>> Xen's public interface offers access to the featuresets known / found /
>>> used by the hypervisor. See XEN_SYSCTL_get_cpu_feature
On Fri, Apr 19, 2024 at 4:29 PM George Dunlap wrote:
>
> On Fri, Jul 7, 2023 at 3:56 PM George Dunlap wrote:
> >> >>> Xen's public interface offers access to the featuresets known / found /
> >> >>> used by the hypervisor. See XEN_SYSCTL_get_cpu_featureset, accessible
> >> >>> via xc_get_cpu_feat
On Fri, Jul 7, 2023 at 3:56 PM George Dunlap wrote:
>> >>> Xen's public interface offers access to the featuresets known / found /
>> >>> used by the hypervisor. See XEN_SYSCTL_get_cpu_featureset, accessible
>> >>> via xc_get_cpu_featureset().
>> >>>
>> >>
>> >> Are any of these exposed in dom0 vi
On Fri, Jul 7, 2023 at 12:45 PM Jan Beulich wrote:
> On 07.07.2023 12:16, Jan Beulich wrote:
> > On 07.07.2023 11:52, George Dunlap wrote:
> >> On Fri, Jul 7, 2023 at 9:00 AM Jan Beulich wrote:
> >>
> >>> On 06.07.2023 17:35, zithro wrote:
> On 06 Jul 2023 09:02, Jan Beulich wrote:
> >
On Fri, Jul 7, 2023 at 11:17 AM Jan Beulich wrote:
> On 07.07.2023 11:52, George Dunlap wrote:
> > On Fri, Jul 7, 2023 at 9:00 AM Jan Beulich wrote:
> >
> >> On 06.07.2023 17:35, zithro wrote:
> >>> On 06 Jul 2023 09:02, Jan Beulich wrote:
> On 05.07.2023 18:20, zithro wrote:
> > So I'm
On 07.07.2023 12:16, Jan Beulich wrote:
> On 07.07.2023 11:52, George Dunlap wrote:
>> On Fri, Jul 7, 2023 at 9:00 AM Jan Beulich wrote:
>>
>>> On 06.07.2023 17:35, zithro wrote:
On 06 Jul 2023 09:02, Jan Beulich wrote:
> On 05.07.2023 18:20, zithro wrote:
>> So I'm wondering, isn't t
On 07.07.2023 11:52, George Dunlap wrote:
> On Fri, Jul 7, 2023 at 9:00 AM Jan Beulich wrote:
>
>> On 06.07.2023 17:35, zithro wrote:
>>> On 06 Jul 2023 09:02, Jan Beulich wrote:
On 05.07.2023 18:20, zithro wrote:
> So I'm wondering, isn't that path enough for correct detection ?
> I
On Fri, Jul 7, 2023 at 9:00 AM Jan Beulich wrote:
> On 06.07.2023 17:35, zithro wrote:
> > On 06 Jul 2023 09:02, Jan Beulich wrote:
> >> On 05.07.2023 18:20, zithro wrote:
> >>> So I'm wondering, isn't that path enough for correct detection ?
> >>> I mean, if "/sys/class/dmi/id/sys_vendor" report
On 06.07.2023 17:35, zithro wrote:
> On 06 Jul 2023 09:02, Jan Beulich wrote:
>> On 05.07.2023 18:20, zithro wrote:
>>> So I'm wondering, isn't that path enough for correct detection ?
>>> I mean, if "/sys/class/dmi/id/sys_vendor" reports Xen (or KVM, or any
>>> other known hypervisor), it's nested
On 7/6/23 17:35, zithro wrote:
> On 06 Jul 2023 09:02, Jan Beulich wrote:
>> On 05.07.2023 18:20, zithro wrote:
>>> So I'm wondering, isn't that path enough for correct detection ?
>>> I mean, if "/sys/class/dmi/id/sys_vendor" reports Xen (or KVM, or any
>>> other known hypervisor), it's nested,
On 06 Jul 2023 09:02, Jan Beulich wrote:
On 05.07.2023 18:20, zithro wrote:
So I'm wondering, isn't that path enough for correct detection ?
I mean, if "/sys/class/dmi/id/sys_vendor" reports Xen (or KVM, or any
other known hypervisor), it's nested, otherwise it's on hardware ?
Is that really ma
On 05.07.2023 18:20, zithro wrote:
> On 05 Jul 2023 17:51, George Dunlap wrote:
>> Hey all,
>>
>> The following systemd issue was brought to my attention:
>>
>> https://github.com/systemd/systemd/issues/28113
>>
>> I think basically, they want `systemd-detect-virt` return the following
>> values:
>
On 05 Jul 2023 17:51, George Dunlap wrote:
Hey all,
The following systemd issue was brought to my attention:
https://github.com/systemd/systemd/issues/28113
I think basically, they want `systemd-detect-virt` return the following
values:
Xen on hardware, from a dom0: `none`
Xen on hardware, f
Hey all,
The following systemd issue was brought to my attention:
https://github.com/systemd/systemd/issues/28113
I think basically, they want `systemd-detect-virt` return the following
values:
Xen on hardware, from a dom0: `none`
Xen on hardware, from a domU: `xen`
Xen in a VM, from a dom0: (
17 matches
Mail list logo