Search results

It sure does not seem like there is any right side in the debate. On the one side, people who demand everything be handed to them in a neat little box for free... so disappointing. Proxmox VE is heavily based on other free technologies: Debian, KVM, ceph, etc. The value they provide (at the...

When you say "serial0: socket" where in the UI would this be applied? It doesn't look like Unix domain sockets are the best approach. It's not clear if it's possible to send a serial BRK over a Unix domain socket (or generate one from e.g. socat, minicom can probably do that). The KVM -serial...

In some cases, it does. Although when required the config is typically minimal. On physical hardware, FreeBSD and some Linux distros have it enabled by default and can be installed from CD-ROM using only serial console, though this sometimes requires BIOS serial console support which you may...

As I think about it, the "-serial telnet:localhost:1234,server,nowait" option might work better than Unix domain sockets, because telnet is already present in the default install and it makes sending breaks (important for kernel debugging) more straightforward/standardized. Port assignments...

Oh, and we haven't upgraded to 3.0 yet, so I haven't played with templates at all, but the ability to have virtual serial ports created automatically with unique, predictable file names when cloning a template would be fantastic as well. As long as the unique, predictable name is based on the...

It would be desirable to add serial ports via the UI, using virtual serial ports, not physical ones. There are not enough physical ones to go around. :) So something like: -serial unix:/path/to/serials/123.tty,server,nowait Then some command line equivalent to "xm console 123." Maybe...

As a console solution, that might be good for many people. (Although I don't think SPICE options on Mac are very good, though I have never had occasion to try.) Nonetheless, that won't help configure and manage serial ports on virtual machines, which as I hoped to illustrate has many useful...

Perhaps I should add that after I did eventually get Java working again, it takes multiple "Don't run this!" popups to get the console running, including one that reads: It's basically saying, "This specific app, the VNC Viewer from Proxmox? Yeah, don't run that, it's probably malware."...

While doing some research on the possibility of setting up Xen-style serial consoles for KVM virtual machines on Proxmox, I found that past comments on the subject by Proxmox folks are basically, "There is ssh and there is VNC. There is no use-case for anything else." The big obvious problem...

Sure thing, friends don't let friends drive Realtek NICs, even if they're emulated. ;-)

I have successfully PXE booted KVM virtual machines under Proxmox with both e1000 and virtio by simply setting the device start order to include the network device on the Options tab under Virtual Machine Configuration. No ISO was required; Proxmox appears to include the necessary PXE...

Thank you very much, that was exactly what I needed to run my tests. We have determined it's definitely related to the checksum offloading and confirmed that every offloaded segment generates one such diagnostic, but have yet to figure out whether it's a problem on the KVM side or the guest...

You may wish to clarify this on the site; it refers to the per-socket option as "Professional Server Subscription." Since software is often called a server (e.g. "Apache server") and software in this space is typically licensed per socket (e.g. VMware, RedHat, Citrix, Oracle all do this), this...

I had something very similar happen. Make sure your existing machine is not touching a serial port. If the serial port was not configured on KVM, attempting to access it from the VM (e.g. for virtual serial console leftover from Xen), CPU usage will go to 100% and the VM will hang.

Along this line, if we have questions about commercial licensing costs and options, is there someone we can contact? There aren't any "sales" or "contact us" links on the site that I could find. I'm as happy as the next guy not to have to deal with "sales" but I do have a couple of questions.

For testing purposes, it is just a right-off-the-install disk configuration on a private network, so there's not any iptables/firewall unless something was set up by the install or behind the scenes. I'm not a Linux expert, but I think this means there's nothing: # iptables --list Chain INPUT...

I have done apt-get update & upgrade on v9. Here's what I have now: pve-manager: 1.9-24 (pve-manager/1.9/6542) running kernel: 2.6.32-6-pve proxmox-ve-2.6.32: 1.9-47 pve-kernel-2.6.32-6-pve: 2.6.32-47 qemu-server: 1.1-32 pve-firmware: 1.0-14 libpve-storage-perl: 1.0-19 vncterm: 0.9-2 vzctl...

Here we go: pve-manager: 1.9-24 (pve-manager/1.9/6542) running kernel: 2.6.32-6-pve proxmox-ve-2.6.32: 1.9-43 pve-kernel-2.6.32-6-pve: 2.6.32-43 qemu-server: 1.1-32 pve-firmware: 1.0-13 libpve-storage-perl: 1.0-19 vncterm: 0.9-2 vzctl: 3.0.28-1pve5 vzdump: 1.2-15 vzprocps: 2.0.11-2 vzquota...

Hello, I have a few Proxmox 1.9 servers running in a test configuration. I noticed this morning one went to "nosync" and I logged in, the root fs was full because /var/log/syslog took up the entire disk. I rotated it out and hupped syslog. Sync is now fine, but the /var/log/syslog file is...