Virtualbox stopped working after a windows update

Running into an issue I don’t understand.

I am getting a warning during win10, from openSUSE that my root partition is running out of space.

What am I doing wrong, and how do I clean this up ? :slight_smile:

Hi
You need to ensure space on another area for /var/lib/libvirt specifically the images directory. I use a separate XFS partition for libvirt and docker…

A soflink will work as well for the images directory.

I managed to install windows 10. ( instead of accepting he default location, I pointed to a new folder I made.)

It seems I cant go full screen like I could in virtualbox.

Some more to google. For now already missing virtual box, but we will see. :slight_smile:

Hi
In the ‘View’ menu item should be the option, there should also be a drop in the top center of the screen if you move the mouse pointer to leave full screen.

Yes , but then the windows screen is way to small to fit the actual screen.

I might have found a solution though, its seems I need to install just like with virtualbox something extra.

https://tflynnhk.wordpress.com/2014/03/24/kvm-windows-guest-resolution-switching/

There is probably no need to install extra stuff. I went in to the windows settings and changed the resolution, now its full screen :slight_smile:

I am starting to like KVM. I can make a screenshot like I am used too. Could not do this on virtualbox, had to do an extra step.

Hi
Excellent, you can do so much more with it :wink: Plus no pesky issues on a kernel update!

Yeah I am starting to think about making another VM. Can you guys guess the os ?

Arch

That should be fun, and I will learn more about Linux.

I seemed to have stopped the virtual machine, but now it wont start.

I already tried

systemctl start libvirtd

But that did not help.

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1331, in startup
    self._backend.create()
  File "/usr/lib64/python3.8/site-packages/libvirt.py", line 1353, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: Gevraagde operatie is niet geldig: network 'default' is not active


When I open the vm, it says: Guest is not running

Hi
What does the output (as root user) from the following say;


virsh net-list

Sounds like networking is not set to auto start.

guus@linux-2ls4:~> virsh net-list 
 Name   State   Autostart   Persistent 
---------------------------------------- 

guus@linux-2ls4:~> sudo virsh net-list 
[sudo] password for root:  
 Name   State   Autostart   Persistent 
---------------------------------------- 

guus@linux-2ls4:~>  



Hi


virsh net-list --all

I use a second interface here as a bridge, but have a read here as well: libvirt: NAT forwarding (aka "virtual networks")

guus@linux-2ls4:~> sudo virsh net-list --all 
[sudo] password for root:  
 Name      State      Autostart   Persistent 
---------------------------------------------- 
 default   inactive   no          yes 

guus@linux-2ls4:~> virsh net-list --all


I just realised this problem started after I killed qemu or something like that in the task manager (ctrl + esp)

That was still running after I had stopped the virtual machine. (and made my pc sometimes stutter)

Gonna read that wiki, and see what happens if I make it active, and set to auto connect. :slight_smile:

I found the XML file and opened it with kate.

<network>
  <name>default</name>
  <bridge name='virbr0'/>
  <forward/>
  <ip address='192.168.122.1' netmask='255.255.255.0'>
    <dhcp>
      <range start='192.168.122.2' end='192.168.122.254'/>
    </dhcp>
  </ip>
</network>


I don’t understand how I add a line though.

Or do I just need to type ( or copy paste) this ?

# virsh net-define /usr/share/libvirt/networks/default.xml
Network default defined from /usr/share/libvirt/networks/default.xml
# virsh net-autostart default
Network default marked as autostarted
# virsh net-start default
Network default started

:slight_smile:

Hi
Yup, virsh net-list --help is your friend :wink: You should also be able to set this via virt-manager…

In the vbox digest thread they have a cure for 15.3.x Kernel and VirtualBox

quoting ‘I can now run everything fine in virtualbox after adding “randomize_kstack_offset=off” to the kernel command line.’

The fix is in this bug report: https://www.virtualbox.org/ticket/20452

Hi
At the expense of security to regain a little bit of performance…

I am starting to remember why I hate computers, but made some progress. rotfl!

guus@linux-2ls4:~> sudo virsh net-list --all    
 Name      State    Autostart   Persistent 
-------------------------------------------- 
 default   active   yes         yes 


And its working again. Thank you :slight_smile:

I typed the command shown on that wiki, but you need to add sudo it seems. (and remove the # if you copy paste)

Minor update, sometimes when I shut down the virtual machine, something called something like qemu lib 64, keeps running.

Most of the time i does not though, so I am happy. And when needed I can kill it through ctrl + esc then terminate. :slight_smile:

Only thing left is how to make a snap shot. Some reading to do. :slight_smile:
I had already found a page explaining it.