I partially answered my own question. Yes for option one but I am using identical servers. What if the servers were not identical? Should the VM work when moved?
Anyway, if it helps anyone, here is what I did to move a Win2000 VM from a kvm-based Ubuntu 9.04-server amd64 to a server running proxmox 1.4 beta2. My transfer medium was an external usb drive formatted using ext3.
#Backup On Prod Server
# Plug in usb drive and locate drive. You might want to use fdisk to help. In fdisk type 'p' to list partitions. 'm' for help.
fdisk /dev/sdb
# mount drive if not mounted
mkdir /mnt/drive2
sudo mount /dev/sdb1 /mnt/drive2
# Find LVM file to copy
sudo lvdisplay
sudo dd if=/dev/vmgroup/vm52 of=/mnt/drive2/vm_2000.dd
ls -lh /mnt/drive2/
sudo umount /mnt/drive2
#Migrate to New Server
# Plug in usb drive and locate drive. See directions above
mkdir /mnt/drive2
sudo mount /dev/sdb1 /mnt/drive2
ls -lh /mnt/drive2/
# Locate desired VM to replace and rename. They are in the images folder.
ls -hl /var/lib/vz/images/103
mv /var/lib/vz/images/103/*.raw /var/lib/vz/images/103/vm-103-disk-1.raw.back
# Copy the external usb file to the proxmox lvm
dd if=/mnt/drive2/vm_2000.dd of=/var/lib/vz/images/103/vm-103-disk-1.raw
# Clean-up
rm /var/lib/vz/images/103/vm-103-disk-1.raw.back
# Unmount
sudo umount /mnt/drive2
Enjoy!
Oslo
sábado, 19 de octubre de 2013
lunes, 12 de agosto de 2013
zimbra How to renew certificate after 365 days
Error you get ...
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Starting logger...Failed.
Starting logswatch...ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.net.ssl.SSLHandshakeException sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed)
zimbra logger service is not enabled! failed.
'''Solution is:'''
as su - zimbra
zmcontrol stop
as root
cd /opt/zimbra/bin
./zmcertmgr createcrt -new -days 365
./zmcertmgr deploycrt self
./zmcertmgr viewdeployedcrt
cd /opt/zimbra/libexec
./zmfixperms
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Starting logger...Failed.
Starting logswatch...ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.net.ssl.SSLHandshakeException sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed)
zimbra logger service is not enabled! failed.
'''Solution is:'''
as su - zimbra
zmcontrol stop
as root
cd /opt/zimbra/bin
./zmcertmgr createcrt -new -days 365
./zmcertmgr deploycrt self
./zmcertmgr viewdeployedcrt
cd /opt/zimbra/libexec
./zmfixperms
sábado, 20 de julio de 2013
RALINK 5360 ..how to install dwa 525 with chipset ralink 5360 on ubuntu 10.04
Re: RALINK 5360 ..how to install dwa 525 with chipset ralink 5360 on ubuntu 10.04..
I love a challenge and so will you, I hope. This is a relatively new device and we are going to have to experiment a bit. Please download RT539x PCIe here: http://www.ralinktech.com/en/04_supp...ort.php?sn=501
Download it to your desktop. Right-click it and select 'extract here.' It is handily a bz2.bz2 file, so you may have to 'extract here' a couple of times. Good work, Ralink! Now open a terminal and, with an internet connection, do:Open the folder you extracted and drill down to os/linux/config.mk and with a text editor change:Code:sudo apt-get install linux-headers-generic build-essentialProofread, save and close the text editor. Now open the file os/linux/pci_main_dev.c with a text editor. Make the addition I've highlighted here:Code:HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
Everything before and after is unchanged. Spacing, punctuation, brackets, etc. are crucial. Proofread carefully twice before you save and close the text editor. Now back to the terminal:Code:#ifdef RT5390 {PCI_DEVICE(NIC_PCI_VENDOR_ID, NIC5390_PCIe_DEVICE_ID)}, {PCI_DEVICE(NIC_PCI_VENDOR_ID, NIC539F_PCIe_DEVICE_ID)}, {PCI_DEVICE(NIC_PCI_VENDOR_ID, NIC5392_PCIe_DEVICE_ID)}, {PCI_DEVICE(NIC_PCI_VENDOR_ID, NIC5362_PCI_DEVICE_ID)}, {PCI_DEVICE(NIC_PCI_VENDOR_ID, NIC5360_PCI_DEVICE_ID)}, #endif /* RT5390 */
Press Tab and the rest will fill in automagically. Press Enter.Code:cd Desktop/2011Your wireless should now be working.Code:sudo su make make install modprobe rt5390sta echo rt5390sta >> /etc/modules exit
jueves, 11 de julio de 2013
sábado, 29 de junio de 2013
instalar xubuntu+postgresql+pgadmin
wget -O -- http://apt.postgresql.org/pub/repos/apt/ACCC4CF8.asc > ok.key
sudo apt-key add ok.key
http://www.ubuntugeek.com/how-to-install-postgresql-9-2-on-ubuntu-13-04-server.html
recovery postgres password http://www.netstorming.com.ar/2009/10/15/resetear-password-de-root-en-postgresql/
Installing PostgreSQL 9.1 on Ubuntu 10.04
27 Replies
PostgreSQL 9.0 final was released on 2010/09/20 which I’ve been waiting for to begin playing with it and evaluating it. The mainline Ubuntu Lucid apt repositories only have 8.4. According to the package maintainer, Martin Pitt, the postgresql-9.0 package won’t be added until Ubuntu Natty. Thankfully, he setup a backports repo for Ubuntu that we can pull from.
This is a very quick and painless process. If you have not done so already, make your life easier by installing python-software-properties:
sudo apt-get install python-software-properties
Next up is adding the backports repo and updating apt:
sudo add-apt-repository ppa:pitti/postgresql
sudo apt-get update
UPDATE: In the comments, Jason Froebe points out that if you already have an earlier version of PostgreSQL installed, you can just upgrade it:
sudo apt-get upgrade
Finally install postgresql-9.1:
The libpq-dev package is for compiling wrappers/clients against libpq.
sudo apt-get install postgresql-9.1 libpq-dev
The libpq-dev package is for compiling wrappers/clients against libpq.
There you’re done!
jueves, 27 de junio de 2013
web shell
https://code.google.com/p/shellinabox/
Basic HTTPS Shell In A Box
First we download and install Shell In A Box. You can download .deb file for your operating systems architecture here by visition Shell In A Box official page here.
Next thing is to install Shell In A Box:
sudo dpkg -i shellinabox*.deb |
Now we need to add a few options to Shell In A Box .conf file:
sudo gedit /etc/default/shellinabox |
You need to replace line:
SHELLINABOX_ARGS="--no-beep" |
with line:
SHELLINABOX_ARGS="--no-beep --disable-ssl" |
Suscribirse a:
Entradas (Atom)