Search results

Wonder how it looks during the install. Maybe the ID of the disks is not right during the intial install? something with the AIC card ?

After you may need to try turning off "KVM Hardware virtualization" on the Windows Server guest.. (It's in the options) It May be slow but... if it works?

You just need to add the delay option. I don't know why they don't do this by default. I see it so much. /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="rootdelay=10 quiet" to get your system to boot just zpool import -N 'rpool' exit EDIT: Note after changing /etc/default/grub read note at...

Did you try cpu: kvm64 instead of cpu : host?

Thanks Aaron, And this is regardless of which vm hard disk type is used (ide/scsi) of the guest vm? So just to be clear, any vm I put on my zfs-raid mirror tank0 should have discard[x] enabled? and I assume ssd emulation. What are the consequences of not doing this, the drive will fill up...

I didn't know of this either. Thanks PS. It keeps defaulting to local each time.. ?

LXC containers are lighter weight that's all. They're not as customizable as a full VM but it's working for me so far. You can use a number of things for containers for example: https://www.turnkeylinux.org/business-management

Yes you can. I use mine in a container. It's not recommended mostly from a infrastructure point of view. If this server goes down you now don't have access to your backups. Other than that it works perfectly.

No the backups from the pbs are in the storage list. Available to see without having to login to the separate pbs server. The way you were looking was for single regular vzdump backups. node: pbs-storage -> backups -> listing..... So if you ever make a second node, just add the pbs server...

Just want to thank the proxmox team for finding a solution and fixing the legacy bios and grub. I am sure many have older systems that don't have UEFI boot but are using ZFS on the rpool. This all works great. I actually fresh installed 6.4 as it was an easy alternative in my scenario.

Try on both. Not sure how to remove on centos but on debian To try: Modify /etc/default/grub Example: GRUB_CMDLINE_LINUX_DEFAULT="quiet mitigations=off" Then update-grub

Could this be due to linux kernel mitigations. I had a similar issue. Try turning mitigations off as a test and see if that improves your performance. At least you'll know why.

I'm running proxmox backup server in a container but I think I may have over complicated my re-install scenario which caused me to lose my data store accidently. [ rpool - zfs 180GB ] proxmox ve container: 900 proxmox backup server - 16GB [tank0] - vm1 - vm2 [tank1] - container...

Thanks for more info on this, but there is still confusion for me. If we're running 6.3 created by an original ISO, on Legacy BIOS do you suggest we reinstall 6.4 from scratch to get vfat on grub? Edit: I see post #2 has some info on trying to use the 512MB partition and initialize with...

This has been a source of confusion for me as well. I know that during a 6.3.x (mid cycle) upgrade the rpool was offered a ZFS pool upgrade that at that time REQUIRED UEFI or it would not boot. I was able to change my bios boot mode to UEFI then it works. Moving forward I am confused if this...

Is the networking working?

Did you clear browser cache? force refresh of page?

I think the point is to make it more apparent, just make the border larger or make the text bold or something... The orange was just an idea. I remember the first time I installed proxmox I had no idea the next button was clickable, looked ghosted.

I noticed this issue as well... Go orange!

Do you mean you ran out of memory and the OOM killer started killing tasks? I have 128G of memory and also am wondering if I really need to commit 64G just to the ZFS arc size.