Search results

That's outside my direct experience as we have no Linux VMs running under Proxmox. If it's just for testing purposes, I could prepare you a minimal disk image with FreeBSD kernel configured for this type of debugging.

That's mostly what I use it for, but I think some other OS's work the same. Also when not used in this fashion the signal info is available to user programs, so there are many other uses.

Ok, here is an example of both methods. First, for this config line: args: -serial telnet:localhost:6123,server,nowait root@testhost:~# telnet localhost 6123 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. ... booting up messages ... Sat Aug 24 00:43:18...

Certainly, that can be done. Hopefully today. In short, serial BRK is an out-of-band signal. The telnet protocol (RFC 854) is not just a bare TCP connection, it supports out-of-band data. You hit ^] to escape to the telnet client prompt and then type "send break" and hit enter and an escaped...

The name is not "test version" or "pvetest" it is "pve-no-subscription." "pve-enterprise" is a paid set of patches that are released fewer and slower than "pve-no-subscription" for people super-conservative about changes (like me). To the best I understand, no patch goes to "pve-enterprise"...

This is the config line I use: args: -serial telnet:localhost:6123,server,nowait (for VM ID 123) If it is written as: serial0: telnet:localhost:6123,server,nowait then the Proxmox web UI says the serial port number is invalid when starting the VM, and it fails to start. How is serial...

As we are deciding whether to get community or basic licenses, it would be helpful to know: is this issue ("we want TSO to work in our VMs") an example of something we could open as a ticket to help us get it working?

On the nag screen, I mentioned this to a colleague today. His response: "Still faster than logging in to (expletive deleted) VMware." :D

Huh, it seems I missed all the great follow-up to this. Thanks for implementing that! FWIW, we were going the args: route as well with the telnet interface, which does work great for sending breaks to the VM's serial console to drop to kernel debugger, etc. Never did get serial0: to work for...

User's name is "nope nope nope," was created yesterday, and has done nothing but complain about nag screen. "Oh I'm a big guy!" "Oh I would have donated lots!" "Oh I will make Proxmox alternative!" They do not give anything, but they will take take take: your software, your attention, your...

At what point in the checkout process does the VAT go away?

If you must have UDP, you can evade the data corruption problem with UDP reassembly and id overflow if you set rsize/wsize less than the MTU so the NFS packets are never fragmented. Which if you can enable jumbo frames is not as ridiculous as it sounds.

Suppose there is a Proxmox server with 4 network interfaces (eth1 - eth4) in a bonded LACP (bond0) configuration and 9 virtual machines evenly spread across three VLANs (1 - 3). What manner of network configuration will give the best performance and functionality? Currently it is configured in...

Checking out the git repository gives you the whole history of the project. You can build it from the current sources or any point in the past. There are no "snapshots" per se. This setup is a little weird, but since most of it seems done by one guy (Dietmar) it is probably manageable for...

Yes, the git repository does seem a little short in the branches & tags department. For the most part it looks like you have to find the commit that says "bump version to 3.1-2" or similar. E.g. for pve-manager: $ git log commit e1f08ccd79752801b92018706f8d9ba63ad2d181 Author: Dietmar Maurer...

Read a dictionary. "You" means you, not Proxmox.

Actually I understand that just fine. But the existence of bug fixes between versions does not mean that Proxmox owes anybody free binary versions of those outside their usual release schedule. Ohh.... you're referring to an AGPL where the "A" stands for "Alternate Reality." Sorry, I...

That is one possibility, but since they are not communicating about this there will be no way to know for sure what upgrade paths they will provide until 3.2 comes out. Doing a "complete reinstall" in a cluster is not that big of a deal though, unless it's one of the many releases where live...

No, according to GPL, which applies to stuff they are using (e.g. Debian), they must make source code of GPL components available, including modifications, if any. It does not mandate how. Offering to mail people disks is still considered adequate under GPL. Git is certainly adequate to this...

Since you are unwilling to pay, it's unclear why you care what people who pay do or don't get. Further, the Proxmox sources are open, and open to all not just those who pay, the link is already posted in this thread. To add a src repo to the default config for production servers makes no sense...