Search results

So... mark (the post) as SOLVED so! Greetings!

When you sayd migrate, you refer to use the "Move disk" from the Web UI? And, the Bus/Devices combination is EXACTLY the same? (for example: VirtIO/0 instead of IDE/1). This is the most commonly problems with XP Guests. Greetings!

But, you already tried the PVE way? Alternatively, you have LDAP auth method. And one more: you can create users in the system as in this post. Greetings!

mmm.... really, i don't know why you get this error. But, you can try cleaning the thing manually. That is, remove the storage in where the rootfs resides (and any other storage medium if any), and then erase the configfile. For that, you need to known (surely that you known) what type of...

for IDofCT i meant ID of Container. So, your command must be: root@agc:~# lxc-destroy -o /tmp/destroyed.log -l INFO -n 104 -f with that, you are saying that want to destroy your LXC 104, that want a INFO logging level, and save it in /tmp/destroyed.log and the -f switch at the end, is for force...

one time i had the same problem and was for disk out of space.

Hello. Try to enable the services in your CTs running (inside your CTs obviously) systemctl enable servicename.service. Gretings!

mmm... let's see... Supposed that you are in pve-node1 host, that is the node in where you have your evil and demoniac CT. So, you are logging through ssh or physically in the front of a monitor connected to that node. Run a commands in your bash shell. You destroyed the CT with ID 666...

Is incorrect. I think that if you want sssd, maybe is because you are thinking in get auth from your AD LDAP. But, you don't need sssd on your node to authenticate against AD in the web based console. For that purpose, you can configure auth against AD from the web interface. Go to Datacenter...

Are the LXC running? What say the command lxc-info --name ID in the State filed? RUNNING? If running, you should stop the LXC first with lxc-stop --name ID. And then, destroy the LXC with lxc-destroy --name ID. Greetings!

According to this article, SCST is much better that LIO... But, good information anyway. Greetings!

Hello. Take a look to this PVE Wiki. Is the more close to a easy way to get scst working without worries in Proxmox 4.x/Debian 8.x The fact of have subscriptions is not envolved in anyway for that. Greetings!

Hello. Any plans to support scst iSCSI targets? Is frustrating to have a working storaged (with scst as target), and no support for use ZFS over iSCSI from Proxmox... (only comstar, istgt, and iet)

The unique problem that I have with PVE 4.x series is with LXC Containers, that in some cases produces a reboot of the node in witch they are. But is a problem related to LXC (that i recently discover, yesterday), and no with PVE 4.x itself... (in PVE 3.x series, the LXC doesn't exist).

Solved! The problem was given with the iSCSI initiator name. Unlike that happened with the other nodes of the cluster, this time there was a change of NICs adapters, that produced a different random iSCSI Initiator names (use the MAC address of the NICs for that). Ok. I knew this, and I had...

mmm... curious.... From the Web GUI, I select Create VM, and when try to list the ISO images from local storage the same problem (show me nothing). Then, I navigate to local (node-name), select 'Content', and the ISOs are there... One more again, I try to Create VM, and when select the local...

We are, without knowing where to focus on my problem (multipath? ISCSI? LVM? or something else that i don't known?) Greetings!

Hello community. (this is my first post :)). I was working with ProxmoxVE from the 3.0 version. I always followed the guidelines, wikis and forums, and so I was able to solve problems without major complications. Thus tasks such as updating, re-installing nodes, configuration of different types...

So, depending the number of nodes in a cluster, is not possible to change the needed votes to get quorum? I want to change these values of needed votes for quorum and the number of votes for each node. So, i'm asking me if can i change the votes of a node? For example, if i have a cluster of 5...