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...
:) OK, I do agree -- shouldn't have been quite so dogmatic about impossibilities :) At some point it's possible to bit-twiddle ANYthing LOL!
Interestingly, even with thin provisioning, performance does vary. (My suspicion: if transferring using a "dumb" utility, it may actually move 450GB of...
Thanks for the thoughts! I've done additional research and for now have solved my issues, and also learned a bunch.
NOTE: ALL of this is applies to GPT (or MBR) Disk/partition management on all typical OS (Linux, MacOS, Windows).
First, a few answers for the curious:
1) Why am I even looking...
Questions:
How do I avoid creating a ZVOL when setting up a VM??? Perhaps by putting images in local instead of local-zfs?
Is there a way to convert a ZVOL to a normal image file?
I am working on a Win10 image. It's too big; want to shrink it. I reduced the partition sizes so I have under 52GB of partitions in a 500GB raw virtual disk.
Config info below.
The hard part: the image (in my local-zfs storage) is actually apparently a set of links to /dev/zd48* which are...
I suspect the Wiki is simply incorrect. I have no sense one can add a VLAN directly to a bond. Maybe it has changed with ProxMox 8???
What DOES work (I've not repeated exactly yours, but this is like mine using my card, vmbr and vlan numbers):
...
auto bond0
iface bond0 inet manual...
(UPDATE: actually I had a configuration error. ProxMox can largely work around my error if I tell it about my PVID... but not completely. I have edited this reply to reflect reality...)
I FOUND IT!!!
Got remote SSH Wireshark running and stared for a while. I finally realized: when the bridge...
Could be! THANK YOU for that link. Even though much of what is on that page does not apply to ProxMox (we use ifupdown2 for one, and it has nothing about /etc/network/interfaces, and...) ... much DOES apply.
I'm going to simplify. Apparently, having an embedded VLAN trunk that is not used by...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.