Check Virtualization Extension 

Run this command to make sure you’ve enabled virtualization in on your computer. It should be above 0

titus@debian:~$  egrep -c '(vmx|svm)' /proc/cpuinfo

If the output is zero then go to bios settings and enable VT-x (Virtualization Technology Extension) for Intel processor and AMD-V for AMD processor.
Install QEMU and Virtual Machine Manager

titus@debian:~$ sudo apt install qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils virtinst libvirt-daemon virt-manager -y

Verify that Libvirtd service is started

titus@debian:~$ sudo systemctl status libvirtd.service

Start Default Network for Networking

VIRSH is a command to directly interact with our VMs from terminal. We use it to list networks, vm-status and various other tools when we need to make tweaks. Here is how we start the default and make it auto-start after reboot. 

titus@debian:~$ sudo virsh net-start default
Network default started
titus@debian:~$ sudo virsh net-autostart default
Network default marked as autostarted

Check status with:

titus@debian:~$ sudo virsh net-list --all
 Name      State      Autostart   Persistent
 default   active       yes          yes

Add User to libvirt to Allow Access to VMs

titus@debian:~$ sudo adduser titus libvirt
titus@debian:~$ sudo adduser titus libvirt-qemu

Reboot and you are Finished!

Taken from:

routing traffic over wireguard with mikrotik to a specific ip address…

Routing traffic for a specific destination over the VPN is definitely much easier. After creating the VPN tunnel between two Mikrotik routers, it was a two-more step process:

/ip firewall nat
add action=masquerade chain=srcnat ipsec-policy=out,none out-interface=NAME-OF-WG-INTERFACE
/ip route
add distance=1 dst-address=ip.ip.ip.ip/32 gateway=IP-OF-WG-SERVER

Larger subnets than a single ip can be routed through the VPN, and multiple subnets can be routed too. The caveat for this simpler method is that you cannot route “all” traffic (ie. to through the VPN, or else the client Mikrotik itself cannot route its own traffic either.

apt update
apt install apache2-utils squid -y
htpasswd -c /etc/squid/passwd kullaniciadi
wget -O /etc/squid/squid.conf
nano /etc/squid/squid.conf (ip adreslerini duzenle)
systemctl restart squid
systemctl enable squid


I’ve got several Ryzen Boxes with AsrockRack X470D4U and X470D4U2-2T Mainboards,

I know a lot of providers here using these exact mainboards here with their Ryzen offerrings, So maybe some help here:

My problem is after updating the latest official BMC Firmware updates,
Here and Here

Each and every mainboards BMC IPMI interface is now not responding to pings or accessible over LAN.

I can send commands using ipmitool application from linux command line.

But no matter what I do, I can’t be able to access to BMC IPMI over LAN.

Only info I can find from AsRock side is this thread from their forum:

But also this has got no official updates from AsRock.

Somebody mentioned this solution in that thread , but I also don’t have the luxury to reboot and flash old version of firmware as all these boxes are production boxes with several virtual servers on them.

Anybody using these mainboards have any clue about what to do to regain access to BMC IPMI Web interface?

As I said I can get response using IPMITOOL from command line. And everything seems to be working.

Please help..


Updates on this matter:

1- After tons / hours of brain thinkering and google searches I figure out that the most sensible way is to downgrade the bmc firmware to a “working” one.

2- I then needed ASPEED socflash utility v 1.2 linux version – which is very hard to get – Aspeed was providing it from their website but no more – After some google foo I found it. If anybody needs socflash utility v1.2 linux version, you are free to contact me.

3- flashed old bmc firmware with socflash linux utilty

root@r5:~/socflash/SOCFLASH# ./ X470D4U_P2.20.00.ima X470D4U_calismayan.ima 
ASPEED SOC Flash Utility v.1.20.00 
SoCflash utility is only for engineers to update the firmware in lab,
it is not a commercialized software product,
ASPEED has not done compatibility/reliability stress test for SoCflash.
Please do not use this utility for any mass production purpose.
Press y to continue if you are agree ....
Find ASPEED Device 1a03:2000 on 22:0.0 
MMIO Virtual Address: a364e000 
Relocate IO Base: f000 
Found ASPEED Device 1a03:2500 rev. 41 
Static Memory Controller Information: 
CS0 Flash Type is SPI 
CS1 Flash Type is SPI 
CS2 Flash Type is SPI 
CS3 Flash Type is NOR 
CS4 Flash Type is NOR 
Boot CS is 0 
Option Information: 
CS: 0 
Flash Type: SPI 
[Warning] Don't AC OFF or Reboot System During BMC Firmware Update!! 
[SOCFLASH] Flash ID : 1940ef 
Find Flash Chip #1: WinbondW25Q256/257 
Backup Flash Chip O.K.                 
Update Flash Chip #1 O.K.            
Update Flash Chip O.K.         

4- After firmware downgrade:

root@r5:~/socflash/SOCFLASH# ipmitool mc info
Device ID                 : 32
Device Revision           : 1
Firmware Revision         : 2.20
IPMI Version              : 2.0
Manufacturer ID           : 49622
Manufacturer Name         : Unknown (0xC1D6)
Product ID                : 514 (0x0202)
Product Name              : Unknown (0x202)
Device Available          : yes
Provides Device SDRs      : no
Additional Device Support :
    Sensor Device
    SDR Repository Device
    SEL Device
    FRU Inventory Device
    IPMB Event Receiver
    IPMB Event Generator
    Chassis Device
Aux Firmware Rev Info     : 
root@r5:~/socflash/SOCFLASH# ipmitool lan print 1
MAC Address             : a8:a1:59:86:f3:ec
SNMP Community String   : AMI
IP Header               : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
BMC ARP Control         : ARP Responses Enabled, Gratuitous ARP Disabled
Gratituous ARP Intrvl   : 0.0 seconds
Default Gateway IP      :
Default Gateway MAC     : 00:00:00:00:00:00
Backup Gateway IP       :
Backup Gateway MAC      : 00:00:00:00:00:00
802.1q VLAN ID          : Disabled
802.1q VLAN Priority    : 0
RMCP+ Cipher Suites     : 0,1,2,3,6,7,8,11,12,15,16,17
Cipher Suite Priv Max   : caaaaaaaaaaaXXX
                        :     X=Cipher Suite Unused
                        :     c=CALLBACK
                        :     u=USER
                        :     o=OPERATOR
                        :     a=ADMIN
                        :     O=OEM
Bad Password Threshold  : 0
Invalid password disable: no
Attempt Count Reset Int.: 0
User Lockout Interval   : 0

5- Now it’s time to Enter the usual ip address / gateway of the IPMI

LAN Configuration

ipmitool lan set 1 ipsrc static
ipmitool lan set 1 ipaddr
ipmitool lan set 1 netmask
ipmitool lan set 1 defgw ipaddr
ipmitool lan set 1 defgw macaddr 00:0e:0c:aa:8e:13
ipmitool lan set 1 arp respond on
ipmitool lan set 1 auth ADMIN MD5
ipmitool lan set 1 access on

User Configuration
A user will now be setup with admin rights.
ipmitool user set name 2 admin
ipmitool user set password 2
Password for user 2: 
Password for user 2: 
ipmitool channel setaccess 1 2 link=on ipmi=on callin=on privilege=4
ipmitool user enable 2


7- Time to upgrade to latest version of BMC firmware now :smile:

Thank you for all your answers!

hello, you can download it here:

full package for all OS’s is here:

cd /usr/local/directadmin/custombuild
./build set litespeed_serialno litespeedlicense#

cd /usr/local/directadmin/custombuild
./build update
./build set webserver litespeed
./build set php1_mode lsphp
./build set php2_mode lsphp
./build set php3_mode lsphp
./build set php4_mode lsphp
./build litespeed
./build php n


Can not find handler with type: 17, name: lsphp70.
Can not find External Application: lsphp70, type: lsapi

Litespeed admin panel -> Configuration -> Server -> External App

Command Line Should Be:

php 56  : /usr/local/php56/bin/lsphp
php 70  : /usr/local/php70/bin/lsphp
php 71  : /usr/local/php71/bin/lsphp
php 72  : /usr/local/php72/bin/lsphp
php 73  : /usr/local/php73/bin/lsphp

save & Graceful Restart


/usr/local/lsws/admin/misc/ apache

Proxmox – Shrink local ZFS disk

1- boot gparted and shrink partitions leaving free space as you like
2- in pve shell

$zfs set volsize=<new size>G rpool/data/vm-<vm id>-disk-<disk number>

Ex: zfs set volsize=50G rpool/data/vm-141-disk-0

3- edit vm config in /etc/pve/qemu-server/vm-id.conf

virtio0: local-zfs:vm-<vm id>-disk-<disk number>,size=<new size>G

IF can not boot and corrupted partition table for shrinked disk:

boot gparted

gdisk /dev/sda