Question about QEMU | copy and paste | bridge network | qemu://session
Hello, I'm using QEMU on Fedora Linux (specifically the graphical virtual machine manager) I decided to use qemu://session mode to store virtual machines on the home directory instead of the system directory, so that if the main system crashes, the virtual systems will not be cleaned up. So, I encountered such a problem that the network bridge does not work, as well as two-way , or even one-way clipboard, ie in general can not copy text from the main system to the guest. I'm not going to use Virtual Box, I'm only considering QEMU for use. I have also tried to solve this problem myself through these methods : 1. http://blog.wikichoon.com/2016/01/qemusystem-vs-qemusession.html 2. http://wiki.libvirt.org/page/FAQ#What_is_the_difference_between_qemu:.2F.2F.2Fsystem_and_qemu:.2F.2F.2Fsession.3F_Which_one_should_I_use.3F . 3. By inserting this text into the config file : ``` [device] chardev = “qemu-vdagent,id=ch1,name=vdagent,clipboard=on” device = “virtio-serial-pci,id=ch1,name=com.redhat.spice.0” ``` 4. Using this video - https://youtu.be/cef8BAeiL8I But none of these methods worked for me. Please help me ! It is very important to configure the network bridge as well as the clipboard between systems.
Bugs in SSH module
Hi Sawyer, I'm running Ubuntu 18.04.5 (5.4.0-60-generic kernel) and a QEMU 5.1.0 build for x86_64. I originally built for all targets including arm and aarch64 but it took too long. I haven't seen this problem. Good luck! Dave Here's my configure line ../../../configure --prefix=/opt/qemu \ --target-list=x86_64-softmmu \ --enable-debug \ --enable-spice \ --enable-virtfs \ --enable-curses \ --enable-libusb And here's a view of all my libssh package versions: linger:229$ DPKG=libssh apt.sh pkg_brief brief DPKG = libssh Listing... Done libssh-4/bionic-updates,bionic-security,now 0.8.0~20170825.94fa1e38-1ubuntu0.7 amd64 [installed] libssh-4/bionic 0.8.0~20170825.94fa1e38-1build1 amd64 libssh-dev/bionic-updates,bionic-security 0.8.0~20170825.94fa1e38-1ubuntu0.7 amd64 libssh-dev/bionic 0.8.0~20170825.94fa1e38-1build1 amd64 libssh-doc/bionic-updates,bionic-updates,bionic-security,bionic-security 0.8.0~20170825.94fa1e38-1ubuntu0.7 all libssh-doc/bionic,bionic 0.8.0~20170825.94fa1e38-1build1 all libssh-gcrypt-4/bionic-updates,bionic-security,now 0.8.0~20170825.94fa1e38-1ubuntu0.7 amd64 [installed,automatic] libssh-gcrypt-4/bionic 0.8.0~20170825.94fa1e38-1build1 amd64 libssh-gcrypt-dev/bionic-updates,bionic-security 0.8.0~20170825.94fa1e38-1ubuntu0.7 amd64 libssh-gcrypt-dev/bionic 0.8.0~20170825.94fa1e38-1build1 amd64 libssh2-1/bionic,now 1.8.0-1 amd64 [installed,automatic] libssh2-1-dbg/bionic 1.8.0-1 amd64 libssh2-1-dev/bionic 1.8.0-1 amd64 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii libssh-4:amd64 0.8.0~20170825.9 amd64tiny C SSH library (OpenSSL flavor) ii libssh-gcrypt-4:amd64 0.8.0~20170825.9 amd64tiny C SSH library (gcrypt flavor) ii libssh2-1:amd64 1.8.0-1 amd64SSH2 client-side library - snip snip --- Date: Fri, 22 Jan 2021 21:12:04 +1100 From: "Berto Furth" To: "Sawyer Liu" , "qemu-discuss@nongnu.org" Subject: Re: [EXT] Re: Bugs in SSH module Message-ID: <1a348279-65f9-4506-8087-1e0b71b65...@www.fastmail.com> Content-Type: text/plain; charset="utf-8" Hi Sawyer, Oh yes, sorry it is libssl-dev. What version do you have installed? According to the link you sent, there's a reference to a problem with some older versions of libssl included with ubuntu libssh-0.8 is detected as 0.7 https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1847514 The version I am using is #apt list libssh-dev Listing... Done libssh-dev/stable,now 0.8.7-1+deb10u1 amd64 [installed] As I said it seems to compile with libssl enabled just fine. I assume you've done "apt update" and "apt upgrade" and all that? Other than making sure you're using a recent version of libssl-dev I don't know what else to suggest.
qemu-system-arm sharing host disk using virtiofsd
Greetings - I'm not sure this is the best group to ask the following question but I'll start here. I use qemu to develop openwrt code. I currently use a 9p mount to share my code/cross-compile directory to the arm guest in order to run/test the code. openwrt uses the musl library so this works pretty well. I use Ubuntu 18.04 for host, qemu 5.1, openwrt 19.07 for guest. I configure/make both the qemu executable and openwrt kernel/rootfs. My research indicates virtiofsd is now the preferred way to share host dirs to the guest and I see points in the qemu 5.1 code that reference virtiofsd. * https://qemu.readthedocs.io/en/latest/tools/virtiofsd.html * There is a $Q_TOP/tools/virtiofsd directory which is empty. * `find . -name "Makefile*" | xargs grep virtiofsd` shows a lot of hits. I cannot figure out how to create virtiofsd using my QEMU 5.1 source tree. And the instructions at `https://virtio-fs.gitlab.io/howto-qemu.html` fail spectatularly. I must be missing something obvious; please point me in the right direction. 9P still works fine so I'm not interested in spending a lot of time on this. Dave Turvene
Re: qemu-system-arm sharing host disk using virtiofsd
On 8/29/21 4:55 PM, Dave Turvene - Work wrote: > Greetings - > > I'm not sure this is the best group to ask the following question but > I'll start here. > > I use qemu to develop openwrt code. I currently use a 9p mount to share > my code/cross-compile directory to the arm guest in order to run/test > the code. openwrt uses the musl library so this works pretty well. > > I use Ubuntu 18.04 for host, qemu 5.1, openwrt 19.07 for guest. I > configure/make both the qemu executable and openwrt kernel/rootfs. > > My research indicates virtiofsd is now the preferred way to share host > dirs to the guest and I see points in the qemu 5.1 code that reference > virtiofsd. > > * https://qemu.readthedocs.io/en/latest/tools/virtiofsd.html > > * There is a $Q_TOP/tools/virtiofsd directory which is empty. > > * `find . -name "Makefile*" | xargs grep virtiofsd` shows a lot of hits. > > I cannot figure out how to create virtiofsd using my QEMU 5.1 source > tree. And the instructions at > `https://virtio-fs.gitlab.io/howto-qemu.html` fail spectatularly. > > I must be missing something obvious; please point me in the right > direction. 9P still works fine so I'm not interested in spending a lot > of time on this. > > Dave Turvene Just to follow up for closure. I was missing something 1) configure flags: --enable-seccomp \ --enable-cap-ng \ 2) a current version of libseccomp-dev: apt-get install libseccomp-dev BTW, the config-host.mak generated file was instrumental in diagnosing this. I have not explored it in the past. David Turvene
