qemu-docker icon indicating copy to clipboard operation
qemu-docker copied to clipboard

A docker container for running x86_64 virtual machines using qemu

Results 7 qemu-docker issues
Sort by recently updated
recently updated
newest added

Failed to send flush request: Operation not permitted RTNETLINK answers: Operation not permitted Error: argument "qemubr0" is wrong: Device does not exist RTNETLINK answers: Operation not permitted Cannot find device...

![image](https://user-images.githubusercontent.com/44870751/233371241-fc86fe90-601d-47ae-976e-262e3022c01e.png) run.sh: ![image](https://user-images.githubusercontent.com/44870751/233371307-ec3e17d3-5c17-49ee-becc-2d9eca240b46.png)

When running the container, the log of my host OS gets spammed with this error: `kernel: qemubr0: received packet on eth0 with own address as source address (addr:03:42:ab:11:00:02, vlan:0)` From...

I always get this error: ``` if len(addr['addr_info']) != 1: raise ValueError('only exactly one address on dev is supported') ``` Because I have an IPv6 interface in Docker. When disabling...

When the container is stopped via Docker, QEMU sends a SIGTERM signal to the Guest OS: `qemu-system-x86_64: terminating on signal 15` And immediately terminates the machine. It would be much...

is it correct that only one instance is allowed? Since its qemubr0 is hardcoded? I tried starting 2 instances, but the second one seemed to be getting the ip address...

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [docker/build-push-action](https://togithub.com/docker/build-push-action) | action | major | `v5` -> `v6` | --- ### Release...