Search results

You set this ? And I not sure, that all 12 port may be use, because minimum one port used for virtual keyboard/mouse.

Download firmware-linux-free, unpack iscsi_firmware.bin to removable media, insert it into the server and try continue install.

This is not a regular file, this is a block device. (but, finally in linux all is a file :) ) In a simple way, lvm-thin storage - like a physical hard drive, /dev/pve/vm-100-disk-1 like a partition on that drive. You can create another disk for that VM with appropriate size. Boot VM from any...

If you don't know, what is lvm, dd - simply create backup of needed VM and restore it to another volume.

The names of you nft storages is ext1, why you use name "nfs_ext1" ? right string is "ext1:vztmpl/ubuntu.tar.gz"

You must configure operation system in guest VM to use serial console. P.S. What limitations in web console block you to configure networks in guests VMs?

It's not console problem. try in console: export LANG=C;dpkg-reconfigure console-setup; and choose appropriate locale and console font

First of all, you must add nfs storage on your proxmox configuration through web interface or manually in storage.cfg (if you know that you do) After that, you can access to the storages by its names: nfs_storage1:iso/somedistro.iso nfs_storage2:vztmpl/somedistro.tar.gz where nfs_storage1 and...

Read this article: https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE Maybe You need "Enable IDE"

You don't describe, what OS in CT used. For test, I created Proxmox CT from debian 9 template, instal cifs-utils inside CT and try mount smb share from another linux box. fstab: //linux-box/share /mnt/share cifs _netdev,username=xxx,password=yyy,iocharset=utf8 0 0 In my situation...

Add '_netdev' to mount options in fstab, like this: //qnap/share /data cifs username=qnap,password=<your_pass>,_netdev,uid=1000,gid=1000 0 0

How you see that? Inside the storage - hardware raid. Raid logical disk shared as iscsi lun. Where is zfs? iscsi - is not file share. We can create numerous raid0 (each for single disk), and export each as iscsi lun, and use it on host as hdd's for zfs (but, IMHO it don't have any sence)

from iscsi you get block device, like hard disk, and you can partitioning and format it as you wish

set for VM configuration: machine: q35 and edit: /usr/share/perl5/PVE/QemuServer.pm find and replace 5 to 9: my $MAX_USB_DEVICES = 9; restart pve-manager.service or reboot host add usb devices in VM config (sample): usb0: host=2-1.4 usb1: host=2-1.3 usb2: host=2-1.5 usb3: host=2-1.6 usb4...

Look in /etc/default/grub and add "acpi=off" in GRUB_CMDLINE_LINUX_DEFAULT string, and run: update-grub

Hard drive crash physically or logically? What OS on VM that cannot start? type in terminal on proxmox host: vgdiaplay lvdisplay -m cat /etc/lvm/backup/* cat /etc/pve/qemu-server/104.conf ls -l /mnt/data2/backup and place output here.

I think, that is not proxmox problem, dig your system, where you running KVM.

What switch/router you use between pxe host and proxmox host?

Install dhcpdump on Proxmox Host and analyze, what happened

Try to use another type network card in VM (not e1000)