linux:proxmox

Linux.proxmox

influx https://forum.proxmox.com/threads/integrating-influxdb2-data-with-temperature-and-disks-info.118615/
cpu and drive temp https://forum.proxmox.com/threads/proxmox-cpu-temp-and-using-in-vms.140742/

add temp in summary table : nvme: 48.85℃ , drivetemp: 40℃ , coretemp: 48℃

see install upper in gpu-virtualization-with-intel-12th-gen-igpu-uhd-730/
samba on Jellyfin <https://chrisatech.wordpress.com/2022/06/20/jellyfin-installation-and-adding-an-smb-server-to-the-library/>

  1. sudo mkdir /mnt/nas
  2. sudo apt-get install cifs-utils
  3. sudo mount -t cifs -o user=video //192.168.114.134/video /mnt/nas
  4.  
  5. # Create the directory /mnt/nas
  6. mkdir /mnt/nas
  7.  
  8. # Create the .smb file with the specified content
  9. echo -e "username=video\npassword=SETPWD" > ~/.smb
  10.  
  11. # Add the mount entry to /etc/fstab, replacing 'chris' with the current user
  12. echo "//192.168.114.134/video /mnt/nas cifs uid=0,credentials=$(eval echo ~)/.smb,iocharset=utf8,vers=3.0,noperm 0 0" | sudo tee -a /etc/fstab
# MOK problem
I solved this problem.
 
Create a Live USB/CD of Ubuntu 17.10.
Boot this USB/CD in UEFI mode (the problem doesn't happen with this version).
Open terminal and use this command: sudo mokutil --reset.
Try to boot with the system you want to install.
If you get this another error "Failed to open \EFI\BOOT\mmx64.efi", change the file name of "grubx64.efi" to "mmx64.efi" (located on /efi/boot on USB/CD).
Boot again and you will see no errors (I hope so).

Виртуализация

создание template из preconfigured cloud imag

5 useful Proxmox VE CLI tools Here are 5 useful Proxmox VE commands for your CLI:

  1. Get a quick overview on how fast your system is:
    pveperf
  2. List all your KVM machines:
    qm list
  3. See how much memory your machine 101 has:
    qm config 101 | grep ^memory
  4. Verify the subscription status of your hardware node:
    pvesubscription get
  5. Start a backup of machine 101:
    vzdump 101 -compress lzo

Want to learn more commands for your Proxmox VE CLI? Just head to https://pve.proxmox.com/wiki/Command_line_tools

If got error trying to acquire lock… TASK ERROR: can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout

 rm /var/lock/qemu-server/lock-102.conf
#  -------------------------
#  P2P migration
#    copy files with image HDD to PVE in tmp directory 
$ /var/lib/vz_local-v3700/tmp
sftp,scp,rsync,nc 
 
#  SFTP    ~80mbit
$sftp root@10.59.6.19:/var/lib/vz_local-v3700/tmp <<< $'put ./isoj-d.hdd.qcow2'
 
#  SCP     ~40mBytes
$scp ./isoj-d.hdd.qcow2 root@10.59.6.19:/var/lib/vz_local-v3700/tmp
# buffered SCP - ~80mBytes
$tar cf - ./isoj-d.hdd.qcow2 | mbuffer | ssh melnikov_ea@10.59.0.64 "tar xf -"
 
#  NETCAT ~~ 40mBytes
#SRC ->
$tar cv ./ | nc -q 1 10.59.6.19  1234
#DST <-
$nc -q 1 -l -p 1234 | pv -pterb -s 500G | tar xv
 
#!!! Rsync ~~ 85-100 MBytes 
$rsync -e 'ssh -c [email protected]' -avP ./ root@10.59.6.19:/var/lib/vz_local-v3700/tmp
# Accelerate Rsync
 
 
# create VM
qm create 120 --bootdisk scsi0 
# import DISK
qm importdisk 120 someImage.img someStorage
# set disk to VM
qm set 120 --scsi0 someStorage:vm-120-disk-0
 
#  or create VM from UI with right size and name
#  replace disk image with source image
$ cd /var/lib/vz_local-v3700/images/102
$ mv ../../tmp/harddisk.hdd.qcow2 vm-102-disk-0.qcow2

Proxmox.AGP

Hostname IP URL Hardware
ispdn-prox01 10.59.6.xx https://prox01.gorod.ru:8006/ IBM x3850 X5 7143
ispdn-prox02 10.59.6.xx https://prox02.gorod.ru:8006/ IBM x3850 X5 7143
ispdn-prox03 10.59.6.xx https://prox03.gorod.ru:8006/ IBM x3850 X5 7143
  • linux/proxmox.txt
  • Last modified: 2024/07/14 12:24
  • by admin