Search results

It's silent when using anything other than a Template as source ;) Good find! (I don't use templates much, yet.) So, revised suggestion: Please include the "Mode" field (Full Clone vs Linked Clone) for non-template sources, grayed out of course to only allow Full. Not that simple or obvious...

Is there no way to detect that it has been written? (If nothing else, do a binary compare before and after the copy ;) ) Since EFI storage is small (typically a few hundred MB), and writes to EFI storage are incredibly rare, why not: 1) Have the migrate fail on EFI write... or better: 2) do...

I should have been clearer (particularly since I am lamenting lack of GUI clarity!) My apologies. SOME is not in the documentation: * Nothing explains that the GUI clone tool silently does linked vs full clone depending on the source. (This of course is best "documented" in the user interface...

@fabian something we do in other circumstances is preserve a copy of such crucial info on occasion, eg during reboot etc. EFI config info doesn't change often... so while it is writable, it is rarely written, correct? This is truly a killer issue. :(

+1 ... I need to clone a crucial running VM. 100% failure when it attempts to make a mirror of the EFI disk. (This makes no sense to me... isn't the EFI partition only used during boot?)

SUGGESTION: Please document and highlight some of the above! It is NOT in the documentation, and as the OP mentioned, it is not said in the GUI. GUI crucial confusing items missing: * If copying from a non-template, call this "Full Clone"; if copying from template, call it "LInked Clone" (I...

I got 7.2 installed on my new host by using two steps: 1) To get the first part of install going, I had to switch "quiet splash = silent" to nomodeset (press 'e' while the "install" option is selected, to get to editor) 2) That went pretty far, then failed with an error about FrameBuffer Mode...

I have a two-node cluster; been running for almost a year. New node configured; time to add it. (All are running the same PVE version; all have same underlying linux; all can ssh to one another; etc etc.) I used the GUI to add the new node to the cluster (pasting the blob of secure info). The...

I was installing VE 7.2 on my brand new host box... first ran into black screen after install begins -- see separate thread on that. Then, install failed, with the X server conking out before anything graphical happened. Here's the generic solution: 1) Hit ctrl-alt-F2 to see the error screen...

I'd really rather avoid installing on top of a non-optimized linux ;) Your "try this" looks interesting... digging with Google found it right here, a couple of years ago ;).... Let's see how well that works for me... (BTW, reviewing the old thread: they saw GUI after 30 min or so. Not me....)...

I'm installing VE 7.2 on a nice new HP SFF Z2 G5... with nVidia T1000 card. Total video overkill since this will be a headless host once set up ;) In any case, while I got other USB boots to work by forcing VGA video (eg GPartEd)... in this case I don't see any ProxMox install options at ALL in...

That's VERY good to hear. I certainly agree that the new version is hugely improved. It caught memory issues for me that were simply invisible to older versions. I just was cautious about it being offered without a bit of caution since memory tests are depended on as a solid confidence builder...

@oguz et al, You might want to highlight that the memtest86+ v6.0 rewrite is currently BETA software. The memtest86.com version is not beta, but also not open source... ;)

Many ISO's come in *.iso.gz form. Right now, a workaround is required in the GUI to accomplish this: * Set up the download * In the filename section, remove the ".gz" or it will complain that it's a bad filename * After the download, in the shell mv xyz.iso xyz.iso.gz gunzip xyz.iso.gz rm...

(FWIW, I am closing in on having a fully functional, no-issues, two-system pfSense with CARP (mirrored settings AND sync'd network states), using a single ISP WAN address. Very nice. Not 100% there but very very close.)

Actually, it is now working better... once I resolved some other issues. Turns out (at least with pfSense), the MAC for the CARP virtual IP address (VIP) is static (00:00:5e:00:01:01) and identical for both systems the secondary CARP VIP and MAC are disabled while not active when a failover...

You're suggesting that the CARP on each router should have the exact same MAC? Hmmm... I'm not sure how well the (physical) switch would handle that. Good idea! I'll look into it.

I'm running a two-node pfSense HA (BSD "CARP") cluster on a couple of Proxmox hosts. Mostly, it works. However, under failover conditions, things don't work well... and I suspect it is because the secondary pfSense takes over the gateway IP address, which causes the MAC address to change...

Ahhh... I already did the much-delayed update/upgrade after manually disabling enough of kdump-tools. I've installed the headers for the future (obviously would need to be redone as well... I'll add this to my little kdump-tools summary in anticipation that it will help someone in the future. :)

Thanks, @Tmanok ... Identifying what packages are responsible for various files/folders sounds like a very helpful process. I see there's apt-file -- is that what you're thinking of? I'll try it... kdump is not a separate package. Sorry to mis-state. kdump-tools is "everything" ;) The primary...