[Dev] "virsh could not find capabilities for arch=x86_64"
by fb.dev.clx
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 years, 1 month
[Dev] Install image fails
by Dwarf Snowcrash
I'm not sure this is the place to post but I don't have any other options.
I followed the instructions for the install pen drive creation and got it to run but was given no choice for a drive to install on. It chose the hard drive without telling me, wiped the drive and failed to install anything leaving me with a boat anchor. I had to install Windows 10, as there was no recovery partition left from the original 8.1 install.
The live image fails to boot.
So far I can't say I'm very impressed.
Any suggestions appreciated.
Dale
Sent from my Xperia™ tablet
4 years, 1 month
[Dev] Virtual Machine Manager and / or SPICE client viewer
by fb.dev.clx
Hi all,
I'm still intenting to setup an environment, where I would like to run
virtual machines with QEMU-KVM (independently of OpenStack), with Clear
Linux installed natively.
As Clear Linux QEMU now supports SPICE, it would be nice to add a SPICE
viewer (spicec) or even better, full virt-manager <http://virt-manager.
org/> support in order to manage KVM VMs through a GUI.
What do you think?
4 years, 2 months
[Dev] sudo should be installed if user is added to sudoers file
by fb.dev.clx
Hi all,
Using Clear Linux 6580 installer, I configured a new user and added it
to the sudoers file as the installer proposed it.
Restarting the system after last install message, I found out that sudo
command was not available until os-utils bundle is added.
Since only root can add a bundle and reboot or shutdown the machine,
this is really a problem as the user is then stuck at the command
prompt.
What do you think?
-- FB
4 years, 2 months
[Dev] How to build 32-bit executables with gcc?
by Per Mildner
Is it possible to build 32-bit executables with the C compiler that comes with Clear Linux?
I tried gcc -m32 but got nowhere:
### TRANSCRIPT BEGIN
foo@clr ~ $ cat main.c
int main (int argc, char **argv) { return 0; }
foo@clr ~ $ gcc main.c -o main
foo@clr ~ $ file main
main: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.10.0, BuildID[sha1]=46c1e44cf71c59b0c3baf4a00533ed259b20c4d7, not stripped
foo@clr ~ $ gcc -m32 main.c -o main32
/usr/bin/ld: skipping incompatible /usr/lib64/gcc/x86_64-generic-linux/5.3.0/libgcc.a when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
/usr/bin/ld: skipping incompatible /usr/lib64/gcc/x86_64-generic-linux/5.3.0/../../../libgcc_s.so when searching for -lgcc_s
/usr/bin/ld: skipping incompatible /usr/lib64/libgcc_s.so when searching for -lgcc_s
/usr/bin/ld: cannot find -lgcc_s
/usr/bin/ld: skipping incompatible /usr/lib64/gcc/x86_64-generic-linux/5.3.0/../../../libc.so when searching for -lc
/usr/bin/ld: skipping incompatible /usr/lib64/libc.so when searching for -lc
/usr/bin/ld: cannot find -lc
/usr/bin/ld: skipping incompatible /usr/lib64/gcc/x86_64-generic-linux/5.3.0/libgcc.a when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
/usr/bin/ld: skipping incompatible /usr/lib64/gcc/x86_64-generic-linux/5.3.0/../../../libgcc_s.so when searching for -lgcc_s
/usr/bin/ld: skipping incompatible /usr/lib64/libgcc_s.so when searching for -lgcc_s
/usr/bin/ld: cannot find -lgcc_s
collect2: error: ld returned 1 exit status
perm(a)r2d2.sics.se's password:
clr_32bit_fail.txt 100% 1430 1.4KB/s 00:00
foo@clr ~ $ uname -a
Linux clr 4.4.4-178.native #1 SMP Fri Mar 4 13:27:14 PST 2016 x86_64 GNU/Linux
foo@clr ~ $ gcc --version
gcc (Clear Linux OS for Intel Architecture) 5.3.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
foo@clr ~ $ ls /usr/share/clear/bundles
bootloader kernel-native os-core os-core-dev os-core-update os-utils
foo@clr ~ $
### TRANSCRIPT END
Regards,
Per Mildner Per.Mildner(a)sics.se
Swedish Institute of Computer Science (SICS Swedish ICT)
4 years, 2 months
[Dev] sssd
by Kent Pirkle
I can't find a bundle that contains sssd. It's what we usually use to
connect to LDAP. Is it already in Clear Linux and if not can it be added?
Thanks
--
Sent from Google Inbox
4 years, 2 months
[Dev] is clear containers with no networking (netwrok driver = null) possible?
by Long, Paul
In regular old Docker on Ubuntu (VM or native) I can say: docker run -itd
-net=none ubuntu which starts a container with only a loopback interface.
This doesn't seem to work for me on Clear. Running on release 6430 I get:
The standard Docker network looks like it is setup properly on the system:
It creates the container, but cannot start it. Is this by design or am I
just doing something wonky?
Thanks,
-pwl
4 years, 2 months
[Dev] segmentation fault in bc -l
by Jan Fikar
> I'm getting segmentation fault using "bc -l" to calculate for example 3*3 in Clear Linux 6580, details are below. Without the -l parameter there is no problem.
>
> Best Regards,
> Jan
>
>
>
> fik@clr ~ $ bc -l
> bc 1.06
> Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc.
> This is free software with ABSOLUTELY NO WARRANTY.
> For details type `warranty'.
> 3*3
> Segmentation fault
> fik@clr ~ $ bc
> bc 1.06
> Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc.
> This is free software with ABSOLUTELY NO WARRANTY.
> For details type `warranty'.
> 3*3
> 9
> fik@clr ~ $ gdb /usr/bin/bc
> GNU gdb (GDB) 7.10.1
> Copyright (C) 2015 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-generic-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from /usr/bin/bc...Reading symbols from /usr/lib/debug/.build-id/e9/0aba169187c4c61a6358b737acfe325b661938.debug...done.
> done.
> (gdb) run -l
> Starting program: /usr/bin/bc -l
> bc 1.06
> Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc.
> This is free software with ABSOLUTELY NO WARRANTY.
> For details type `warranty'.
> 3*3
>
> Program received signal SIGSEGV, Segmentation fault.
> addbyte (byte=byte@entry=75 'K') at load.c:68
> 68 if (pc >= f->f_body_size)
> (gdb) bt
> #0 addbyte (byte=byte@entry=75 'K') at load.c:68
> #1 0x0000000000405d72 in addbyte (byte=75 'K') at load.c:348
> #2 load_code (code=<optimized out>) at load.c:307
> #3 0x000000000040765d in generate (str=str@entry=0x40c3b6 "K") at util.c:278
> #4 0x0000000000402c85 in yyparse () at bc.y:545
> #5 0x00000000004012fe in main (argc=2, argv=0x7fffffffe888) at main.c:259
4 years, 2 months
[Dev] virsh cannot find suitable emulator for x86_64
by fb.dev.clx
Hi all,
I'm unable to start KVM VMs (without OpenStack) anymore as virsh 'could
not find capabilities for arch=x86_64'.
```
$ virsh version
Compiled against library: libvirt 1.3.1
Using library: libvirt 1.3.1
Using API: QEMU 1.3.1
error: failed to get the hypervisor version
error: internal error: Cannot find suitable emulator for x86_64
```
Of course, libvirtd is running and my standard user (clruser) belongs
to the following groups:
```
$ id
uid=1000(clruser) gid=1000(clruser)
groups=1000(clruser),200(qemu),201(kvm),203(libvirt)
```
Clear Linux version:
```
# cat /usr/share/clear/version
6470
```
Clear Linux Bundles installed so far:
```
# ls /usr/share/clear/bundles/
containers-basic
kernel-native
kvm-host
os-core
os-core-update
os-utils
os-utils-gui
```
Any suggestions appreciated.
Thanks
-- FB
4 years, 2 months
