Re: android

[Patrick O'Callaghan]

On Wed, 2020-12-23 at 15:48 -0700, Joe Zeff wrote:
> On 12/23/20 2:54 PM, Patrick Dupre wrote:
> > 2) It seems that to install an app. I need to use google play
> > but I do not remember my passwd, and I cannot find a find to have it
> > restored (it has been set 2 years ago).
> 
> Alas, this is outside the scope of the Fedora mailing list.  If your 
> device has a user's forum, that would be the best place to ask.  If not, 
> try the company's customer service.

You can also sideload apps in Android without going through the Play
Store, though that has its risks, and is of course also outside the
scope of the Fedora list.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: Creating a Btrfs subvolume

[Patrick O'Callaghan]

On Wed, 2020-12-23 at 19:51 -0700, Chris Murphy wrote:
> (I did read the whole thread but I'm gonna reply three times anyway :D)
> 
> On Wed, Dec 23, 2020 at 6:29 AM Patrick O'Callaghan
>  wrote:
> > 
> > I have a directory I use to hold a Windows VM disk image
> > (/home/Windows/...), and would like to snapshot it before playing with
> > the QEMU settings. However it's already part of the /home subvolume, so
> > is there a way of splitting it off on its own without having to create
> > a new subvolume and sending the contents over? AFAIK subvolumes can be
> > hierarchical so it would seem like a useful thing to be able to convert
> > a subtree without all the copying, but the man page doesn't seem to
> > address it.

I'm going to take some time to digest the full answer, but I'll just
reply to this part for now:

> Your best bet really is to
> fallocate a raw file in a subvolume or directory with chattr +C set
> and don't snapshot or reflink copy it.

The Windows image file is in fact just an fallocated file used as a raw
disk, not a qcow. It's on an SSD and seems quite fast, so I wouldn't
worry overmuch about fragmentation. This system is basically only used
for gaming with GPU passthrough so pretty much everything can be lost.
My interest in snapshotting it is just to avoid the pain of a misconfig
in QEMU, which is notoriously picky (lomng story short, I'm trying to
modify it to use a Q35 CPU instead of the basic i440). The VM was set
up on virt-manager when the filesystem was ext4, so it won't have any
of the special BTRFS stuff unless I add it myself.

Expect further questions later :-)

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: Unable to login into custom live image

[Sreyan Chakravarty]

On Thu, 24 Dec 2020, 12:09 am Ed Greshko,  wrote:

> On 24/12/2020 01:07, Sreyan Chakravarty wrote:
> >
> >
> > On Wed, 23 Dec 2020, 7:09 am Samuel Sieb,  sam...@sieb.net>> wrote:
> >
> >
> >
> > What do you think was left out?  There are not going to be specific
> docs
> > for this particular situation.  If you're making modifications like
> > this, you're expected to have an idea of what you're doing.  This is
> not
> > a general end-user tool that you're trying to use.
> >
> >
> > There could have been a process via which they documented how they
> created the fedora iso that is available for download.
> >
> > My next step is to unsquash the Fedora 33 KDE live image and basically
> see how they are implementing the SDDM login.
>
> Why don't you do as suggested?  Get the
> fedora-kickstarts-0.31.0-0.4.fc33.noarch.rpm and
> unpack it?  There you will find
>
> fedora-arm-base.ksfedora-live-games.ks
> fedora-arm-kde.ks fedora-live-jam_kde.ks
> fedora-arm-lxde.ksfedora-live-kde-base.ks
> fedora-arm-lxqt.ksfedora-live-kde.ks
> fedora-arm-mate.ksfedora-live-lxde.ks
> fedora-arm-minimal.ks fedora-live-lxqt.ks
> fedora-arm-python-classroom.ksfedora-live-mate_compiz.ks
> fedora-arm-server.ks  fedora-live-minimization.ks
> fedora-arm-soas.ksfedora-live-python-classroom.ks
> fedora-arm-workstation.ks fedora-live-robotics.ks
> fedora-arm-xbase.ks   fedora-live-scientific_kde.ks
> fedora-arm-xfce.ksfedora-live-security.ks
> fedora-cinnamon-common.ks fedora-live-soas.ks
> fedora-cloud-atomic-pxetolive.ks  fedora-live-workstation.ks
> fedora-cloud-base.ks  fedora-live-xfce.ks
> fedora-cloud-base-vagrant.ks  fedora-lxde-common.ks
> fedora-cloud-bigdata.ks   fedora-lxqt-common.ks
> fedora-cloud-experimental.ks  fedora-mate-common.ks
> fedora-container-base.ks  fedora-minimal-common.ks
> fedora-container-base-minimal.ks  fedora-modular-arm-server.ks
> fedora-container-common.ksfedora-modular-disk-minimal.ks
> fedora-disk-base.ks   fedora-python-classroom-common.ks
> fedora-disk-minimal.ks fedora-python-classroom-gnome-common.ks
> fedora-disk-server.ks fedora-python-classroom-vagrant.ks
> fedora-disk-workstation.ksfedora-repo.ks
> fedora-disk-xbase.ks  fedora-repo-not-rawhide.ks
> fedora-iot.ks fedora-repo-rawhide.ks
> fedora-kde-common.ks  fedora-scientific-common.ks
> fedora-kde-minimization.ksfedora-scientific-vagrant.ks
> fedora-live-astronomy_kde.ks  fedora-soas-common.ks
> fedora-live-base.ks   fedora-workstation-common.ks
> fedora-live-cinnamon.ks   fedora-xfce-common.ks
> fedora-live-design_suite.ks
>
> Which are all the kickstart files used to create the various live images.
>


That's what I have been doing.

You can verify for yourself.

Try generating the live image from fedora- live-kde.ks and then boot from
the image. You will find that you can't login.

>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: Unable to login into custom live image

[Ed Greshko]

On 24/12/2020 22:29, Sreyan Chakravarty wrote:

That's what I have been doing.

You can verify for yourself.


But the info you are asking about is in fedora-live-kde-base.ks, right?

# set up autologin for user liveuser
if [ -f /etc/sddm.conf ]; then
sed -i 's/^#User=.*/User=liveuser/' /etc/sddm.conf
sed -i 's/^#Session=.*/Session=plasma.desktop/' /etc/sddm.conf
else
cat > /etc/sddm.conf << SDDM_EOF
[Autologin]
User=liveuser
Session=plasma.desktop
SDDM_EOF
fi


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

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: vncserver program disappered on FC32??

[Robert G. (Doc) Savage via users]

On Wed, 2020-12-23 at 18:15 +1000, Michael D. Setzer II via users
wrote:
> On 22 Dec 2020 at 23:04, Samuel Sieb wrote:
> 
> Subject:Re: vncserver program disappered on FC32??
> To: Community support for Fedora users 
> 
> From:   Samuel Sieb 
> Date sent:  Tue, 22 Dec 2020 23:04:46 -0800
> Send reply to:  Community support for Fedora users 
> 
> 
> > On 12/22/20 10:06 PM, Michael D. Setzer II wrote:
> > > On 22 Dec 2020 at 20:28, Samuel Sieb wrote:
> > > > On 12/22/20 8:13 PM, Michael D. Setzer II wrote:
> > > > > Problem is: If it works, you can no longer locally log into
> > > > > that user id,
> > > > > since it is configured for only the vnc session on that
> > > > > user??
> > > > 
> > > > That doesn't make sense.  Can you explain what you mean?
> > > 
> > > Never said it made sense. Just what it is.
> > > 
> > > If you set up a user account they way they say. It will start a
> > > vnc session
> > > on boot up with that user and that port. You can then vnc into
> > > the
> > > computer on that port and use the computer.
> > > 
> > > If you try to log in locally on that computer with that user id,
> > > the log in
> > > doesn't work, and it goes immediately back to the log in screen..
> > 
> > Oh, that's what you mean.  I thought you meant you couldn't ssh
> > into it 
> > using that user or something like that.  Ok, then that's just the
> > same 
> > thing that you were saying further down.  You can't have multiple 
> > graphical sessions for the same user.  It just doesn't work.  Have
> > you 
> > ever been able to do that with vncserver?  It's never worked for
> > me.  Or 
> > it sort of worked briefly, but sooner or later things go badly
> > wrong.
> 
> I think if you try and run a local session and vnc session with both
> using 
> gnome desktop there are issues with it. But I always run the vnc
> session 
> with the xfce desktop and never had a problem. I've also had no
> problem 
> running xfce locally with a vnc xfce session. Seems gnome is doing 
> something with dbus, and causes a conflict with both sessions trying
> to 
> use the same dbus settings??

My situation is similar, except that I use MATE exclusively. I am
trying to understand why the upstream maintainer's solution allows only
a single TigerVNC logon using a particular UserID. In other words, if I
have a local USER-A and a TigerVNC USER-A, if one is logged on the
other cannot. Does this mean that a TigerVNC USER-A will not have
access to local USER-A's home directory, and vice versa. If so, this is
ludicrous.

If TigerVNC has been so badly mangled in the name of systemd support,
what alternative VNC can folks recommend in its place? I seriously need
one to support development of virtual machines hosted on a server with
huge storage, and the local console of that storage machine is not in a
suitable place for development.

--Doc Savage
    Fairview Heights, IL
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: problem with NVMe disk at install

[Robert G. (Doc) Savage via users]

On Wed, 2020-12-23 at 09:46 -0500, C Linus Hicks wrote:
> On Wed, 2020-12-23 at 02:55 -0700, Chris Murphy wrote:
> > 
> > 
> > On Tue, Dec 22, 2020, 11:10 AM François Patte
> >  wrote:
> > > Bonjour,
> > > 
> > > I want to install fedora 33 on NVMe SSD disks and I have 2 such
> > > devices 
> > > but anaconda sees only one of them...
> > > 
> > > I can see both in the bios.
> > 
> > Does the firmware have an option for these drives? Such as, raid or
> > ahci?
> > 
> > Pretty sure it needs to be ahci.
> > 
> 
> You need to find a driver for that specific device that works with
> Fedora, then load that driver
> during the install process. There's an option you can specify on the
> boot command to tell it where
> to look for the custom driver.

I have two NVME SSDs in my ThinkPad laptop. They were originally joined
in a RAID1 array using an Intel fake-RAID chip. I had to logically
separate them in the BIOS by changing a storage setting from RAID to
AHCI and rebooting. I was then able to install Fedora to one of the two
devices which then appeared as /dev/nvme0 and /dev.nvme1. Like always,
a Fedora installation to a system which already has Windows 10
installed allowed me to choose one of the NVME drives for Fedora. GRUB2
allows me to dual boot to either.

--Doc Savage
    Fairview Heights, IL
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: Book for Fedora & one for bash

[Robert G. (Doc) Savage via users]

On Sat, 2020-12-19 at 08:36 -0400, George N. White III wrote:
> On Fri, 18 Dec 2020 at 15:55, Kostas Sfakiotakis
>  wrote:
> > 
> > Can someone suggest a good book for Fedora ( well at least with
> > systemd 
> > ) and one for bash a relatively recent one but please not just for
> > bash 
> > scripting .
> > 
> 
> 
> It is usually a mistake to focus on a single distro and shell
> environment.   If you
> plan to be around for a while you will encounter many changes, so a
> broader
> perspective is useful.   I started on unix when the documentation was
> a binder
> of reprints of papers by people at AT&T Bell Labs
> 
> and man pages.  Those early papers are still worth reading for
> perspective 
> on the underlying reasoning behind the shell and utilities.   
> 
> In many fields, work is increasingly done by distributed groups
> working in 
> different enterprises, each with different choices of Linux distro,
> so
> linux users often need to understand differences between
> distributions.   As an
> example, I developed and maintained a (very specialized) scientific
> application 
> that started out with Fortran on a CDC Cyber, moved to Dec VAX,
> Ardent/Stardent 
> UNIX, SGI IRIX, and then various linux distros, macOS, and (thanks to
> COVID-19, 
> Cygwin) (all this was with a single employer).
> 
> The application uses a number of shell scripts that started out using
> ksh on IRIX, 
> then bash for macOS and linux.  I recently updated the scripts to
> work with dash.   
> Either I'm slowing down or the pace of change has been increasing.
> 
> I've owned many editions of UNIX and Linux System Administration,
> see 
> .   
> > 
> > Also another question if i may ask , is there a way to monitor the
> > boot 
> > process on Fedora and see what get's written to the disk and if
> > possible 
> > where
> > 
> > ( granted pressing the F1 button will pop up a message saying for 
> > example  Starting the httpd daemon but a bit more detail on that if
> > possible ) ??
> > 
> 
> 
> Most daemons have debugging options that provide more detail.  
> UNIX and Linux System Administration has a good introduction, 
> then you may need to read the detailed documentation for the 
> version you are using.

If you haven't already done so, carefully review the Fedora 33
documentation
at https://docs.fedoraproject.org/en-US/fedora/f33/, especially the
Installation and System Administration guides. As I have just
discovered with the TigerVNC application, this documentation may not be
universally perfect. Stuff changes all the time. Buta, together with
the bash PDF previously cited, these two guides should answer 99.99% of
your Fedora questions.

--Doc Savage
    Fairview Heights, IL
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: nvme crash

[Robert G. (Doc) Savage via users]

On Mon, 2020-12-14 at 20:19 +1100, Eyal Lebedinsky wrote:
> 
> 
> On 14/12/2020 13.20, Chris Murphy wrote:
> > On Sun, Dec 13, 2020 at 4:42 PM Eyal Lebedinsky
> >  wrote:
> > > 
> > > I am not sure which list this should go to, so I am starting
> > > here.
> > > 
> > > I run f32 fully updated
> > >  5.9.13-100.fc32.x86_64
> > > on relatively new hardware
> > >  kernel: DMI: Gigabyte Technology Co., Ltd. Z390 UD/Z390
> > > UD, BIOS F8 05/24/2019
> > 
> > > boot/root/swap/data is on nvme
> > >  WD Blue SN550 1TB M.2 2280 NVMe SSD WDS100T2B0C
> > 
> > I can't tell from WD's website if there's any newer firmware
> > available. They seem to hide this information within the Windows-
> > only
> > software "Western Digital Dashboard". If you have Windows already
> > installed, it's straightforward to install this and find out if the
> > firmware is up to date.
> 
> Option 1) My nvme disk is on the mobo which has only one slot. I have
> access to a windows laptop
> but I will also need an external nvme/USB adapter - will the
> Dashboard work this way?
> Will a fw update leave the disk content safe?
> 
> I will try something else first.
> 
> > There is a boot parameter 'nvme_core.default_ps_max_latency_us'
> > which
> > takes a value in usec, but I can't find a value specific to this
> > make/model NVMe. My gut instinct is, it's a hack put in by upstream
> > kernel developers to work around a proper autodetect solution
> > between
> > PCIe intereface and the drive. I would sooner return the drive and
> > get
> > one known to work. I can vouch for Crucial, Seagate, and Samsung
> > SSD
> > and NVMe for the most part.
> 
> Option 2) Reading the reports (and more) I decided to test the boot
> param
> nvme_core.default_ps_max_latency_us=0
> which I understand turns off the APSTE feature.
> 
> > Oh here's a bug report
> > https://bugzilla.redhat.com/show_bug.cgi?id=1844905
> > 
> > That leads here:
> > https://bugzilla.kernel.org/show_bug.cgi?id=208123
> > 
> > comment 1 is a more solid lead than comment 2, because comment 2 is
> > a
> > value that is based on what? A guess? Reading the rest of the
> > thread,
> > it's still uncertain.
> > 
> > 
> > > For the second time this disk stopped working (first was about
> > > two months ago).
> > > It seems that the disk failed hard and could not be reset, the
> > > machine was powered off/on.
> > > I think (not sure) that last time I just hit the reset button but
> > > it did not boot.
> > > 
> > > The machine was booted (after dnf update) around 8pm, and crashed
> > > at 4am.
> > > 
> > > Following the earlier crash a serial console was set up which is
> > > how I can see the failure messages.
> > > 
> > > == nvme related messages
> > > [    7.488638] nvme nvme0: pci function :06:00.0
> > > [    7.536593] nvme nvme0: allocated 32 MiB host memory buffer.
> > > [    7.541819] nvme nvme0: 8/0/0 default/read/poll queues
> > > [    7.558122]  nvme0n1: p1 p2 p3 p4
> > > [   19.590010] EXT4-fs (nvme0n1p3): mounted filesystem with
> > > ordered data mode. Opts: (null)
> > > [   20.653500] Adding 16777212k swap on /dev/nvme0n1p2. 
> > > Priority:-2 extents:1 across:16777212k SSFS
> > > [   20.820539] EXT4-fs (nvme0n1p3): re-mounted. Opts: (null)
> > > [   23.137206] EXT4-fs (nvme0n1p1): mounted filesystem with
> > > ordered data mode. Opts: (null)
> > > [   23.210717] EXT4-fs (nvme0n1p4): mounted filesystem with
> > > ordered data mode. Opts: (null)
> > > ## nothing unusual for 8 hours, then
> > > [28972.459036] nvme nvme0: I/O 840 QID 6 timeout, aborting
> > > [28972.464757] nvme nvme0: I/O 565 QID 7 timeout, aborting
> > > [28972.470277] nvme nvme0: I/O 566 QID 7 timeout, aborting
> > > [28973.291025] nvme nvme0: I/O 989 QID 1 timeout, aborting
> > > [28978.603061] nvme nvme0: I/O 990 QID 1 timeout, aborting
> > > [29002.667243] nvme nvme0: I/O 840 QID 6 timeout, reset
> > > controller
> > > [29032.875421] nvme nvme0: I/O 24 QID 0 timeout, reset controller
> > > [29074.097644] nvme nvme0: Device not ready; aborting reset,
> > > CSTS=0x1
> > > [29074.110354] nvme nvme0: Abort status: 0x371
> > > [29074.114953] nvme nvme0: Abort status: 0x371
> > > [29074.119523] nvme nvme0: Abort status: 0x371
> > > [29074.124114] nvme nvme0: Abort status: 0x371
> > > [29074.128710] nvme nvme0: Abort status: 0x371
> > > [29096.645478] nvme nvme0: Device not ready; aborting reset,
> > > CSTS=0x1
> > > [29096.652210] nvme nvme0: Removing after probe failure status: -
> > > 19
> > > [29119.165921] nvme nvme0: Device not ready; aborting reset,
> > > CSTS=0x1
> > > ## many I/O errors on nvme0 (p2/p3/p4) repeating until a reboot
> > > at 8:30am
> > > ## one different message, appearing just once:
> > > [29123.800844] nvme nvme0: failed to set APST feature (-19)
> > 
> > I'd take the position that it's defective and permit the
> > manufacturer
> > a short leash to convince me otherwise via a tech support call or
> > email. But I really wouldn't just wait around for another

