xen   6887

« earlier    

Win 7, Server 2008 'Total Meltdown' exploit lands, pops admin shells • The Register
Create a new set of page tables which will allow access to any physical memory address;
Create a set of signatures which can be used to hunt for _EPROCESS structures in kernel memory;
Find the _EPROCESS memory address for our executing process, and for the System process; and
Replace the token of our executing process with that of System, elevating us to NT AUTHORITY\System.
microsoft  meltdown  vulnerability  exploit  xen 
8 weeks ago by bwiese
A fully supported solution on a great hardware platform for development. If you plan to develop an e…
embedded  Xen  from twitter_favs
february 2018 by vielmetti
XCP-ng | Building XenServer from the sources
What is XCP-ng?

XCP (Xen Cloud Platform) was the free/libre equivalent of XenServer before this last one was open sourced. It was logically shutdown then.

But since XenServer 7.3 removed a lot of free features, we need a community solution again: XCP-ng is now the logical successor.
xen  server  cloud 
january 2018 by euler
Remus provides transparent, comprehensive high availability to ordinary virtual machines running on the Xen virtual machine monitor. It does this by maintaining a completely up-to-date copy of a running VM on a backup server, which automatically activates if the primary server fails.
sysadmin  xen  kvm  vm  virtualization 
january 2018 by dusko
AWS EC2 Virtualization 2017: Introducing Nitro
Hardware virtualization for cloud computing has come a long way, improving performance using technologies such as VT-x, SR-IOV, VT-d, NVMe, and APICv. At Netflix, we've been using these technologies as they've been made available for instance types in the AWS EC2 cloud. The latest AWS hypervisor, Nitro, uses everything to provide a new hardware-assisted hypervisor that is easy to use and has near bare-metal performance. It's an exciting development in cloud computing: hardware virtualization is now fast.

I've summarized hypervisor developments in EC2 with the above diagram. The columns show dimensions of instance performance, ordered in importance for typical workloads at Netflix (CPU-bound being the most important). The rows of this table are virtualization types, and the cells show the type of virtualization and are colored by the expected performance.

You may first notice that, over time, green is creeping in from the left. That's deliberate engineering: optimizing the most important workloads first. Each dimension has progressed through these stages:
aws  virtualization  xen  hypervisors 
january 2018 by euler

« earlier    

related tags

aarch32  agl  archlinux  arm  arm32  arm64  armhf  armservers  asian  availability  aws  backup  bhyve  binary  bookmarks_toolbar  booting  bootloader  boxgrinder  bsd  bugs  carti  cloud  cloudstack  coink  compiler  computer  configuration  containers  craig  datacenter  debian  devops  docker  documentation  domu  download  drivers  elixir  embedded  erlang  exokernel  exploit  faq  floss  ford  freebsd  golang  guy  ha  high  hip  homelab  hop  hyper-v  hyperconverged  hypervisor  hypervisors  ifttt  info  ip  kernel  kernelmodule  kickstarter  kvm  libvirt  linux  lvm  lxc  meltdown  meta  microsoft  networking  no.os  ocaml  opensource  openstack  openvswitch  operating  operatingsystem  operations  os  oss  oz  paper  pink  pizza  playboy  plugin  privacy  programming  public_bookmarks  python  qemu  qubes  raff  rap  raspberrypi  reference  riff  rock64  rootkovska  router  rsnapshot  rsync  secure  security  server  sgx  sle  snapshot  snowden  spectre  studio  suse  sysadmin  system  tids  tips  toms  troubleshooting  uboot  ubuntu  unikernel  vagrant  virtual  virtualbox  virtualisation  virtualization  vm  vmdp  vms  vmware  vtd  vulnerability  webui  whonix  wikientry  windows  windowserver  wordpress  work  xcp  xenserver  yocto 

Copy this bookmark: