Search results

Hi, after boot on console a message appears: "To configure this server connect to https:ipadress:8006/" Where is this message located? I've changed the server IP, but the message still shows the old one.

Yes, I did enable it during VM setup. But when I have a look at the verbose output: Is there any use of the guest agent if all these features are disabled anyway?

I've installed a FreeBSD test VM, wgich works so far. I've also installed qemu inside the VM (pkg install qemu), but I cannot start the qemu guest agent: root@freebsd-test ~# qemu-ga -v 1584543339.176037: debug: disabling command: guest-suspend-disk 1584543339.176059: debug: disabling command...

Hi, should I expect problems when running FreeBSD as VM? Serious bugs, performance issues, etc.? Or should it run fine like any Linux VM? Thanks

Still the question: does pve-zsync freeze the guest FS before snapshot?

Well, I guess most DBs should be power-off save, as long as the underlying FS does not do any mess.

But the Qemu wiki syays something else:

Will pve-zsync freeze the guest file system via the guest agent? https://wiki.qemu.org/Features/Snapshots#Guest_Agent

According to what I read here, this should be possible: https://wiki.qemu.org/Features/Snapshots#Guest_Agent Communication to the guest agent should be done via serial interface: https://wiki.qemu.org/Features/GuestAgent Maybe there is a simplier method?

Why not just do it this way: Install Proxmox with ZFS Install backup server with ZFS (Proxmox, FreeNAS, ...) To do the backup: Freeze the guest file system and create a snapshot of the guest's zvol Use zfs send to sync the snapshot to the backup server Rsync additional config files (that are...

Hi, I've set up an Debian 10 container, installed cifs-utils and trying to mount a Samba share (from Synology NAS), which fails: mount --verbose -t cifs -o user=myuser,domain=mydomain,vers=3.0 //nas1.mydomain.local/Share /mnt/Share Password for myuser@//nas1.mydomain.local/Share: *** mount.cifs...

OK, but that means I cannot set stuff like root password or IP address while setting up the CT?

That's why I'm currently adding a workstation PC to the rack, that does some lower priority server tasks. Just because it's not allowed to run Windows 10 Pro in a VM and the whole workstation is cheaper than a Server 2019 license o_O

Wow, that sucks again for Proxmox users :( I wish less things were dependent on Windows.

So for a server with 1 CPU socket and 16 physical cores I need to by 16 core licenses. Licenses are sold as "2 core", so I need 8x "2 core" license? So when running on Proxmox PVE hypervisor the license enables me to run: Server Standard: 2 Windows Server VMs Datacenter: Unlimited number of...

Actually ~6 TB is the storage size in the host, that is available for VMs. So the worst case scenario is that the whole 6 TB size is used by various VMs with full disks. Also the 6 TB is on a ZFS volume, which is compressed by lz4. So compressing the backups may not drastically reduce the size.

Actually my plan is to store the vzdump backups via NFS on a backup NAS that is connected via 10G SFP+. But that way each backup will be a full backup: 6 VMs with a size of 1 TB each will need to transfer 6 TB for a backup. Even with a fast transfer of 300 MB/s this takes up to 6 hours.

Hi, I'd like to create a Salix OS container (Slackware based, https://salixos.org/). Therefore I need to create a container template first, but I have no idea how to do it. Actually I've thought I basically can just create a tar.gz of the root file system, add some description/config files and...

Hi, thanks for your reply. Also these two articles are worth a read: https://www.ixsystems.com/blog/zfs-pool-performance-2/ https://www.ixsystems.com/blog/zfs-pool-performance-1/

Here is a link comparing some ZFS RAID options: https://calomel.org/zfs_raid_speed_capacity.html Interesting numbers (without lz4 compression):