Re: vncserver program disappered on FC32??

[Matthew Miller]

On Thu, Dec 24, 2020 at 11:29:02AM -0600, Robert G. (Doc) Savage via users 
wrote:
> what alternative VNC can folks recommend in its place? I seriously need
> one to support development of virtual machines hosted on a server with
> huge storage, and the local console of that storage machine is not in a
> suitable place for development.

Does X2Go work for your use cases?

https://wiki.x2go.org/doku.php/start

Or, wait, since you're running VMs, have you considered using VNC as the
graphics console for your VMs and connecting directly?


-- 
Matthew Miller

Fedora Project Leader
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: vncserver program disappered on FC32??

[Robert G. (Doc) Savage via users]

On Thu, 2020-12-24 at 13:07 -0500, Matthew Miller wrote:
> On Thu, Dec 24, 2020 at 11:29:02AM -0600, Robert G. (Doc) Savage via
> users wrote:
> > what alternative VNC can folks recommend in its place? I seriously
> > need
> > one to support development of virtual machines hosted on a server
> > with
> > huge storage, and the local console of that storage machine is not
> > in a
> > suitable place for development.
> 
> Does X2Go work for your use cases?
> 
> https://wiki.x2go.org/doku.php/start
> 
> Or, wait, since you're running VMs, have you considered using VNC as
> the
> graphics console for your VMs and connecting directly?
> 
> 
> -- 
> Matthew Miller
> 
> Fedora Project Leader

