Another way to move Virtualbox VDI to Proxmox VE

There is another way to do the importing Virtualbox VDI to Proxmox VE 3.5-8.

Similar to my previous post.

Step 1, Copy the VDI into the Proxmox VE host

No need to covert the VDI file to RAW format. Just copy the vdi file into the local folder. For me, I will just put it at /root/testing.vdi

Step 2, Create a new VM in Proxmox

On the “OS” tab, choose “Do not use any media”

On the “Hard Disk” tab, choose “local-lvm”, as storage, Disk size is any size you want, for example, 8GB. Format, choose “Raw disk image (raw)”, On CPU and Memory, choose the same as the Virtualbox settings.

Confirm to create the new VM.

Step 3, Detach and Remove the Hard Disk

Say my VM ID is 109, choose Virtual Machine 109, Hardware, Hard Disk, choose “Detach” button.

Detach the Hard Disk

At this point, the hard disk will be listed as “Unused Disk.” It still exists but is not attached to the system. To destroy it completely, select the Unused Disk and click Remove again; and confirm when prompted.

Continue reading “Another way to move Virtualbox VDI to Proxmox VE”

Move Virtualbox VDI to Proxmox VE System

I have some Virtualbox virtual machine on my desktop. Now I have Proxmox VE 5.3-8 installed on a separate machine. So I would like to move the VM to Proxmox.

Let me list the existing installation.

  • My Desktop, Windows 10 Pro version 1809.
  • Virtualbox 6.0.4 r128413
  • Guest VM inside of Virtualbox is Ubuntu 18.04 with 1G memory and 20GB disk space.
  • Proxmox VE 5.3-8, VM and LXC are stored in the local-lvm

 

Step 1, Located the vdi file and convert it to RAW format

Virtualbox vdi file location

Check the settings of the virtual machine, storage, and located the location of the vdi file. Mine is in the d:\Virtualbox VM\

Then open a command prompt window, enter the following command to convert the vdi file to raw image file.

d:
cd "program files\oracle\virtualbox"
vboxmanage clonehd --format RAW "d"\virtualbox vm\ubuntu 18.04 (122)\ubuntu 18.04.vdi" d:\testing.img

After a while the new image file is ready. The time depends on the size of your VM. Maybe 10 minutes or half an hour.

Converting

Continue reading “Move Virtualbox VDI to Proxmox VE System”

Error when doing update on Proxmox VE

I got these errors when trying to run an update on my Proxmox VE 5.3-8

root@pve:/etc/apt# apt update Hit:1 http://security.debian.org stretch/updates InRelease Ign:2 http://ftp.ca.debian.org/debian stretch InRelease Get:3 http://download.proxmox.com/debian jessie InRelease [2,413 B] Hit:4 http://ftp.ca.debian.org/debian stretch-updates InRelease Err:3 http://download.proxmox.com/debian jessie InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C23AC7F49887F95A Hit:5 http://ftp.ca.debian.org/debian stretch Release Ign:7 https://enterprise.proxmox.com/debian/pve stretch InRelease Err:8 https://enterprise.proxmox.com/debian/pve stretch Release 401 Unauthorized Reading package lists... Done W: GPG error: http://download.proxmox.com/debian jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C23AC7F49887F95A E: The repository 'http://download.proxmox.com/debian jessie InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'https://enterprise.proxmox.com/debian/pve stretch Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.

How to fix these errors?

Continue reading “Error when doing update on Proxmox VE”

Upgrade of my Desktop PC

It is time to upgrade my desktop. The six years old computer.

CPU:  AMD Ryzen 5 2400G

  • CPU has 4 Cores, 8 Threads.
  • GPU has 11 Cores
  • Base clock: 3.6Ghz, Max Boost Clock: 3.9GHz
  • Cache: L1 384KB, L2 2MB, L3 4MB
  • Unlocked: Yes
  • CMOS: 14nm FinFET
  • Package: AM4
  • PCIe: PCIe 3.0×8
  • Thermal Solution: Wraith Stealth
  • TDP: 65W
  • Max Temps: 95°C

Vi.

CPU-Z: AMD Ryzen 5 2400G

 

Ryzen 5 2400G Caches information

 

AMD Radeon RX Vega 11 Graphics

