Is there any 8086 emulator (free or paid) for Fedora 17? I am learning assembly language using AT&T style.

QEMU documentation describes the options -nographic vs -display none. However I'm confused by them. What exactly they are supposed to do and which is the difference ?

I'm running Cisco IOS-XRv-9000 sw on a qemu/kvm VM using Virsh on my linux Ubuntu system root@eve-ng62:/tmp# virsh list Id Name State ------------------------------------ 17 IOS-XRv-9000-carlo running root@eve-ng62:/tmp# From qemu monitor I turned on logging on cpu registers: (qemu) info version 6.2.0Debian 1:6.2+dfsg-2ubuntu6.26 (qemu) log cpu (qemu) logfile /tmp/qemu.log However I can't see any message stored in log file (/tmp/qemu.log). It basically remains empty: root@eve-ng62:/tmp# ll qemu.log -rw-rw-r-- 1 libvirt-qemu kvm 0 May 2 11:21 qemu.log root@eve-ng62:/tmp# Which could be the problem ?

I'm working with a Bluetooth LE device in my project and I want to test bluetooth-related host code without having an actual Bluetooth device. Currently, I have a Linux machine with BT dongle as a host and BTLE sensor. On Linux machine I'm running a Python code which communicates with BTLE sensor using library called bluepy . And the question is: Is it possible to create a simulated HCI interface in Linux, so that bluepy will think it communicates with a real BT module on my laptop, but in reality - that module will be fully virtual and it will allow Python code to communicate with virtual BTLE sensor that I written. I already did something similar with simulating RS232 device. Back then I created pseudo TTY to represent RS232 device and my simulation code listened to commands from main code and responded exactly in the same way as real device responded. So I want to have similar solution with Bluetooth sensor. How this could be achieved? **Update:** Seems like bluez gives you a tool called "btvirt". With it you can create a pair (or more) of virtual hci interfaces. And also seems like this tool isn't quite popular as I can't find any documentation on it other than source code itself in github repo .

Got a steamdeck recently and have been setting it up for emulation. It's running SteamOS 3.0 which, from what I could find, is based on Arch Linux. I need two versions of PPSSPP. The latest build for most of my library and v1.10.3 specifically to play Phantasy Star Portable 2 Infinity over the internet with friends. I'm able to downgrade the currently installed flatpak to this version but now I've hit a roadblock trying to install the latest build without overwriting the other. Having never used Linux before in my life...I'm lost.

In Debian11/KDE with Wayland I can't launch games anymore with the Dolphin emulator. Created a bug report with some more details here . Don't know if that's due to building a newer version of Dolphin than the version with which launching games worked on this machine, or due to switching from X11 to Wayland. However, because for a while launching games with Dolphin still worked on it but with Lutris it didn't , I think it must be due to a newer version of Dolphin. If there's an easy way to install the version from the Debian repos without parallel to the built version, I'd try if it works with that version. I installed mesa-vulkan-drivers and then in Dolphin changed "OpenGL" to "Vulkan" in Options->Graphics Settings->Backend. When I try to launch a ROM game that used to work before, I get an error message saying Failed to create Vulkan surface. and when I close it also Failed to initialize video backend!. If I have OpenGL set as backend I only get the second error. I don't have a graphics card but the game was working fine with the same hardware earlier. I'm using i915 graphics drivers. The only output in the console is: MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0. Has anybody solved this issue or a suggestion what I should try?

So I'm trying to get Qemu to use more cores on my Raspberry Pi 4b due to the poor performance on emulating Windows 10, but it seems to be using one of the cores, but not any others. I did use the -smp option, but that didn't work. I've tried solutions on the internet, but nothing is working. The same thing is happening to Windows 7 too when I attempt to emulate it. What am I missing? Is there some config I'm missing, or is it just impossible for the Raspberry Pi to do anything like that? I am on the latest version of QEMU by the way (Referencing Answer here ) Command to run emulator:

qemu-system-x86_64 -M pc -m 4G -cpu qemu64 -smp sockets=1,cores=4,threads=4 -vga cirrus -device qemu-xhci -device usb-kbd -device usb-tablet -nic user,model=virtio-net-pci -vnc 0.0.0.0:2,websocket -drive file=meep.vhd,if=virtio,cache=writeback