Matt,

The primary mission of the server is mass storage (19 TB ZFS). Direct
console (MATE) and ssh connections meet those needs just fine. It's the
new mission objective of using that huge back-end storage space for
creating virtual machines to prototype new client servers (not yet
purchased). A VNC supporting the MATE desktop would be ideal since the
local console is located in an inconvenient space. My plans to use
TigerVNC to access virtual machines on this server now seem to be
torpedoed.

--Doc Savage
    Fairview Heights, IL
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: vncserver program disappered on FC32??

[Matthew Miller]

On Thu, Dec 24, 2020 at 12:30:19PM -0600, Robert G. (Doc) Savage via users 
wrote:
> The primary mission of the server is mass storage (19 TB ZFS). Direct
> console (MATE) and ssh connections meet those needs just fine. It's the
> new mission objective of using that huge back-end storage space for
> creating virtual machines to prototype new client servers (not yet
> purchased). A VNC supporting the MATE desktop would be ideal since the
> local console is located in an inconvenient space. My plans to use
> TigerVNC to access virtual machines on this server now seem to be
> torpedoed.

For this use case, have you considered using the built-in VNC functionality
of virt-manager?



-- 
Matthew Miller

Fedora Project Leader
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: vncserver program disappered on FC32??

[Ed Greshko]

On 25/12/2020 02:47, Matthew Miller wrote:

On Thu, Dec 24, 2020 at 12:30:19PM -0600, Robert G. (Doc) Savage via users 
wrote:

The primary mission of the server is mass storage (19 TB ZFS). Direct
console (MATE) and ssh connections meet those needs just fine. It's the
new mission objective of using that huge back-end storage space for
creating virtual machines to prototype new client servers (not yet
purchased). A VNC supporting the MATE desktop would be ideal since the
local console is located in an inconvenient space. My plans to use
TigerVNC to access virtual machines on this server now seem to be
torpedoed.

For this use case, have you considered using the built-in VNC functionality
of virt-manager?


When it comes to connecting to a VM I use remmina along with the 
remmina-plugins-spice.
Works fine, and there is no need to configure a VNC server on the VM.

---
The key to getting good answers is to ask good questions.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

f33 mediawriter :: SslHandshakeFailedError

[Adrian Sevcenco]

Hi! While using fedora media writer (with custom isos) i see this errors:

W@542ms: Error reading from QUrl("https://getfedora.org/releases.json";) 
: "Unknown error"
W@542ms: SSL error "The issuer certificate of a locally looked up 
certificate could not be found"
W@542ms: Was not able to fetch new releases: "Unknown error" Retrying in 
10 seconds.
W@542ms: Error QNetworkReply::SslHandshakeFailedError reading from 
QUrl("https://getfedora.org/releases.json";) : "SSL handshake failed"


