For one time floppy support (to install some drivers) it's even possible without hack with following steps:
*) Create and start the machine as usual via Webinterface.
*) Search for the kvm process: 'ps ax --width 800 | grep kvm' - and copy the line from that machine beginning from...
If you would clone just data not the hole virtual harddisk maybe that could be intereresting for you: http://www.andybotting.com/wordpress/how-do-you-clone-an-lvm-partition
It is no final "How-To". To use this with proxmox you must think about additional steps. For example you should use LVM as...
Your "/etc/apt/sources.list" finaly should not really differ if you install a Debian-Lenny and PVE afterwards or if you install Proxmox VE from .iso. You need both. Debian for all non-modified files and Proxmox for all PVE files (including a patched kernel). When you install Lenny you would...
Re: software raid1 seems to work ok
Just make that:
grep -q raid1 /etc/modules || echo raid1 >> /etc/modules
...before you make the initrd (in the example it´s called "/boot/test" - however I would recommend to call it somewhat more like a initrd should look like maybe...
This feature sounds interesting for me too. Even smaller companies have reason why live migration would be better then downtime. In my opinion adoII bring up some good points. Some NFS server can be created quickly but SPOF is in fact something to think about.
Greetings,
user100
Is there a way to migrate in a cluster from local-LVM to local-LVM directly? Creating a machine in local-LVM works well. Even migration did complete. But currently it seems just a file was created at migration out of the local-LVM storage instead of creating (again) a locial volume (as he did...
We use software raid-1 with Proxmox V 1.5 and are able to install from DVD or iso-image to file-storage or to local-LVM as storage like it (more ore less) works on another Host with a HW-Raid-controller (on IDE or virtio). Installed successfully CentOS, Debian, and Win2K (used KVM and 2.6.32...
If you can make "D" then you can make a workaround like this (to try to solfe the problem finaly otherwise) ;):
For example:
server01:~# `echo DF | tr [:upper:] [:lower:]`
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md0 9614052 7793040 1332644...
Sounds strange. PuTTY is working here (even VNC-Console after setting the right keyboard-layout in System>Options). Have you maybe installed from a template and use some special term or encoding (which is not included in the template and so not installed out of the box in the VM now)? Have you...
Good point! If the OpenVZ guys would support a newer kernel in near future then this thread can be closed, right? Currently 2.6.18 is still the stable OpenVZ kernel. So I think it´s clear why this vote was started? When "new-features AND openvz" was an option this vote would not really make...
No it´s no "pve-kernel". Those kernels came from the nice proxmox guys. ;) - And there are no pve*.deb packets compiled from me. It´s just a vanilla kernel that got openvz patch and the net-socket-security patch applied. KVM and openvz are running now and looks good. But I have not testet this...
If I have to choose between the two options I would prefer the newer kernel. But between those lines I would prefer a 2.6.27 kernel with support for both. :)
I have compiled a 2.6.27 kernel with openvz patch these days and at a first look it worked so far with already setup openvz guest on Proxmox-VE. However currently I did not have luck with KVM. It´s enabled in the kernel but I guess that there is something additional to do (like getting some...
From another thread I remembered that something was written regarding 2.6.24 as the next stable openvz-kernel (but that was an etch to lenny discussion so i would add here):
However it seems to me (at least since March 2009) a little bit more it´s not 2.6.24 but 2.6.27? And not enough...
If you understand the reasons can you please tell me? I still don´t know a proxmox specific reason. I read some erlier diskussion too and still don´t know. In my opinion the arguments regarding "why not sw-raid" sounds a little bit more like a generic "SW vs HW raid" diskussion at all. Should SW...
You mean all of them? ;) - Why should I go to test this when it just does not work when I need it? But anyway when the hardware-raid-controller fail (yes we use hardware-raid too) and the tapes are all crap you got a chance to start with a brand new ehhrm... fast and "clean" system, right? :D
Yes /proc/mdstat is fine (and is showing you the state when rebuilding the raid). These days (SATA/SAS) maybe somebody is happy to own some (cheap) hotplug-slots too (and have the idea to write some sda, sdb stuff on a sticker)... :D
Greetings,
user100
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.