Re: [libvirt-users] Xen died - Fedora upgrade from 21 to 26
by Dominik Psenner
Note that this does not help with the original problem but points out a
critical design flaw.
To me your it infrastructure design has no working disaster recovery plan.
You should always be able to access critical functionality and from there
be able to restore complete functionality step by step. In your case the
outermost functionality is the vm host. You should always be able to log
into that machine once it has all cables plugged in, regardless of what
runs on it (or not).
This means that even though you might get this to work you should rethink
your design so that you do not have to rely on the vm that does the
networking.
On 26 Jul 2017 12:50 p.m., "G Crowe" <gclvirtlist(a)crowie.net> wrote:
Jim,
Thanks for that, I had manually installed libvirt-daemon-driver-xen,
but also needed to install libvirt-daemon-driver-libxl. I can now create
VMs and convert config formats.
However the daemon still fails to start on bootup. It starts fine when I
manually start it with "systemctl start libvirtd" but setting it to
autostart with "systemctl enable libvirtd" seems to have no effect. When I
look at the status, it tells me that the service is "enabled" which means
that it starts on bootup (well, that's what it means for any other service).
This is rather critical on this PC, as it has unattended restarts and the
VPN/routing is done in one of the VMs (i.e. I can't get to it unless it
auto-starts at least one VM).
Unfortunatley there is nothing appearing in the libvirtd log over a reboot
to help diagnose.
Any suggestions?
Thank you
GC
[root@testhost ~]# systemctl status libvirtd
● libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled;
vendor preset: enabled)
Active: inactive (dead)
Docs: man:libvirtd(8)
http://libvirt.org
On 25/07/2017 1:20 AM, Jim Fehlig wrote:
> On 07/23/2017 04:25 PM, G Crowe wrote:
>
>> Hi,
>> I am trying to upgrade my Xen host (Dom0) and are having troubles
>> getting it to work.
>>
>> I think that it has booted into a kernel that supports Xen (running 'xl
>> info' does list some Xen capabilities), but I have three problems (that I
>> have found so far).
>>
>> Firstly, the "libvirtd" daemon doesn't start on bootup (and as a result
>> all 'virsh' commands fail). It is set to auto-start (systemctl enable
>> libvirtd), and can be manually started (systemctl start libvirtd), but it
>> will not auto-start on reboot.
>>
>> Secondly, Once I have manually started libvirtd, when I try to define a
>> domain it gives me an error "could not find capabilities for arch=x86_64
>> domaintype=xen" and I haven't yet been able to define any domains. This
>> domain type works fine on Fedora 21.
>>
>> Thirdly, I am unable to convert to/from xml config format, it gives me
>> the error "error: invalid argument: unsupported config type xen-xl" however
>> the format "xen-xl" works fine on the Fedora 21 machine.
>>
>
> It sounds like the libvirt libxl driver is not loaded. Is the
> libvirt-daemon-driver-libxl package installed? If it's installed, enabling
> debug logging in libvirtd can provide hints why it is not loading
>
> http://libvirt.org/logging.html
>
> Regards,
> Jim
>
>
>> I had these same issues when I tried to upgrade to Fedora 25 and assumed
>> that something had been broken and so abandoned further attempts to
>> upgrade, however since Fedora 26 is the same I am now assuming that I have
>> stuffed something up myself (or missed something).
>>
>> Fedora 21 uses kernel 3.19.3 and xen 4.4.1
>> Fedora 26 uses kernel 4.11.8 and xen 4.8.1
>>
>> I have tried following the info on https://wiki.xen.org/wiki/Fedo
>> ra_Host_Installation but it appears to be out of date now (I used this
>> site when I started using Xen under Fedora 19, and when I upgraded to
>> Fedora 21)
>>
>> Does anyone have any suggestions? outputs from "xl info" and the domain
>> config are below. I have also tried disabling SELinux, but it made no
>> difference.
>>
>>
>> Thanks
>>
>> GC
>>
>> -----------------------------------------------
>> On the fedora 26 box.....
>> # xl info
>> host : family.mydomain.mytld
>> release : 4.11.8-300.fc26.x86_64
>> version : #1 SMP Thu Jun 29 20:09:48 UTC 2017
>> machine : x86_64
>> nr_cpus : 4
>> max_cpu_id : 3
>> nr_nodes : 1
>> cores_per_socket : 4
>> threads_per_core : 1
>> cpu_mhz : 2712
>> hw_caps : b7ebfbff:77faf3bf:2c100800:000
>> 00121:0000000f:009c67af:00000000:00000100
>> virt_caps : hvm hvm_directio
>> total_memory : 8072
>> free_memory : 128
>> sharing_freed_memory : 0
>> sharing_used_memory : 0
>> outstanding_claims : 0
>> free_cpus : 0
>> xen_major : 4
>> xen_minor : 8
>> xen_extra : .1
>> xen_version : 4.8.1
>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
>> hvm-3.0-x86_32p hvm-3.0-x86_64
>> xen_scheduler : credit
>> xen_pagesize : 4096
>> platform_params : virt_start=0xffff800000000000
>> xen_changeset :
>> xen_commandline : placeholder
>> cc_compiler : gcc (GCC) 7.0.1 20170421 (Red Hat 7.0.1-0.15)
>> cc_compile_by : mockbuild
>> cc_compile_domain : [unknown]
>> cc_compile_date : Wed May 3 21:23:49 UTC 2017
>> build_id : 1c6e5a40165e05837303942b54757ae1f2d5033d
>> xend_config_format : 4
>>
>> ---------------------------------------------------
>> # cat vmtest.xml
>> <domain type='xen' id='21'>
>> <name>testVM</name>
>> <memory unit='KiB'>2097152</memory>
>> <currentMemory unit='KiB'>2097152</currentMemory>
>> <vcpu placement='static'>1</vcpu>
>> <os>
>> <type arch='x86_64' machine='xenfv'>hvm</type>
>> <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader>
>> <boot dev='network'/>
>> </os>
>> <features>
>> <acpi/>
>> <apic/>
>> <pae/>
>> </features>
>> <clock offset='variable' adjustment='0' basis='utc'/>
>> <on_poweroff>destroy</on_poweroff>
>> <on_reboot>restart</on_reboot>
>> <on_crash>restart</on_crash>
>> <devices>
>> <interface type='bridge'>
>> <mac address='02:02:00:03:00:00'/>
>> <source bridge='enp1s0'/>
>> <script path='vif-bridge'/>
>> </interface>
>> <serial type='pty'>
>> <target port='0'/>
>> </serial>
>> <console type='pty'>
>> <target type='serial' port='0'/>
>> </console>
>> <input type='mouse' bus='ps2'/>
>> <input type='keyboard' bus='ps2'/>
>> <graphics type='vnc' port='5901' autoport='no'
>> listen='192.168.131.54'>
>> <listen type='address' address='192.168.131.54'/>
>> </graphics>
>> </devices>
>> </domain>
>>
>> --------------------------------------
>>
>> _______________________________________________
>> libvirt-users mailing list
>> libvirt-users(a)redhat.com
>> https://www.redhat.com/mailman/listinfo/libvirt-users
>>
>>
>
_______________________________________________
libvirt-users mailing list
libvirt-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
7 years, 1 month
[libvirt-users] Why cannot block copy local storage to network disk
by wyang
Hi, guys
I was executing the following command to lively migrate local storage to
network storage,
[root@192-168-152-51 ~]# virsh blockcopy
a75056a4-44e0-4b97-bc77-78142ee17038 vda —xml rbd.xml —wait —verbose
—pivot
error: argument unsupported: non-file destination not supported yet
but I get the following error:
error: argument unsupported: non-file destination not supported yet
I check my libvirt source code, and find the following code sniff in
/qemuDomainBlockCopyCommon/ function
|if (!virStorageSourceIsLocalStorage(mirror)) {
virReportError(VIR_ERR_ARGUMENT_UNSUPPORTED, "%s", _("non-file
destination not supported yet")); } |
it was introduced by Eric.
commit e53ee6c123321a1775ef3b36e15a5fa351d10fe4
Author: Eric Blake eblake(a)redhat.com <http://mailto:eblake@redhat.com>
Date: Fri Aug 29 16:30:46 2014 -0600
blockcopy: tweak how rebase calls into copy
So my question is that why we cannot block copy to network storage?
Thanks
Wei
7 years, 1 month
[libvirt-users] About seclabel configure,Migrate error
by 露露
libvirt
version: 3.4.0
architecture: x86_64 ubuntu16.04-server
hypervisor: kvm,qemu
When migrate vm, I encounter error:
"Migrate VM virt21 failed unsupported configuration: Unable to find security driver for model apparmor"
but two host are same environment.before this error, migrate can be success.
the source host seclabel configure is this :
<seclabel type='dynamic' model='apparmor' relabel='yes'>
<label>libvirt-8e4ec209-17ca-4b59-abb7-72f3984244f3</label>
<imagelabel>libvirt-8e4ec209-17ca-4b59-abb7-72f3984244f3</imagelabel>
</seclabel>
I create a vm on the destination host ,the vm configure not seclabel congfigure.
I reinstall libvirt on the destination host and migrate same vm, this error disappear.vm seclabel configure is default.
I recreate a vm on the destination host ,the vm configure has the seclabel configure , I don't known the reason.
Another question:
I configure a vm xml's seclabel like this:
<seclabel type='none' model='none'/>
and then call virDomainCreate create the vm, call virsh dumpxml, the vm xml's seclabel is this:
<seclabel type='none' model='none'/>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+0</label>
<imagelabel>+0:+0</imagelabel>
</seclabel>
I don't the reason.
Is a vm seclabel configure dynamic change when it running?
Thanks
7 years, 1 month
[libvirt-users] how libvirt create virbr0
by 露露
libvirt
version: 3.4.0
architecture: x86_64 ubuntu16.04-server
hypervisor: kvm,qemu
when install libvirt from ubuntu distribution deb install libvirt, a virtual bridge virbr0 will be create . But when I build libvirt from souce code, how can I create a virbr0.
If I want create another virtual bridge ,How can I create and start the virtual bridge.
Thanks
7 years, 1 month
[libvirt-users] transient configure turn to persistent configure
by 露露
libvirt
version: 3.4.0
architecture: x86_64 ubuntu16.04-server
hypervisor: kvm,qemu
I call virDomainCreate create a transient vm, After a period of time ,I call virDomainDestroy, the vm configure is stil exist, the vm turn to persistent, I don't known the reason.
Thanks
7 years, 1 month
[libvirt-users] memory snapshot save error
by 露露
libvirt
version: 3.4.0
architecture: x86_64 ubuntu16.04-server
hypervisor: kvm,qemu
when I want make a memery snapshot for a vm ,and I call virsh save ,but tell me this error:
error: Failed to save domain 177 to /datapool/mm.img
error: operation failed: domain save job: unexpectedly failed
xml configure:
<domain type='kvm' id='177'>
<name>virt23</name>
<uuid>e50c1d59-c4a3-4413-b6c9-20e90cced343</uuid>
<metadata/>
<memory unit='KiB'>10485760</memory>
<currentMemory unit='KiB'>10485760</currentMemory>
<vcpu placement='static'>1</vcpu>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-i440fx-2.5'>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/kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/datapool/zhuohf/virt23.qcow2'/>
<backingStore/>
<target dev='vdc' bus='virtio'/>
<alias name='virtio-disk2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/datapool/zhuohf/ubuntu-16.04.2-desktop-amd64.iso'/> [40/38156]
<backingStore/>
<target dev='hdc' bus='ide'/>
<readonly/>
<alias name='ide0-1-0'/>
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
</disk>
<controller type='usb' index='0' model='piix3-uhci'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<controller type='ide' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<interface type='network'>
<mac address='52:54:00:e0:31:68'/>
<source network='default' bridge='virbr0'/>
<target dev='vnet11'/>
<model type='rtl8139'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<input type='mouse' bus='ps2'>
<alias name='input0'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input1'/>
</input>
<graphics type='vnc' port='5909' autoport='yes' listen='0.0.0.0'>
<listen type='address' address='0.0.0.0'/>
</graphics>
<video>
<model type='cirrus' vram='16384' heads='1' primary='yes'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='virtio'>
<stats period='1'/>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</memballoon>
</devices>
<seclabel type='none' model='none'/>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+0</label>
<imagelabel>+0:+0</imagelabel>
</seclabel>
</domain>
before I encounter the same error,that time is my disk not free space,but this time I can't find error reason.
Thanks
7 years, 1 month
[libvirt-users] cannot set maxMemory
by 임영빈
Hi all,
I'm testing the memory hotplugging on devstack (ocata version).
According to the article in
https://medium.com/@juergen_thomann/memory-hotplug-with-qemu-kvm-and-libv...
,
I'm trying to create a virtual machine by setting <maxMemory>.
However, I've got an error message in libvirt log as below.
2017-07-20 20:33:21.175+0000: 529: error :
virDomainDefCheckUnsupportedMemoryHotplug:1192 : unsupported configuration:
memory hotplug tunables <maxMemory> are not supported by this hypervisor
driver
virt-aa-helper: error: could not parse XML
virt-aa-helper: error: could not get VM definition
I'm using qemu hypervisor (2.8), and libvirt (2.5.0).
As I know, these qemu, libvirt versions support hotplugging memory.
Below is the xml file I used to create a virtual machine by using 'virsh
create test.xml' command.
<domain type='qemu'>
<name>QEmu-fedora-i686</name>
<uuid>c7a5fdbd-cdaf-9455-926a-d65c16db1809</uuid>
<maxMemory slots='4' unit='KiB'>2097152</maxMemory>
<memory>219200</memory>
<currentMemory>219200</currentMemory>
<vcpu>2</vcpu>
<cpu>
<numa>
<cell id="0" cpus="0" memory="2097152" unit="KiB"/>
</numa>
</cpu>
<driver name="qemu" type="qcow2" cache="none"/>
<os>
<type arch='i686' machine='pc'>hvm</type>
<boot dev='cdrom'/>
</os>
<devices>
<emulator>/usr/bin/qemu-system-ppc</emulator>
<disk type='file' device='cdrom'>
<source file='/home/user/boot.iso'/>
<target dev='hdc'/>
<readonly/>
</disk>
<disk type='file' device='disk'>
<source file='/home/user/fedora.img'/>
<target dev='hda'/>
</disk>
<interface type='network'>
<source network='default'/>
</interface>
</devices>
</domain>
Does anyone know the reason?
Thanks,
Youngbin
7 years, 1 month
[libvirt-users] SSH from host to domain using hostname
by c.monty@web.de
Hello!
I want to SSH from host to specific guest using hostname, e.g.
ssh <user>@<guest>
or
ssh test@vm02-fai
ssh to guest using IP works w/o issues.
I found Wiki article for "NSS module" (http://wiki.libvirt.org/page/NSS_module), but there are no results for the following commands:
ld4004:/home # virsh net-dhcp-leases default
Expiry Time MAC address Protocol IP address Hostname Client ID or DUID
-------------------------------------------------------------------------------------------------------------------
ld4004:/home # virsh domifaddr --source lease vm02-fai
Name MAC address Protocol Address
-------------------------------------------------------------------------------
ld4004:/home # virsh list
Id Name State
----------------------------------------------------
1 vm02-fai running
dnsmasq is running:
ld4004:/home # netstat -nulpd | grep dnsmasq
udp 0 0 192.168.33.1:53 0.0.0.0:* 10318/dnsmasq
udp 0 0 192.168.100.1:53 0.0.0.0:* 20145/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 20145/dnsmasq
How can I fix this issue?
THX
7 years, 1 month