Search results

I do agree it could do with a few more features but at the same time I think the official line is if you want more you need a third party product. For instance if backing up a Windows VM you really want something that is VSS aware. I do have the guest agent inside the Windows VM's which is...

You can run scripts on the end of the backup. I've got mine uploading some backups to Azure Cold Blob Storage and also I restore some VM's across to a second host with it's own storage so I have a simple DR solution for them as well. First script is what vzdump calls (See the Backup docs on...

Sorry just read your message again but if this a VM your trying to switch from SeaBIOS to EFI without a re-install? I don't think that works on Windows, you need to reinstall unless your on the latest and follow a process like mentioned in this article...

You need to add a special EFI disk to the VM for this to work. If you go into the GUI and Hardware for the VM and then add you'll see EFI Disk.

Very true. Missed that bit but well spotted :) Yeah there's a few ways to skin a cat. This works for me but tweak as you need.

Sure of course. So first of all you need the following lines in your LXC.conf for the container. You can find that in /etc/pve/lxc and then the number of the container.conf. You'll need to be a privileged container vs unprivileged for this one to work. lxc.cgroup.devices.allow: c 10:200 rwm...

I've something similar to this only I have OpenVPN running inside an LXC with iptables masq to allow it to effectively be a router. I added on dnsmasq as well and can then point an LXC at that for its gateway and DNS server to force all traffic via the VPN. This works well for me and keeps the...

Just for reference but I've got a virtual Sophos UTM running on my Proxmox and that also is using VLAN's so I can attach VM's / LXC's to different VLAN interfaces on Sophos UTM. I do have a VLAN capable switch but if it's all on the same box you don't have to add in all the VLAN's, I only add...

I like to see this so I can control the barriers setting for some containers as that's where people are seeing huge increases in IO waits when using servers without battery / flash based RAID controllers. compared to Proxmox 3.

Are you coming from an older Proxmox like v3? If so this is likely the changes to barriers being enabled by default and no way currently to disable this on Thin LVM. There's a feature request to have it as an option which I hope will get implemented sooner or later for lxc.rootfs.options like...

Hi Richard, I'd have to disagree that this is a sensible approach. If you're taking a storage snapshot on ZFS then you've not got the RAM, if you snapshot in Proxmox then you've got a performance hit the more snapshots you get. Proxmox's backup with the qemu agent does support freezing the...

Well if you was to try a new server I wouldn't burn another license key as it's only for a test. The trial version runs for 180 days which should be more than enough time ;) Clearly as you say that's not a lot running on it and I'd not really expect those services to swallow all that RAM...

Interesting. I've noticed that Server 2016 seems to use a lot more RAM than 2012 R2 did on a clean system in my experience but not seen this yet. Just having a look but I've got a DC which has been up for 21 days with AD Connect running on it as well using 3.43GB out of 5GB I've allocated to it...

Agreed. You don't often see figures like that. I have to say when ever I've seen servers with such a long uptime I always start to feel concerned if it'll come back up when you reboot it. I'm not sure why but the fear in me grows greater the higher the uptime number. Some update or config...

Same for me. No SMART data either on my system. EDIT: Just checked the syslog and see this Sep 27 22:47:43 kt-proxmox-01 pvedaemon[28722]: Argument "Read_scanning" isn't numeric in addition (+) at /usr/share/perl5/PVE/Diskmanage.pm line 91. Sep 27 22:47:43 kt-proxmox-01 pvedaemon[28722]...

So just want to add my opinion on this. I work for a large consultancy that mostly is full of developers where I'm from an ops background. As I see it a lot of development as others have said is starting to go along the docker route. Especially for certain tasks. As an example take a front end...

I noticed that my Proxmox is on Qemu 2.6.1 now. Not sure when it updated but I tried this again and just want to confirm it works correctly now.

Is the problem with LVM Thin or RAW simply that these volumes are mounted with barriers=1 then? Clearly they are not mounted inside /etc/fstab so unable to change the mount options but could be why chroot is faster. Is it possible to add an option like on KVM for the disks where write back...

All I see in dmesg is "(Nothing has been logged yet.)" Not too familiar with systemd at all yet but is it related to the bootlog stuff being masked? bootlogd.service masked bootlogs.service masked bootmisc.service masked I...

So just as an update but ESXi is exactly the same, drivers crash in DOTA so seems it could just be AMD drivers / hardware not working well with this or this particular motherboard (SuperMicro server board). Probably going to have to give up on this :(