Search results

It doesn't work for me that way if I add such line in the config file for a guest - the arguments are not passed. It only works if I start "kvm" from command line and add "-serial ...". Is "args: " line parsed by "qm"? I don't see it mentioned in the manual. "args" is not present in "qm" and...

Does the web backend use VNC for "monitor" as well? I though it is something more lightweight (at least, I've seen such lightwell SSH-web-shells). I already mentioned a usage scenario: - you reconfigure your network on the guest and you loose connectivity - VNC is slow - what I didn't mention...

I think it's better to use a unix socket, for at least three reasons: - when using telnet as above, password is passed on the screen; it's not the case with a "real" serial connection - we don't really want to open any new ports - it's easier for the backend to generate such line, because the...

I used it when I emulated Debian (ARM) in Qemu some time ago, so it's perfectly possible. Would be great to have it integrated in the Proxmox VE web backend, but I don't mind using it with minicom on the console. And of course, it's OK to have to configure the guest to have (min)getty started...

I added some FAQ notes about sending keys using Qemu monitor: http://pve.proxmox.com/wiki/FAQ Feel free to comment/edit.

Thanks for adding that to the TODO list. I'm using 6 bridges right now, so it's not hard for me to imagine hitting that barrier.

Currently I'm evaluating Proxmox VE to see how it compares with other virtualization solutions. One thing that is very nice about Xen is its serial console access to guests (it works out of the box for paravirtualized hosts). It allows to login to a guest even when it's network-disconnected...

Right now, one has to look at system/index.htm to make sure what interfaces does a given bridge use. So the description would surely help. What you mean I think would be (when we "Create" a new virtual machine): Network -> Bridge: vmbr0 (main interface) vmbr1 (VLAN for mail services) vmbr2...

What is more intuitive to you: vmbr1 in VLAN 113 vmbr2 in VLAN 125 vmbr3 in VLAN 214 vmbr4 in VLAN 221 Or: vmbr113 in VLAN 113 vmbr125 in VLAN 125 vmbr214 in VLAN 214 vmbr221 in VLAN 221 This is true, network configuration is complex, that's why I'm looking for a way to simplify it.

That's bad. That's one feature I didn't like in VMware. But I see it's enough to edit some files in /var/www/pve and /usr/share/perl5/PVE, look for things like: vmbr[0-9] and replace them with: vmbr[0-9]+ I have "additional" bridges at least displaying now, but I still need to make some...

I guess there are some misunderstandings about using software RAID here. Anyway, if the installer doesn't offer that option, you do it "low level" - this method works for all distros and all setups ;) Do you want to use RAID for everything, or just for /var/lib/vz? If just for /var/lib/vz...

Not all HW RAID controllers come with a battery. Also, in case of a power failure, the risk of loosing data is the same if you use: - no RAID at all - Linux software RAID - hardware RAID with no battery backup Also, disabling write-cache in your disks just eliminates that risk at a slight cost...

Web interface only allows to create bridges vmbr0 up to vmbr9. However, I usually create bridges with a name resembling the VLAN they are in, i.e. vmbr115, vmbr200 etc. Is it possible to use such bridges with Proxmox VE? I have them already created in /etc/network/interfaces and they are running.

I mostly miss an updated kernel. I.e. starting with 2.6.25 (or 2.6.26?) it is possible to see how much a given process is being swapped out. Why is it useful? To see which of your KVM guests are being swapped out (i.e. because they were not doing anything, or just because you don't have enough...

BTW, is it a 3rd-party VNC viewer or is it developed by Proxmox? It would be nice to be able to send key combinations to the client from within the VNC viewer (i.e., alt+F1, ctrl+alt+F1, sysrq+b etc.). Perhaps it's possible to send them from Qemu console though - I guess it's just easier to...

I was thinking of booting off a tftp-capable "live" distro and rsyncing all files from an already installed Proxmox. Plus, installing the bootloader, recreating initrd. Done. But now as you gave me an alternative, I need to think deep what to choose ;)

Is it the only thing which the installer does? Installs Proxmox packages (and perhaps, does some basic network settings etc.)?

Is it possible to install Proxmox VE over network (using tftp/PXE)? If not, what would be the best approach? Launch the server from a tftp-bootable distro, copy Proxmox CD to the HDD, then what...? How should I start the installer? I have a remote server with a KVM switch connected, no access...

kvm-84 was just released: http://article.gmane.org/gmane.comp.emulators.kvm.devel/28430 Interesting changes: - add virtio-console device - fix rtc time drift on Windows (-rtc-td-hack option) - add -vga none option for running headless guests - better block device error propagation...

It is VMware 1.0.3 (so perhaps any 1.0.x version should do). Windows 2003 is installed on a "raw device" (i.e., /dev/sdh). "Migration" is pretty simple: - create a new virtual machine in Proxmox VE - edit /etc/qemu-server/<new-VM>.conf, replace the HDD (pointing to a file) with a raw device...