Search results

No, the problem is not solved. The container didn't work the way I did it first. I suppose I need to make a template out of the RHEL 4 iso I have, but I don't know how? What do you mean "could have cloned the RHEL container" ?

Well, I had to delete the content, as the container i need to restore is based on RHEL 4AS, and so any files already in the container will not be compatible. I can't find any RHEL 4AS container. I have an iso with it, but I don't know how I get from an iso to a template, nor can I find it...

Ok, installed on the host using the guide mentioned earlier works fine.

Ok, that worked fine, and I was able to make at tar backup of the server. I then created a CT, and mounted it (without starting it), removed the content and restored the tar backup. Unfortunately the container again starts briefly and then stops. daemon.oog has this about it, which isn't...

Ok, thanks.

Ok, I just thought it was generally discouraged to run services on the host.

Do you run this from the host or in a vm or container?

Ok, thanks. Unfortunately xfs is the default FS for RHEL/Centos. So I suppose the only solution is the xfsdump | xfsrestore route. :confused:

I need to shrink a Proxmox-KVM raw volume with LVM and XFS. Now, XFS doesn't support shrinking as such. It's possible to hack around this with xfsdump and xfsrestore, but this would require 250G data to be copied offline, and that's more downtime than I like. Whats the alternative? I was...

Problem solved. After conferring with Cpanel support they suggested removing a loopback /tmp partition used for security https://docs.cpanel.net/knowledge-base/security/tips-to-make-your-server-more-secure/ - after removing this the fsfreeze/thaw now appear to function correctly.

Uh, another rabbithole ... The Debian page is quite limited. I found a better guide on Server World. Still, after installing, trying to run targetcli i get this error: b"modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file...

So here's the plan. After having having disabled qemu-guest-agent and having run an fstrim in the VM I was finally able to successfully create a vzdump of the VM. This VM is using 180G of a 350G disk. Now I'd like to restore this vzdump with qmrestore, to a smaller disk, to see if that would...

I just tried the fsfreeze while having top running in the client, and it turns out that the client isn't actually freezing up immediately. It starts by running up loadavg like crazy. I don't see any particular process doing this, it's just increasing until that at last cause the client to be...

Ok, I understand. Anyway, installed ploop, and mounted, but failed: (pve) # ploop mount /var/lib/lxc/2529/rootfs/root.hdd/DiskDescriptor.xml Opening delta /var/lib/lxc/2529/rootfs/root.hdd/root.hdd Error in ploop_getdevice (ploop.c:870): Can't open /proc/vz/ploop_minor: No such file or...

I think you're probably right - but why isn't it automatically extracted or whatever, when I import the dump in pcs ?

I already read that thread. It says "mount the root.hdd file" but not how you do it. How do you mount a root.hdd file? Anyway, I still don't get why /sbin/init is missing when it obviously is there in the openvz container.

Yes, it mounts to /var/lib/lxc/CTID/rootfs -- where we find: ./dev ./proc ./root.hdd ./root.hdd/root.hdd ./root.hdd/DiskDescriptor.xml.lck ./root.hdd/DiskDescriptor.xml ./root.hdd/root.hdd.{0793f2f5-b890-4117-b473-126a412c2f51} ./dump ./Snapshots.xml ./vzpbackup_snapshot ./etc ./etc/vzdump...

Sorry but I don't have much experience with LXD. In Openvz the container would be under /vz/root, and when mounted you could see the content under /vz/private. With LXD I only see the root.hdd (under /var/lib/vz/images/) where can I see the actual filesystem?

Well, seeing it seems it might have something to do with Cpanel's jailshell's I went ahead and disabled all jailshells, and tried again ... and still NO difference. :/ So I removed the qemu-guest-agent and tried running the vzdump. That works ok - of course without the freeze - but then, due to...

Yes I know that RHEL 4 obviously is no longer supported by anyone in this world, but if I dump a full RHEL 4 openvz container, should I not be able to restore it again, with everything that was there in the working container? I mean, without having to find a RHEL 4 ISO somewhere?