The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,091 other followers

Archive for the ‘Proxmox’ Category

« Previous Entries

Always use SCSI for your VM guest disks – Jeroen Wiert Pluimers – Google+

Posted by jpluimers on 2020/01/20

Rephrased from [WayBack] Jeroen Wiert Pluimers – Google+:

If you install a virtual machine, ensure the disk controller and disks are SCSI based.

This has many advantages, including:

  • speed (usually the SCSI drivers can be paravirtualised)
  • hot addition of new disks

It holds for virtually any virtualization platform including all non-ancient (less than ~10 year old) versions of:

  • VMware (Workstation, Viewer, but I expect this also to work on vSphere, ESXI, Fusion)
  • Hyper-V
  • KVM (and therefore Proxmox)
  • VirtualBox

Based on my notes in the above link and the links below:

Note this isn’t just for Linux guests/hosts: Most guests (including Windows) can do a SCSI bus re-scan and detect new SCSI devices.

The trick here is that the guest must already have a virtual SCSI controller (adding that will require a reboot of the guest).

Then adding a new SCSI disk on that controller from any host (Windows, Mac, ESXi, vSphere) should work fine.

–jeroen

Posted in ESXi4, ESXi5, ESXi5.1, ESXi5.5, ESXi6, ESXi6.5, Fusion, Hyper-V, KVM, Power User, Proxmox, View, VirtualBox, Virtualization, VMware, VMware ESXi, VMware Workstation | Leave a Comment »

airbus-seclab/crashos

Posted by jpluimers on 2018/10/30

Cool repository, but contact your cloud provider before trying…: [WayBack] airbus-seclab/crashos.

via:

–jeroen

Posted in Fusion, Hyper-V, KVM, Power User, Proxmox, View, VirtualBox, Virtualization, VMware, VMware ESXi, VMware Workstation | Leave a Comment »

Check If A Linux System Is Physical Or Virtual Machine

Posted by jpluimers on 2018/10/08

One day I am going to try to extend this for a few other virtualisation environments and Linux distributions: [WayBack] Check If A Linux System Is Physical Or Virtual Machine

Via: [WayBack] Check If A Linux System Is Physical Or Virtual Machine #Linux – Joe C. Hecht – Google+

–jeroen

Posted in *nix, *nix-tools, Fusion, Hyper-V, KVM, Power User, Proxmox, View, VirtualBox, Virtualization, VMware, VMware ESXi, VMware Workstation | Leave a Comment »

Virtual Machine Startup and Shutdown Behavior – Proxmox VE

Posted by jpluimers on 2018/02/23

For my link archive as this is configured per VM on the VM level which is different from for instance ESXi: [WayBack] Virtual Machine Startup and Shutdown Behavior – Proxmox VE

  • Start at boot yes/no
  • Start/Shutdown order: order=# (or any) up=## (or nothing)

–jeroen

Posted in Power User, Proxmox, Virtualization | 2 Comments »

Some useful commands for Proxmox high IO troubleshooting

Posted by jpluimers on 2018/02/13

After trying to move an operating system from one disk to another, Proxmox stalled the console and ended up in a really high I/O delay.

These commands helped me finding out what was wrong:

apt-get install iotop
iotop
ps -aux | grep usbbackup
ps -aux | grep rsync
zpool status
lvscan
qm list
qm unlock ###
qm stop ###

Somehow Proxmox was thinking the VM ### was still in use, but on Linux level it wasn’t:

# lvscan
ACTIVE '/dev/pve/swap' [8.00 GiB] inherit
ACTIVE '/dev/pve/root' [27.75 GiB] inherit
ACTIVE '/dev/pve/data' [62.04 GiB] inherit
ACTIVE '/dev/pve/vm-###-disk-1' [40.00 GiB] inherita

–jeroen

Posted in *nix, Power User, Proxmox, Virtualization | Leave a Comment »

« Previous Entries
 
%d bloggers like this: