Search results

Another computer in your network boot on PXE? Firewall on Proxmox Host on/off? configured? Show from Proxmox Host: /etc/network/interfaces /etc/pve/qemu-server/xxx.conf - config your VM

Remove "quiet intel_iommu=on" and add "rootdelay=10 scsi_mod.scan=sync" parameters and try boot. How do it: When the server boots up, you will see the Grub countdown, which is set to 4 seconds by default. Press "Esc" to intercept this countdown and go enter a Grub menu. Press 'e' to start...

systemctl disable systemd-timesyncd.service

Change type VM disk to IDE, take windows live CD iso image, connect it to VM and boot from these CD, check file system on VM disk and explore it. After that, revert back type VM disk and try boot VM.

In normal situation, proxmox can't boot by hardware issues, or, if you doing something on OS by hand. If you have critical data on VMs, backup it frequently. 1. IMHO it not possible (without problems and underwater rocks) 2. Boot from CD/USB Debian Live resque system (like this), and after...

https://kernel-handbook.alioth.debian.org/ch-common-tasks.html

If You don't ran vgimportclone -n pve_old /dev/sdb1 to rename VG on sdb1, you have one VG named pve, but two UUD for it on different PV run vgcfgbackup -f /tmp/pve_cfg.vg pve it's safe and look inside /tmp/pve_cfg.vg If you rename VG on sdb1, run vgcfgbackup -f /tmp/pve_old_cfg.vg pve_old too

Right parameters: vgimportclone -n pve_old /dev/sdb1 but better run: vgcfgbackup -f /tmp/pve_cfg.vg pve and attach file /tmp/pve_cfg.vg to message, I look it, edit and send back, after that you try run vgcfgrestore -f /tmp/pve_cfg_new.vg pve

Safest way - use vgimportclone to rename VG on /dev/sdb, and, if you need, save data from these volume and reinitialize it. Another way - use vgcfgbackup to save VG metadata, edit it by hand (remove abcent volume, change UUID) and use vgcfgrestore to restore correct VG metadata.

Proxmox must upgrade by: # apt-get dist-upgrade If you can choose boot to older kernel version, try it and # apt-get update # apt-get dist-upgrade It's look like no initrd image generated for new kernel

How you update OS? What you did, step by step.

First you need read documentation... http://pve.proxmox.com/wiki/Main_Page http://pve.proxmox.com/wiki/Backup_and_Restore or read video tutorial... https://www.youtube.com/user/ProxmoxVE/videos how to VM backup schedule...

pvdisplay lvdisplay -m And look, where free space stolen.

If you dont mount on host system any partition from these HDD, stop VM and add in VMs config something like this: virtio0: /dev/disk/by-id/ata-M4-CT064M4SSD2_000000001203032B27D9 virtio1: /dev/disk/by-id/ata-WDC_WD3200AAJS-00L7A0_WD-WMAV2M315911

Create logical disk in LVM group and mount it as /backup

When You create VM, chose local-lvm storage, that is pve/data LVM-Thin storage pool. cat /etc/pve/storage.cfg and look all storages in You pve instance. And carefully read this link. Maybe You need read some books...

This simply idea, I don't tested it. /etc/network/interfaces auto lo iface lo inet loopback iface eth0 inet manual iface tap1 inet manual pre-up ip tuntap add tap1 mode tap user root up ip link set dev tap1 up post-down ip link del dev tap1 auto vmbr0 iface vmbr0 inet static address...

Please, read carefully: Proxmox Cluster file system Proxmox node name change

Please, read carefully these docs: Storage Model Storage LVM Storage ZFS

lvdisplay -m and look, what use all space.