I was unable to connect to the SPICE.
But the SPICE is configured normally.
I can connect with VNC after adding it to the VMs.
The day after SPICE was working again. And i cant figure out what happens in
the meantime.
No related update happens those days.
--
You received this bug notification be
The Virtual Manager start working again with SPICE
Has someone any idea what could have caused this problem?
** Changed in: virt-manager (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/virt-manager/+question/699413
--
You receive
Public bug reported:
I have an UBUNTU server (20.04) with libvirtd installed.
I used to connect to that server using Virt Manager from an UBUNTU desktop
(18.04).
Starting today (2021-11-08) the Virt Manager does not shows the screen
of the virtual machines.
I added the VNC server to one VM and
Public bug reported:
The keyboard layout is changing to "en" in some applications.
I am using UBUNTU 18.04 and the system keyboard layout is "Português (Brasil)"
Three months ago i realized that in some applications the keyboard was working
as if it were english.
Looking in the internet for this
I was able to recreate the topology on my home machine and was able to
reproduce the problem.
I will make more tests and report upstream soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853489
Ti
I will recreate this scenario on my home computer so i could have more
flexibility on making tests.
I am sick and will be off for this week.
But i will return to this ASAP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I found that the problem only happens when the "virtio" device model is used in
both pfSense internal and UBUNTU interfaces.
I tested all combinations and get the following results:
pfSense
default confinada UBUNTU result
virtio virtio virtioERR
virtio virtio rtl8139 OK
I made some more tests and found that ICMP packets are NAT'ed OK
independent of the device model used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853489
Title:
Ignoring the default NAT when usin
I tried with and without the driver option set to qemu and the problem
continues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853489
Title:
Ignoring the default NAT when using the virtio adapter
** Description changed:
I am using libvirt with KVM on a UBUNTU 18.04.3 LTS
I have the following topology inside libvirt/KVM
The default virtual network with IP range 10.0.0.0/24 on virbr0 interface
with IP 10.0.0.1 and DHCP enabled
Another virtual network named "confinada" with IP ra
Public bug reported:
I am using libvirt with KVM on a UBUNTU 18.04.3 LTS
I have the following topology inside libvirt/KVM
The default virtual network with IP range 10.0.0.0/24 on virbr0 interface with
IP 10.0.0.1 and DHCP enabled
Another virtual network named "confinada" with IP range 192.168.2
11 matches
Mail list logo