while the url opens just fine in the browser ..
while i use only already downloaded isos, it's a little bit of 
unsettling to see these errors in console .. beside that i have to kill 
the application because it's getting stuck after writing the image and 
trying to verify it ..


Any idea about these problems? are they known or it's something 
particular to my installation?


Thank you!
Adrian



smime.p7s
Description: S/MIME Cryptographic Signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: Creating a Btrfs subvolume

[Chris Murphy]

On Thu, Dec 24, 2020 at 4:23 AM Patrick O'Callaghan
 wrote:
>
> The Windows image file is in fact just an fallocated file used as a raw
> disk, not a qcow. It's on an SSD and seems quite fast, so I wouldn't
> worry overmuch about fragmentation. This system is basically only used
> for gaming with GPU passthrough so pretty much everything can be lost.

Latencies are much lower on SSD.

> My interest in snapshotting it is just to avoid the pain of a misconfig
> in QEMU, which is notoriously picky (lomng story short, I'm trying to
> modify it to use a Q35 CPU instead of the basic i440). The VM was set
> up on virt-manager when the filesystem was ext4, so it won't have any
> of the special BTRFS stuff unless I add it myself.

Note that the VM image file contains no VM settings. So a snapshot of
the VM image only helps you preserve/rollback to a previous state of
that image. The image contains only file systems. So if the idea is to
roll back the guest's file system, then you're on the right track. If
the idea is to be able to rever qemu configuration, you want something
else.

