[libvirt-users] [virtual interface] detach interface during boot succeed with no changes
by Yalan Zhang
Hi guys,
when I detach an interface from vm during boot (vm boot not finished), it
always fail. I'm not sure if there is an existing bug. I have
confirmed with someone that for disk, there is similar behavior, if
this is also acceptable?
# virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 2; virsh
detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh
dumpxml rhel7.2 |grep /interface -B9
Domain rhel7.2 destroyed
Domain rhel7.2 started
Interface detached successfully
<address type='pci' domain='0x0000' bus='0x00' slot='0x06'
function='0x0'/>
</controller>
<interface type='network'>
<mac address='52:54:00:98:c4:a0'/>
<source network='default' bridge='virbr0'/>
<target dev='vnet0'/>
<model type='rtl8139'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</interface>
When I detach after the vm boot, expand the sleep time to 10, it will succeed.
# virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 10; virsh
detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh
dumpxml rhel7.2 |grep /interface -B9
Domain rhel7.2 destroyed
Domain rhel7.2 started
Interface detached successfully
-------
Best Regards,
Yalan Zhang
IRC: yalzhang
Internal phone: 8389413
2 years, 2 months
[libvirt-users] Question about disabling UFO on guest
by Bao Nguyen
Hello everyone,
I would like to ask a question regarding to disable UFO of virtio vNIC in
my guest. I have read the document at https://libvirt.org/formatdomain.html
*host*
The csum, gso, tso4, tso6, ecn and ufo attributes with possible
values on and off can be used to turn off host offloading options. By
default, the supported offloads are enabled by QEMU. *Since 1.2.9 (QEMU
only)* The mrg_rxbuf attribute can be used to control mergeable rx buffers
on the host side. Possible values are on (default) and off. *Since 1.2.13
(QEMU only)*
*guest*
The csum, tso4, tso6, ecn and ufo attributes with possible
values on and off can be used to turn off guest offloading options. By
default, the supported offloads are enabl
ed by QEMU.
*Since 1.2.9 (QEMU only)*
Then I disabled UFO on my vNIC on guest as the following configuration
<devices>
<interface type='network'>
<source network='default'/>
<target dev='vnet1'/>
<model type='virtio'/>
<driver name='vhost' txmode='iothread' ioeventfd='on' event_idx='off'
queues='5' rx_queue_size='256' tx_queue_size='256'>
*<host gso='off' ufo='off' />*
*<guest ufo='off'/>*
</driver>
</interface>
</devices>
Then I reboot my node to get the change effect and it works. However, can I
disable the UFO without touching the host OS? or it always has to disable
on both host and guest like that?
Thanks,
Brs,
Natsu
4 years, 3 months
[libvirt-users] Add support for vhost-user-scsi-pci/vhost-user-blk-pci
by Li Feng
Hi Guys,
And I want to add the vhost-user-scsi-pci/vhost-user-blk-pci support
for libvirt.
The usage in qemu like this:
Vhost-SCSI
-chardev socket,id=char0,path=/var/tmp/vhost.0
-device vhost-user-scsi-pci,id=scsi0,chardev=char0
Vhost-BLK
-chardev socket,id=char1,path=/var/tmp/vhost.1
-device vhost-user-blk-pci,id=blk0,chardev=char1
What type should I add for libvirt.
Type1:
<hostdev mode='subsystem' type='vhost-user'>
<source protocol='vhost-user-scsi' path='/tmp/vhost-scsi.sock'></source>
<alias name="vhost-user-scsi-disk1"/>
</hostdev>
Type2:
<disk type='network' device='disk'>
<driver name='qemu' type='raw' cache='none' io='native'/>
<source protocol='vhost-user' path='/tmp/vhost-scsi.sock'>
</source>
<target dev='sdb' bus='vhost-user-scsi'/>
<boot order='3'/>
<alias name='scsi0-0-0-1'/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<disk type='network' device='disk'>
<driver name='qemu' type='raw' cache='none' io='native'/>
<source protocol='vhost-user' path='/tmp/vhost-blk.sock'>
</source>
<target dev='vda' bus='vhost-user-blk'/>
<boot order='1'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07'
function='0x0'/>
</disk>
Could anyone give some suggestions?
Thanks,
Feng Li
--
The SmartX email address is only for business purpose. Any sent message
that is not related to the business is not authorized or permitted by
SmartX.
本邮箱为北京志凌海纳科技有限公司（SmartX）工作邮箱. 如本邮箱发出的邮件与工作无关,该邮件未得到本公司任何的明示或默示的授权.
4 years, 11 months
[libvirt-users] libvirt_lxc memory limit, emulator process part of the cgroup?
by Maximilian Philipps
hi,
I am currently investigating a bug with libvirt lxc. Whenever I do a
systemctl daemon-reload on the host, my container loses his memory limit
and then reports having access to 8 exabyte of memory.
I have tracked the issue down to two parts:
memory.limit_in_bytes jumps from the correct value to 9223372036854771712.
libvirt lxc appears to set the memory limit in transient way without
writing a config for systemd. I can't prevent memory.limit_in_bytes
changing by setting the correct value through systemctl set-property
--runtime <scope> MemoryLimit=
tasks in the memory cgroup gets cleaned up.
After starting the container the cgroup contains 3 pid. The pid of the
libvirt_lxc process, the pid of the init process in the container and
third unknown pid that doesn't exists in /proc/.
After a demon-reload only the init process remains in the cgroup and
unless I move the libvirt_lxc process into the cgroup the memory limit
isn't enforced.
I have also noticed that when starting libvirtd it complains about
GetMachineByPID failing for the libvirt_lxc process.
This leaves me with one big question, the the emulator process
libvirt_lxc supposed to be part of the container's cgroup or not? The
leader of the container is the init process in the container. I am
unsure on how the additional emulator process is supposed to be registered.
Using: Debian Stretch, libvirt 5.0.0-4, systemd 241-7~deb10u1 and hybrid
cgroups.
Regards,
Maximilian Philipps
5 years
[libvirt-users] 32 bit support
by Phill. Whiteside
Hi good people,
I've got a bit of a weird issue. I'm using QEMU emulator version
2.11.1(Debian 1:2.11+dfsg-1ubuntu7.19) And after some considerable time of
not using it for 32bit installations I now find that it can no longer
install some older 32 bit installations (e.g.
https://phillw.net/isos/lubuntu/natty/ ) The CPU goes to 100% and then
after a while it just stops (I'm using virt-manager v1.5.1) I'm running
lubuntu 18.04 (64 bit) on an i7 chipset that runs 64 bit debian / centos
and MS server 2019 KVM instances via virt-manager without problems.
Any pointers would be appreciated,
Phill.
5 years
[libvirt-users] win10 vm stuck in automatic repair
by Jack Kamm
Hello,
I have a Windows 10 guest, when I boot it, it goes in to Automatic
Repair mode, and after some time reports it was unable to repair the PC.
This is from an older snapshot ("snapshot1"), and if I try switching
back to a more recent snapshot ("snapshot2"), libvirt reports that it
can't find the snapshot:
> libvirt.libvirtError: internal error: Child process (/usr/bin/qemu-img
> snapshot -a snapshot2 /var/lib/libvirt/images/win10.qcow2) unexpected
> exit status 1: qemu-img: Could not apply snapshot 'snapshot2': Failed
> to load snapshot: Invalid argument
Does anyone have any ideas why this might have happened, or any
suggestions for how I can go about diagnosing/fixing this?
This was a pretty simple Windows 10 VM, that I used for Microsoft
Office. Everything was managed through virt-manager and most settings
left at the original defaults.
Thanks,
Jack
5 years
[libvirt-users] Reg: Adding "edu" device using XML file
by bharath paulraj
Hi Team,
I am exploring "edu" device in QEMU to add my own custom device. I am able
to add the device using the command line. Would it be possible to add the
device using XML file through libvirt?
--
Regards,
Bharath
5 years, 1 month
