Recent content by bitbud

-the ability to dynamically expand the size of the Volume Group by adding additional storage Usually the NAS/SAN can resize the iscsi target, so there are other ways to get the same result. Unless your SAN is full, and you want to connect an additional SAN that you have available, for...

Thanks for the info Dietmar, you are always helpful. True, while 1 to 1 PV to VG is easier to manage, there are huge benefits to having multiple PVs connected to a VG, such as: - the ability to dynamically expand the size of the Volume Group by adding additional storage - the ability to migrate...

Via the web interface storage configuration form, I've created multiple iSCSI targets. I've then created an LVM Volume Group selecting a single target as the 'base storage' and assigned a 'volume group name' How can I add the second iSCSI target to the volume group? It appears the web...

One solution would be to install Munin, and then create a separate bridge for each VM. That will give you good stats over time, and web accessable. Munin install is easy http://bitbud.com/2009/11/27/detailed-historical-performance-monitoring-for-proxmox/ By using an individual bridge for...

How to fix proxmox time skew To fix time skew for Windows Guests: - edit the conf file for your guest (located in /etc/qemu-server), labeled <guestid>.conf - add the following line: args: -rtc-td-hack We run this on all Windows Guests. That would be a nice feature, a way to add args via the...

I think the point was to never turn off iSCSI storage if PVE is still connected (via the Storage manager). Remove the iSCSI storage from PVE, then you can shut it off.

Since 1.4 included unlimited bridges, I title each bridge by the vLAN it is assigned. For example vLAN56 is vmbr56. This removes any need for a description for me.

Peterx, If you do not have shared storage, the only way to use Live Migration will be to setup DRBD mirroring between the two servers with local storage. There is a HowTo here: http://pve.proxmox.com/wiki/DRBD.

Full virtualization is the future (and present) so my vote is for KVM only. The older kernels are holding back the feature set available (unless you are back porting, which isn't fun either). While Red Hat has a nice offering, Proxmox is unique in it's all includive install, and easy web...

You need to install the iSCSI initiator: From the console: apt-get install open-iscsi

There is a known issue with some KVM based Windows Guests. I was able to resolve it with a simple change to the confoiguration file for the virtual. - Make sure you are on the latest rev of Proxmox (1.3), which has KVM-86. - In the web browser console for Proxmox, make a note of the KVM...

Still testing Thanks for the quick turn-around. I download the patch and have been testing since then. I haven't been able to get it to work yet, but I need to test it more. I am trying to pass the full string as above, so I am not sure if there is a problem with the quotes, or a need to...

Dietmar, Grateful for the new "args" option in the conf files. However, there is a "no whitespace" problem with it. Several of the most useful arguments to pass require white spaces, and quotes. I am trying to pass a single argument of: -incoming "exec:dd if=fedstate.img" This is what it...

Found solution I found the solution. The issue is specific with Windows SMP and AMD processors. To resolve, you simply need to make a small change to the VM Guest BOOT.INI file. For the OS you select, add /usepmtimer to the line in the BOOT.INI file (on Windows computer c:\). This fixes the...

Dietmar - two words: THANK YOU!!!!! That tiny little configuration option args has opened up so many options. All the features of KVM are now available to me. What a fast response too. You guys rock - keep up the great work! THANKS AGAIN!