qemu,virtualbox, host bridge => vbox vm fails to start

[promeneur]

openSuse 15.2
qemu 5.2.0
virtualbox 6.1.22

The host network : a bridge br0 with eth0 as slave.

The qemu vm uses br0 without no problem.

The virtualbox vm fails to start using NAT or "bridge with eth0"

If I replace br0 by just eth0 then the virtualbox vm does not fail to start.

I need br0 for the qemu vm.

What to do ?

[promeneur]

Here is the text of the error window:

A critical error occurred while the virtual machine was running and the virtual machine was shut down.
For help you can go to the Community section of virtualbox site or view your support contract. Post the VBox.log log file and the VBox.png image file that you will find in the / home / roubach / VirtualBox VMs / openSuse 15.3 / Logs folder, along with a description of what you were doing when the error occurred. produced. Normally you can access these logs by choosing View History from the Machine menu in the VirtualBox main window.
Click OK to shut down the machine, or click Skip to leave it as is for debugging. Debugging requires specialized knowledge and tools, you are advised to choose OK.

[promeneur]

How to search the problem in Vbox.log ?

[mpack]

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

[promeneur]

@mpack

How to attach a file ?

[promeneur]

Here is the vbox.log

[promeneur]

nmcli con show
NAME UUID TYPE DEVICE
bridge-br0 3543c198-a4b4-413a-ad8a-3bcc1441e309 bridge br0
bridge-br0-eth0-slave bd420019-ff2d-41e6-8919-6c5a7ab57ead ethernet eth0
tap0 82b64e11-bd83-44c0-97fa-35b7d934a7c1 tun tap0

tap0 is a connection created when launching qemu vm.

[promeneur]

If there is no qemu vm launched then vbox vm does not fail to start !

[promeneur]

I assume there is a problem about sharing eth0.

[fth0]

If there is no qemu vm launched then vbox vm does not fail to start !

Hardware virtualization (VT-X, AMD-V) usually cannot be shared by multiple hypervisors (e.g. VirtualBox, QEMU/KVM). Depending on what you want to do inside the QEMU VM, you could try using QEMU without KVM.

[mpack]

I would not expect bridging to a br0 to work, but happily that doesn't seem to be what you've done. Bridging to eth0 should be fine, though of course you'll only get a connection if eth0 is connected and something is there to hand out local IP addresses.

You have over-allocated host CPU cores (you left none for the host - your CPU has 4 cores, not 8), otherwise I'm not seeing much wrong with this config.

The log switches to an error dump for no obvious reason, with VERR_INVALID_STATE. Are you running this VirtualBox VM inside another hypervisor?

[promeneur]

@fth0

Hello

Thanks

i use a guest android-x86 to be able to use whatsapp on my desktop PC openSuse.

i use "qemu-kvm -enable-kvm"

I read that if i don't use "-enable-kvm" then it is slower.

[promeneur]

@mpack

for vbox vm i don't use br0. I use "bridge" and "eth0"

[promeneur]

@fth0

if i use just "qemu-kvm" thus without -"-enable-kvm" ton invoke the qemu vm then vbov vm keeps on failing to start.

I made this experiment:

i launch first the vbox vm then no problem.
then
i launch the qemu vm then immediately i get the same error window at the vbox vm and the vbox vm is a state we can't use it.

[promeneur]

i confirm we can't use qemu and virtualbox.

see

https://askubuntu.com/questions/413511/ ... each-other