[libvirt-users] How to assign to PCI slot 0
by Fortman, Andrew
Hi,
I'm new to this group so bear with me.
So I need to passthrough a pci device on a particular bus and slot to get Linux to recognize it correctly.
I need pci bus 6, slot 0.
However whenever I try to use this slot inside of virsh edit it complains:
error: XML error: Invalid PCI address 0000:06:00.0. slot must be >= 1
Failed. Try again? [y,n,i,f,?]:
Is there a way to work around this ? Like can I disable the strict XML checking or even run the qemu commands manually?
Thanks,
Andy
7 years, 1 month
[libvirt-users] virsh does no longer respond to commands
by Dominik Psenner
Hi,
after a recent live backup done with a snapshot, blockcommit failed and a
subsequent (manual) blockjob abort got stuck. Now we are unable to do basic
operations on the virtual machine like if it was frozen and when issuing
another command we see the following:
$ virsh shutdown $domain
error: Failed to shutdown domain $domain
error: Timed out during operation: cannot acquire state change lock (held
by remoteDispatchDomainBlockJobAbort)
$ virsh blockcommit $domain --active --pivot
error: Timed out during operation: cannot acquire state change lock (held
by remoteDispatchDomainBlockJobAbort)
$ virsh blockjob $domain --abort
error: Timed out during operation: cannot acquire state change lock (held
by remoteDispatchDomainBlockJobAbort)
Houston, we've got a problem. We have roughly 16 hours to fix this. Any
help is appreciated!
--
Dominik Psenner
7 years, 1 month
[libvirt-users] Need to increase the rx and tx buffer size of my interface
by Ashish Kurian
Dear Users/Developers,
I am using a KVM Ubuntu VM as a degrader to apply specific delays to
incoming packets. As the delay for my packets can be higher than 7.5
seconds, there is not enough buffer on my interface to buffer all the
packets. Therefore those overflowing packets are dropped in the machine and
not forwarded.
When I tried to use the command ethtool -G ens8 rx 512 to increase the
buffer size, I get the following error.
Cannot set device ring parameters: Operation not permitted
I have kept the VM xml files as specified in the link :
https://libvirt.org/formatdomain.html. The value that I kept in my xml file
is as follows.
<interface type='direct'>
<mac address='52:54:00:72:f9:eb'/>
<source dev='enp7s0f0' mode='vepa'/>
<model type='virtio'/>
<driver name='vhost' queues='5' rx_queue_size='512'
tx_queue_size='512'>
<host csum='off' gso='off' tso4='off' tso6='off' ecn='off' ufo='off'
mrg_rxbuf='off'/>
<guest csum='off' tso4='off' tso6='off' ecn='off' ufo='off'/>
</driver>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08'
function='0x0'/>
</interface>
<interface type='direct'>
<mac address='52:54:00:00:b5:99'/>
<source dev='enp7s0f1' mode='vepa'/>
<model type='virtio'/>
<driver name='vhost' queues='5' rx_queue_size='512'
tx_queue_size='512'>
<host csum='off' gso='off' tso4='off' tso6='off' ecn='off' ufo='off'
mrg_rxbuf='off'/>
<guest csum='off' tso4='off' tso6='off' ecn='off' ufo='off'/>
</driver>
<address type='pci' domain='0x0000' bus='0x00' slot='0x09'
function='0x0'/>
After I saved the xml and redefined the machine and started it up, I
checked to see if the buffers are increased. I still see that the buffers
are as follows.
Ring parameters for ens9:
Pre-set maximums:
RX: 4096
RX Mini: 0
RX Jumbo: 0
TX: 4096
Current hardware settings:
RX: *256*
RX Mini: 0
RX Jumbo: 0
TX: *256*
How can I increase the buffer on my KVM VM?
Best Regards,
Ashish Kurian
7 years, 1 month
[libvirt-users] virsh + remote VirtualBox
by Konstantin Suvorov
Hello,
I have the following setup:
1. MacOS host with VirtualBox installed
2. Ubuntu 16.04 host with libvirt installed
What I try to do:
Manage VMs executed inside VirtualBox on host 1 with libvirt tools from
host 2.
I have vboxwebsrv up and running on my MacOS host.
I can successfully manage VMs remotely (e.g. with phpvirtualbox).
But libvirt (virsh in particular) doesn't work.
Reading debug logs, manuals and numerous internet threads leads me to a
conclusion, that libvirt does not support remote connection to VirtualBox
directly and only via libvirtd daemon installed on the same remote host as
VirtualBox. Is this correct?
If my assumption is correct, why is that so? Why libvirt can't manage
remote VirtualBox directly?
Regards, Konstantin.
7 years, 1 month
[libvirt-users] domain CPU topology
by llilulu
Hi
When I create a domain from xml file, the vcpu number point in <vcpu/>, I not point <cpu><topology> in xml file, when allocate more than 2 vpcus, some(windows) system can't use all vcpu. But I point <cpu><topology sockets='1' cores='num' threads='1'/></cpu>. num is <vcpu>'num'</vcpu>. then whindows can use all vcpus. I want to know when no ponit <cpu><topology> ,what default cpu topology. if point cpu topology, what rule guide cpu topology, I find VMware Workstation can point cpu num,and core of per cpu. all cores is cpu*core.
7 years, 2 months
[libvirt-users] libvirtd audit log
by llilulu
Hi
I according to libvirt.org Audit log guide ,I install auditd in my system(ubuntu 16.04.2), but when I operate guest running in host, I can't not find guest audit log in /var/log/audit/audit.log, audit_level=1.
when I change audit_level=2, I restart libvirtd, libvirtd start failed.
Thanks
7 years, 2 months
[libvirt-users] terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
by Matwey V. Kornilov
Hello,
I use libvirt 3.3.0 and qemu 2.9.0
My domain XML spec is the following:
<domain type='qemu'>
<name>s390_generic</name>
<uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid>
<memory unit='KiB'>1048576</memory>
<currentMemory unit='KiB'>1048576</currentMemory>
<vcpu placement='static'>1</vcpu>
<os>
<type arch='s390x' machine='s390-ccw-virtio-2.9'>hvm</type>
<boot dev='hd'/>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-s390x</emulator>
<disk type='block' device='disk'>
<driver name='qemu' type='raw' cache='none' io='native'/>
<source dev='/dev/lvm_pda/libvirt_s390'/>
<target dev='vda' bus='virtio'/>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<target dev='sda' bus='scsi'/>
<readonly/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='scsi' index='0' model='virtio-scsi'>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:e8:61:7e'/>
<source bridge='br0'/>
<model type='virtio'/>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0001'/>
</interface>
<console type='pty'>
<target type='sclp' port='0'/>
</console>
<memballoon model='virtio'>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0003'/>
</memballoon>
<panic model='s390'/>
</devices>
</domain>
The issue is that when I try to start it, it starts and shutdowns
immediately:
virsh # start s390_generic
Domain s390_generic started
virsh #
In the domain log file I see the following:
2017-10-19 18:10:21.633+0000: starting up libvirt version: 3.3.0, qemu
version: 2.9.0(openSUSE Leap 42.3), hostname: oak.local
LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-s390x -name
guest=s390_generic,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-7-s390_generic/master-key.aes
-machine s390-ccw-virtio-2.9,accel=tcg,usb=off,dump-guest-core=off -m
1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
82b4d16e-b636-447e-9fda-41d44616bce8 -display none -no-user-config
-nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-s390_generic/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
-no-shutdown -boot strict=on -device
virtio-scsi-ccw,id=scsi0,devno=fe.0.0002 -drive
file=/dev/lvm_pda/libvirt_s390,format=raw,if=none,id=drive-virtio-disk0,cache=none,aio=native
-device
virtio-blk-ccw,scsi=off,devno=fe.0.0000,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-drive if=none,id=drive-scsi0-0-0-0,readonly=on -device
scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0
-netdev tap,fd=26,id=hostnet0 -device
virtio-net-ccw,netdev=hostnet0,id=net0,mac=52:54:00:e8:61:7e,devno=fe.0.0001
-chardev pty,id=charconsole0 -device
sclpconsole,chardev=charconsole0,id=console0 -device
virtio-balloon-ccw,id=balloon0,devno=fe.0.0003 -msg timestamp=on
2017-10-19T18:10:21.701184Z qemu-system-s390x: -chardev
pty,id=charconsole0: char device redirected to /dev/pts/5 (label
charconsole0)
2017-10-19T18:10:21.721299Z qemu-system-s390x: terminating on signal 15
from pid 2146 (/usr/sbin/libvirtd)
2017-10-19 18:10:21.985+0000: shutting down, reason=shutdown
What is the issue?
7 years, 2 months
[libvirt-users] Fwd: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
by Matwey V. Kornilov
Hello,
I use libvirt 3.3.0 and qemu 2.9.0
My domain XML spec is the following:
<domain type='qemu'>
<name>s390_generic</name>
<uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid>
<memory unit='KiB'>1048576</memory>
<currentMemory unit='KiB'>1048576</currentMemory>
<vcpu placement='static'>1</vcpu>
<os>
<type arch='s390x' machine='s390-ccw-virtio-2.9'>hvm</type>
<boot dev='hd'/>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-s390x</emulator>
<disk type='block' device='disk'>
<driver name='qemu' type='raw' cache='none' io='native'/>
<source dev='/dev/lvm_pda/libvirt_s390'/>
<target dev='vda' bus='virtio'/>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<target dev='sda' bus='scsi'/>
<readonly/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='scsi' index='0' model='virtio-scsi'>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:e8:61:7e'/>
<source bridge='br0'/>
<model type='virtio'/>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0001'/>
</interface>
<console type='pty'>
<target type='sclp' port='0'/>
</console>
<memballoon model='virtio'>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0003'/>
</memballoon>
<panic model='s390'/>
</devices>
</domain>
The issue is that when I try to start it, it starts and shutdowns
immediately:
virsh # start s390_generic
Domain s390_generic started
virsh #
In the domain log file I see the following:
2017-10-19 18:10:21.633+0000: starting up libvirt version: 3.3.0, qemu
version: 2.9.0(openSUSE Leap 42.3), hostname: oak.local
LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-s390x -name
guest=s390_generic,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-7-s390_generic/master-key.aes
-machine s390-ccw-virtio-2.9,accel=tcg,usb=off,dump-guest-core=off -m
1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
82b4d16e-b636-447e-9fda-41d44616bce8 -display none -no-user-config
-nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-s390_generic/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
-no-shutdown -boot strict=on -device
virtio-scsi-ccw,id=scsi0,devno=fe.0.0002 -drive
file=/dev/lvm_pda/libvirt_s390,format=raw,if=none,id=drive-virtio-disk0,cache=none,aio=native
-device
virtio-blk-ccw,scsi=off,devno=fe.0.0000,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-drive if=none,id=drive-scsi0-0-0-0,readonly=on -device
scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0
-netdev tap,fd=26,id=hostnet0 -device
virtio-net-ccw,netdev=hostnet0,id=net0,mac=52:54:00:e8:61:7e,devno=fe.0.0001
-chardev pty,id=charconsole0 -device
sclpconsole,chardev=charconsole0,id=console0 -device
virtio-balloon-ccw,id=balloon0,devno=fe.0.0003 -msg timestamp=on
2017-10-19T18:10:21.701184Z qemu-system-s390x: -chardev
pty,id=charconsole0: char device redirected to /dev/pts/5 (label
charconsole0)
2017-10-19T18:10:21.721299Z qemu-system-s390x: terminating on signal 15
from pid 2146 (/usr/sbin/libvirtd)
2017-10-19 18:10:21.985+0000: shutting down, reason=shutdown
What is the issue?
--
With best regards,
Matwey V. Kornilov
7 years, 2 months
[libvirt-users] "virsh define" modify xml configuration file
by d tbsky
hi:
I upgrade my system from rhel 7.3 to 7.4. so libvirt upgrade to 3.2.
I found command "virsh define vm.xml" sometimes modify "vm.xml". I
thought the command will read vm.xml, not write to it. is this kind of
behavior by design?
for example vm.xml with the line
<cpu mode='custom' match='exact'>
will be replaced with
<cpu mode='custom' match='exact' check='partial'>
Regards,
tbskyd
7 years, 2 months