My advice is to use:
virsh dumpxml $vmname > $vmname.xml

You can then make modifications, and dump that out as a separate name,
and you can diff the xml files.

You can also create a new vm from this exported xml using

virsh create $vmname.xml

Note that the name of the VM is in this file, so if you want to create
a new VM you need to edit the xml file and change the name of the VM
so it gets created with a new name.


> Expect further questions later :-)


Welcome!

-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: Creating a Btrfs subvolume

[Patrick O'Callaghan]

On Thu, 2020-12-24 at 14:27 -0700, Chris Murphy wrote:
> On Thu, Dec 24, 2020 at 4:23 AM Patrick O'Callaghan
>  wrote:
> > 
> > The Windows image file is in fact just an fallocated file used as a raw
> > disk, not a qcow. It's on an SSD and seems quite fast, so I wouldn't
> > worry overmuch about fragmentation. This system is basically only used
> > for gaming with GPU passthrough so pretty much everything can be lost.
> 
> Latencies are much lower on SSD.
> 
> > My interest in snapshotting it is just to avoid the pain of a misconfig
> > in QEMU, which is notoriously picky (lomng story short, I'm trying to
> > modify it to use a Q35 CPU instead of the basic i440). The VM was set
> > up on virt-manager when the filesystem was ext4, so it won't have any
> > of the special BTRFS stuff unless I add it myself.
> 
> Note that the VM image file contains no VM settings. So a snapshot of
> the VM image only helps you preserve/rollback to a previous state of
> that image. The image contains only file systems. So if the idea is to
> roll back the guest's file system, then you're on the right track. If
> the idea is to be able to rever qemu configuration, you want something
> else.

Yes, good point.

> My advice is to use:
> virsh dumpxml $vmname > $vmname.xml
> 
> You can then make modifications, and dump that out as a separate name,
> and you can diff the xml files.
> 
> You can also create a new vm from this exported xml using
> 
> virsh create $vmname.xml
> 
> Note that the name of the VM is in this file, so if you want to create
> a new VM you need to edit the xml file and change the name of the VM
> so it gets created with a new name.

Yes.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: Creating a Btrfs subvolume

[Patrick O'Callaghan]

On Thu, 2020-12-24 at 14:27 -0700, Chris Murphy wrote:
> You can also create a new vm from this exported xml using
> 
> virsh create $vmname.xml
> 
> Note that the name of the VM is in this file, so if you want to create
> a new VM you need to edit the xml file and change the name of the VM
> so it gets created with a new name.

Looks like you also have to change the UUID, or virsh will complain
that it already exists. Fortunately it's just a matter of running
uuidgen and plugging in the result. You also have to globally change
pci to pcie, but I already knew that.

This seems to have worked and I'm now running the new VM. Unfortunately
it still has crackly sound (I was hoping a change to the Q35 would
improve this), but that's a separate issue.

Thanks for your help Chris.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Re: Creating a Btrfs subvolume

[Chris Murphy]

Two other ideas:

You could create an "original" copy of the VM that you never touch,
and then clone it to restore. What I don't know is whether clone
implies duplicating all the storage too. If so then you might want the
original to have no file set for the virtual drive.

I've gotten somewhat adept at fiddling with the xml using 'virsh edit
$vm' but there's a somewhat recent feature you can enable in
virt-manager to directly edit xml in virt-manager. For every device on
the left side UI, there's GUI configuration on the right side, but at
the top there's a tab to see the xml. You have to go dig in
virt-manager preferences to enable xml editing, otherwise you just get
to look at the xml, not change it. I've started doing this rather than
editing the xml directly via virsh edit.

--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org