Search results

i never see any script like that.. Anyhow, at prox 7.2 they change setting and adjustment need to be made. and a on the part, different setting to be done with vm and grub base on your hrdw. Or simply, disconnect your modem, install prox 7.1 iso, set the setting and hop all work. or 7.4iso, set...

While it look simple to run in a script.. it look there is not a full backup ? As yes, /root/ is not important, the /sbin and /usr/local/, might be best to add.. If we install any package, some config end up to the /var, so having just the: /var/lib/pve-cluster/* might cause missing file ...

hehe this cannot be more clear than this. great!

While i do see the need to change the controller scsihw: to LSI 935.. or Lsi 810 wasn't it give slower performance as well ? In the smbios, is putting like: given by O.E.M at sku or at model is needed / help ? I will try to play with the setting : balloon: 0 if any help as affecting...

Could it be possible to post the content of your vmxxx .conf file ? It will help to see what the controller effect and cpu args you set at to have it work. thanks

If you read and apply different 'tuto you find online' as you mention, just follow them properly as different version have different setting, but not too much change. Basically: disconnect your modem, install prox 7.1-2, add 8-9 setting, boot xubuntu live iso and pass do work fine.

As you hare running a simple nuc system with 2 drive and not 4-5.. just install prox in ext4 on 1 and put vm on the faster drive. And all will be ok, no need of zfs on limited drive... multiple like those 24bay drives in datacenter.. sure.

What is the command: udevadm control do ? As just plugging any usb unit with automatically load up and be shown in lsusb.

There is multiple guide on how to pass and forum have multiple topic on that. Mostly : disconnect the modem, install prox iso, put the 7-8 config files and you pass. But i rarely see dealing with the rom file. skip that for sure. If you never did this before , simply put a vm with xubuntu and...

it's same issues with every new upgrade/kernel. Lr-link and this chip is not used anymore. Driver over esxi made it work somehow, but cause error to pump every 2 sec. cheap to just get a 25g card instead and passthrough the card to a vm and the nas will handle the card directly as being built-in...

I don't understand the .. permissions path including the node itself... Was it just to set : pveum aclmod / -group UserGroupAllowedToPowerOff -role Sys.PowerMgmt and that give the user into the group the power on/off of the system. And doing a power off, mean a normal shutdown of all vm and...

Can it be possible to disativate this rrdcached extra service ? It's only made for logging or have any other used ?

Indeed don't understand the need for lxc, what difference does it make ? Yes the vm can have the resource to pass pci device, but as we don't used that.. it should be quite transparent ? As to set it, it's quite easy: your vmNetwork on as nic2 being the wan. And nic 1 a random new vswith that...

To recap, you add x number of vm to each of the group you want, like doing 1 by 1 : pveum acl modify /vms/101 -user pveUser -role noAccess .. ? merci

Hi So what setting did you put/change in the vm config ? And while most of this script look interesting for system with 2 cpu, like big server.. Just for game, cpu and storage have very low effect vs gpu used.

Prox passing usb to vm, via prox itself is for convenience. yes having 1 controller for the whole thing did not help, but the only solution and proper way is to pass the usb ctrl to the vm. not : usb- ctrl, debian, prox, vm , win10 vm. And on cable, a usb10gb will give 10g under 1m and about 18%...

Many aspect missing, but many guide do exist to create a default vm. And to try out an install, download xubuntu, install, all default and reboot. -eject media disc iso from the vm. nothing urgent, more like a normal vm install step done wrong.

To have proxmox shutdown full first , before the ups going down... What do you put in your config, in the nut server? You add a delay..? Like did you install the nut client on prox just as is , with no upssched.conf ..

Hi / Guten tag. So did you figure out how to run the script for shutdown ? And was it one to close all vm first and the shutdown prox after ?

it work fine over a nuc skull , tested with 2 sfp. Or just update fw of the nic.