Re: Kernel panic - not syncing: Unable to initialise architected timer : unable to boot Android 14 with qemu-system-aarch64 on Ubuntu 24.04 X64 bit
2024-08-28 15:10, Mario Marietto wrote: Hello. maybe I did some progress using these parameters : console:/ # [7.812969] init: Service 'recovery' (pid 106) received signal 11 [7.813381] init: Sending signal 9 to service 'recovery' (pid 106) process group... You go a shell prompt (#) so you can just press Enter ant type something, you should get result. Regards, Nerijus
Re: Converting VMWare Workstation VM's to Qemu/KVM
2023-12-12 22:10, Sbob rašė: Can someone point me to the right way to convert VMWare Workstation VM's to Qemu/KVM/libvirt VM's Then I took these steps: 1) use qemu-img convert to convert the Dev-Fedora.vmdk file: # qemu-img convert -f vmdk -O qcow2 Dev-Fedora.vmdk Dev-Fedora.qcow2 this created the Dev-Fedora.qcow2 file 2) create a new VM with virt-manager and use the Dev-Fedora.qcow2 file as the disk image via the 'Import existing disk image' option 3) I start the new VM and I get 'No bootable devices found' There is virt-v2v tool, have you tried it? Regards, Nerijus
Re: Busybox wget problem with qemu
2021-11-11 14:51, Sukreet pal rašė: I have a armv7 processor virtualized with qemu and busybox. I am unable to use the wget command to download anything. I have searched endless possible solution but did not found any good solution. It is not a question for this list. Please ask in some busybox forum etc. Regards, Nerijus
Re: wget: note: TLS validation certificate not implemented
2021-09-22 14:26, Sukreet pal rašė: I have a arm v7 processor which I am emulating in qemu and I have made a root file system with busybox - 1.33.1. I am unable to use wget command to download anything on my virtual board but I can ping to any addresses (8.8.8.8) I am getting this error - How to get this TLS validation? It would be really helpful if someone could guide me on this. This question is not for this list. It is your root file system with busybox question - please ask there. (BTW, you can use http instead of https - it will work; or disable certificate verification in wget). Regards, Nerijus
Re: {Disarmed} Re: QEMU autosar question
Most probably somewhere at https://wiki.autosar.org/ 2021-07-14 15:26, Evan Meyer via rašė: Attached are the lines of code that could be of use before running the code, I then would run runqemu qemux86 core-image-apd-devel nographic qemuparams="-net socket,mcast=MailScanner warning: numerical links are often malicious: 224.244.224.245:30490 [1]" The terminal then prompts for a 192.168.7.2 login: and then asks for a password Does anybody know where I could obtain these Login/Passwords from?? On Tue, Jul 13, 2021 at 6:03 PM Peter Maydell wrote: On Tue, 13 Jul 2021 at 22:10, Evan Meyer via wrote: after running the command runqemu qemux86 core-image-apd-devel nographic qemuparams="-net socket,mcast=MailScanner warning: numerical links are often malicious: 224.244.224.245:30490 [1]" The terminal then prompts for a 192.168.7.2 login: and then asks for a password Does anybody know where I could obtain these Login/Passwords from?? I am following these https://wiki.autosar.org/doku.php?id=apd_user_guide:run:qemu and https://wiki.autosar.org/doku.php?id=apd_user_guide:build:general links. These links just give "permission denied" and ask for a login... You would do better asking somewhere specific to autosar (whatever that is), rather than here: this isn't QEMU related, it's just whatever your guest OS is set up to use for its default username and password. thanks -- PMM -- Evan Meyer Embedded Software Intern eme...@intrepidcs.com Intrepid Control Systems, Inc. 1850 Research Drive Troy MI 48083 USA PH: +1-586-731-7950 Fax: +1-586-731-2274 www.intrepidcs.com/ [2] Links: -- [1] http://224.244.224.245:30490 [2] http://www.intrepidcs.com/
Re: installing ubuntu on a virtual machine.. how to install qemu-efi-aarch64 ?
2021-04-30 14:22, c...@etri.re.kr wrote: Hi, list members, Trying to install ubuntu on a virtual machine, I found this page : https://futurewei-cloud.github.io/ARM-Datacenter/qemu/how-to-launch-aarch64-vm/ But I can't install qemu-efi-aarch64 package on ubuntu 16.04. (I was to upgrade my ubuntu 16.04 to 18.04 but there is a intel repos problem so I'm waiting) Can anybody give me an advice? Either upgrade OS or compile qemu-efi-aarch64 yourself. Regards, Nerijus
Re: Need Help with starting the qemu Emulator
2021-04-09 18:05, Jagannadha Bhamidipati rašė: I have raspberry pi 400 Installed OS - Ubuntu (Release 20.10 (Groovy Gorilla) 64-bit) Mate (MATE 1.24.1) Kernel Linux - Kernel Linux 5.8.0-1019-raspi aarch64 I am trying to install skype for linux version on the above for video call purpose. However, the software does not work. Hence the roundabout solution of emulating x86 on raspi thereby using skype. It will be very slow and unusable. Is there any alternative? web.skype.com in a browser or any other non skype client, available for Linux on ARM.
Re: How do I move my VM's from root to a user
It is a virt-manager (libvirt), not qemu question, please ask in the correct list. 2020-07-06 15:09, ToddAndMargo rašė: Hi All, Fedora 32, x64 qemu-kvm-4.2.0-7.fc32.x86_64 Since I have figure out how to run virt-manager as a user without having to hassle with the pol kit prompt, I would like to move my virtual machines out of root (or wherever the are) and into a particular user. I can start virt-manager as a user, but all my VM are missing. How to do migrate all my vm's from root to a user? Many thanks, -T
Re: [Qemu-discuss] qemu-system-aarch64 doesn't close after guest executes halt -f
2019-09-05 14:10, Shlomo Pongratz rašė: I've added the GONFIG_GPIO_PL061 (isn't it emulated on realview only?) and CONFIG_KEYBOARD_GPIO and also added The CONFIG_POWER_RESET_GPIO. But the QEMU still doesn't exit after halt -f. Don't you need to use -p as well?
Re: [Qemu-discuss] Issue related to mounting /dev/nbd0p1
Please try kpartx -a /dev/nbd0 2018-11-29 12:38, ramakanth varala rašė: thanks for the reply .. But i get below error when i do .. [root@localhost ~]# partx -a /dev/nbd0 HDIO_GETGEO: Inappropriate ioctl for device On Thu, Nov 29, 2018 at 4:04 PM Nerijus Baliūnas < neri...@users.sourceforge.net> wrote: 2018-11-29 12:10, ramakanth varala rašė: > [root@localhost ~]# mount /dev/nbd0p1 /home/test.1.3.debug/mnt/boot > mount: special device /dev/nbd0p1 does not exist partx -a /dev/nbd0
Re: [Qemu-discuss] Issue related to mounting /dev/nbd0p1
2018-11-29 12:10, ramakanth varala rašė: [root@localhost ~]# mount /dev/nbd0p1 /home/test.1.3.debug/mnt/boot mount: special device /dev/nbd0p1 does not exist partx -a /dev/nbd0
Re: [Qemu-discuss] High host CPU load and slow Windows 10 vm after upgrade to 1803
2018-07-31 13:35, utdilya rašė: Thank you. This is solution not working for me. Maybe, because of Centos7. I have in the log: 3707 : host doesn't support hyperv 'relaxed' feature 3707 : host doesn't support hyperv 'vapic' feature 3707 : host doesn't support hyperv 'spinlocks' feature /usr/libexec/qemu-kvm --version QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-156.el7_5.3) It's a very old version. Please use a version from centos-release-qemu-ev, currently qemu-kvm-ev-2.10.0-21.el7_5.4.1.x86_64: yum install centos-release-qemu-ev yum install qemu-kvm-ev
Re: [Qemu-discuss] kvm is busy
2018-05-11 12:29, Mahmood Naderan rašė: Hi How can I find why kvm is busy and who is using that? Although I have installed virtualbox, I want to use qemu too. qemu-system-x86_64: failed to initialize KVM: Device or resource busy [mahmood@rocks7 ~]$ lsmod | grep kvm kvm_amd69849 0 kvm 566604 1 kvm_amd irqbypass 13503 1 kvm Any idea? You have to rmmod virtualbox kernel modules. Regards, Nerijus
Re: [Qemu-discuss] Cannot opening qwoc2 image with qemu-nbd
2017-10-25 17:27, Pierre Couderc rašė: #modprobe nbd max_part=8 #qemu-nbd -c /dev/nbd0 /home/nous/qemu/xp/XPVM.qcow2 #mount /dev/nbd0p1 /media/a mount: special device /dev/nbd0p1 does not exist partx -a /dev/nbd0
Re: [Qemu-discuss] Wonky cursor problem
Virtual machine manager is part of libvirt (virt-manager), not Qemu. 2017-09-19 18:45, Gary Roach rašė: And what might that helper software be? The virtual machine manager window seems to be malfunctioning and it is part of qemu. With that, the main problem is still the wonky cursor. Gary R. On 09/19/2017 12:00 AM, Narcis Garcia wrote: You seem to not be talking about Qemu but about a helper software for Qemu. El 18/09/17 a les 22:32, Gary Roach ha escrit: Hi all, For the first time I have set up a qemu-kvm virtual machine on my Debian Linux system. I then loaded a Ubuntu guest. Everything works OK except the cursor. If I press the left key of my mouse and try to drag something on the screen the dragged object jumps all over the place. The cursor movement with out the mouse button is not as bad but still is erratic. If I hit ctl-alt to release the cursor the problem disappears. I hated the Gnome desktop so I ripped out Ubuntu and loaded Kubuntu. There was no change in the problem. I found one fix that said to do the following: go to virtual machine details > add hardware > input > EvTouch USB Graphics Tablet. this is supposed to fix the problem somehow. But there is a problem with this. When go to the virtual machine manager window and click on vm details the window closes back to the tray at the bottom of the screen. This problem is very annoying and has been around for a while. I want a solution where I don't have to write a whole bunch of code. Not very good at it. Please help Gary R.
Re: [Qemu-discuss] Windows 10 guest on qemu 2.9
2017-07-12 00:59, Sam Varshavchik rašė: FWIW, here's my VM config from libvirt: Offtopic - I'd suggest using virtio instead of IDE disks with drivers from https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/
Re: [Qemu-discuss] Network driver problem with the guest
2017-01-16 19:24, Mahmood Naderan rašė: Hi, A windows xp (x64) shows the network connection with the following command -devive e1000,netdev=host_files -netdev user,net=10.0.2.0/24,id=host_files,restrict=off,smb=/home/mahmood,smbserver=10.0.2.4 [1] However, with the same command, a windows xp (32bit) doesn't detect the driver and the driver shows a question mark in front of network adapter. Any way to fix that? Install Windows driver for the device? Regards, Nerijus
Re: [Qemu-discuss] Some not working devices in Windows 10 guest
Could you please do not top post? It makes very difficult to reply normally. Yes, the solution has typos - hiinterrupt.inf and bidinterrupt.inf should be hidinterrupt.inf. I did exactly what solution says and that got rid of device with exclamation mark. 2017-01-05 14:00, Xi Shen rašė: Hi Nerijus, i tried the trick, but it does not work. First I don't have the key mentioned. I have HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\hidinterrupt.inf_amd64_d01b78dcb2395f49 And under HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DeviceIds\ACPI\ACPI0010, I have "hidinterrupt.inf" Which looks close, but not the same. I made a copy of those values and tried to delete them, but I got an error. Maybe it is not the same issue? Regards, David On Thu, Jan 5, 2017 at 8:34 AM Xi Shen wrote: "Looks like MS is trying to extend their acpi impl. to support more recent ACPI specs (which is good thing) but they made a typo and ACPI0011 "Generic Buttons Device" became ACPI0010." A typo...seriously? Lol~ Thank you Nerijus. On Thu, Jan 5, 2017 at 1:17 AM Nerijus Baliunas wrote: On Wed, 4 Jan 2017 17:24:44 +0100 Vincenzo Romano wrote: I have installed all the drivers shipped with that ISO, plus the qemu agent, and spice guest tool. That "HID Button over Interrupt Driver" still has a exclamation mark on it. So far the guest system works well. I just wonder what could it be. I have exclamation mark too on Windows 10. There's an answer about it. Read previous messages. I found https://bugzilla.redhat.com/show_bug.cgi?id=1377155 It seems it is a Microsoft bug and there is info how to workaround it: According to MS the solution is to remove the device: 1. Uninstall the existed driver package for this device, if can check delete button, please check it too. 2. Download the PsTools from https://technet.microsoft.com/en-us/sysinternals/pstools.aspx 3. Unzip PsTools, and locate the folder of PsTools, then input in CMD (Run as Administrator): psexec -s -i regedit.exe 4. Delete subkey ACPI0010 under HKLM\SYSTEM\DriverDataBase\DriverPackage\hiinterrupt.inf_x86_instance ID>\Descriptors\ACPI0010 And delete subkey "bidinterrupt.inf" under HKLM\SYSTEM\DriverDataBase\DeviceIds\ACPI\ACPI0010 5. Rescan device to see the effect. Regards, Nerijus
Re: [Qemu-discuss] Is there any spec file to make qemu rpm
As I told already - in Fedora src.rpm package. Or this repo - https://fedoraproject.org/wiki/Virtualization_Preview_Repository 2016-08-22 05:30, lifuqiong rašė: Hi, I found that Centos has only qemu-kvm-ev's src.rpm , has no qemu 2.5's src.rpm or spec file. Where can I find that ? Thank you Mark -邮件原件- 发件人: Qemu-discuss [mailto:qemu-discuss-bounces+lifuqiong=cncloudsec@nongnu.org] 代表 Nerijus Baliūnas 发送时间: 2016年8月19日 15:49 收件人: qemu-discuss@nongnu.org 主题: Re: [Qemu-discuss] Is there any spec file to make qemu rpm 2016-08-19 09:33, lifuqiong rašė: I found there is no spec file in qemu, where can I find the spec file and build a rpm file? In Fedora or CentOS src.rpm package.
Re: [Qemu-discuss] Is there any spec file to make qemu rpm
2016-08-19 09:33, lifuqiong rašė: I found there is no spec file in qemu, where can I find the spec file and build a rpm file? In Fedora or CentOS src.rpm package.
Re: [Qemu-discuss] openstack with kvm CPU usage issue
2016-08-17 19:46, Laurentiu Soica rašė: The baremetal and compute are both running CentOS 7 and on the baremetal I've enabled nested KVM feature. Kernel is 3.10.0-327.22.2.el7.x86_64 qemu-kvm is 1.5.3-105.el7_2.7 It is quite old. I would use a newer one, for example, qemu-kvm-ev from https://lists.centos.org/pipermail/centos-announce/2015-October/021445.html
Re: [Qemu-discuss] qemu hangs
2016-08-16 21:49, Peter Maydell rašė: It is nvidia binary driver. Running LD_PRELOAD=/usr/lib64/libGL.so.1 Is there something that can be done/workarounded in qemu or should I just patch libvirtd systemd unit file to include LD_PRELOAD=/usr/lib64/libGL.so.1? QEMU's just doing fork() and fork is supposed to work. If this driver is supplied by Fedora I would suggest reporting the bug to them and they can decide whether they want to get the driver fixed or work around it in libvirt. Otherwise if I were you I would uninstall the binary blob :-) It is from rpmfusion, not Fedora. Unfortunately I cannot uninstall it because nouveau does not work on this notebook and I didn't have time to investigate.
Re: [Qemu-discuss] qemu hangs
2016-08-16 21:21, Nerijus Baliūnas rašė: I've tried gdb without daemonize on a working PC and got the same backtrace. So it seems it is daemonize code which has a problem. Debugging the child revealed the problem: # gdb /usr/bin/qemu-system-alpha (gdb) set follow-fork-mode child (gdb) r -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize [New Thread 0x7fffc9708700 (LWP 16179)] [New process 16180] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". ^C Thread 2.1 "qemu-system-alp" received signal SIGINT, Interrupt. [Switching to Thread 0x77eb9fc0 (LWP 16180)] base::internal::SpinLockDelay (w=0x7fffdbf1f280 , value=2, loop=) at src/base/spinlock_linux-inl.h:88 88 errno = save_errno; (gdb) bt #0 0x7fffdbce9e47 in base::internal::SpinLockDelay(int volatile*, int, int) (w=0x7fffdbf1f280 , value=2, loop=) at src/base/spinlock_linux-inl.h:88 #1 0x7fffdbce9d64 in SpinLock::SlowLock() (this=0x7fffdbf1f280 ) at src/base/spinlock.cc:119 #2 0x7fffdbcdacba in tcmalloc::CentralFreeList::RemoveRange(void**, void**, int) (this=0x7fffdbf1f280 ) at src/base/spinlock.h:71 #3 0x7fffdbcdacba in tcmalloc::CentralFreeList::RemoveRange(void**, void**, int) (this=0x7fffdbf1f280 , start=start@entry=0x7fffdd38, end=end@entry=0x7fffdd40, N=2) at src/central_freelist.cc:248 #4 0x7fffdbcddcda in tcmalloc::ThreadCache::FetchFromCentralCache(unsigned long, unsigned long) (this=this@entry=0x564ae0c0, cl=, byte_size=byte_size@entry=253952) at src/thread_cache.cc:126 #5 0x7fffdbcedf03 in tc_calloc(size_t, size_t) (cl=, size=, this=) at src/thread_cache.h:368 #6 0x7fffdbcedf03 in tc_calloc(size_t, size_t) (size=, heap=) at src/tcmalloc.cc:1193 #7 0x7fffdbcedf03 in tc_calloc(size_t, size_t) (size=) at src/tcmalloc.cc:1208 #8 0x7fffdbcedf03 in tc_calloc(size_t, size_t) (size=) at src/tcmalloc.cc:1219 #9 0x7fffdbcedf03 in tc_calloc(size_t, size_t) (elem_size=out>, n=) at src/tcmalloc.cc:1232 #10 0x7fffdbcedf03 in tc_calloc(size_t, size_t) (n=, elem_size=) at src/tcmalloc.cc:1645 #11 0x7fffd162778c in () at /usr/lib64/nvidia-304xx/libGL.so.1 #12 0x7fffcb4440cf in () at /usr/lib64/nvidia-304xx/libnvidia-glcore.so.304.131 #13 0x7fffd160220d in () at /usr/lib64/nvidia-304xx/libGL.so.1 #14 0x7fffd160958f in () at /usr/lib64/nvidia-304xx/libGL.so.1 #15 0x7fffd16096c4 in () at /usr/lib64/nvidia-304xx/libGL.so.1 #16 0x7fffd1609e4f in () at /usr/lib64/nvidia-304xx/libGL.so.1 #17 0x7fffda8b9a0e in __libc_fork () at ../sysdeps/nptl/fork.c:211 #18 0x557d6324 in os_daemonize () at /usr/src/debug/qemu-2.7.0-rc2/os-posix.c:216 #19 0x5573ac9e in main (argc=, argv=, envp=) at /usr/src/debug/qemu-2.7.0-rc2/vl.c:3989 It is nvidia binary driver. Running LD_PRELOAD=/usr/lib64/libGL.so.1 /usr/bin/qemu-system-alpha -S... works OK. Is there something that can be done/workarounded in qemu or should I just patch libvirtd systemd unit file to include LD_PRELOAD=/usr/lib64/libGL.so.1?
Re: [Qemu-discuss] qemu hangs
2016-08-16 20:58, Nerijus Baliūnas rašė: Does the same binary work on one PC and not on the other? (not just the same command). Yes, both OS (Fedora 24) and binaries are identical. On one PC it works, on another - does not. I've tried gdb without daemonize on a working PC and got the same backtrace. So it seems it is daemonize code which has a problem.
Re: [Qemu-discuss] qemu hangs
2016-08-16 20:53, Peter Maydell rašė: Has it actually hung, or is it just waiting for you to talk QMP protocol to it on the socket ? Probably hung, because the same command launches on another PC, process is running and the shell returns. Even with -daemonize not supplied? It shouldn't return you to the shell prompt if you don't pass that option! With -daemonize. It does not return to the shell without -daemonize of course. Yes, but as I wrote above, the command runs on another PC even without libvirt. So most probably something wrong with qemu. Does the same binary work on one PC and not on the other? (not just the same command). Yes, both OS (Fedora 24) and binaries are identical. On one PC it works, on another - does not.
Re: [Qemu-discuss] qemu hangs
2016-08-16 20:26, Peter Maydell rašė: Yes, it still hangs: # gdb /usr/bin/qemu-system-alpha (gdb) r -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile Starting program: /usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffc9708700 (LWP 13010)] ^C Has it actually hung, or is it just waiting for you to talk QMP protocol to it on the socket ? Probably hung, because the same command launches on another PC, process is running and the shell returns. I think what is happening here is that libvirt starts these QEMU processes to query them for what they support. What should happen is that QEMU is started, libvirt talks QMP protocol to them and then stops the QEMU processes when it's found out the answers to its questions. I think we need to somehow get a log of what libvirt is doing on the QMP socket to find out whether this bug is in QEMU (eg libvirt asks it to do something and it hangs) or in libvirt (eg libvirt doesn't tell QEMU to quit). Yes, but as I wrote above, the command runs on another PC even without libvirt. So most probably something wrong with qemu. The PC with a problem is quite old AMD Athlon 64 X2 Dual-Core Processor TK-55.
Re: [Qemu-discuss] qemu hangs
2016-08-16 19:58, Peter Maydell rašė: This is the outer process waiting for the child process to tell it it's got started in os_daemonize(). Does QEMU still hang if you don't pass it -daemonize ? If so, then it will be easier to debug that. Yes, it still hangs: # gdb /usr/bin/qemu-system-alpha (gdb) r -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile Starting program: /usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffc9708700 (LWP 13010)] ^C Thread 1 "qemu-system-alp" received signal SIGINT, Interrupt. 0x7fffda8e83f1 in __GI_ppoll (fds=0x56cfb000, nfds=5, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 50result = SYSCALL_CANCEL (ppoll, fds, nfds, timeout, sigmask, _NSIG / 8); (gdb) bt #0 0x7fffda8e83f1 in __GI_ppoll (fds=0x56cfb000, nfds=5, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x559455bb in qemu_poll_ns (__ss=0x0, __timeout=0x0, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 0x559455bb in qemu_poll_ns (fds=, nfds=out>, timeout=timeout@entry=-1) at /usr/src/debug/qemu-2.7.0-rc2/qemu-timer.c:313 #3 0x55944fba in main_loop_wait (timeout=-1) at /usr/src/debug/qemu-2.7.0-rc2/main-loop.c:252 #4 0x55944fba in main_loop_wait (nonblocking=) at /usr/src/debug/qemu-2.7.0-rc2/main-loop.c:506 #5 0x5573be65 in main () at /usr/src/debug/qemu-2.7.0-rc2/vl.c:1908 #6 0x5573be65 in main (argc=, argv=, envp=) at /usr/src/debug/qemu-2.7.0-rc2/vl.c:4603
Re: [Qemu-discuss] qemu hangs
I tried to debug with gdb: # gdb /usr/bin/qemu-system-alpha Reading symbols from /usr/bin/qemu-system-alpha...Reading symbols from /usr/lib/debug/usr/bin/qemu-system-alpha.debug...done. done. (gdb) r -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize Starting program: /usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffc9708700 (LWP 12596)] Detaching after fork from child process 12597. ^C Thread 1 "qemu-system-alp" received signal SIGINT, Interrupt. 0x7fffdabc2dad in read () at ../sysdeps/unix/syscall-template.S:84 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) (gdb) bt #0 0x7fffdabc2dad in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x557d63d3 in os_daemonize (__nbytes=1, __buf=0x7fffdfdf, __fd=) at /usr/include/bits/unistd.h:44 #2 0x557d63d3 in os_daemonize () at /usr/src/debug/qemu-2.7.0-rc2/os-posix.c:224 #3 0x5573ac9e in main (argc=, argv=, envp=) at /usr/src/debug/qemu-2.7.0-rc2/vl.c:3989 2016-08-16 12:45, Nerijus Baliūnas rašė: Hello, qemu 2.7.0-0.1.rc2.fc24, but the same happened with 2.6.0. I start systemctl start libvirtd, and systemctl status libvirtd shows: Active: active (running) since Pr 2016-08-15 22:41:43 EEST; 30s ago CGroup: /system.slice/libvirtd.service ├─2907 /usr/sbin/libvirtd ├─2932 /usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib └─2934 /usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib These processes (/usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize) hang indefinitely. The same happens if I run it manually. Disabling selinux does not help. If I kill qemu-system-alpha, qemu-system-arm is started and so on. I cannot connect to libvirt with virt-manager. Any ideas why qemu hangs? Regards, Nerijus
[Qemu-discuss] qemu hangs
Hello, qemu 2.7.0-0.1.rc2.fc24, but the same happened with 2.6.0. I start systemctl start libvirtd, and systemctl status libvirtd shows: Active: active (running) since Pr 2016-08-15 22:41:43 EEST; 30s ago CGroup: /system.slice/libvirtd.service ├─2907 /usr/sbin/libvirtd ├─2932 /usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib └─2934 /usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib These processes (/usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize) hang indefinitely. The same happens if I run it manually. Disabling selinux does not help. If I kill qemu-system-alpha, qemu-system-arm is started and so on. I cannot connect to libvirt with virt-manager. Any ideas why qemu hangs? Regards, Nerijus
