Re: vncserver program disappered on FC32??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 28/12/2020 06:04, Robert G. (Doc) Savage via users wrote:
Here's the environment:

Bulk storage server for whole home
- 45drives.com Storinator
- 1 of 3 payload bays populated with 15 x 4TB drives in a 39 TB ZFS raidz3 array
- OS is CentOS 8.3 with array
- NFS shared as /tank
- /etc/exports  contains   /tank  192.168.1.0/24(rw/sync,root_squash)
- samba not yet configured

Linux laptop
- ThinkKPad P72 with 2 TB NVME boot drive
- OS is Fedora 33
- /etc/fstab contains   store:/tank /tank nfs defaults 0 0
- tank array mounted on /tank

Windows 10 Pro PC

My original concept was to create a 240 GB VM in the /tank/VM/ space and prototype C7, C8, or F33 versions of a physical storage server at a client site with a 240 GB SSD boot drive and 4 x 500 GB LVM RAID5 array served out with Samba to multiple client PCs and MACs.

I wanted to use a TigerVNC client on the Linux laptop to set up and configure the 240 GB VM on the storage server, but because the upstream author has munged its systemd conversion this is no longer possible. I also wanted to use RDP to connect the Windows PC to test samba connections on the VM running TigerVNC server.

Unfortunately I've run into permissions hell and can get none of these working. I would like to find an alternative to TigerVNC that will work in the target environment.

To verify.

1.  The VM's disk will be located on the file system mounted on that laptop at /tank in a subdirectory VM.
2.  The VM is running on the laptop.  That is, the laptop is running virt-manager.  Meaning the laptop is the host.
3.  Your user is a member of the libvirt group.

(Ignoring for the moment that it isn't clear to me what you mean by, and where the 240 GB SSD boot drive
and 4 x 500 GB LVM RAID5 array resides.  And/or, if that storage is to be part of the C7, C8 VM's in some
manner.)

If the above is true, then I see no need to connect to the storage server via VNC.

On the laptop I would run something akin to....

qemu-img create -f qcow2 /tank/VM/F33.qcow2 240G

Then running virt-manager on the laptop follow the steps to create a new VM and in the step to create or choose
the storage location point to /tank/VM/F33.qcow2.


---
The key to getting good answers is to ask good questions.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux