- Users - libvirt List Archives

[libvirt-users] public IP for VM
by scar 08 Dec '17

08 Dec '17

I can't seem to figure out how to setup a public IP for the VM so we could use it as a second public webserver. The host machine runs our primary webserver with CentOS 6.9 and one public ipv4 address configured on physical interface eth0. Now i have configured a new bridge interface br0: DEVICE=br0 TYPE=Bridge BOOTPROTO=static The IP settings are for a second public ipv4 address in the same network. Now i setup the VM to use br0 for the NIC and set the same IP settings inside the VM... but it doesn't work. The VM can't resolve any hosts, and if i try to ssh to the second public IP, it just sends me to the host machine instead of the VM.

5 4

[libvirt-users] public IP for VM
by Chandler 08 Dec '17

08 Dec '17

I can't seem to figure out how to setup a public IP for the VM so we could use it as a second public webserver. The host machine runs our primary webserver with CentOS 6.9 and one public ipv4 address configured on physical interface eth0. Now i have configured a new bridge interface br0: DEVICE=br0 TYPE=Bridge BOOTPROTO=static The IP settings are for a second public ipv4 address in the same network. Now i setup the VM to use br0 for the NIC and set the same IP settings inside the VM... but it doesn't work. The VM can't resolve any hosts, and if i try to ssh to the second public IP, it just sends me to the host machine instead of the VM. I read the Bridged Networking section but it seems to want to set br0 to the public IP and not use eth0. I want to use two public IP's over the same shared phys interface, eth0 with our first IP and br0 with the second IP for the VM... or another similar configuration that will have the same effect. Thanks

2 1

[libvirt-users] How to use virtio-gpu to output
by Rogue S.T 07 Dec '17

07 Dec '17

Hello, lads, owing to i study video card on my guest recently. So i have a notion that whether we can get video with virtio-vga or not. It's seem that we are using a graphics card truth. Maybe we can finish? And if this is not likelihood? Tell me why please. Thanks following is my host system environment: host: ubuntu 1604 qemu: 2.11 libvirt: 3.9 kernel: 4.14 guest: window 7 professor

1 0

[libvirt-users] problem when use tls to connect libvirt
by Yalan Zhang 06 Dec '17

06 Dec '17

Hi guys, I met a problem when I use tls to connect libvirt. When I set the CN in client.info, server.info as hostname(FDQN), the tls check will fail with ip; and vice versa, when set CN as ip address, the tls check will fail with hostname. Only use what we set in can succeed. If this is expected? or I there was some issue in my env. or setup steps? 1. set tls env with hostname, then it will fail to check with ip # virsh -c qemu+tls://192.168.122.4/system 2017-12-06 13:24:52.346+0000: 3954: info : libvirt version: x.x.x, package: 4.el7 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2017-11-30-07:57:27, x.x.x.redhat.com) 2017-12-06 13:24:52.346+0000: 3954: info : hostname: work.englab.cn 2017-12-06 13:24:52.346+0000: 3954: warning : virNetTLSContextCheckCertificate:1125 : Certificate check failed Certificate [session] owner does not match the hostname 192.168.122.4 error: failed to connect to the hypervisor error: authentication failed: Failed to verify peer's certificate 2. use the hostname as what we set can succeed. # virsh -c qemu+tls://test.englab.cn/system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # # ping test.englab.cn PING test.englab.cn (192.168.122.4) 56(84) bytes of data. 64 bytes from test.englab.cn (192.168.122.4): icmp_seq=1 ttl=64 time=0.235 ms 64 bytes from test.englab.cn (192.168.122.4): icmp_seq=2 ttl=64 time=0.204 ms ... ------- Best Regards, Yalan Zhang

2 1

[libvirt-users] Libvirt checkout graphics card
by Rogue S.T 06 Dec '17

06 Dec '17

