Search results

In regular LXC the rootfs is just a dir in the host. How do I achieve the same effect in Proxmox? I want to enter the live or off containers rootfs from the host. Same with VMs. Is it possible?

is there a way to reload the configuration of Proxmox after changing storage.cfg? I had to reboot a server that takes 15 min to come back.

I defined a storage and later changed the directory names on the box, but I cannot find a way to edit the properties of the storage using the web. Is it possible? If not, and I change directly the definition on storage.cfg, how to I force the Web to resync? Also, in 5.2, how I mount a live or...

I am trying to access the rootfs of all my live containers, how do I do that? Alternatively, I want to create a container that resides on the disk, on a directory, like regular LXC containers. How do I do that? I need to bring in several LXC containers from another regular box with LXC. I do...

I disabled memory groups in the Kernel command line, because I care less about how much memory my containers use, I want them to use all the available memory. But the the containers do not start since memory cgroups is disabled. I need to remove these 2 lines lxc.cgroup.memory.limit_in_bytes =...

I need to virtualize several dozen Windows 10 Pro boxes, does anybody know if the Virtio drivers do work and also how does the memory sharing works? I need to show 16G RAM per box, but naturally, I want to use only what is needed so I may overcommit.

Proxmox wants to be a "bare metal" system, but in reality, it would work great as a pure container solution, inside a virtual machine with a lot of resources, either on Hyper-V or Vmware.

The response has no merit. All ISOs from every Operating System install just fine in Hyper-V. The only case where it fails is the Proxmox ISO. It absolutely is a bug in the installation script. Please notice that if it got so far, there is no need for a CDROM, since it booted from the ISO.

I want to use Proxmox for the container functionality only, under Hyper-V. The installation launches as machine type II, and the installer starts, but it fails because it cannot find a cdrom. Kindly fix this or give me a workaround.

I upgraded to the pvetest but it still crashes, even with the line added.

I did add the line, and it still crashes. Any ideas? I can give you direct access to the box. The fact that this works fine in Red Hat 6.4 shows that the issue is in Proxmox. I mean, a 64 bit virtual machine should not be affected by this bug. Or maybe I am misunderstanding the issue. Thanks in...

Any idea when it will be fixed inside Proxmox?

I have been trying all day to reuse a Windows 2012 virtual hard drive from my Centos 6.4 KVM Host and I keep getting a crash on start. Finally, I remember that a few weeks ago I opened a bug with redhat https://bugzilla.redhat.com/show_bug.cgi?id=821741 . This is the same bug and it means that...

My container is Centos 6.31 based. Is there any option?

Is there a set of instructions to turn my container into a new template?

I am wondering if anybody has developed a cloning script that would take an existing container and build a new one based the old one, taking as parameters a new IP address, hardware node and bridge? If the container is set for DHCP, the parameter would be "DHCP". I need to clone the same...

Please delete this post

This is what I get inside my container service network restart Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0...

Version latest, new machine. I am having an issue that according to what I read, it was fixed in https://bugzilla.proxmox.com/show_bug.cgi?id=15 but it is not working. I created a new bridge, vmbr1, and set the network for dhcp inside my container. The packets reach the router, which correctly...

I have the same issue with a container based on Centos 6. I set the configuration inside for dhcp, and restart the network. On the router I see that the dhcp server gave an IP to the mac address of the container, but the container never uses such an IP. It means the packets reach the dhcp...