Motherboard: Gigabyte B450M DS3H

  • Chipset: AMD B450
  • Memory: 4 x DDR4 DIMM  sockets supporting up to 64 GB, Dual channel, Support for DDR4 3200(O.C.)/2933/2667/2400/2133 MHz, Support ECC/Non-ECC, XMP.
  • Onboard Graphics: 1 x DVI-D port, 1X HDMI port.
  • Expansion Slots: 1 x PCI express x 16 slot, running at x16; 1 x PCI express x 16 slot, running at x4; 1 x PCI express x 1 slot.
  • Storage Interface: 1 x M.2 connector(Socket 3, M key); 4 x SATA 6Gb/s connectors; Support for RAID 0, 1, 10.
  • USB: Chipset supports 2 x USB 3.1 Gen 1 ports through internal USB header; 8 x USB 2.0/1.1 ports(4ports on the back panel, 4 ports available through the internal USB headers)
    CPU supports 4 x USB 3.1 Gen 1 ports on the back panel

vi

Gigabyte B450M DS3H

 

RAM: Corsair Vengeance LPX DDR4 2X8GB

#CMK16GX4M2Z2400C16

  • Configuration: Dual/Quad Channel
  • Series: VENGEANCE LPX
  • Size: 16GB Kit (2 x 8GB)
  • Latency: 16-16-16-39
  • Voltage: 1.2V
  • Speed: 2400MHz
  • Color: Black
  • Rating: PC4-19200 (24MHz)
  • Heat Spreader: Anodized Aluminum
  • Format:L DIMM
  • Profile: XMP 2.0
  • Pin: 288
DDR4 16GB Dual channel, Corsair Vengeance LPX

 

SPD information of Corsair Vengeance LPX 2400

 

Look at the pictures.

Continue reading “Upgrade of my Desktop PC”

Lots of favicon.ico requests from Mainland China

I check the Nginx error log file regularly. I noticed that a lot of attempted accesses to favicon.ico coming from mainland China.

They come from different IP addresses and with different User Agents.  Each of these IPs is only doing this, sometimes repeatedly.

They are just waste my server’s time and CPU.  How to stop them or reduce the effect on my VPS.

Continue reading “Lots of favicon.ico requests from Mainland China”

SSL Certificate Checker

After installing the SSL certificate on the Nginx web server, you need to check if it is installed correctly.

I installed the SSL certificate two months ago. The Sectigo ECC certificate.

Now I change the certificate files.

Previously, I put the site SSL certificate file content and the SSL-bundle file altogether. The final SSL certificate file is 4.36KB. It includes three certificates. The guide is from Comodo official site. Sectigo site has a similar guide here.

Now, I remove the last one. Just keep the site certificate and the middle one. Total size is  3.01KB.

The certificate I deleted from the old file is for USERTrust ECC Certification Authority. It is already included in the Trusted Root CA list.

Then, I tested the new certificate file, which has two certificates only, on different online SSL checking tools.

 

Geocerts SSL checking Result

Continue reading “SSL Certificate Checker”

New Campaign for my Blog

It is a new year, 2019. Almost passed the first quarter.

I would like to increase Blog traffic in 2019. So, It is a new two weeks campaign.

There are certain things I will do on my blog.

  • Clean the old post.
  • Fix or remove the broken links.
  • Blog UI re-design or change.
  • Improve the web page load speed.
  • Fix the featured image of each post.
  • Make more post on my Blog.
  • Promote the Blog on Search Engine.
  • Promote the Blog on Social Media Site.
  • Connection with other blog and/or web sites.
  • On-site optimization.

Continue reading “New Campaign for my Blog”

AMD B450 Motherboard

My computer I am using now has A55M-P33 motherboard. It uses AMD A55 chipset. I have ordered a new motherboard for my next PC upgrade.

Gigabyte B450M DS3H

GIGABYTE B450M DS3H (AMD Ryzen AM4/M.2/HMDI/DVI/USB 3.1/DDR4/Micro ATX/Motherboard)

Some pictures of it.

Front View
Main View
Back Panel

When I upgrade my desktop with this new motherboard, there are some upgrade for whole system.

Let me list these news below:

  • DDR3 to DDR4
  • SATA II to SATA III
  • USB 2.0 to USB 3.1
  • PCIE Gen.2 to PCIE 3.0

Continue reading “AMD B450 Motherboard”

Desktop PC I am using for six years