I'm using Gentoo Linux and have Python 3.10 and 3.11 installed. I have a registered version of Crossover 20.0.4 that I'm trying to install using the `.bin` installer and I hit this error and installation fails:

Traceback (most recent call last):
  File "/home/dev/Software/cxoffice/lib/python/cxconfig.py", line 12, in 
    from collections import MutableMapping
ImportError: cannot import name 'MutableMapping' from 'collections' (/usr/lib/python3.11/collections/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/dev/Software/cxoffice/bin/cxtie", line 135, in 
    import cxtiemain
  File "/home/dev/Software/cxoffice/lib/python/cxtiemain.py", line 6, in 
    import c4parser
  File "/home/dev/Software/cxoffice/lib/python/c4parser.py", line 10, in 
    import cxproduct
  File "/home/dev/Software/cxoffice/lib/python/cxproduct.py", line 7, in 
    import cxconfig
  File "/home/dev/Software/cxoffice/lib/python/cxconfig.py", line 15, in 
    from UserDict import DictMixin as MutableMapping
ModuleNotFoundError: No module named 'UserDict'

I'm not the only one who seems to have had this issue: There's this thread: https://www.codeweavers.com/support/forums/general/?ft=25;t=26;msg=267771 and this Ask Ubuntu question: https://askubuntu.com/questions/1437185/cant-install-packages-after-trying-to-install-deb-file How do I get it to install or do I have to upgrade?

Am currently trying to automate running emacs on a Distrobox container (the Docker container is silex/emacs:29.2-alpine, although I've also tried silex/emacs:29.2 which uses a Debian image), and am getting the error emacs: Could not open file: /dev/tty. Here's what I'm doing:

distrobox create --name test --image silex/emacs:29.2-alpine --home /home/dbhome
distrobox enter test -nw -- /nix/store/emacs/bin/emacs-29.2

Which produces the mentioned error. However, running first distrobox enter test -nw, and then running /nix/store/emacs/bin/emacs-29.2 does successfully start emacs within the distrobox container. The issue is, I want to automate this emacs startup, so I need to find a way that would allow me to startup the emacs from the container from a sequence of commands ran outside the container. Anyone know what my be causing emacs: Could not open file: /dev/tty in this way? The reason I'm using Distrobox instead of just a regular container is that I eventually want to use Distrobox's ootb support for connecting to the host's X11 sockets. EDIT: strace confirms the error is -1 ENXIO (No such device or address) EDIT2: The problem subsides if we replace a bit of the docker exec command ran by distrobox enter. The docker exec command ends with CONTAINERNAME su USERNAME -c COMMAND; the issue gets fixed when we use CONTAINERNAME COMMAND directly.

Configuration: - MacOS arm64 M1 Apple Silicon as host - Live USB with Ubuntu 20.04 amd64 within a squashfs filesystem as guest - QEMU emulator on the host OS I want to strip the OS out the squashfs and boot it on a emulated amd64 virtual machine on my mac. I managed to extract the Ubuntu OS. I mounted the squashfs an copied the content into an img file I created using dd. I copied the image on the mac but when I try to boot the VM says "No bootable device". Here are the commands I used, from a supporting Linux virtual machine mount -t squashfs -o loop /path/to/filesystem.squashfs /sqshfs/mount/point I created an empty image and made an ext4 fs dd if=/dev/zeroes of=image.img bs=1M count=15000 mkfs.ext4 image.img mounted it and copied the files mount -t auto image.img /img/mount/point cp -r /sqshfs/mount/point/* /img/mount/point now on the image I have this folders total 112 drwxr-xr-x 2 root root 4096 Jan 10 02:37 bin drwxr-xr-x 3 root root 4096 Jan 10 02:37 boot drwxr-xr-x 4 root root 4096 Jan 10 02:37 dev drwxr-xr-x 147 root root 12288 Jan 10 02:37 etc drwxr-xr-x 3 root root 4096 Jan 10 02:37 home lrwxrwxrwx 1 root root 33 Jan 10 02:37 initrd.img -> boot/initrd.img-5.4.0-150-generic lrwxrwxrwx 1 root root 33 Jan 10 02:37 initrd.img.old -> boot/initrd.img-5.4.0-148-generic drwxr-xr-x 23 root root 4096 Jan 10 02:37 lib drwxr-xr-x 2 root root 4096 Jan 10 02:37 lib64 drwx------ 2 root root 16384 Jan 10 02:36 lost+found drwxr-xr-x 2 root root 4096 Jan 10 02:37 media drwxr-xr-x 2 root root 4096 Jan 10 02:37 mnt drwxr-xr-x 5 root root 4096 Jan 10 02:37 opt drwxr-xr-x 2 root root 4096 Jan 10 02:37 proc drwx------ 3 root root 4096 Jan 10 02:37 root drwxr-xr-x 2 root root 4096 Jan 10 02:37 run drwxr-xr-x 2 root root 12288 Jan 10 02:37 sbin drwxr-xr-x 2 root root 4096 Jan 10 02:37 snap drwxr-xr-x 2 root root 4096 Jan 10 02:37 srv drwxr-xr-x 2 root root 4096 Jan 10 02:37 sys drwxr-xr-t 2 root root 4096 Jan 10 02:37 tmp drwxr-xr-x 11 root root 4096 Jan 10 02:38 usr drwxr-xr-x 15 root root 4096 Jan 10 02:38 var lrwxrwxrwx 1 root root 30 Jan 10 02:38 vmlinuz -> boot/vmlinuz-5.4.0-150-generic lrwxrwxrwx 1 root root 30 Jan 10 02:38 vmlinuz.old -> boot/vmlinuz-5.4.0-148-generic converted the img in qcow2 qemu-img convert -f raw -O qcow2 -c image.img image.qcow2 and configured QEMU as follows qemu-system-x86_64 \ -name TEST \ -cpu qemu64-v1 \ -smp cpus=4,sockets=1,cores=4,threads=1 \ -machine pc-q35-7.2,vmport=off,i8042=off,hpet=off \ -accel tcg,thread=multi,tb-size=1024 \ -m 4096 \ -drive file=/Users/steve/VMs/image.qcow2 \ -boot menu=on When I try to boot the VM says "No bootable device". I'm very new abt QEMU and I know this configuration miss something but it should at least try to boot the kernel. GUID?

I am just a newbie that is trying to learn. I can't see anything in the OLED display (ssd0303). I am just using this demo: https://www.freertos.org/portlm3s811keil.html as you can see it says that: > The print task is the only task permitted to access the LCD - thus > ensuring mutual exclusion and consistent access to the resource. Other > tasks do not access the LCD directly, but instead send the text they > wish to display to the print task. The print task spends most of its > time blocked - only waking when a message is queued for display. but actually, if I compile using make and running using qemu-system-arm -M lm3s811evb -kernel gcc/RTOSDemo.bin I can only see that black screen. Why? Is there something I am not considering? It should work out of the box, since it's also writen in the official doc that I mentioned. So why I see black screen? Probably there is something I am not considering because I am a newbie

I have successfully run an old UNix SVR4 guest on Slackware 15.0 host. This is the config for unix "vm" [General] vid_renderer = qt_opengl3 confirm_save = 0 confirm_reset = 0 language = en-US confirm_exit = 0 vid_resize = 1 [Machine] machine = p5sp4 cpu_family = pentium_p5 cpu_speed = 66666666 cpu_multi = 1 cpu_use_dynarec = 1 time_sync = local fpu_type = internal mem_size = 16384 [Video] gfxcard = vga [Input devices] mouse_type = ltserial [Sound] fm_driver = nuked midi_device = system_midi midi_in_device = midi_in [Network] net_01_link = 0 net_02_link = 0 net_03_link = 0 net_04_link = 0 net_01_net_type = pcap net_01_host_device = br0 net_01_card = wd8003e [Storage controllers] hdc = internal cassette_mode = load [Ports (COM & LPT)] lpt1_device = text_prt [Hard disks] hdd_01_parameters = 63, 16, 1013, 0, ide hdd_01_fn = unix.img hdd_01_speed = ramdisk hdd_01_ide_channel = 0:0 [Floppy and CD-ROM drives] fdd_01_type = 525_2hd cdrom_01_parameters = 1, atapi cdrom_01_ide_channel = 0:1 [Western Digital WD8003E #1] mac = **:**:** base = 0300 irq = 2 ram_addr = D8000 The machine start and recognize the old WD card I can ping from internal to internal (sic!) but not from host to guest and vice-versa. This is the network situation, no interface appear sudo brctl show bridge name bridge id STP enabled interfaces br0 **************** yes eth0 sudo ip link show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc pfifo_fast master br0 state UP mode DEFAULT group default qlen 1000 link/ether ************ brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether **:**:**:**:**:** brd ff:ff:ff:ff:ff:ff I have tried to bind to.. br0 (which is a bridge with eth0..) FAIL eth0 FAIL virbr0 (an adapter created by libvirt) FAIL

I'm facing a challenge with my Raspberry Pi 4 and software setup. The Pi connects to my server to download a weekly-updated database. The problem arises from the Mass Storage Gadget's CD emulator, which limits storage to 2.3 GB, while my database is almost 6 GB (using ISO file). I believe i've come across this issue: "That means some restrictions, especially a hardcoded limit on the size of a backing (.iso) file. In case the file size exceeds 1152000 2KiB blocks (approx. 2.36GB / 2.2GiB), the driver will complain "file too big" and limit the usable range (sector count). If the filesystem driver on the USB host requests any sector beyond that, it will encounter I/O errors ("attempt to access beyond end of device")." from https://linux-sunxi.org/USB_Gadget/Mass_storage Some potential fixes i found: - https://lkml.org/lkml/2015/3/7/388 - https://patchwork.ozlabs.org/project/openbmc/patch/20210626211820.107310-5-i.kononenko@yadro.com/ Has anyone faced this issue and has any idea how to proceed?

The Google Android emulator requires execheap permissions, otherwise it segfaults when SElinux is in enforcing mode. For those who are not familiar with the Android emulator: It uses a forked version of qemu. The two easy solutions are - setenforce 0 - setsebool -P allow_execheap 1 Obviously, those are far from ideal from a security perspective. Also, hoping for a patch so the emulator does not need execheap might take a very long time. In my audit logs, I found that the offending process was indeed qemu-system-x86_64-headless, however, the bundled binary and not the "original" one. Therefore, the labels differ.

semanage fcontext --list | grep qemu-kvm
/usr/bin/qemu-kvm                                  regular file       system_u:object_r:qemu_exec_t:s0

ls -laZ /root/android_sdk/emulator/qemu/linux-x86_64
-rwxr-xr-x. 1 root root unconfined_u:object_r:user_home_t:s0 31174856 Aug  1 16:32 qemu-system-x86_64-headless

Other reports where execheap was the issue pointed to GPU drivers. The machine I'm running on has neither a GPU nor iGPU. The Vulkan device used is Swiftshader. Unfortunately, I am completely new to SElinux. - Do I need to write a custom policy for the emulator? How? And how do I run it with said policy? - Is labeling the executable(s) enough? How do I do that? - How else can I make it work without enabling execheap globally or setting SElinux to permissive mode?

**Does anyone know how to get libx86emu x86emu-demo to work?** https://github.com/wfeldt/libx86emu Test.bin 00000000 55 8B EC 51 C7 45 FC 00 00 00 00 8B 45 FC 50 E8 00000010 09 00 00 00 83 C4 04 33 C0 8B E5 5D C3 55 8B EC 00000020 B8 01 00 00 00 5D C3 00: 55 push ebp 01: 8b ec mov ebp,esp 03: 51 push ecx 04: c7 45 fc 00 00 00 00 mov DWORD PTR [ebp-0x4],0x0 0b: 8b 45 fc mov eax,DWORD PTR [ebp-0x4] 0e: 50 push eax 0f: e8 09 00 00 00 call 0x1d 14: 83 c4 04 add esp,0x4 17: 33 c0 xor eax,eax 19: 8b e5 mov esp,ebp 1b: 5d pop ebp 1c: c3 ret 1d: 55 push ebp 1e: 8b ec mov ebp,esp 20: b8 01 00 00 00 mov eax,0x1 25: 5d pop ebp 26: c3 ret ./x86emu-demo -l 0 -s 0 Test.obj I need to be able to execute x86 machine code similar to the above sample. libx86emu decodes and executes the first three instructions then decodes the fourth instruction incorrectly. I only need to be able to emulate 32-bit x86, I don't need any OS support. Only about half of the libx86emu x86test regression tests pass.

I have a kernel module (ko) file that is designed for the aarch64 architecture. I'm currently attempting to use qemu on a non-aarch64 system to utilize this aarch64 kernel module for mounting a specific file system within the non-aarch64 system. I'm curious if it's possible to load and use this module using qemu?

I am trying to boot fedora vm on Linux Test Pc from qemu. It actually shows the temporary password for first login. But when I try that password it is saying Login is Incorrect. I don't know why the password is showing incorrect although I entered the correct password. I downloaded fedora cloud image from https://mirror.genesisadaptive.com/fedora/linux/releases/36/Cloud/x86_64/images/ The command I used is:

virt-install --connect qemu:///system --name CXL-Test --memory 4096 --cpu host --vcpus 4 --os-variant fedora35 --import --graphics none --disk /var/lib/libvirt/images/CXL-Test.qcow2,format=qcow2,bus=virtio --cloud-init

The tutorial I am following is: https://stevescargall.com/blog/2022/01/20/how-to-emulate-cxl-devices-using-kvm-and-qemu/#configure-the-guest-os-using-a-cloud-init-boot-strap-image The console shows:

Defaulting to --cloud-init root-password-generate=yes,disable=yes

Starting install...

Password for first root login is: gjxGCzxrSzkknlu4

Creating domain... | 0 B 00:00:00

Running text console command: virsh --connect qemu:///system console CXL-Test

Connected to domain 'CXL-Test'

Fedora Linux 36 (Cloud Edition)

Kernel 5.17.5-300.fc36.x86_64 on an x86_64 (ttyS0)

fedora login: root

Password: Login incorrect

As I understand emulators (in a simple way), they do translate or substitute the function calls of a program using functions of system X into functions used by system Y in which the program is being run onto. Wine project claims that Wine Is Not an Emulator, because: > Instead of simulating internal Windows logic like a virtual machine or > emulator, Wine translates Windows API calls into POSIX calls > on-the-fly, eliminating the performance and memory penalties of other > methods and allowing you to cleanly integrate Windows applications > into your desktop. Well, how emulators and virtual machines simulate internal Windows logic on host non-Windows systems? Isn't that by translating Windows system calls into the host's own respective calls? Is the difference between emulators and non-emulators (like Wine) is that emulators emulate a whole operating system then the application uses that system APIs without knowing that it is talking to an emulator, while non-emulators directly translates application's calls into the host's (and the application also may not know it)? Is the extra level of indirection is the only different between emulators and Wine?

I'm writing a program for controlling USB storage device connections (this is a classic subject). All it's ok with my program, but now, I want to write some tests. So in order to do that, I realized I'll need some way of simulate USB connections. And not only the connections, I need to be able to set the device properties: capacity, format, etc...

I'm currently running the Asahi (Linux on the M1 Macbook pro) beta with Arch Linux, but would like to run some x86/x86_64 binaries, and am wondering the best way to do that. I saw [this](https://unix.stackexchange.com/questions/577953/is-it-possible-to-run-x86-executable-on-arm) thread discussing how to do it on Debian, but couldn't get any success. Here are some various things I've tried: * Installing [qemu](https://wiki.archlinux.org/title/QEMU) for emulation (package can't satisfy dependencies) * Installing [FEX-Emu](https://github.com/FEX-Emu/FEX) (after I installed it from the AUR, I had no fex command) * Installing [Bochs](https://archlinux.org/packages/community/x86_64/bochs/) from the Community repository, but it gives error: target not found: bochs * Installing [box86](https://aur.archlinux.org/packages/box86) from the AUR, but it fails to build since it doesn't seem compatible with aarch hosts Anyone have any suggestions? I'm just looking for what's easiest to get up and running.