- Users - libvirt List Archives

[libvirt-users] unable to list virtualbox domain remotely
by François Marsy 25 Jan '19

25 Jan '19

Hi dear all, I have the following issue : I have a libvirtd intstalled on an ubuntu desktop. The libvirtd is listening on port 16509 (options listen_tls = 0 and listen_tcp = 1) On the desktop I have a virtualbox installed with a running VM : "styx32-dry-run3" I want to control my VM remotely by using libvirt. I performed following tests : 1)Local virsh running fine : virsh -c vbox:///session list Id Name State ---------------------------------------------------- 2 styx32-dry-run3 running 2)Using the tcp port is showing an empty list: virsh -c vbox+tcp://127.0.0.1:16509/session list Id Name State ---------------------------------------------------- 3)net-list command works virsh -c vbox+tcp://127.0.0.1:16509/session net-list Name State Autostart Persistent ---------------------------------------------------------- vboxnet0 active no autostart yes Can any of you help me please, I really don't understand why my VM is not showing up in the 2 ) list .. and I really don't know where to look at :-( Kind regards Francois

1 0

[libvirt-users] stuck in pxe loop from uefi + tianocore/ovmf
by jsl6uy js16uy 24 Jan '19

24 Jan '19

Hello all, hope all is well Was wondering if I'm doing something wrong/missing something. I have pxe+tftp+uefi working between 2 vms. However after the build is done and I reboot, I still come up to pxe b/c tianocore always starts, from what I've seen, with trying PXE first. Great for initial builds :) but I would like to it stop after. In the xml I am pointing to the disk to boot first. if I virsh destory and run qemu directly on the qcow image, the vm comes up as expected and boots into the OS I have tried removing the nvram under /var/lib/libvirt/qemu/nvram/virtmachine. But the vm boots up and starts looking for pxe again. If I let that timeout, then type exit and select continue in the tianocore boot firmware, I just loop back into trying pxe over ipv4 etc I tried <rom bar='off'/> on the e1000 and that does work to stop pxe. Then I get to the uefi shell quickly, but all I see at that point is 2 BLK maps pointing to floppy 1 and 2. I see nothing when I try to manually add a new boot option. any help/wisdom would be appreciated. libvirtd (libvirt) 4.9.0 qemu command: sudo qemu-system-x86_64 -m 2048 -L /usr/share/ovmf/x64/ -bios OVMF_CODE.fd -drive file=/images/rdhcli02,format=qcow2,cache=writeback,if=virtio -device virtio-net,netdev=net10,mac=52:54:00:11:22:33 -netdev tap,id=net10,ifname=rdhcli02,script=no,downscript=no Is there a way to address this?

1 1

[libvirt-users] Problems with incoming multicasts
by David Gra 24 Jan '19

24 Jan '19

Hello I have realized a problem with incomming multicast packages to a VM. My Setup is: 1 Host with 1 VM. On the external Network (Host: eth0), there ist a Multicast Stream. The packages are visible at the hosts eth0. The Guest is connected via macvtap to the eth0 from the Host. Host and Guest ist CentOS 7.6 in Future it should be RedHat 7.6. The guest is connected via macvtap0 to eth0. If i performe tcpdump on eth0 of the host, i can see teh packages. If i performe tcpdump on macvtap0 on the host, i can see the packages anyway. If i performe tcpdump on the guests eth0, i can't see the multicast packages. Normal unicast communications to the external systems are still working. All my network is only IPv4. Is there a limitation to multicast on libvirt? Best regards and thank's a lot for your help!

1 0

[libvirt-users] LXC guest to have/make a device node (FUSE)
by lejeczek 22 Jan '19

22 Jan '19

hi guys With lxc container under libvirt control - how can guest create device nodes? I'm specifically looking for FUSE device. Is it possible somehow to get it to the guest(passthrough?) or allow the guest to create dev node? many thanks, L.

3 2

[libvirt-users] Slow ssh
by Pascal Legrand 22 Jan '19

22 Jan '19

Hello, i'm using libvirt/kvm/qemu on a stable Debian Linux KVM 4.9.0-6-amd64 . qemu-kvm : 1:2.8+dfsg-6+deb9u5 libvirt-daemon : 3.0.0-4+deb9u3 libvirt-clients : 3.0.0-4+deb9u3 virt-manager : 1:1.4.0-5 virt-viewer : 5.0-1 virtinst : 1:1.4.0-5 My guests are made with this kind of command line : virt-install --connect=qemu:///system --name=debian --ram=2048 --disk /home/vm/debian.qcow2,size=10,format=qcow2 --network=bridge:bridge-0-1,model=virtio --network=bridge:bridge-0-2,model=virtio --network=bridge:bridge-0-3,model=virtio --accelerate --noautoconsole --vnc --vnclisten=0.0.0.0 --keymap=fr --cdrom=/home/iso/debian-6.0.1a-i386-netinst.iso --os-type=linux --os-variant=debiansqueeze --hvm Since a long time ago now (may be a Debian upgrade) i noticed that ssh session from my personal PC to guests are very slow (connection and behaviour) My ssh configuration is the same on all my real/vm servers. The problem occure only on my guest. Have you got a solution or an idea to solve this problem ? Thanks for your help -- Pascal