The PC I am using right now is more than six years.  I checked my blog and found the post of flash the bios in Feb 2013. I did a search in my Gmail. Wow, I found the receipt which I made the order on NCIX. NCIX has closed for years already.

There are three items. All are running on my desktop now.

  • Kingston Hyper X  KHX 1600C9D3K2/8GB  (RAM)
  • Western Digitial Caviar Blue 1TB (HDD)
  • AMD A8-3870K Black APU Quad Core Processor and MSI A55M-P33 mATX FM! Motherboard (MoBo CPU bundle)

Later I bought a Crucial SDD for Windows system.

Continue reading “Desktop PC I am using for six years”

Report the bad IP address to the AbuseIPDB

I have a VPS on DigitalOcean.  Web server is Nginx web server. I checked the web server log files, including an access log and error log.

The error log always gives information about the strange activities from some IP address.

2019/03/17 03:08:02 [error] 781#781: *140434 access forbidden by rule, client: 183.240.196.121, server: www.yinfor.com, request: "HEAD //com/.zip HTTP/1.1", host: "www.yinfor.com", referrer: "http://www.yinfor.com//com/.zip"
2019/03/17 03:08:04 [error] 781#781: *140451 access forbidden by rule, client: 183.240.196.121, server: www.yinfor.com, request: "HEAD //com/..zip HTTP/1.1", host: "www.yinfor.com", referrer: "http://www.yinfor.com//com/..zip"
2019/03/17 03:08:06 [error] 781#781: *140452 access forbidden by rule, client: 183.240.196.121, server: www.yinfor.com, request: "HEAD //www.yinfor.com/..zip HTTP/1.1", host: "www.yinfor.com", referrer: "http://www.yinfor.com//www.yinfor.com/..zip"
2019/03/17 03:08:07 [error] 781#781: *140453 access forbidden by rule, client: 183.240.196.121, server: www.yinfor.com, request: "HEAD //com/.rar HTTP/1.1", host: "www.yinfor.com", referrer: "http://www.yinfor.com//com/.rar"
2019/03/17 03:08:08 [error] 781#781: *140454 access forbidden by rule, client: 183.240.196.121, server: www.yinfor.com, request: "HEAD //com/..rar HTTP/1.1", host: "www.yinfor.com", referrer: "http://www.yinfor.com//com/..rar"
2019/03/17 03:08:10 [error] 781#781: *140456 access forbidden by rule, client: 183.240.196.121, server: www.yinfor.com, request: "HEAD //www.yinfor.com/..rar HTTP/1.1", host: "www.yinfor.com", referrer: "http://www.yinfor.com//www.yinfor.com/..rar"
2019/03/17 06:10:41 [error] 781#781: *145806 access forbidden by rule, client: 192.99.35.63, server: www.yinfor.com, request: "GET /wp-content/uploads/2019/03/settings_auto.php HTTP/1.1", host: "www.yinfor.com"
2019/03/17 13:21:35 [error] 781#781: *160016 access forbidden by rule, client: 139.99.121.91, server: www.yinfor.com, request: "GET /.htaccess?c=askjhGQVFcrwqevq&q=ZWNobyA0Mzc0NTc1NDc7 HTTP/1.1", host: "www.yinfor.com"
2019/03/17 13:22:21 [error] 781#781: *160124 access forbidden by rule, client: 139.99.121.91, server: www.yinfor.com, request: "GET /.well-known.zip HTTP/1.1", host: "www.yinfor.com"
2019/03/17 13:22:22 [error] 781#781: *160125 access forbidden by rule, client: 139.99.121.91, server: www.yinfor.com, request: "GET /.well-known.tar.gz HTTP/1.1", host: "www.yinfor.com"
2019/03/17 13:22:22 [error] 781#781: *160126 access forbidden by rule, client: 139.99.121.91, server: www.yinfor.com, request: "GET /.well-known.gz HTTP/1.1", host: "www.yinfor.com"

You can see the URL requested is so strange. Actually, I banned these IP address already. So the Nginx server recorded the access forbidden log.

I am not banning these IP address, but also want to report it to the AbusedIPDB.

When finding a bad IP address, I will sign in the AbuseIPDB site and report it.

Please enter the information of the behave and the details of the IP log.

 

AbuseIPDB is not just a reporting tool. The registered users can also use its API to check the IP if it is bad or spam IP. It works with Fail2Ban.

  • Archives