10:37 p.m.
Hi all,
After updating Clear Linux from 6970 to 7090, I was unable to start KVM
VMs (without OpenStack) as virsh gave the following error message:
"virsh could not find capabilities for arch=x86_64"
I then decided to reinstall Clear Linux with latest (7090) installer
but this doesn't solve the problem:
$ sudo virsh define VM1000.xml
error: Failed to define domain from VM1000.xml
error: invalid argument: could not find capabilities for arch=x86_64
Bellow are a few commands with their output:
$ cat /usr/share/clear/version
7090
$ sudo swupd check-update
swupd-client software update checker 3.3.0
Copyright (C) 2012-2016 Intel Corporation
Querying server version.
Attempting to download version string to memory
There are no updates available
$ ls -1 /usr/share/clear/bundles
kernel-native
kvm-host
os-core
os-core-update
os-utils
os-utils-gui
$ systemctl status libvirtd
* libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; disabled;
vendor preset: disabled)
Active: active (running) since Thu 2016-03-
31 21:49:44 UTC; 6min ago
Docs: man:libvirtd(8)
http://li
bvirt.org
Main PID: 340 (libvirtd)
CGroup:
/system.slice/libvirtd.service
`-340 /usr/bin/libvirtd
Warning: Journal has been rotated since unit was started. Log output is incomplete or
unavailable.
$ sudo virsh version
Compiled against library: livirt 1.3.2
Using library: libvirt 1.3.2
Using API: QEMU 1.3.2
error: failed to get the hypervisor version
error: internal error: Cannot find suitable emulator for x86_64
$ sudo virsh capabilities
(Output available as an attachement: 'virsh-capabilities.txt')
Any suggestions appreciated.
-- FB
9:20 p.m.
Hi,
Was this working before with this VM1000.xml file?
I’m attaching a domain example file. I’m also testing with you domain file and will be
back with you.
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
On 3/31/16, 4:37 PM, "Dev on behalf of fb.dev.clx"
<dev-bounces(a)lists.clearlinux.org on behalf of fb.dev.clx(a)gmail.com> wrote:
Hi all,
After updating Clear Linux from 6970 to 7090, I was unable to start KVM
VMs (without OpenStack) as virsh gave the following error message:
"virsh could not find capabilities for arch=x86_64"
I then decided to reinstall Clear Linux with latest (7090) installer
but this doesn't solve the problem:
$ sudo virsh define VM1000.xml
error: Failed to define domain from VM1000.xml
error: invalid argument: could not find capabilities for arch=x86_64
Bellow are a few commands with their output:
$ cat /usr/share/clear/version
7090
$ sudo swupd check-update
swupd-client software update checker 3.3.0
Copyright (C) 2012-2016 Intel Corporation
Querying server version.
Attempting to download version string to memory
There are no updates available
$ ls -1 /usr/share/clear/bundles
kernel-native
kvm-host
os-core
os-core-update
os-utils
os-utils-gui
$ systemctl status libvirtd
* libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; disabled;
vendor preset: disabled)
Active: active (running) since Thu 2016-03-
31 21:49:44 UTC; 6min ago
Docs: man:libvirtd(8)
http://li
bvirt.org
Main PID: 340 (libvirtd)
CGroup:
/system.slice/libvirtd.service
`-340 /usr/bin/libvirtd
Warning: Journal has been rotated since unit was started. Log output is incomplete or
unavailable.
$ sudo virsh version
Compiled against library: livirt 1.3.2
Using library: libvirt 1.3.2
Using API: QEMU 1.3.2
error: failed to get the hypervisor version
error: internal error: Cannot find suitable emulator for x86_64
$ sudo virsh capabilities
(Output available as an attachement: 'virsh-capabilities.txt')
Any suggestions appreciated.
-- FB
10:39 p.m.
Hi,
VM1000.xml file used to work with Clear Linux 6970.
The domain example file CLRDomain.txt you've sent doesn't work either:
```
$ sudo virsh define CLRDomain.txt
error: Failed to define domain from CLRDomain.txt
error: invalid argument: could not find capabilities for domaintype=kvm
```
Regards,
-- FB
On Fri, 2016-04-01 at 21:20 +0000, Munoz, Obed N wrote:
Hi,
Was this working before with this VM1000.xml file?
I’m attaching a domain example file. I’m also testing with you domain
file and will be back with you.
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
On 3/31/16, 4:37 PM, "Dev on behalf of fb.dev.clx" <dev-bounces@lists
.clearlinux.org on behalf of fb.dev.clx(a)gmail.com> wrote:
>
> Hi all,
>
> After updating Clear Linux from 6970 to 7090, I was unable to start
> KVM
> VMs (without OpenStack) as virsh gave the following error message:
>
> "virsh could not find capabilities for arch=x86_64"
>
> I then decided to reinstall Clear Linux with latest (7090)
> installer
> but this doesn't solve the problem:
>
> $ sudo virsh define VM1000.xml
> error: Failed to define domain from VM1000.xml
> error: invalid argument: could not find capabilities for
> arch=x86_64
>
>
> Bellow are a few commands with their output:
>
> $ cat /usr/share/clear/version
> 7090
>
> $ sudo swupd check-update
> swupd-client software update checker 3.3.0
> Copyright (C) 2012-2016 Intel Corporation
>
> Querying server version.
> Attempting to download version string to memory
> There are no updates available
>
>
> $ ls -1 /usr/share/clear/bundles
> kernel-native
> kvm-host
> os-core
> os-core-update
> os-utils
> os-utils-gui
>
>
> $ systemctl status libvirtd
> * libvirtd.service - Virtualization daemon
>
> Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; disabled;
> vendor preset: disabled)
> Active: active (running) since Thu 2016-03-
> 31 21:49:44 UTC; 6min ago
> Docs: man:libvirtd(8)
> http://li
> bvirt.org
> Main PID: 340 (libvirtd)
> CGroup:
> /system.slice/libvirtd.service
> `-340 /usr/bin/libvirtd
>
> Warning: Journal has been rotated since unit was started. Log
> output is incomplete or unavailable.
>
>
> $ sudo virsh version
> Compiled against library: livirt 1.3.2
> Using library: libvirt 1.3.2
> Using API: QEMU 1.3.2
> error: failed to get the hypervisor version
> error: internal error: Cannot find suitable emulator for x86_64
>
>
> $ sudo virsh capabilities
> (Output available as an attachement: 'virsh-capabilities.txt')
>
>
> Any suggestions appreciated.
>
> -- FB
11:37 p.m.
Hi,
I did some testing with your domain file and made it work on latest release 7160 (I
attached my domain file)
I just needed to remove the smx feature from it (it’s not available in my dev box).
Could you try to upgrade your box, the latest available version is the 7160
- We’re verifying what’s the root cause in 7090 release
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
On 4/1/16, 4:39 PM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
Hi,
VM1000.xml file used to work with Clear Linux 6970.
The domain example file CLRDomain.txt you've sent doesn't work either:
```
$ sudo virsh define CLRDomain.txt
error: Failed to define domain from CLRDomain.txt
error: invalid argument: could not find capabilities for domaintype=kvm
```
Regards,
-- FB
On Fri, 2016-04-01 at 21:20 +0000, Munoz, Obed N wrote:
> Hi,
>
> Was this working before with this VM1000.xml file?
>
> I’m attaching a domain example file. I’m also testing with you domain
> file and will be back with you.
>
>
> Regards,
> --
> Obed N Munoz
> Cloud Engineer @ ClearLinux Project
> Open Source Technology Center
>
>
>
>
>
>
>
> On 3/31/16, 4:37 PM, "Dev on behalf of fb.dev.clx" <dev-bounces@lists
> .clearlinux.org on behalf of fb.dev.clx(a)gmail.com> wrote:
>
> >
> > Hi all,
> >
> > After updating Clear Linux from 6970 to 7090, I was unable to start
> > KVM
> > VMs (without OpenStack) as virsh gave the following error message:
> >
> > "virsh could not find capabilities for arch=x86_64"
> >
> > I then decided to reinstall Clear Linux with latest (7090)
> > installer
> > but this doesn't solve the problem:
> >
> > $ sudo virsh define VM1000.xml
> > error: Failed to define domain from VM1000.xml
> > error: invalid argument: could not find capabilities for
> > arch=x86_64
> >
> >
> > Bellow are a few commands with their output:
> >
> > $ cat /usr/share/clear/version
> > 7090
> >
> > $ sudo swupd check-update
> > swupd-client software update checker 3.3.0
> > Copyright (C) 2012-2016 Intel Corporation
> >
> > Querying server version.
> > Attempting to download version string to memory
> > There are no updates available
> >
> >
> > $ ls -1 /usr/share/clear/bundles
> > kernel-native
> > kvm-host
> > os-core
> > os-core-update
> > os-utils
> > os-utils-gui
> >
> >
> > $ systemctl status libvirtd
> > * libvirtd.service - Virtualization daemon
> >
> > Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; disabled;
> > vendor preset: disabled)
> > Active: active (running) since Thu 2016-03-
> > 31 21:49:44 UTC; 6min ago
> > Docs: man:libvirtd(8)
> > http://li
> > bvirt.org
> > Main PID: 340 (libvirtd)
> > CGroup:
> > /system.slice/libvirtd.service
> > `-340 /usr/bin/libvirtd
> >
> > Warning: Journal has been rotated since unit was started. Log
> > output is incomplete or unavailable.
> >
> >
> > $ sudo virsh version
> > Compiled against library: livirt 1.3.2
> > Using library: libvirt 1.3.2
> > Using API: QEMU 1.3.2
> > error: failed to get the hypervisor version
> > error: internal error: Cannot find suitable emulator for x86_64
> >
> >
> > $ sudo virsh capabilities
> > (Output available as an attachement: 'virsh-capabilities.txt')
> >
> >
> > Any suggestions appreciated.
> >
> > -- FB
12:29 a.m.
Hi,
I've upgraded from 7090 to 7160 without any success: both domain files
don't work and error messages are same as before.
Regards,
-- FB
On Fri, 2016-04-01 at 23:37 +0000, Munoz, Obed N wrote:
Hi,
I did some testing with your domain file and made it work on latest
release 7160 (I attached my domain file)
I just needed to remove the smx feature from it (it’s not available
in my dev box).
Could you try to upgrade your box, the latest available version is
the 7160
- We’re verifying what’s the root cause in 7090 release
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
On 4/1/16, 4:39 PM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
>
> Hi,
>
> VM1000.xml file used to work with Clear Linux 6970.
>
> The domain example file CLRDomain.txt you've sent doesn't work
> either:
> ```
> $ sudo virsh define CLRDomain.txt
> error: Failed to define domain from CLRDomain.txt
> error: invalid argument: could not find capabilities for
> domaintype=kvm
> ```
>
> Regards,
>
> -- FB
>
>
> On Fri, 2016-04-01 at 21:20 +0000, Munoz, Obed N wrote:
> >
> > Hi,
> >
> > Was this working before with this VM1000.xml file?
> >
> > I’m attaching a domain example file. I’m also testing with you
> > domain
> > file and will be back with you.
> >
> >
> > Regards,
> > --
> > Obed N Munoz
> > Cloud Engineer @ ClearLinux Project
> > Open Source Technology Center
> >
> >
> >
> >
> >
> >
> >
> > On 3/31/16, 4:37 PM, "Dev on behalf of fb.dev.clx" <dev-bounces@l
> > ists
> > .clearlinux.org on behalf of fb.dev.clx(a)gmail.com> wrote:
> >
> > >
> > >
> > > Hi all,
> > >
> > > After updating Clear Linux from 6970 to 7090, I was unable to
> > > start
> > > KVM
> > > VMs (without OpenStack) as virsh gave the following error
> > > message:
> > >
> > > "virsh could not find capabilities for arch=x86_64"
> > >
> > > I then decided to reinstall Clear Linux with latest (7090)
> > > installer
> > > but this doesn't solve the problem:
> > >
> > > $ sudo virsh define VM1000.xml
> > > error: Failed to define domain from VM1000.xml
> > > error: invalid argument: could not find capabilities for
> > > arch=x86_64
> > >
> > >
> > > Bellow are a few commands with their output:
> > >
> > > $ cat /usr/share/clear/version
> > > 7090
> > >
> > > $ sudo swupd check-update
> > > swupd-client software update checker 3.3.0
> > > Copyright (C) 2012-2016 Intel Corporation
> > >
> > > Querying server version.
> > > Attempting to download version string to memory
> > > There are no updates available
> > >
> > >
> > > $ ls -1 /usr/share/clear/bundles
> > > kernel-native
> > > kvm-host
> > > os-core
> > > os-core-update
> > > os-utils
> > > os-utils-gui
> > >
> > >
> > > $ systemctl status libvirtd
> > > * libvirtd.service - Virtualization daemon
> > >
> > > Loaded: loaded (/usr/lib/systemd/system/libvirtd.service;
> > > disabled;
> > > vendor preset: disabled)
> > > Active: active (running) since Thu 2016-03-
> > > 31 21:49:44 UTC; 6min ago
> > > Docs: man:libvirtd(8)
> > > http://li
> > > bvirt.org
> > > Main PID: 340 (libvirtd)
> > > CGroup:
> > > /system.slice/libvirtd.service
> > > `-340 /usr/bin/libvirtd
> > >
> > > Warning: Journal has been rotated since unit was started. Log
> > > output is incomplete or unavailable.
> > >
> > >
> > > $ sudo virsh version
> > > Compiled against library: livirt 1.3.2
> > > Using library: libvirt 1.3.2
> > > Using API: QEMU 1.3.2
> > > error: failed to get the hypervisor version
> > > error: internal error: Cannot find suitable emulator for x86_64
> > >
> > >
> > > $ sudo virsh capabilities
> > > (Output available as an attachement: 'virsh-capabilities.txt')
> > >
> > >
> > > Any suggestions appreciated.
> > >
> > > -- FB
4:38 a.m.
Hi,
I cannot replicate the issue. I just downloaded a new image from:
https://download.clearlinux.org/image/clear-7160-live.img.xz
and it worked. I had to tested this as a VM inside a VM and had to remove some CPU
features. But after that, everything worked. I’m attaching the domain XML I used. And
below is the output of domain start and qemu command line.
Other thing you could try is the below command, in order to verify that there are not
corrupted files in your system.
# swupd verify --fix
##############################################################
root@clr /var/lib/swupd # EDITOR=emacs virsh start VM1000.obed
Domain VM1000.obed started
root@clr /var/lib/swupd # virsh list
Id Name State
----------------------------------------------------
3 VM1000.obed running
root@clr /var/lib/swupd # ps aux | grep qemu
qemu 29974 6.1 0.7 4814144 57624 ? Sl 04:28 0:01
/usr/bin/qemu-system-x86_64 -name VM1000.obed -S -machine pc-i440fx-2.5,accel=kvm,usb=off
-cpu
SandyBridge,+invpcid,+erms,+bmi2,+smep,+avx2,+bmi1,+fsgsbase,+abm,+pdpe1gb,+rdrand,+f16c,+osxsave,+movbe,+pcid,+fma,+vmx,+ht,+ss,+vme
-m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid
d1810229-895d-46e9-ad6b-4199c78b3895 -no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-VM1000.obed/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot
order=c,menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
ahci,id=sata0,bus=pci.0,addr=0x8 -device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive
file=/tmp/nanolinux64-1.3.iso,format=raw,if=none,media=cdrom,id=drive-sata0-0-1,readonly=on
-device ide-cd,bus=sata0.1,drive=drive-sata0-0-1,id=sata0-0-1 -netdev
tap,fd=21,id=hostnet0,vhost=on,vhostfd=22 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:74:6a:6b,bus=pci.0,addr=0x3 -chardev
pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev
spicevmc,id=charchannel0,name=vdagent -device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
-device usb-tablet,id=input0 -spice
port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -device
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2
-device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on
root 29989 0.0 0.0 3088 936 pts/0 S+ 04:28 0:00 grep qemu
root@clr /var/lib/swupd # cat /usr/share/clear/version
7160
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
On 4/1/16, 6:29 PM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
Hi,
I've upgraded from 7090 to 7160 without any success: both domain files
don't work and error messages are same as before.
Regards,
-- FB
On Fri, 2016-04-01 at 23:37 +0000, Munoz, Obed N wrote:
> Hi,
>
> I did some testing with your domain file and made it work on latest
> release 7160 (I attached my domain file)
> I just needed to remove the smx feature from it (it’s not available
> in my dev box).
>
> Could you try to upgrade your box, the latest available version is
> the 7160
> - We’re verifying what’s the root cause in 7090 release
>
> Regards,
> --
> Obed N Munoz
> Cloud Engineer @ ClearLinux Project
> Open Source Technology Center
>
>
>
>
>
>
>
> On 4/1/16, 4:39 PM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
>
> >
> > Hi,
> >
> > VM1000.xml file used to work with Clear Linux 6970.
> >
> > The domain example file CLRDomain.txt you've sent doesn't work
> > either:
> > ```
> > $ sudo virsh define CLRDomain.txt
> > error: Failed to define domain from CLRDomain.txt
> > error: invalid argument: could not find capabilities for
> > domaintype=kvm
> > ```
> >
> > Regards,
> >
> > -- FB
> >
> >
> > On Fri, 2016-04-01 at 21:20 +0000, Munoz, Obed N wrote:
> > >
> > > Hi,
> > >
> > > Was this working before with this VM1000.xml file?
> > >
> > > I’m attaching a domain example file. I’m also testing with you
> > > domain
> > > file and will be back with you.
> > >
> > >
> > > Regards,
> > > --
> > > Obed N Munoz
> > > Cloud Engineer @ ClearLinux Project
> > > Open Source Technology Center
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 3/31/16, 4:37 PM, "Dev on behalf of fb.dev.clx"
<dev-bounces@l
> > > ists
> > > .clearlinux.org on behalf of fb.dev.clx(a)gmail.com> wrote:
> > >
> > > >
> > > >
> > > > Hi all,
> > > >
> > > > After updating Clear Linux from 6970 to 7090, I was unable to
> > > > start
> > > > KVM
> > > > VMs (without OpenStack) as virsh gave the following error
> > > > message:
> > > >
> > > > "virsh could not find capabilities for arch=x86_64"
> > > >
> > > > I then decided to reinstall Clear Linux with latest (7090)
> > > > installer
> > > > but this doesn't solve the problem:
> > > >
> > > > $ sudo virsh define VM1000.xml
> > > > error: Failed to define domain from VM1000.xml
> > > > error: invalid argument: could not find capabilities for
> > > > arch=x86_64
> > > >
> > > >
> > > > Bellow are a few commands with their output:
> > > >
> > > > $ cat /usr/share/clear/version
> > > > 7090
> > > >
> > > > $ sudo swupd check-update
> > > > swupd-client software update checker 3.3.0
> > > > Copyright (C) 2012-2016 Intel Corporation
> > > >
> > > > Querying server version.
> > > > Attempting to download version string to memory
> > > > There are no updates available
> > > >
> > > >
> > > > $ ls -1 /usr/share/clear/bundles
> > > > kernel-native
> > > > kvm-host
> > > > os-core
> > > > os-core-update
> > > > os-utils
> > > > os-utils-gui
> > > >
> > > >
> > > > $ systemctl status libvirtd
> > > > * libvirtd.service - Virtualization daemon
> > > >
> > > > Loaded: loaded (/usr/lib/systemd/system/libvirtd.service;
> > > > disabled;
> > > > vendor preset: disabled)
> > > > Active: active (running) since Thu 2016-03-
> > > > 31 21:49:44 UTC; 6min ago
> > > > Docs: man:libvirtd(8)
> > > > http://li
> > > > bvirt.org
> > > > Main PID: 340 (libvirtd)
> > > > CGroup:
> > > > /system.slice/libvirtd.service
> > > > `-340 /usr/bin/libvirtd
> > > >
> > > > Warning: Journal has been rotated since unit was started. Log
> > > > output is incomplete or unavailable.
> > > >
> > > >
> > > > $ sudo virsh version
> > > > Compiled against library: livirt 1.3.2
> > > > Using library: libvirt 1.3.2
> > > > Using API: QEMU 1.3.2
> > > > error: failed to get the hypervisor version
> > > > error: internal error: Cannot find suitable emulator for x86_64
> > > >
> > > >
> > > > $ sudo virsh capabilities
> > > > (Output available as an attachement:
'virsh-capabilities.txt')
> > > >
> > > >
> > > > Any suggestions appreciated.
> > > >
> > > > -- FB
1:35 p.m.
Hi,
Here is the output of the suggested command:
```
$ sudo swupd verify --fix
swupd-client software verify 3.3.0
Copyright (c) 2012-2016 Intel Corporation
Verifying version 7160
Attempting to download version string to memory
Starting download of remaining update content. This may take a while...
Finishing download of update content...
Adding any missing files
Fixing modified files
Hash mismatch for file: /usr/lib/firmware/car19170fw/GPL
fixed
Deleted /usr/share/defaults/sudo/sudoers.d
Inspected 81224 files
0 files were missing
1 files did not match
1 of 1 files were fixed
0 of 1 files were not fixed
1 files found which should be deleted
1 of 1 files were deleted
0 of 1 files were not deleted
Calling
post-update helper scripts.
Mounting boot partition with UUID=57bdc35d-
5487-32df-6397-48d23ce3bfcd
Installing new gummiboot binary... please
wait...
/usr/lib/gummiboot/gummibootx64.efi not found. Nothing to do.
In
stalling new systemd bootx binary... please wait...
systemd bootloader
update successful.
Fix successful
```
After reboot, I started to play again with the domain files without any
success: both domain files don't work and error messages are same as
before.
As it's the second time I'm stuck with a similar problem <https://lists
.clearlinux.org/pipermail/dev/2016-February/000201.html> and it seems
not reproducible for you, I'm going to reinstall Clear Linux with 7160
installer...
---------------------
NOTE: FYI, each time I run `swupd verify --fix`, the command says that
`/usr/share/defaults/sudo/sudoers.d` was deleted, but the directory
is still available:
```
$ ls -la /usr/share/defaults/sudo/sudoers.d
total 8
drwxr-xr-x 2 root root 4096 Mar 31 19:30 .
drwxr-xr-x 3 root root 4096 Mar 31 20:27 ..
```
---------------------
Regards,
-- FB
On Sat, 2016-04-02 at 04:38 +0000, Munoz, Obed N wrote:
Hi,
I cannot replicate the issue. I just downloaded a new image from: htt
ps://download.clearlinux.org/image/clear-7160-live.img.xz
and it worked. I had to tested this as a VM inside a VM and had to
remove some CPU features. But after that, everything worked. I’m
attaching the domain XML I used. And below is the output of domain
start and qemu command line.
Other thing you could try is the below command, in order to verify
that there are not corrupted files in your system.
# swupd verify --fix
##############################################################
root@clr /var/lib/swupd # EDITOR=emacs virsh start VM1000.obed
Domain VM1000.obed started
root@clr /var/lib/swupd # virsh list
Id Name State
----------------------------------------------------
3 VM1000.obed running
root@clr /var/lib/swupd # ps aux | grep qemu
qemu 29974 6.1 0.7 4814144 57624 ? Sl 04:28 0:01
/usr/bin/qemu-system-x86_64 -name VM1000.obed -S -machine pc-i440fx-
2.5,accel=kvm,usb=off -cpu
SandyBridge,+invpcid,+erms,+bmi2,+smep,+avx2,+bmi1,+fsgsbase,+abm,+pd
pe1gb,+rdrand,+f16c,+osxsave,+movbe,+pcid,+fma,+vmx,+ht,+ss,+vme -m
4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid
d1810229-895d-46e9-ad6b-4199c78b3895 -no-user-config -nodefaults
-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-
VM1000.obed/monitor.sock,server,nowait -mon
chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-
shutdown -boot order=c,menu=on,strict=on -device piix3-usb-
uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
ahci,id=sata0,bus=pci.0,addr=0x8 -device virtio-serial-pci,id=virtio-
serial0,bus=pci.0,addr=0x5 -drive file=/tmp/nanolinux64-
1.3.iso,format=raw,if=none,media=cdrom,id=drive-sata0-0-1,readonly=on
-device ide-cd,bus=sata0.1,drive=drive-sata0-0-1,id=sata0-0-1 -netdev
tap,fd=21,id=hostnet0,vhost=on,vhostfd=22 -device virtio-net-
pci,netdev=hostnet0,id=net0,mac=52:54:00:74:6a:6b,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device isa-
serial,chardev=charserial0,id=serial0 -chardev
spicevmc,id=charchannel0,name=vdagent -device
virtserialport,bus=virtio-
serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice
.0 -device usb-tablet,id=input0 -spice
port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on
-device qxl-
vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=p
ci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-
balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on
root 29989 0.0 0.0 3088 936 pts/0 S+ 04:28 0:00 grep
qemu
root@clr /var/lib/swupd # cat /usr/share/clear/version
7160
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
On 4/1/16, 6:29 PM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
>
> Hi,
>
> I've upgraded from 7090 to 7160 without any success: both domain
> files
> don't work and error messages are same as before.
>
> Regards,
>
> -- FB
>
> On Fri, 2016-04-01 at 23:37 +0000, Munoz, Obed N wrote:
> >
> > Hi,
> >
> > I did some testing with your domain file and made it work on
> > latest
> > release 7160 (I attached my domain file)
> > I just needed to remove the smx feature from it (it’s not
> > available
> > in my dev box).
> >
> > Could you try to upgrade your box, the latest available version
> > is
> > the 7160
> > - We’re verifying what’s the root cause in 7090 release
> >
> > Regards,
> > --
> > Obed N Munoz
> > Cloud Engineer @ ClearLinux Project
> > Open Source Technology Center
> >
> >
> >
> >
> >
> >
> >
> > On 4/1/16, 4:39 PM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
> >
> > >
> > >
> > > Hi,
> > >
> > > VM1000.xml file used to work with Clear Linux 6970.
> > >
> > > The domain example file CLRDomain.txt you've sent doesn't work
> > > either:
> > > ```
> > > $ sudo virsh define CLRDomain.txt
> > > error: Failed to define domain from CLRDomain.txt
> > > error: invalid argument: could not find capabilities for
> > > domaintype=kvm
> > > ```
> > >
> > > Regards,
> > >
> > > -- FB
> > >
> > >
> > > On Fri, 2016-04-01 at 21:20 +0000, Munoz, Obed N wrote:
> > > >
> > > >
> > > > Hi,
> > > >
> > > > Was this working before with this VM1000.xml file?
> > > >
> > > > I’m attaching a domain example file. I’m also testing with
> > > > you
> > > > domain
> > > > file and will be back with you.
> > > >
> > > >
> > > > Regards,
> > > > --
> > > > Obed N Munoz
> > > > Cloud Engineer @ ClearLinux Project
> > > > Open Source Technology Center
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On 3/31/16, 4:37 PM, "Dev on behalf of fb.dev.clx"
<dev-bounc
> > > > es@l
> > > > ists
> > > > .clearlinux.org on behalf of fb.dev.clx(a)gmail.com> wrote:
> > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi all,
> > > > >
> > > > > After updating Clear Linux from 6970 to 7090, I was unable
> > > > > to
> > > > > start
> > > > > KVM
> > > > > VMs (without OpenStack) as virsh gave the following error
> > > > > message:
> > > > >
> > > > > "virsh could not find capabilities for
arch=x86_64"
> > > > >
> > > > > I then decided to reinstall Clear Linux with latest (7090)
> > > > > installer
> > > > > but this doesn't solve the problem:
> > > > >
> > > > > $ sudo virsh define VM1000.xml
> > > > > error: Failed to define domain from VM1000.xml
> > > > > error: invalid argument: could not find capabilities for
> > > > > arch=x86_64
> > > > >
> > > > >
> > > > > Bellow are a few commands with their output:
> > > > >
> > > > > $ cat /usr/share/clear/version
> > > > > 7090
> > > > >
> > > > > $ sudo swupd check-update
> > > > > swupd-client software update checker 3.3.0
> > > > > Copyright (C) 2012-2016 Intel Corporation
> > > > >
> > > > > Querying server version.
> > > > > Attempting to download version string to memory
> > > > > There are no updates available
> > > > >
> > > > >
> > > > > $ ls -1 /usr/share/clear/bundles
> > > > > kernel-native
> > > > > kvm-host
> > > > > os-core
> > > > > os-core-update
> > > > > os-utils
> > > > > os-utils-gui
> > > > >
> > > > >
> > > > > $ systemctl status libvirtd
> > > > > * libvirtd.service - Virtualization daemon
> > > > >
> > > > > Loaded: loaded (/usr/lib/systemd/system/libvirtd.service;
> > > > > disabled;
> > > > > vendor preset: disabled)
> > > > > Active: active (running) since Thu 2016-03-
> > > > > 31 21:49:44 UTC; 6min ago
> > > > > Docs: man:libvirtd(8)
> > > > > http://li
> > > > > bvirt.org
> > > > > Main PID: 340 (libvirtd)
> > > > > CGroup:
> > > > > /system.slice/libvirtd.service
> > > > > `-340 /usr/bin/libvirtd
> > > > >
> > > > > Warning: Journal has been rotated since unit was started.
> > > > > Log
> > > > > output is incomplete or unavailable.
> > > > >
> > > > >
> > > > > $ sudo virsh version
> > > > > Compiled against library: livirt 1.3.2
> > > > > Using library: libvirt 1.3.2
> > > > > Using API: QEMU 1.3.2
> > > > > error: failed to get the hypervisor version
> > > > > error: internal error: Cannot find suitable emulator for
> > > > > x86_64
> > > > >
> > > > >
> > > > > $ sudo virsh capabilities
> > > > > (Output available as an attachement: 'virsh-
> > > > > capabilities.txt')
> > > > >
> > > > >
> > > > > Any suggestions appreciated.
> > > > >
> > > > > -- FB
5:10 p.m.
Hi,
This is what I've done so far after a successful newly Clear Linux rev.
7160 install as host in order to run virtual machines with QEMU-KVM
(independently of OpenStack):
1. logged in using the administrative (sudo) user created
at install time
2. ensured that there were not corrupted files in the system,
running `swupd verify --fix`. See:
<https://lists.clearlinux.org/pipermail/dev/2016-April/000249.html>
3. installed `kvm-host` bundle
4. ensured again that there were not corrupted files in the system,
running `swupd verify --fix`. See:
<https://lists.clearlinux.org/pipermail/dev/2016-April/000248.html>
5. checked `libvirtd` status with:
```
$ sudo systemclt status livirtd
```
6. started `libvirtd` as it is not enabled by default
```
$ sudo systemctl start libvirtd
```
7. checked `virsh` version
```
$ sudo virsh version
```
and got the following output:
```
Compiled against library: libvirt 1.3.2
Using library: libvirt 1.3.2
Using API: QEMU 1.3.2
error: failed to get the hypervisor version
error: internal error: Cannot find suitable emulator for x86_64
```
None of the domain files we have used so far work.
So, I'm still expecting any suggestions.
Regards,
-- FB
On Sat, 2016-04-02 at 07:35 -0600, fb.dev.clx wrote:
Hi,
Here is the output of the suggested command:
```
$ sudo swupd verify --fix
swupd-client software verify 3.3.0
Copyright (c) 2012-2016 Intel Corporation
Verifying version 7160
Attempting to download version string to memory
Starting download of remaining update content. This may take a
while...
Finishing download of update content...
Adding any missing files
Fixing modified files
Hash mismatch for file: /usr/lib/firmware/car19170fw/GPL
fixed
Deleted /usr/share/defaults/sudo/sudoers.d
Inspected 81224 files
0 files were missing
1 files did not match
1 of 1 files were fixed
0 of 1 files were not fixed
1 files found which should be deleted
1 of 1 files were deleted
0 of 1 files were not deleted
Calling
post-update helper scripts.
Mounting boot partition with UUID=57bdc35d-
5487-32df-6397-48d23ce3bfcd
Installing new gummiboot binary... please
wait...
/usr/lib/gummiboot/gummibootx64.efi not found. Nothing to do.
In
stalling new systemd bootx binary... please wait...
systemd bootloader
update successful.
Fix successful
```
After reboot, I started to play again with the domain files without
any
success: both domain files don't work and error messages are same as
before.
As it's the second time I'm stuck with a similar problem <https://lis
ts
.clearlinux.org/pipermail/dev/2016-February/000201.html> and it seems
not reproducible for you, I'm going to reinstall Clear Linux with
7160
installer...
---------------------
NOTE: FYI, each time I run `swupd verify --fix`, the command says
that
`/usr/share/defaults/sudo/sudoers.d` was deleted, but the directory
is still available:
```
$ ls -la /usr/share/defaults/sudo/sudoers.d
total 8
drwxr-xr-x 2 root root 4096 Mar 31 19:30 .
drwxr-xr-x 3 root root 4096 Mar 31 20:27 ..
```
---------------------
Regards,
-- FB
On Sat, 2016-04-02 at 04:38 +0000, Munoz, Obed N wrote:
>
> Hi,
>
> I cannot replicate the issue. I just downloaded a new image from:
> htt
> ps://download.clearlinux.org/image/clear-7160-live.img.xz
> and it worked. I had to tested this as a VM inside a VM and had to
> remove some CPU features. But after that, everything worked. I’m
> attaching the domain XML I used. And below is the output of domain
> start and qemu command line.
>
> Other thing you could try is the below command, in order to verify
> that there are not corrupted files in your system.
>
> # swupd verify --fix
>
>
> ##############################################################
>
> root@clr /var/lib/swupd # EDITOR=emacs virsh start VM1000.obed
> Domain VM1000.obed started
>
> root@clr /var/lib/swupd # virsh list
> Id Name State
> ----------------------------------------------------
> 3 VM1000.obed running
>
> root@clr /var/lib/swupd # ps aux | grep qemu
> qemu 29974 6.1 0.7 4814144 57624 ? Sl 04:28 0:01
> /usr/bin/qemu-system-x86_64 -name VM1000.obed -S -machine pc-
> i440fx-
> 2.5,accel=kvm,usb=off -cpu
> SandyBridge,+invpcid,+erms,+bmi2,+smep,+avx2,+bmi1,+fsgsbase,+abm,+
> pd
> pe1gb,+rdrand,+f16c,+osxsave,+movbe,+pcid,+fma,+vmx,+ht,+ss,+vme -m
> 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid
> d1810229-895d-46e9-ad6b-4199c78b3895 -no-user-config -nodefaults
> -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-
> VM1000.obed/monitor.sock,server,nowait -mon
> chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-
> shutdown -boot order=c,menu=on,strict=on -device piix3-usb-
> uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> ahci,id=sata0,bus=pci.0,addr=0x8 -device virtio-serial-
> pci,id=virtio-
> serial0,bus=pci.0,addr=0x5 -drive file=/tmp/nanolinux64-
> 1.3.iso,format=raw,if=none,media=cdrom,id=drive-sata0-0-
> 1,readonly=on
> -device ide-cd,bus=sata0.1,drive=drive-sata0-0-1,id=sata0-0-1
> -netdev
> tap,fd=21,id=hostnet0,vhost=on,vhostfd=22 -device virtio-net-
> pci,netdev=hostnet0,id=net0,mac=52:54:00:74:6a:6b,bus=pci.0,addr=0x
> 3
> -chardev pty,id=charserial0 -device isa-
> serial,chardev=charserial0,id=serial0 -chardev
> spicevmc,id=charchannel0,name=vdagent -device
> virtserialport,bus=virtio-
> serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spi
> ce
> .0 -device usb-tablet,id=input0 -spice
> port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on
> -device qxl-
> vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus
> =p
> ci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4
> -device
> hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-
> balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on
> root 29989 0.0 0.0 3088 936 pts/0 S+ 04:28 0:00
> grep
> qemu
>
>
> root@clr /var/lib/swupd # cat /usr/share/clear/version
> 7160
>
>
>
> Regards,
> --
> Obed N Munoz
> Cloud Engineer @ ClearLinux Project
> Open Source Technology Center
>
>
>
>
>
>
>
> On 4/1/16, 6:29 PM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
>
> >
> >
> > Hi,
> >
> > I've upgraded from 7090 to 7160 without any success: both domain
> > files
> > don't work and error messages are same as before.
> >
> > Regards,
> >
> > -- FB
> >
> > On Fri, 2016-04-01 at 23:37 +0000, Munoz, Obed N wrote:
> > >
> > >
> > > Hi,
> > >
> > > I did some testing with your domain file and made it work on
> > > latest
> > > release 7160 (I attached my domain file)
> > > I just needed to remove the smx feature from it (it’s not
> > > available
> > > in my dev box).
> > >
> > > Could you try to upgrade your box, the latest available version
> > > is
> > > the 7160
> > > - We’re verifying what’s the root cause in 7090 release
> > >
> > > Regards,
> > > --
> > > Obed N Munoz
> > > Cloud Engineer @ ClearLinux Project
> > > Open Source Technology Center
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 4/1/16, 4:39 PM, "fb.dev.clx" <fb.dev.clx(a)gmail.com>
wrote:
> > >
> > > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > VM1000.xml file used to work with Clear Linux 6970.
> > > >
> > > > The domain example file CLRDomain.txt you've sent doesn't
> > > > work
> > > > either:
> > > > ```
> > > > $ sudo virsh define CLRDomain.txt
> > > > error: Failed to define domain from CLRDomain.txt
> > > > error: invalid argument: could not find capabilities for
> > > > domaintype=kvm
> > > > ```
> > > >
> > > > Regards,
> > > >
> > > > -- FB
> > > >
> > > >
> > > > On Fri, 2016-04-01 at 21:20 +0000, Munoz, Obed N wrote:
> > > > >
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > Was this working before with this VM1000.xml file?
> > > > >
> > > > > I’m attaching a domain example file. I’m also testing with
> > > > > you
> > > > > domain
> > > > > file and will be back with you.
> > > > >
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Obed N Munoz
> > > > > Cloud Engineer @ ClearLinux Project
> > > > > Open Source Technology Center
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 3/31/16, 4:37 PM, "Dev on behalf of fb.dev.clx"
<dev-
> > > > > bounc
> > > > > es@l
> > > > > ists
> > > > > .clearlinux.org on behalf of fb.dev.clx(a)gmail.com> wrote:
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > After updating Clear Linux from 6970 to 7090, I was
> > > > > > unable
> > > > > > to
> > > > > > start
> > > > > > KVM
> > > > > > VMs (without OpenStack) as virsh gave the following error
> > > > > > message:
> > > > > >
> > > > > > "virsh could not find capabilities for
arch=x86_64"
> > > > > >
> > > > > > I then decided to reinstall Clear Linux with latest
> > > > > > (7090)
> > > > > > installer
> > > > > > but this doesn't solve the problem:
> > > > > >
> > > > > > $ sudo virsh define VM1000.xml
> > > > > > error: Failed to define domain from VM1000.xml
> > > > > > error: invalid argument: could not find capabilities for
> > > > > > arch=x86_64
> > > > > >
> > > > > >
> > > > > > Bellow are a few commands with their output:
> > > > > >
> > > > > > $ cat /usr/share/clear/version
> > > > > > 7090
> > > > > >
> > > > > > $ sudo swupd check-update
> > > > > > swupd-client software update checker 3.3.0
> > > > > > Copyright (C) 2012-2016 Intel Corporation
> > > > > >
> > > > > > Querying server version.
> > > > > > Attempting to download version string to memory
> > > > > > There are no updates available
> > > > > >
> > > > > >
> > > > > > $ ls -1 /usr/share/clear/bundles
> > > > > > kernel-native
> > > > > > kvm-host
> > > > > > os-core
> > > > > > os-core-update
> > > > > > os-utils
> > > > > > os-utils-gui
> > > > > >
> > > > > >
> > > > > > $ systemctl status libvirtd
> > > > > > * libvirtd.service - Virtualization daemon
> > > > > >
> > > > > > Loaded: loaded (/usr/lib/systemd/system/libvirtd.service;
> > > > > > disabled;
> > > > > > vendor preset: disabled)
> > > > > > Active: active (running) since Thu 2016-03-
> > > > > > 31 21:49:44 UTC; 6min ago
> > > > > > Docs: man:libvirtd(8)
> > > > > > http://li
> > > > > > bvirt.org
> > > > > > Main PID: 340 (libvirtd)
> > > > > > CGroup:
> > > > > > /system.slice/libvirtd.service
> > > > > > `-340 /usr/bin/libvirtd
> > > > > >
> > > > > > Warning: Journal has been rotated since unit was started.
> > > > > > Log
> > > > > > output is incomplete or unavailable.
> > > > > >
> > > > > >
> > > > > > $ sudo virsh version
> > > > > > Compiled against library: livirt 1.3.2
> > > > > > Using library: libvirt 1.3.2
> > > > > > Using API: QEMU 1.3.2
> > > > > > error: failed to get the hypervisor version
> > > > > > error: internal error: Cannot find suitable emulator for
> > > > > > x86_64
> > > > > >
> > > > > >
> > > > > > $ sudo virsh capabilities
> > > > > > (Output available as an attachement: 'virsh-
> > > > > > capabilities.txt')
> > > > > >
> > > > > >
> > > > > > Any suggestions appreciated.
> > > > > >
> > > > > > -- FB
5:15 p.m.
On 4/2/2016 10:10 AM, fb.dev.clx wrote:
error: failed to get the hypervisor version
error: internal error: Cannot find suitable emulator for x86_64
is there anything sounding suspicious in /var/log/libvirt/libvirtd.log ?
(taking a peek at this now, I normally don't use libvirt, it's too slow for my
taste)
5:42 p.m.
Hi,
It seems that there is no dedicated log file for `libvirtd` by default
and `journalctl` only reports already revealed command errors.
Is there a way to enable temporarily more verbose output for `libvirtd`
in `journalctl`?
(taking a peek at this now, I normally don't use libvirt,
it's too
slow for my taste)
So, what are you using for Windows VMs?
Regards,
-- FB
On Sat, 2016-04-02 at 10:15 -0700, Arjan van de Ven wrote:
> On 4/2/2016 10:10 AM, fb.dev.clx wrote:
> >
> > error: failed to get the hypervisor version
> > error: internal error: Cannot find suitable emulator for x86_64
> is there anything sounding suspicious
> in /var/log/libvirt/libvirtd.log ?
>
(taking a peek at this now, I normally don't use libvirt,
it's too
slow for my taste)
>
5:44 p.m.
On 4/2/2016 10:42 AM, fb.dev.clx wrote:
Hi,
It seems that there is no dedicated log file for `libvirtd` by default
and `journalctl` only reports already revealed command errors.
Is there a way to enable temporarily more verbose output for `libvirtd`
in `journalctl`?
> (taking a peek at this now, I normally don't use libvirt, it's too
> slow for my taste)
So, what are you using for Windows VMs?
I'll admit not to have started Windows VMs...
but normally I just use the qemu command line directly
some other work popped up to get done first, but will try things later in the day for
sure
5:55 p.m.
Hi,
You can add more debugging information by creating this file:
/etc/systemd/system/libvirtd.service.d/libvirtd.conf
With the above content:
[Service]
Environment="LIBVIRT_DEBUG=1"
You will need to restart the libvirtd service
# systemctl restart libvirtd
Then, you can see the detailed logging at:
# journalctl -u libvirtd -f
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
On 4/2/16, 11:42 AM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
Hi,
It seems that there is no dedicated log file for `libvirtd` by default
and `journalctl` only reports already revealed command errors.
Is there a way to enable temporarily more verbose output for `libvirtd`
in `journalctl`?
> (taking a peek at this now, I normally don't use libvirt, it's too
> slow for my taste)
So, what are you using for Windows VMs?
Regards,
-- FB
On Sat, 2016-04-02 at 10:15 -0700, Arjan van de Ven wrote:
> On 4/2/2016 10:10 AM, fb.dev.clx wrote:
> >
> > error: failed to get the hypervisor version
> > error: internal error: Cannot find suitable emulator for x86_64
> is there anything sounding suspicious
> in /var/log/libvirt/libvirtd.log ?
>
> (taking a peek at this now, I normally don't use libvirt, it's too
> slow for my taste)
>
5:57 p.m.
Fixing my type inline. :)
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
On 4/2/16, 11:55 AM, "Dev on behalf of Munoz, Obed N"
<dev-bounces(a)lists.clearlinux.org on behalf of obed.n.munoz(a)intel.com> wrote:
Hi,
You can add more debugging information by creating this file:
/etc/systemd/system/libvirtd.service.d/libvirtd.conf
With the above content:
With the below content:
[Service]
Environment="LIBVIRT_DEBUG=1"
You will need to restart the libvirtd service
# systemctl restart libvirtd
Then, you can see the detailed logging at:
# journalctl -u libvirtd -f
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
On 4/2/16, 11:42 AM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
>Hi,
>
>It seems that there is no dedicated log file for `libvirtd` by default
>and `journalctl` only reports already revealed command errors.
>
>Is there a way to enable temporarily more verbose output for `libvirtd`
>in `journalctl`?
>
>> (taking a peek at this now, I normally don't use libvirt, it's too
>> slow for my taste)
>So, what are you using for Windows VMs?
>
>Regards,
>
>-- FB
>
>
>
>On Sat, 2016-04-02 at 10:15 -0700, Arjan van de Ven wrote:
>> On 4/2/2016 10:10 AM, fb.dev.clx wrote:
>> >
>> > error: failed to get the hypervisor version
>> > error: internal error: Cannot find suitable emulator for x86_64
>> is there anything sounding suspicious
>> in /var/log/libvirt/libvirtd.log ?
>>
>> (taking a peek at this now, I normally don't use libvirt, it's too
>> slow for my taste)
>>
_______________________________________________
Dev mailing list
Dev(a)lists.clearlinux.org
https://lists.clearlinux.org/mailman/listinfo/dev
6:30 p.m.
Probably will need a systemctl daemon-reload, but systemd will likely advise you of that
anyway.
-Rob
On Apr 2, 2016, at 10:55 AM, Munoz, Obed N
<obed.n.munoz(a)intel.com> wrote:
Hi,
You can add more debugging information by creating this file:
/etc/systemd/system/libvirtd.service.d/libvirtd.conf
With the above content:
[Service]
Environment="LIBVIRT_DEBUG=1"
You will need to restart the libvirtd service
# systemctl restart libvirtd
Then, you can see the detailed logging at:
# journalctl -u libvirtd -f
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
> On 4/2/16, 11:42 AM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
>
> Hi,
>
> It seems that there is no dedicated log file for `libvirtd` by default
> and `journalctl` only reports already revealed command errors.
>
> Is there a way to enable temporarily more verbose output for `libvirtd`
> in `journalctl`?
>
>> (taking a peek at this now, I normally don't use libvirt, it's too
>> slow for my taste)
> So, what are you using for Windows VMs?
>
> Regards,
>
> -- FB
>
>
>
>> On Sat, 2016-04-02 at 10:15 -0700, Arjan van de Ven wrote:
>>> On 4/2/2016 10:10 AM, fb.dev.clx wrote:
>>>
>>> error: failed to get the hypervisor version
>>> error: internal error: Cannot find suitable emulator for x86_64
>> is there anything sounding suspicious
>> in /var/log/libvirt/libvirtd.log ?
>>
>> (taking a peek at this now, I normally don't use libvirt, it's too
>> slow for my taste)
_______________________________________________
Dev mailing list
Dev(a)lists.clearlinux.org
https://lists.clearlinux.org/mailman/listinfo/dev
7:18 p.m.
Hi all,
I will try later to add the `LIBVIRT_DEBUG=1` parameter.
Otherwise, is there a way to upgrade/downgrade Clear Linux to a
specific released <https://download.clearlinux.org/releases/> revision?
Maybe this could help us to find a fix more quickly.
Regards,
-- FB
On Sat, 2016-04-02 at 18:30 +0000, Nesius, Robert A wrote:
Probably will need a systemctl daemon-reload, but systemd will
likely
advise you of that anyway.
-Rob
>
> On Apr 2, 2016, at 10:55 AM, Munoz, Obed N <obed.n.munoz(a)intel.com>
> wrote:
>
> Hi,
>
> You can add more debugging information by creating this file:
>
> /etc/systemd/system/libvirtd.service.d/libvirtd.conf
>
> With the above content:
>
> [Service]
> Environment="LIBVIRT_DEBUG=1"
>
>
>
> You will need to restart the libvirtd service
>
> # systemctl restart libvirtd
>
>
> Then, you can see the detailed logging at:
>
> # journalctl -u libvirtd -f
>
>
>
> Regards,
9:14 p.m.
On 4/2/2016 12:18 PM, fb.dev.clx wrote:
Hi all,
I will try later to add the `LIBVIRT_DEBUG=1` parameter.
Otherwise, is there a way to upgrade/downgrade Clear Linux to a
specific released <https://download.clearlinux.org/releases/> revision?
Maybe this could help us to find a fix more quickly.
there is; our swupd can go forwards and backwards
swupd verify --fix -m <version number>
will put you at said version number
9:53 p.m.
Hi,
Thank you for your answer.
I'm going to determine the latest working revision.
Regards,
-- FB
On Sat, 2016-04-02 at 14:14 -0700, Arjan van de Ven wrote:
On 4/2/2016 12:18 PM, fb.dev.clx wrote:
>
> Hi all,
>
> I will try later to add the `LIBVIRT_DEBUG=1` parameter.
>
> Otherwise, is there a way to upgrade/downgrade Clear Linux to a
> specific released <https://download.clearlinux.org/releases/>
> revision?
> Maybe this could help us to find a fix more quickly.
there is; our swupd can go forwards and backwards
swupd verify --fix -m <version number>
will put you at said version number
12:42 a.m.
Hi all,
I used `swupd verify --fix -m <version number>` (thank you Arjan) to
determine the version from which the system has stopped working
properly and found out that all went well till Clear Linux rev. 7050.
With Clear Linux rev. 7050, all goes well:
```
$ sudo virsh version
Compiled against library: libvirt 1.3.2
Using library: libvirt 1.3.2
Using API: QEMU 1.3.2
Running hypervisor: QEMU 2.5.0
```
Clear Linux rev. 7060 is not available...
```
swupd-client software verify 3.3.0
Copyright (C) 2012-2016 Intel Corporation
Verifying version 7060
Attempting to download version string to memory
Unable to download 7060 Manifest.MoM
[...]
```
error appears with rev. 7070:
```
Compiled against library: libvirt 1.3.2
Using library: libvirt 1.3.2
Using API: QEMU 1.3.2
error: failed to get the hypervisor version
error: Cannot check QEMU binary /usr/sbin/qemu-system-x86_64: No such
file or directory
```
So, please let me know if there is a way to fix (or a workaround for)
this in order to update the system to its latest revision.
Regards,
-- FB
On Sat, 2016-04-02 at 14:14 -0700, Arjan van de Ven wrote:
On 4/2/2016 12:18 PM, fb.dev.clx wrote:
>
> Hi all,
>
> I will try later to add the `LIBVIRT_DEBUG=1` parameter.
>
> Otherwise, is there a way to upgrade/downgrade Clear Linux to a
> specific released <https://download.clearlinux.org/releases/>
> revision?
> Maybe this could help us to find a fix more quickly.
there is; our swupd can go forwards and backwards
swupd verify --fix -m <version number>
will put you at said version number
1:02 a.m.
On 4/2/2016 5:42 PM, fb.dev.clx wrote:
Hi all,
I used `swupd verify --fix -m <version number>` (thank you Arjan) to
determine the version from which the system has stopped working
properly and found out that all went well till Clear Linux rev. 7050.
With Clear Linux rev. 7050, all goes well:
so 7050 - 7070 is the break... that's great!
(as you've noticed, this allows you to go to versions that don't always work... we
did not release 7060 for example)
time to dig up the changelogs ;-)
Release notes for the update from 7050 to 7070...
Updated packages:
aodh 2.0.0.0b2-4 -> 2.0.0.0rc1-5
gnocchiclient 2.1.0-3 -> 2.2.0-4
oslo.messaging 4.5.1-38 -> 4.5.1-39
Added packages:
seabios 1.9.1-1
that's 3 openstack things and one seabios as a separate package (instead of qemu), but
that did not yet get put into any bundles in 7070.
some of the bundles seem to have gotten reshuffled between 7050 and 7070 (based on looking
at Manifest.full)
will dig more, but wanted to get this mail out first
1:16 a.m.
On 4/2/2016 5:42 PM, fb.dev.clx wrote:
Hi all,
I used `swupd verify --fix -m <version number>` (thank you Arjan) to
determine the version from which the system has stopped working
properly and found out that all went well till Clear Linux rev. 7050.
ok so I had issues getting virsh version to work, but when I did
systemctl stop libvirtd.socket
systemctl stop libvirtd.service
systemctl start libvirtd.socket
it works on my machine.
1:28 a.m.
Hi,
Please find attached for Clear Linux rev.7050 and rev.7070 the output
of the following command:
```
$ sudo LIBVIRT_DEBUG=1 virsh version
```
Regards,
-- FB
On Sat, 2016-04-02 at 18:16 -0700, Arjan van de Ven wrote:
On 4/2/2016 5:42 PM, fb.dev.clx wrote:
>
> Hi all,
>
> I used `swupd verify --fix -m <version number>` (thank you Arjan)
> to
> determine the version from which the system has stopped working
> properly and found out that all went well till Clear Linux rev.
> 7050.
>
ok so I had issues getting virsh version to work, but when I did
systemctl stop libvirtd.socket
systemctl stop libvirtd.service
systemctl start libvirtd.socket
it works on my machine.
1:21 p.m.
Hi all,
Back from vacations, I intented to update Clear Linux from 7050 to
latest 7210 but problem still remains.
The workaround that works on your machine:
```
systemctl stop
libvirtd.socket
systemctl stop libvirtd.service
systemctl start
libvirtd.socket
```
...doesn't work here:
```
$ sudo virsh version
Compiled against library: libvirt 1.3.2
Using library: libvirt 1.3.2
Using API: QEMU 1.3.2
error: failed to get the hypervisor version
error: internal error: Cannot find suitable emulator for x86_64
```
Right now, I'm still stuck with 7050 latest working version on my
computer.
Anymore idea?
-- FB
On Sat, 2016-04-02 at 18:16 -0700, Arjan van de Ven wrote:
On 4/2/2016 5:42 PM, fb.dev.clx wrote:
>
> Hi all,
>
> I used `swupd verify --fix -m <version number>` (thank you Arjan)
> to
> determine the version from which the system has stopped working
> properly and found out that all went well till Clear Linux rev.
> 7050.
>
ok so I had issues getting virsh version to work, but when I did
systemctl stop libvirtd.socket
systemctl stop libvirtd.service
systemctl start libvirtd.socket
it works on my machine.
1:39 p.m.
what do you get if you run 'virsh capabilities'
On Sun, Apr 24, 2016 at 9:21 AM, fb.dev.clx <fb.dev.clx(a)gmail.com> wrote:
Hi all,
Back from vacations, I intented to update Clear Linux from 7050 to
latest 7210 but problem still remains.
The workaround that works on your machine:
```
systemctl stop
libvirtd.socket
systemctl stop libvirtd.service
systemctl start
libvirtd.socket
```
...doesn't work here:
```
$ sudo virsh version
Compiled against library: libvirt 1.3.2
Using library: libvirt 1.3.2
Using API: QEMU 1.3.2
error: failed to get the hypervisor version
error: internal error: Cannot find suitable emulator for x86_64
```
Right now, I'm still stuck with 7050 latest working version on my
computer.
Anymore idea?
-- FB
On Sat, 2016-04-02 at 18:16 -0700, Arjan van de Ven wrote:
> On 4/2/2016 5:42 PM, fb.dev.clx wrote:
> >
> > Hi all,
> >
> > I used `swupd verify --fix -m <version number>` (thank you Arjan)
> > to
> > determine the version from which the system has stopped working
> > properly and found out that all went well till Clear Linux rev.
> > 7050.
> >
> ok so I had issues getting virsh version to work, but when I did
>
> systemctl stop libvirtd.socket
> systemctl stop libvirtd.service
> systemctl start libvirtd.socket
>
> it works on my machine.
>
>
_______________________________________________
Dev mailing list
Dev(a)lists.clearlinux.org
https://lists.clearlinux.org/mailman/listinfo/dev
2:47 p.m.
Hi Andrew,
Please find attached `virsh capabilities` output with Clear Linux 7050
and 7210 respectively.
-- FB
On Sun, 2016-04-24 at 09:39 -0400, Andrew Cathrow wrote:
what do you get if you run 'virsh capabilities'
On Sun, Apr 24, 2016 at 9:21 AM, fb.dev.clx <fb.dev.clx(a)gmail.com>
wrote:
> Hi all,
>
> Back from vacations, I intented to update Clear Linux from 7050 to
> latest 7210 but problem still remains.
>
> The workaround that works on your machine:
> ```
> systemctl stop
> libvirtd.socket
> systemctl stop libvirtd.service
> systemctl start
> libvirtd.socket
>
> ```
>
> ...doesn't work here:
>
> ```
> $ sudo virsh version
> Compiled against library: libvirt 1.3.2
> Using library: libvirt 1.3.2
> Using API: QEMU 1.3.2
> error: failed to get the hypervisor version
> error: internal error: Cannot find suitable emulator for x86_64
>
> ```
>
> Right now, I'm still stuck with 7050 latest working version on my
> computer.
>
> Anymore idea?
>
> -- FB
>
>
> On Sat, 2016-04-02 at 18:16 -0700, Arjan van de Ven wrote:
> > On 4/2/2016 5:42 PM, fb.dev.clx wrote:
> > >
> > > Hi all,
> > >
> > > I used `swupd verify --fix -m <version number>` (thank you
> Arjan)
> > > to
> > > determine the version from which the system has stopped working
> > > properly and found out that all went well till Clear Linux rev.
> > > 7050.
> > >
> > ok so I had issues getting virsh version to work, but when I did
> >
> > systemctl stop libvirtd.socket
> > systemctl stop libvirtd.service
> > systemctl start libvirtd.socket
> >
> > it works on my machine.
> >
> >
> _______________________________________________
> Dev mailing list
> Dev(a)lists.clearlinux.org
> https://lists.clearlinux.org/mailman/listinfo/dev
>
11:39 p.m.
Hi all,
The problem is gone with Clear Linux 7650. I hope this will not come
back again in the next releases ;-)
Thank you all.
-- FB
On Sun, 2016-04-24 at 09:47 -0500, fb.dev.clx wrote:
Hi Andrew,
Please find attached `virsh capabilities` output with Clear Linux
7050
and 7210 respectively.
-- FB
On Sun, 2016-04-24 at 09:39 -0400, Andrew Cathrow wrote:
>
> what do you get if you run 'virsh capabilities'
>
>
> On Sun, Apr 24, 2016 at 9:21 AM, fb.dev.clx <fb.dev.clx(a)gmail.com>
> wrote:
> >
> > Hi all,
> >
> > Back from vacations, I intented to update Clear Linux from 7050
> > to
> > latest 7210 but problem still remains.
> >
> > The workaround that works on your machine:
> > ```
> > systemctl stop
> > libvirtd.socket
> > systemctl stop libvirtd.service
> > systemctl start
> > libvirtd.socket
> >
> > ```
> >
> > ...doesn't work here:
> >
> > ```
> > $ sudo virsh version
> > Compiled against library: libvirt 1.3.2
> > Using library: libvirt 1.3.2
> > Using API: QEMU 1.3.2
> > error: failed to get the hypervisor version
> > error: internal error: Cannot find suitable emulator for x86_64
> >
> > ```
> >
> > Right now, I'm still stuck with 7050 latest working version on my
> > computer.
> >
> > Anymore idea?
> >
> > -- FB
> >
> >
> > On Sat, 2016-04-02 at 18:16 -0700, Arjan van de Ven wrote:
> > >
> > > On 4/2/2016 5:42 PM, fb.dev.clx wrote:
> > > >
> > > >
> > > > Hi all,
> > > >
> > > > I used `swupd verify --fix -m <version number>` (thank you
> > Arjan)
> > >
> > > >
> > > > to
> > > > determine the version from which the system has stopped
> > > > working
> > > > properly and found out that all went well till Clear Linux
> > > > rev.
> > > > 7050.
> > > >
> > > ok so I had issues getting virsh version to work, but when I
> > > did
> > >
> > > systemctl stop libvirtd.socket
> > > systemctl stop libvirtd.service
> > > systemctl start libvirtd.socket
> > >
> > > it works on my machine.
> > >
> > >
> > _______________________________________________
> > Dev mailing list
> > Dev(a)lists.clearlinux.org
> > https://lists.clearlinux.org/mailman/listinfo/dev
12:52 a.m.
On 4/24/2016 6:39 PM, fb.dev.clx wrote:
Hi all,
The problem is gone with Clear Linux 7650. I hope this will not come
back again in the next releases ;-)
Thank you all.
I wish I could tell you why it went away.
thanks for working through this with us; we'll be adding QA checks for some of this
(but since your commands worked for me at least, it's not leaving me a good feeling)
2102
days inactive
2127
days old
25 comments
5 participants
participants (5)
-
Andrew Cathrow -
Arjan van de Ven -
fb.dev.clx -
Munoz, Obed N -
Nesius, Robert A