Search results

Ummm... PLP is greatly limited. It can only handle a few tens of ms of data transfer, which should be enough to stabilize what was already sent to the device. In fact, modern NVRAM SSD's claim to provide equivalent protection, and the OpenZFS team believes it (see link below.) Beyond...

1) Is pfSense on your Proxmox server or elsewhere? 2) You're certain the link to the switch is 100% fine? If not, I would temporarily simplify by backing off from LACP/LAG group. Keep it a simple one-connection link until you have this solved. Fewer variables. 3) Here's how I have trunk +...

We're talking PCIe Pass Through here. The VM configuration includes the exact PCIe slot. Here's what the *.conf line it looks like for an nVidia GPU... with the final .* removed so both the GPU and audio devices are passed through (required for the nVidia driver/installer to recognize the card):

How certain are you that the other host is 100% identical? Exact same devices in every PCIe slot? Same firmware versions? (I can kinda guarantee the S/N's are different but that is hopefully never an issue.) You can certainly come close even if PVE won't directly do it: Shut down VM Edit the...

I just finished accomplishing this. It's not too tough once you know how to get past a few nigglies. Many thanks to @Dunuin and to the author linked below. And of course to the awesome ProxMox team. Prerequisites This sequence is based on a few assumptions. If your situation is significantly...

WIreshark is your friend. And tcpdump within a VM. And learn how to do live remote (ssh-based) tcpdump to wireshark as needed. But for this situation where you're not getting the DHCP, just doing tcpdump in pfSense and in your VM ought to tell you a lot. You're certain the hash policy is...

Also: MUST pass through both the video and audio devices, or the VM's nVidia drivier may not see the pass through. See my post.

Final notes: Once the above (see "A few hints..." (NON-copying) sgdisk sequence is performed to create the new GPT and three partitions on the new disk) is complete, the job is finished after these commands (change sdx to your drive, or better to disk/by-id/xxxx) proxmox-boot-tool format...

A few hints maybe should make their way into that part of the wiki at some point. Obviously, overwriting partition tables is Dangerous Ground :) Something perhaps-safer: here's how to set up a drive the ProxMox Way, without doing a copy at all ;) For testing... Save and restore partition tables

OK, I have rescued my partitions*** and am up and running again. However, there's still this nagging question... I understand. That's honestly how it is supposed to work. And I seriously questioned my sanity. Honestly, it didn't work that way for me. Makes me nervous about sgdisk and/or...

There is a SERIOUS error in the instructions on the wiki! I'm working my way back to repair the damage... sgdisk <healthy bootable device> -R <new device> SHOULD be sgdisk --replicate=<new device> <healthy bootable device> Supposedly the wiki version works. Did NOT for me. It wiped my...

I realize this is an old issue, but I just ran across it for the first time. I have extensive ddrescue experience, having helped the author add some improvements. Here are a few suggestions based on more experience than I wish ;) For both rotating and SSD storage, if you have any concern that...

I see info discussing the Installer layout of ProxMox EFI boot drives, with 3 partitions: I want to add a second mirror drive. There are complex methods, but I'm seeking something simple for myself and others. To that end, a few questions: 1) Is there a script to duplicate what the Installer...

I found the presenting issue. Sad. 1) HINT: the code nicely pointed by @fiona above is only one aspect. It uses verify_spice_connect_url() and I can't find the actual source for that. (In this module, there's only a stub.) 2) That was a red herring anyway. The REAL issue is not documented...

THANKS!!! I will dig in on that ASAP. :) (To view the contents of the .vv I used my text/binary file editor. To open for use, I used remote-viewer as recommended.)

Thank you, that helped me get a bit further. Now I understand: * On PVE, we don't directly connect to the VM at all (eg via VM IP address) but always and only via the host. * I now see spiceproxy in the host, etc. I've now run spiceproxy in debug mode to examine why the connection isn't...

I am trying to get SPICE going for the first time, and failing miserably. I *think* I've debugged to the following point: * firewalls are not an issue. I can ping everywhere, can RDP in, can ping, etc. * I've loaded all of the various bits that need loading AFAIK into local machine, into guest...

I just got this fully working; thought I'd share my notes on what it required to succeed in my context. Host: HP Z2 SFF box, Xeon CPU with full virtualization support. A. MUST follow standard ProxMox host pass-through instructions (.../pve-docs/chapter-qm.html#qm_pci_passthrough) including...

Where did I hear this? Just following Fine Documentation :) Nice: root@proxmox:~# qm resize 555 scsi0 +5G root@proxmox:~# grep scsi0: /etc/pve/nodes/pve2a/qemu-server/555.conf scsi0: local-zfs:vm-555-disk-0,iothread=1,size=13G,ssd=1 Not So Nice: root@proxmox:~# qm resize 555 scsi0 -5G Unknown...

Yet the (easy CLI) tools for shrinking do not work on block devices. ZVOL is a block device. QCOW2 does have maybe 10% overhead, but the practical benefits outweigh that small cost IMHO. Others have identified a litany of benefits to QCOW2. Don't get me wrong: in a fully stable mature...