#xen — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #xen, aggregated by home.social.
-
XenServer 9: Now from Citrix again – and not just for desktops
Citrix introduces XenServer 9 as a preview. The new major version updates the hypervisor and aligns it for all workload types.
-
XenServer 9: Now from Citrix again – and not just for desktops
Citrix introduces XenServer 9 as a preview. The new major version updates the hypervisor and aligns it for all workload types.
-
XenServer 9: Now from Citrix again – and not just for desktops
Citrix introduces XenServer 9 as a preview. The new major version updates the hypervisor and aligns it for all workload types.
-
XenServer 9: Now from Citrix again – and not just for desktops
Citrix introduces XenServer 9 as a preview. The new major version updates the hypervisor and aligns it for all workload types.
-
XenServer 9: Now from Citrix again – and not just for desktops
Citrix introduces XenServer 9 as a preview. The new major version updates the hypervisor and aligns it for all workload types.
-
XenServer 9: Jetzt wieder von Citrix – und nicht nur für Desktops
Citrix stellt XenServer 9 als Preview vor. Die neue Hauptversion aktualisiert den Hypervisor und richtet ihn auf alle Workload-Typen aus.
-
XenServer 9: Jetzt wieder von Citrix – und nicht nur für Desktops
Citrix stellt XenServer 9 als Preview vor. Die neue Hauptversion aktualisiert den Hypervisor und richtet ihn auf alle Workload-Typen aus.
-
XenServer 9: Jetzt wieder von Citrix – und nicht nur für Desktops
Citrix stellt XenServer 9 als Preview vor. Die neue Hauptversion aktualisiert den Hypervisor und richtet ihn auf alle Workload-Typen aus.
-
XenServer 9: Jetzt wieder von Citrix – und nicht nur für Desktops
Citrix stellt XenServer 9 als Preview vor. Die neue Hauptversion aktualisiert den Hypervisor und richtet ihn auf alle Workload-Typen aus.
-
XenServer 9: Jetzt wieder von Citrix – und nicht nur für Desktops
Citrix stellt XenServer 9 als Preview vor. Die neue Hauptversion aktualisiert den Hypervisor und richtet ihn auf alle Workload-Typen aus.
-
What would be the equivalent of Scheduler KIST (a C-tor option at one time) in #Rust #Arti #tor? Certainly not an option in the future paradigm. A man pages for the Cargo modules at (crates.io)? We can see "low water" in Arti which is exactly the cure. But it appears that a priesthood of operators will be in control of the fine tuning the torrc once had.
- Tor network adversary obstructs and degrades service with traffic shaping techniques.
"active bandwidth perturbations"
https://arxiv.org/pdf/2605.05887- Threat Actor blocks tor from VMs
but TAILS not obstructed (virtuio pci, module xen uevent -- abstractions from hardware) -- pvh destroyed in Xen (libxl)
#TargetedHardware #LibrariesWeaponizedAgainstThePublic
#Qemu #KVM #Xen #Virtualization #Censorship #MT #TickTalk #SuperFilter -
What would be the equivalent of Scheduler KIST (a C-tor option at one time) in #Rust #Arti #tor? Certainly not an option in the future paradigm. A man pages for the Cargo modules at (crates.io)? We can see "low water" in Arti which is exactly the cure. But it appears that a priesthood of operators will be in control of the fine tuning the torrc once had.
- Tor network adversary obstructs and degrades service with traffic shaping techniques.
"active bandwidth perturbations"
https://arxiv.org/pdf/2605.05887- Threat Actor blocks tor from VMs
but TAILS not obstructed (virtuio pci, module xen uevent -- abstractions from hardware) -- pvh destroyed in Xen (libxl)
#TargetedHardware #LibrariesWeaponizedAgainstThePublic
#Qemu #KVM #Xen #Virtualization #Censorship #MT #TickTalk #SuperFilter -
as far as I understand
#Xen: What is the minimal hardware we need to emulate to get a VM? We might need to customise/change the operating system.
qemu(+kvm): Let's emulate the full PC with mainboard and all chipsets and everything. Damn that is slow. Lets reinvent optimised virtual hardware in the #VirtIO project.
-
Is there any technical reason why one would consider using Xen (or XCP-ng) over KVM at this point?
-
Is there any technical reason why one would consider using Xen (or XCP-ng) over KVM at this point?
-
[Перевод] Как я убедил виртуальную машину, что у неё есть кулер
Зачем вообще этим заморачиваться? Некоторые образцы malware выполняют различные проверки, чтобы определить, запущены ли они в виртуальной машине. Один из самых частых способов — проверка наличия определённых аппаратных компонентов, обычно не эмулируемых в виртуальных средах. Один из таких компонентов — кулер процессора . Например, malware может проверять наличие кулера процессора, поискав в WMI класс Win32_Fan : wmic path Win32_Fan get * Они делают это, чтобы не запускаться в виртуальных машинах, усложнив таким образом процесс анализа для исследователей безопасности. Зловредное ПО может определять, запущено ли оно в виртуальной машине, множеством разных способов. Есть различные классы WMI, позволяющие обнаружит присутствие виртуальной машины, например, Win32_CacheMemory , Win32_VoltageProbe и множество других . В этом посте я расскажу о кулере процессора. Мне просто понравилась идея убедить виртуальную машину, что он у неё есть. Однако такой же подход можно применить к другим аппаратным компонентам и классам WMI.
-
#KpopMonday theme: #CoversOfNotKpop
We Don't Talk Anymore covered by Xen of Omega X
https://www.youtube.com/watch?v=g0QgBP67SJA&ab_channel=OMEGAX
-
Interestingly, #seL4 would be a worse choice that #Xen for #QubesOS, due to its worse support for x86 speculative execution mitigations. Xen typically provides patches the day the embargo breaks, and Qubes OS users rely on that. There are various ways to make speculative execution less of a concern, but they don’t work for Qubes OS. This is because Qubes OS heavily overcommits CPU and allows execution of arbitrary untrusted code in VMs.
I don’t fault the seL4 developers for not focusing on a use-case that is practically the worst-case scenario for it. It just means that Qubes OS is very much more like a server than an embedded system, and so it needs a hypervisor that is designed for the kinds of workloads it runs.
-
Interestingly, #seL4 would be a worse choice that #Xen for #QubesOS, due to its worse support for x86 speculative execution mitigations. Xen typically provides patches the day the embargo breaks, and Qubes OS users rely on that. There are various ways to make speculative execution less of a concern, but they don’t work for Qubes OS. This is because Qubes OS heavily overcommits CPU and allows execution of arbitrary untrusted code in VMs.
I don’t fault the seL4 developers for not focusing on a use-case that is practically the worst-case scenario for it. It just means that Qubes OS is very much more like a server than an embedded system, and so it needs a hypervisor that is designed for the kinds of workloads it runs.