Hello, everybody!My guest has two graphics card when it is running, one is GTX960, and other is video card that is created by qemu.But my guest use video card default, and my screen is not light. I try checkout graphics card with vnc or spice, But it is suspend.Could you help me? And may i checkout card in my host system with command? Because my connection with vnc or spice is not stable.This is my vga card message: Bus 0, device 7, function 0: VGA controller: PCI device 1234:1111 BAR0: 32 bit prefetchable memory at 0xf2000000 [0xf2ffffff]. BAR2: 32 bit memory at 0xfe09e000 [0xfe09efff]. BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe]. id "video0" Bus 0, device 8, function 0: VGA controller: PCI device 10de:1401 IRQ 11. BAR0: 32 bit memory at 0xfd000000 [0xfdffffff]. BAR1: 64 bit prefetchable memory at 0xe0000000 [0xefffffff]. BAR3: 64 bit prefetchable memory at 0xf0000000 [0xf1ffffff]. BAR5: I/O at 0xc000 [0xc07f]. BAR6: 32 bit memory at 0xffffffffffffffff [0x0003fffe]. id "" And following message is my envireoment: host: ubuntu 1604 guest: window 7 professor qemu: 2.11.0-rc0 seabiois: 2.10.7 (qemu set) libvirt: 3.9

1 0

[libvirt-users] Guest Reboot After Plug HDMI
by Lying 04 Dec '17

04 Dec '17

Hello, Everybody. I encounter a problem when i using my guest. I booting my guest without HDMI primarily, Then i add it, but my guest is be rebooted. To know what cause it, i do it again, especially i check my guest is running normal or not with "ping" before plugging, that's well. What i was suffer? can you help me solve it? Following message is detailed!!! Guest: window 7 profession Linux: Ubuntu 1604 Qemu:1 v2.11.0-rc0 Libvirt: 3.9 method of booting: virsh start myGuest1 method of plug HDMI: virsh qemu-monitor-command myGuest1 --hmp 'device_add driver=vfio-pci,host=01:00.0,xvga=on,multifunction=yes' phenomenon: after plugging, my Guest is failed to check with "ping", for a while, my display is light and load windows. expect: my guest is running when i plug HDMI, it seem that hot add a device.

3 2

[libvirt-users] vga passthroufh fail
by Lying 29 Nov '17

29 Nov '17

Hello, I encounter a problem, my display is not light when guest running. But it's successful that i check guest with command "ping". Following message is my xml and refer topic from https://libvirt.org/formatdomain.html#elementsHostDev: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio' /> <source> <address domain='0x0000' bus='0x06' slot='0x02' function='0x0'/> </source> </hostdev>

1 0

[libvirt-users] Export Video on Graphics Card
by Lying 22 Nov '17

22 Nov '17

I have two graphics card on my machine And i want to export my video on one card when VM switched on What should i do?

1 0

[libvirt-users] virtlock - a VM goes read-only
by Branimir Pejakovic 21 Nov '17

21 Nov '17

