Search results

Also, the OpenVZ method allowed for expanding and shrinking as required. If a container needed an extra 100GB for some temporary files, you could just increase it, then decrease it later when those files were gone. You can effectively "move" the free space from one container to another. This is...

I cheated a little bit with mine. I only needed to recover 1 LXC container back to VZ, and it was only 20GB. I shut down the LXC container, then copied the raw image file to our NAS. Then I reinstalled 3.4, and recovered the old VZ version of the backup for that container. Once it was restored...

I'd like to know this too... I'm hitting space issues after doing our upgrade because the imported containers are seemingly taking far more space than before. And you can't shrink the images. So now I've managed to restore 3 of our VMs, with another 3 that won't fit. Wishing I had just left...

I just had this problem too. To help anyone else who's panicking (since this is the top result on Google for the error): Go to the failing container's network settings in the web interface. Double click the interface to edit it. Change something and OK, then go back and fix it. If there's more...

Yes, of course. Which is why I said when choosing Linux. The OS type is selected before any storage or network stuff.

I'm just creating yet another Linux KVM machine for testing some stuff, and I started wondering if there's any technical reason virtio isn't pre-selected when choosing Linux as the guest OS... Almost all Linux distros have support for virtio out of the box, so to me it would make sense to have...

I realise this is an old thread, but in case it helps anyone, I'll post my 2 cents... If the card is supported by the Proxmox kernel out of the box and you're trying to feed it into a Linux VM, OpenVZ will be many times easier... And OpenVZ containers should run a lot smoother and use less...

Figured out why mine was being stupid (even after making sure Proxmox was up to date)... It seems Java decided to cache the old, now broken jar file and not update it for some reason. Went into the Java control panel, "temporary internet files", ticked everything and hit delete. Started Proxmox...

Err, is that no subscription or enterprise only? Edit: I ask because the server I was fiddling on today was only updated a few days ago. Was this cert change done in the last week or further back?

Yep. That's the one I started getting today (different to the manifest one a few weeks ago) after being forced to update Java. Adding the Proxmox server as an exception in the Java control panel fixes it, but that's kind of painful if you have a dozen servers (at different sites, not in a cluster).

No, it was a different warning that started in a later version of Java... I doubt that's the issue, but given the only change in my case was Java, it's odd to go from that manifest error to this signing one, with no further manifest warnings once I "trust" the applet.

It makes no sense that Java's complaining about it either... ;) I'm wondering, with my Java-n00b brain, if this error is related to the recent manifest permissions error some of us were seeing... It did warn the applet may be blocked in the future. Maybe they've got it throwing up the wrong error.

Every release since Oracle took over has been a new adventure in stupidity. Why on earth they bundle malware with security updates, I don't know. I spent nearly an hour yesterday trying to get a console open on a remote server. Never got it to work (the exceptions list wouldn't show up in Java...

LOL - sometimes I think they don't even know what they're trying to do. That would mean a client is required on every system you want to run it on, right? Will you keep the Java as a fallback option for those who can't install a SPICE client (or don't want to)? A lot of the times I need to...

It's all good - I created a script over the last hour or so, and it seems to work OK. I'll post it here after I finish testing and cleaning it up in case anyone else wants to do this. Edit: And to answer my own question in the first post - vzdump aborts the backup if it gets a non-zero exit...

It's a kernel default - if the kernel folks don't think it's wise as a default, there's probably a reason for it.

I know I can do this myself, but why reinvent the wheel? Does anyone already have a basic hook script that simply mounts a device at "job-start" and unmounts it at "job-end"? Also, while I'm asking, is there a why to abort a backup from the hook scripts is errors are detected (such as the...

I noticed that too. The double up was the only reason I looked in the thread since the title is meaningless, so I tend to ignore it... New since when? Perhaps a date in the title so we know (thread started date is meaningless too if the thread is edited and last post is useless if the thread is...

I actually just came here to suggest EXACTLY this! :D My backup storage filled up during the latest backup, partially due to the lack of flexibility in the retention settings. I have a few larger VMs that I really only need a couple of copies of, but a few smaller ones that I want daily backups...

Tried it in another slot? Sometimes it's a hardware limitation of the motherboard I believe. What sort of card/device is it?