2 1

[libvirt-users] *-sock created as part of normal daemon startup?
by Keith Bierman 18 Jan '19

18 Jan '19

As noted in another thread, I've not had success with homebrew/Mac OSX's libvirt install. On Ubuntu and CentOS virtual machines, installing "libvirt-daemon" and friends, I end up with various "-sock" files in /var/run/libvirt. This seems sensible. After installing on MacOS X with homebrew ls /usr/local/var/run/libvirt hostdevmgr lockd qemu storage so perhaps it isn't surprising that virsh -c vbox:/// fails. Am I right in believing that the lack of -sock files means that the "brew services start libvirt" is either misconfigured or otherwise failing?

1 0

[libvirt-users] virt-install and IOThreads
by Igor Gnatenko 18 Jan '19

18 Jan '19

Hello, is there any way of specifying iothreads via virt-install command? I've tried appending ",iothread='1'" but that didn't work. Thanks in advance! -- -Igor Gnatenko

3 3

[libvirt-users] VM running with storage image file deleted
by Roosen, Nicolas 17 Jan '19

17 Jan '19

Hello, I have a strange issue I'd like to have some insights on. We have 2 running VM, the storage pool is over NFS. Unfortunately, the backend storage folder has been deleted (so the image file in it as well, obviously) ... Yet, the 2 VM are still up and running, with their root filesystem being mounted "rw". - how does that work? I was expecting that with the file image being deleted, the VM would not work at all. - since the VM is still running, is there a way to create a snapshot of it in order to re-create the image file on another storage pool ? I'm currently exploring "virsh snapshot-create-as ...", but if access to the image file is needed, it will fail. Thanks. -- Nicolas

4 5

[libvirt-users] cpu0 unhandled rdmsr:
by Christophe Dumont 16 Jan '19

16 Jan '19

Hello, Do you know what this means : kvm: 2918: cpu0 unhandled rdmsr: 0x345 kvm: 2918: cpu0 unhandled rdmsr: 0x1c9 kvm: 2918: cpu0 unhandled rdmsr: 0x1a6 kvm: 2918: cpu0 unhandled rdmsr: 0x1a7 kvm: 2918: cpu0 unhandled rdmsr: 0x3f6 tap110i0: no IPv6 routers present kvm: 2952: cpu0 unhandled rdmsr: 0x345 kvm: 2952: cpu0 unhandled rdmsr: 0x1c9 kvm: 2952: cpu0 unhandled rdmsr: 0x1a6 kvm: 2952: cpu0 unhandled rdmsr: 0x1a7 kvm: 2952: cpu0 unhandled rdmsr: 0x3f6 I think it causes instability, we had to reboot the server twice and a backup script still fails. Thx -- Christophe Dumont 4, Passage du Lycée 38000 Grenoble 0633475733

2 2

[libvirt-users] forcing order of vnet creation
by daggs 13 Jan '19

13 Jan '19

dummy0 Link encap:Ethernet HWaddr C6:C8:2A:04:FD:23 BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:22048 errors:0 dropped:0 overruns:0 frame:0 TX packets:22048 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1068960 (1.0 MiB) TX bytes:1068960 (1.0 MiB) Greetings, I have a host that has two vms, one is a router that all the machines on the network connect to it and that other a test virtual machine. the router vm is connected to the host using a virt net, the test virtual machine is connected to the router via a virtual switch. my /etc/network/interfaces defines vnet1 as dhcp by assuming that it is the vnet for the host (it was seen multiple times). yesterday I came back from a vacation, booted the system and didn't got any ip to the host, the rest of the machines on the network got ip. at the end, the issue was that vnet1 was the virtual switch rather than the host's virtual nic. is there a way for "lock" the vnics config so they won't change? the host is Debian 9.6, the output of ifconfig -a is below (the "faulty" scenario) virtsw0 Link encap:Ethernet HWaddr 52:54:00:6B:1B:92 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:92908 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13257095 (12.6 MiB) TX bytes:756 (756.0 B) virtsw0-nic Link encap:Ethernet HWaddr 52:54:00:6B:1B:92 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) vnet0 Link encap:Ethernet HWaddr FE:54:00:8B:66:C1 inet addr:10.0.0.3 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::fc54:ff:fe8b:66c1/64 Scope:Link inet6 addr: fdab:9802:eb52:0:fc54:ff:fe8b:66c1/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:528665 errors:0 dropped:0 overruns:0 frame:0 TX packets:752585 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:44311555 (42.2 MiB) TX bytes:2165654771 (2.0 GiB) vnet1 Link encap:Ethernet HWaddr FE:54:00:A7:79:6B inet6 addr: fe80::fc54:ff:fea7:796b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:92983 errors:0 dropped:0 overruns:0 frame:0 TX packets:81658 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14566221 (13.8 MiB) TX bytes:4249914 (4.0 MiB) vnet2 Link encap:Ethernet HWaddr FE:54:00:54:78:BE inet6 addr: fe80::fc54:ff:fe54:78be/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:257 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1962 (1.9 KiB) TX bytes:42261 (41.2 KiB) thanks, Dagg.

1 1