Search results

Would it be possible to have proxmox manage custom invocations of kvm/qemu, that is proxmox lists the system in the ui and can start/stop it and add the network bridges etc as required, but the majority of the command line is entered by hand by the user (basically an extension of the args...

I've had no luck using the new virtio scsi support with windows guests... The driver loads, and shows up as "RedHat Virtio SCSI Pass-through driver", but various problems occur when i try to use it. If i use LVM backed storage, the disk shows up inside the guest with the full capacity of my raw...

KVM 1.4 has a few new features, x-data-plane for improved virtio block performance and machine type "q35" which is supposed to become the default in the future... Is it possible/planned for proxmox to introduce support for these features? In particular, q35 support is intended to be the...

I noticed proxmox 2.0 defaults to using port 8006 for the web interface, and port 443 is simply a redirect to 8006... Is there any particular reason for this? And any reason i couldn't change it back to 443? It is relatively common for corporate internet access policies to block access to ssl...

I have a cluster of 2 nodes running PVE 2.0, which were upgraded from 1.9... The old primary node works fine, no problems... The second node however will run fine for a while, and then the cluster services seem to shut down for no apparent reason... There is nothing obvious in the logs on the...

After upgrading to the 2.6.32-10 kernel, certain guest images now crash with the following errors: --- init-early.sh[845]: segfault at ffffffffff600400 ip ffffffffff600400 sp 000003961c08f5b8 error 5 grsec: Segmentation fault occurred at ffffffffff600400 in...

I have an existing proxmox 1.9 cluster with 2 nodes, using iSCSI shared storage with virtual images spread over both nodes. In the install guide it mentions upgrading a cluster, but what's not clear to me is if the images on all the nodes will be preserved, or if only the images on the master...

I have made a simple change to QemuServer.pm to allow the "cache=unsafe" option to be used on virtio disks... Now while i realise the risks of using this option and would not advocate it as a default or even to be encouraged, it can provide improved performance in some cases. In particular, i...

Currently i have a number of linux images running under KVM on proxmox, however i find that if any of these images start to swap then performance of the whole host is dragged down considerably... As i use separate virtual disks for swap, is it possible, or would it be feasible to enable write...

I have a setup whereby i have 2 proxmox installs, connected to an iscsi back end for storage over gigabit ethernet... The setup works well, and live migration works nicely... However, if any of the images get bogged down and start to swap heavily it very quickly saturates the iscsi link. I...

I have an HP server with Intel gigabit server nics and an HP p410 raid controller acting as an iscsi target using SCST... Performance locally of the disks is: /dev/sda: Timing cached reads: 13156 MB in 2.00 seconds = 6585.94 MB/sec Timing buffered disk reads: 704 MB in 3.00 seconds =...

I have a small cluster of proxmox servers talking to an iSCSI storage box... Currently, if the storage box goes away even briefly i start getting serious errors on the guest images, which assume there is a hardware fault and either crash or remount the filesystem read only. Is there any...

I have been running proxmox systems for a while now, and a few features i can think of which would be useful but which don't seem to appear in the roadmap: Serial console support: currently i manually configure a serial console on each image, for instance: args: -serial...

Hi, I read today about the vhost-net project, which aims to decrease latency and improve throughput for the virtio drivers... It consists of a kernel patch (which is now integrated in the recently released 2.6.34 kernel) and a patch to kvm... http://www.linux-kvm.org/page/VhostNet Is...

I have Proxmox 1.3 installed on a Quad-Core AMD Opteron(tm) Processor 1354 and am attempting to install FreeBSD... The boot loader which gives you the option to press 1 to boot, 7 to reboot and a bunch of options in between seems to hang immediately (it usually gives you a 10 second...

I have been using Proxmox VE to host several instances of FreeBSD and encountered a number of issues... When using SCSI disks in the kvm image, after installing FreeBSD 6.3 or 7.0 the system fails to boot, the bootloader cannot find the boot disk When using IDE disks in the kvm image...