Dear colleagues, I am facing a problem that has been troubling me for last week and a half. Please if you are able to help or offer some guidance. I have a non-prod POC environment with 2 CentOS7 fully updated hypervisors and an NFS filer that serves as a VM image storage. The overall environment works exceptionally well. However, starting a few weeks ago I have been trying to implement virtlock in order to prevent a VM running on 2 hypervisors at the same time. Here is the description how the environment looks like in terms of virtlock configuration on both hypervisors: -- Content of /etc/libvirt/qemu.conf -- lock_manager = "lockd" Only the above line is uncommented for direct locking. # libvirtd --version; python -c "import platform; print(platform.platform())"; virtlockd -V libvirtd (libvirt) 3.2.0 Linux-3.10.0-693.2.2.el7.x86_64-x86_64-with-centos-7.4.1708-Core virtlockd (libvirt) 3.2.0 # getenforce Permissive Here is the issue: h1 # virsh list Id Name State ---------------------------------------------------- 1 test09 running h1 # virsh domblklist test09 Target Source ------------------------------------------------ vda /storage_nfs/images_001/test09.qcow2 h1 # h2 # virsh list Id Name State ---------------------------------------------------- h2 # virsh list --all | grep test09 - test09 shut off h2 # virsh start test09 error: Failed to start domain test09 error: resource busy: Lockspace resource '/storage_nfs/images_001/test09.qcow2' is locked h2 # virsh list Id Name State ---------------------------------------------------- h2 # Before I start test09 I open a console to the guest and observe what is going on in it. Once I try to start test09 (and get a message about locked resource) on h2 hypervisor, I can see the following messages in the console and the vm goes to ro mode: on test09's console: [ 567.394148] blk_update_request: I/O error, dev vda, sector 13296056 [ 567.395883] blk_update_request: I/O error, dev vda, sector 13296056 [ 572.871905] blk_update_request: I/O error, dev vda, sector 8654040 [ 572.872627] Aborting journal on device vda1-8. [ 572.873978] blk_update_request: I/O error, dev vda, sector 8652800 [ 572.874707] Buffer I/O error on dev vda1, logical block 1081344, lost sync page write [ 572.875472] blk_update_request: I/O error, dev vda, sector 2048 [ 572.876009] Buffer I/O error on dev vda1, logical block 0, lost sync page write [ 572.876727] EXT4-fs error (device vda1): ext4_journal_check_start:56: Detected aborted journal[ 572.878061] JBD2: Error -5 detected when updating journal superblock for vda1-8. [ 572.878807] EXT4-fs (vda1): Remounting filesystem read-only [ 572.879311] EXT4-fs (vda1): previous I/O error to superblock detected [ 572.880937] blk_update_request: I/O error, dev vda, sector 2048 [ 572.881538] Buffer I/O error on dev vda1, logical block 0, lost sync page write I also observe the guests'log: -- /var/log/libvirt/qemu/test09.log -- block I/O error in device 'drive-virtio-disk0': Permission denied (13) block I/O error in device 'drive-virtio-disk0': Permission denied (13) block I/O error in device 'drive-virtio-disk0': Permission denied (13) block I/O error in device 'drive-virtio-disk0': Permission denied (13) block I/O error in device 'drive-virtio-disk0': Permission denied (13) block I/O error in device 'drive-virtio-disk0': Permission denied (13) block I/O error in device 'drive-virtio-disk0': Permission denied (13) If it helps, here is the disk portion of an XML file: <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/storage_nfs/images_001/test09.qcow2'/> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> I usually do implement SELinux on a hypervisor to isolate guests even further but this time I set it to permissive mode just to rule out SELinux factor. The same thing happens when SELinux is in enforcing mode (virt_use_nfs is set to on in that case) and audit2why doesn't report any anomalies when parsing audit logs. I have tried to use indirect locking via the same filer and with a separated export for the hashes by removing the comment in /etc/libvirt/qemu-lockd.conf for the following line: file_lockspace_dir = "/var/lib/libvirt/lockd/files" In this case the hashes are normally created on the NFS export mounted under /var/lib/libvirt/lockd/files. I have also tried playing with both QCOW2 and raw disk images for VMs (and even with XFS/ext4 based guests) but the outcome is always the same. I have a couple of KVM books - consulted them on this topic, consulted Red Hat and SUSE docs but pretty much the configuration instructions are, naturally, the same. I saw that some colleagues posted a few emails (ie https://www.redhat.com/archives/libvirt-users/2015-September/msg00004.html) to the list related to virtlock but it seems that it is not the same issue. I have also, as a last resort, completely disabled SELinux, rebooted both hypervisors, created a new vm, repeated all the steps listed above but with the same results. Now, I am pretty sure that I am missing something simple here since this is a standard feature and should work out of the box if set correctly but so far I cannot see what I am missing. I would really appreciate any tip/help. Thank you very much!! Regards, Branimir

2 2

[libvirt-users] Does libvirt-sanlock support network disk?
by Han Han 20 Nov '17

20 Nov '17

Hello, As we know, libvirt sanlock support file type storage. I wonder *if it supports network storage.* I tried *iSCSI*, but found it didn't generate any resource file: Version: *qemu-2.10 libvirt-3.9 sanlock-3.5* 1. Set configuration: qemu.conf: *lock_manager = "sanlock"* qemu-sanlock.conf: *auto_disk_leases = 1disk_lease_dir = "/var/lib/libvirt/sanlock"host_id = 1user = "sanlock"group = "sanlock"* # systemctl restart sanlock # systemctl restart libvirtd 2. Start a VM with iSCSI disk and check *resource file* VM disk xml: <disk type='network' device='disk'> <driver name='qemu' type='raw'/> <source protocol='iscsi' name='iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.cb4bfb00df2f/0'> <host name='xx.xx.xx.xx' port='3260'/> </source> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> Start VM: # virsh start iscsi Domain iscsi started Check resource file: # ls /var/lib/libvirt/sanlock __LIBVIRT__DISKS__ No resource file generated. So, does libvirt sanlock only support file or block type storage? -- Han Han Quality Engineer Redhat. Email: hhan(a)redhat.com Phone: +861065339333

2 2