#xen — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #xen, aggregated by home.social.
-
Reading up a bit on Linux containers
I wonder if the efficiency of them is close to that of freeBSD jails
#Containers #VM #freeBSD #jails #programming #XEN #networking
-
Reading up a bit on Linux containers
I wonder if the efficiency of them is close to that of freeBSD jails
#Containers #VM #freeBSD #jails #programming #XEN #networking
-
Reading up a bit on Linux containers
I wonder if the efficiency of them is close to that of freeBSD jails
#Containers #VM #freeBSD #jails #programming #XEN #networking
-
Reading up a bit on Linux containers
I wonder if the efficiency of them is close to that of freeBSD jails
#Containers #VM #freeBSD #jails #programming #XEN #networking
-
Reading up a bit on Linux containers
I wonder if the efficiency of them is close to that of freeBSD jails
#Containers #VM #freeBSD #jails #programming #XEN #networking
-
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.
-
citrix XenServer 9 has been published today.
be aware of some changes:
* systemd "predictable" network interface names in dom0
* Host BIOS Boot Support has been removed
* Linux Bridge Network Stack has been removed
https://docs.xenserver.com/en-us/xenserver/9/whats-new
#citrix #XenServer #Xen -
citrix XenServer 9 has been published today.
be aware of some changes:
* systemd "predictable" network interface names in dom0
* Host BIOS Boot Support has been removed
* Linux Bridge Network Stack has been removed
https://docs.xenserver.com/en-us/xenserver/9/whats-new
#citrix #XenServer #Xen -
citrix XenServer 9 has been published today.
be aware of some changes:
* systemd "predictable" network interface names in dom0
* Host BIOS Boot Support has been removed
* Linux Bridge Network Stack has been removed
https://docs.xenserver.com/en-us/xenserver/9/whats-new
#citrix #XenServer #Xen -
citrix XenServer 9 has been published today.
be aware of some changes:
* systemd "predictable" network interface names in dom0
* Host BIOS Boot Support has been removed
* Linux Bridge Network Stack has been removed
https://docs.xenserver.com/en-us/xenserver/9/whats-new
#citrix #XenServer #Xen -
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 -
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 -
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.
-
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.
-
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.
-
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.
-
-
-
-
-
-
CW: На днях появился BlueHammer — опубликованный прототип уязвимости нулевого дня в Windows-системах. Позволяет повысить права (привелегии) в системе до уровня учётной записи SYSTEM или расширенных админских.
Уязвимость нулевого дня оказалась опубликована вместе с протипом (примером) использования. Опубликовано человеком (Chaotic Eclipse), которому не удалось сообщить о проблеме через официальные каналы Microsoft, потому что соответствующее подразделение (MSRC) захотело прямо аж видео с подтверждением работоспособности данной уязвимости. Отказываясь иначе вести диалог и принимать информацию к сведению.
Это тот апофеоз тотальной идиотии, который преобладает в Microsoft последние 10+ лет. Ниже расписано более детально по этой теме.
Очередное дно пробито, но это не первый раз, а стабильность — это верный признак мастерства.
Нет такого, что Linux или BSD-системы вдруг стали модными и популярными, это людям приходится уходить с Windows-систем из-за такого качества работы Microsoft.
#bluehammer #microsoft #windows #cve #lang_ru @Russia
RE: https://hub.hubzilla.de/item/fadba136-52e4-46e3-9101-5d8c7b0d61fb -
Xen Hypervisor – Open-Source-Virtualisierung für Systemadministratoren
Hier kommt die Einleitung in das Thema mit Hinweisen, wozu du Xen als Systemadministrator wissen solltest. Xen ist ein leistungsstarker, open-source Type-1-Hypervisor, der dir ermöglicht, mehrere virtuelle Maschinen (Domains) parallel auf einem physischen Host zu betreiben, ohne dass ein Host-Betriebssystem dazwischen funktioniert. Du solltest Xen kennen, weil es in älteren Linux-Umgebungen wie Red Hat Enterprise Linux 5 eine Standardlösung für Virtualisierung war und dir hilft, […]https://andreas-moor.de/xen-hypervisor-open-source-virtualisierung-fuer-systemadministratoren/
-
#Xen jetzt mit 5 Jahren Sicherheitssupport
-
#Xen jetzt mit 5 Jahren Sicherheitssupport
-
#Xen jetzt mit 5 Jahren Sicherheitssupport
-
#Xen jetzt mit 5 Jahren Sicherheitssupport
-
#Xen jetzt mit 5 Jahren Sicherheitssupport
-
At @bawuenet we're in the process of upgrading our #Xen #xcpng hypervisors to #uefi boot. Of course, we automate things and want to be able to reinstall our hypervisors from network boot. Our EFI netboot system is based on #ipxe which means it can only load EFI binaries. But xcp-ng ships the Xen kernel as a multiboot2 based image.
As probably one of the most weird ways to solve this problem, I've decided to chainload #grub2 from iPXE and learned a bit! 🧵 -
At @bawuenet we're in the process of upgrading our #Xen #xcpng hypervisors to #uefi boot. Of course, we automate things and want to be able to reinstall our hypervisors from network boot. Our EFI netboot system is based on #ipxe which means it can only load EFI binaries. But xcp-ng ships the Xen kernel as a multiboot2 based image.
As probably one of the most weird ways to solve this problem, I've decided to chainload #grub2 from iPXE and learned a bit! 🧵 -
At @bawuenet we're in the process of upgrading our #Xen #xcpng hypervisors to #uefi boot. Of course, we automate things and want to be able to reinstall our hypervisors from network boot. Our EFI netboot system is based on #ipxe which means it can only load EFI binaries. But xcp-ng ships the Xen kernel as a multiboot2 based image.
As probably one of the most weird ways to solve this problem, I've decided to chainload #grub2 from iPXE and learned a bit! 🧵 -
At @bawuenet we're in the process of upgrading our #Xen #xcpng hypervisors to #uefi boot. Of course, we automate things and want to be able to reinstall our hypervisors from network boot. Our EFI netboot system is based on #ipxe which means it can only load EFI binaries. But xcp-ng ships the Xen kernel as a multiboot2 based image.
As probably one of the most weird ways to solve this problem, I've decided to chainload #grub2 from iPXE and learned a bit! 🧵 -
At @bawuenet we're in the process of upgrading our #Xen #xcpng hypervisors to #uefi boot. Of course, we automate things and want to be able to reinstall our hypervisors from network boot. Our EFI netboot system is based on #ipxe which means it can only load EFI binaries. But xcp-ng ships the Xen kernel as a multiboot2 based image.
As probably one of the most weird ways to solve this problem, I've decided to chainload #grub2 from iPXE and learned a bit! 🧵 -
I wish this post by the Xen Project existed years ago when I was trying to understand the differences between Xen and KVM. Would have been a great jumping point to dig deeper.
https://xenproject.org/blog/xen-at-fosdem-real-world-conversations-about-xen-and-kvm/
-
So back on #QubesOS / #Xen. There is definitely something wrong with how it forwards the A380 into the #windows VM.
Now that I've remote desktop enabled (and can conenct with the A380 disconnected just fine) I now can also see a black screen via RDP when the A380 is passed into it.
(Note: passing the two end devices, aka the one for the video and the one for the audio of the A380 worked just fine in KVM on #NixOS. So it is something Xen/QubesOS does that breaks it...
-
So back on #QubesOS / #Xen. There is definitely something wrong with how it forwards the A380 into the #windows VM.
Now that I've remote desktop enabled (and can conenct with the A380 disconnected just fine) I now can also see a black screen via RDP when the A380 is passed into it.
(Note: passing the two end devices, aka the one for the video and the one for the audio of the A380 worked just fine in KVM on #NixOS. So it is something Xen/QubesOS does that breaks it...
-
So back on #QubesOS / #Xen. There is definitely something wrong with how it forwards the A380 into the #windows VM.
Now that I've remote desktop enabled (and can conenct with the A380 disconnected just fine) I now can also see a black screen via RDP when the A380 is passed into it.
(Note: passing the two end devices, aka the one for the video and the one for the audio of the A380 worked just fine in KVM on #NixOS. So it is something Xen/QubesOS does that breaks it...
-
So back on #QubesOS / #Xen. There is definitely something wrong with how it forwards the A380 into the #windows VM.
Now that I've remote desktop enabled (and can conenct with the A380 disconnected just fine) I now can also see a black screen via RDP when the A380 is passed into it.
(Note: passing the two end devices, aka the one for the video and the one for the audio of the A380 worked just fine in KVM on #NixOS. So it is something Xen/QubesOS does that breaks it...