<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I believe this problem also exists in F25.</p>
<p>There are upsides to having a vm do the networking and I have
used that scheme for something like a decade.</p>
<p>The point is that libvirt should start up and start its VM's
correctly.</p>
<p>If you cannot depend on the system starting correctly then very
quickly you cannot depend on the system at all and then your
backing out to your switches and network cables and power supplies
.....</p>
<p>My guess is that its related to libvirt trying to start before
the xen subsystems have come up.</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 07/26/2017 09:32 AM, Dominik Psenner
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+0K2P-_irhVSB2hWszgMasNRz98jw+xenn+zE_LjV28gdoCKQ@mail.gmail.com">
<div dir="auto">Note that this does not help with the original
problem but points out a critical design flaw.
<div dir="auto"><br>
<div dir="auto">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).</div>
<div dir="auto"><br>
</div>
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.<br>
<div class="gmail_extra" dir="auto"><br>
<div class="gmail_quote">On 26 Jul 2017 12:50 p.m., "G
Crowe" <<a href="mailto:gclvirtlist@crowie.net"
moz-do-not-send="true">gclvirtlist@crowie.net</a>>
wrote:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Jim,<br>
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.<br>
<br>
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).<br>
<br>
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).<br>
<br>
Unfortunatley there is nothing appearing in the libvirtd
log over a reboot to help diagnose.<br>
<br>
Any suggestions?<br>
<br>
<br>
Thank you<br>
<br>
GC<br>
<br>
<br>
[root@testhost ~]# systemctl status libvirtd<br>
● libvirtd.service - Virtualization daemon<br>
Loaded: loaded (/usr/lib/systemd/system/libvi<wbr>rtd.service;
enabled; vendor preset: enabled)<br>
Active: inactive (dead)<br>
Docs: <a class="moz-txt-link-freetext" href="man:libvirtd(8)">man:libvirtd(8)</a><br>
<a href="http://libvirt.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://libvirt.org</a>
<div class="elided-text"><br>
<br>
<br>
<br>
<br>
On 25/07/2017 1:20 AM, Jim Fehlig wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 07/23/2017 04:25 PM, G Crowe wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
I am trying to upgrade my Xen host (Dom0) and
are having troubles getting it to work.<br>
<br>
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).<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
</blockquote>
<br>
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<br>
<br>
<a href="http://libvirt.org/logging.html"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://libvirt.org/logging.htm<wbr>l</a><br>
<br>
Regards,<br>
Jim<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
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).<br>
<br>
Fedora 21 uses kernel 3.19.3 and xen 4.4.1<br>
Fedora 26 uses kernel 4.11.8 and xen 4.8.1<br>
<br>
I have tried following the info on <a
href="https://wiki.xen.org/wiki/Fedora_Host_Installation"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.xen.org/wiki/Fedo<wbr>ra_Host_Installation</a>
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)<br>
<br>
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.<br>
<br>
<br>
Thanks<br>
<br>
GC<br>
<br>
------------------------------<wbr>-----------------<br>
On the fedora 26 box.....<br>
# xl info<br>
host : family.mydomain.mytld<br>
release : 4.11.8-300.fc26.x86_64<br>
version : #1 SMP Thu Jun 29
20:09:48 UTC 2017<br>
machine : x86_64<br>
nr_cpus : 4<br>
max_cpu_id : 3<br>
nr_nodes : 1<br>
cores_per_socket : 4<br>
threads_per_core : 1<br>
cpu_mhz : 2712<br>
hw_caps :
b7ebfbff:77faf3bf:2c100800:000<wbr>00121:0000000f:009c67af:000000<wbr>00:00000100<br>
virt_caps : hvm hvm_directio<br>
total_memory : 8072<br>
free_memory : 128<br>
sharing_freed_memory : 0<br>
sharing_used_memory : 0<br>
outstanding_claims : 0<br>
free_cpus : 0<br>
xen_major : 4<br>
xen_minor : 8<br>
xen_extra : .1<br>
xen_version : 4.8.1<br>
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<br>
xen_scheduler : credit<br>
xen_pagesize : 4096<br>
platform_params :
virt_start=0xffff800000000000<br>
xen_changeset :<br>
xen_commandline : placeholder<br>
cc_compiler : gcc (GCC) 7.0.1 20170421
(Red Hat 7.0.1-0.15)<br>
cc_compile_by : mockbuild<br>
cc_compile_domain : [unknown]<br>
cc_compile_date : Wed May 3 21:23:49 UTC
2017<br>
build_id :
1c6e5a40165e05837303942b54757a<wbr>e1f2d5033d<br>
xend_config_format : 4<br>
<br>
------------------------------<wbr>---------------------<br>
# cat vmtest.xml<br>
<domain type='xen' id='21'><br>
<name>testVM</name><br>
<memory unit='KiB'>2097152</memory><br>
<currentMemory
unit='KiB'>2097152</currentMem<wbr>ory><br>
<vcpu placement='static'>1</vcpu><br>
<os><br>
<type arch='x86_64'
machine='xenfv'>hvm</type><br>
<loader type='rom'>/usr/lib/xen/boot/h<wbr>vmloader</loader><br>
<boot dev='network'/><br>
</os><br>
<features><br>
<acpi/><br>
<apic/><br>
<pae/><br>
</features><br>
<clock offset='variable' adjustment='0'
basis='utc'/><br>
<on_poweroff>destroy</on_powe<wbr>roff><br>
<on_reboot>restart</on_<wbr>reboot><br>
<on_crash>restart</on_crash><br>
<devices><br>
<interface type='bridge'><br>
<mac address='02:02:00:03:00:00'/><br>
<source bridge='enp1s0'/><br>
<script path='vif-bridge'/><br>
</interface><br>
<serial type='pty'><br>
<target port='0'/><br>
</serial><br>
<console type='pty'><br>
<target type='serial' port='0'/><br>
</console><br>
<input type='mouse' bus='ps2'/><br>
<input type='keyboard' bus='ps2'/><br>
<graphics type='vnc' port='5901'
autoport='no' listen='192.168.131.54'><br>
<listen type='address'
address='192.168.131.54'/><br>
</graphics><br>
</devices><br>
</domain><br>
<br>
------------------------------<wbr>--------<br>
<br>
______________________________<wbr>_________________<br>
libvirt-users mailing list<br>
<a href="mailto:libvirt-users@redhat.com"
target="_blank" moz-do-not-send="true">libvirt-users@redhat.com</a><br>
<a
href="https://www.redhat.com/mailman/listinfo/libvirt-users"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://www.redhat.com/mailman<wbr>/listinfo/libvirt-users</a><br>
<br>
</blockquote>
<br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
libvirt-users mailing list<br>
<a href="mailto:libvirt-users@redhat.com"
target="_blank" moz-do-not-send="true">libvirt-users@redhat.com</a><br>
<a
href="https://www.redhat.com/mailman/listinfo/libvirt-users"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://www.redhat.com/mailman<wbr>/listinfo/libvirt-users</a></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
libvirt-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:libvirt-users@redhat.com">libvirt-users@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/libvirt-users">https://www.redhat.com/mailman/listinfo/libvirt-users</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Alvin Starr || land: (905)513-7688
Netvel Inc. || Cell: (416)806-0133
<a class="moz-txt-link-abbreviated" href="mailto:alvin@netvel.net">alvin@netvel.net</a> ||
</pre>
</body>
</html>