Is it possible to add a hint to each node interface like
just to intercept correctly (when adding a new machine) the correct interface to join machine to???
I know that this is not in the code and i can write it myself... and send the patch, obviously...
Just a simple question:
anyone tested openvswitch on Proxmox?
Or, better, is it in the future of Proxmox or do you have any other solution for
a virtual switch?
I'm testing 3.x rc1 and i think it's a good solution
(testing on my own lan as stable server)
Found the bug, i hope that Dietmar will be so kind to include the solution.
This code says that the exclude-path is ALWAYS read from command-line
and despite each line in /etc/vzdump.conf will be skipped
# exclude-path list need to be 0 separated
With the 1.9 i should always apply this metod while adding an usb passthrough:
dpkg -i pve-qemu-kvm_0.14.1-1_amd64.deb
With 2.0 this problem was resolved or should i use a differente...
Changed the name via hostname but in the Datacenter
i see the already existent VM mapped on the oldnode
and the new mapped on the new renamed node.
I think that this information will be stored on /etc/pve/.members
but it/s unchangeable...
In many cases happens that, during backup, vzdump using snapshot exits with error 5...
and the the snapshot partition will not be umounted due to it-s busy state.
Locate (updatedb) is the guilty program!
It happens that if updatedb is running the mount point can be busy and despite
Hi, i have two machines correctly seen when they are up and running but, when i start only one of the two and i probe creating a new VM i have an error:
Boot: Starting cluster OK
Starting cman OK
all oK until quorum that obviously says:
Waiting for quorum... timed out...
I know that the VMID.conf file allows to add an
argument that is passed to kvm
Is there a possiblity to launch a script before launching vm?
if a script like VMID.sh exists in that dir it shoud be before at startup
of the VM...
Hi, due to my personal need of the module iscsi_trgt i've tryed installing it
with the normal debian methods:
apt-get install iscsitarget-source
apt-get install build-essential
m-a a-i iscsitarget
I've this sources.list
deb http://ftp.it.debian.org/debian lenny main contrib
# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian lenny pve
# security updates
deb http://security.debian.org/ lenny/updates main contrib
and installed the pve-2.6.32-4.pve
many days ago i installed a new PVE with 8 machines, 3 kvm and 5 openvz...
one of the openvz did non work well....
search.... research, boot, reboot and bingo....
2 openvz vm's had the SAME HWaddr.....
i don't know why but going on the interface, disabled the network on the VZ and then...
if you want to hide other vps processes from openvz container you can insert this line
into /etc/sysctl.conf of the PVE itself (not the container):
then restart all container and ps or htop or top do not show anymore
other container processes
just for fun...
Hi, i've tested both freenas and openfiler
created the luns and the system finds the luns but....
when i try to create a volume with the iscsi as device it does not find any base volume....
if i test with the commandline interface i've a response like this
iscsiadm -m node -L all