On Fri, Mar 6, 2015 at 3:55 PM, Karanbir Singh kbsingh@centos.org wrote:
We are pleased to announce CentOS Atomic host rolling builds for CentOS Linux.
This release is tagged 20150228_01 : It represents content from Feb 2015 CentOS Linux 7 + Atomic SIG and Virtualisation SIG.
[snip]
Note that the Generic Cloud image ( qcow2 file ) still requires a NoCloud cloud-init configuration iso to enable access. The Vagrant images, do not. They will just work with the vagrant default access policy.
[snip]
File: CentOS-7-x86_64-AtomicHost-20150228_01.qcow2
Sha256: ec94554d92558328e2ce7627996ce21faf76105be125d7f711615c1850956e0a
File: CentOS-7-x86_64-AtomicHost-20150228_01.qcow2.xz Sha256: b366f73e4445e139a2df2bef935be863a377960714bdad22d5b47593d7ccec93
[snip]
Symlinks are provided that will always map to the latest released builds, as follows ( including their current mapping )
http://buildlogs.centos.org/rolling/7/isos/x86_64/CentOS-7-x86_64-AtomicHost...
- -> CentOS-7-x86_64-AtomicHost-20150228_01.qcow2
http://buildlogs.centos.org/rolling/7/isos/x86_64/CentOS-7-x86_64-AtomicHost...
- -> CentOS-7-x86_64-AtomicHost-20150228_01.qcow2.xz
Hello, the web links of the two images referred above seem not valid any more... Was there any problem with them? I ask because I already downloaded and am having problmes using them in virt-manager on Fedora 21. $ sha256sum /ssd840pool/ssd840_vmpool/CentOS-7-x86_64-AtomicHost-20150228_01.qcow2 ec94554d92558328e2ce7627996ce21faf76105be125d7f711615c1850956e0a /ssd840pool/ssd840_vmpool/CentOS-7-x86_64-AtomicHost-20150228_01.qcow2
$ qemu-img info /ssd840pool/ssd840_vmpool/CentOS-7-x86_64-AtomicHost-20150228_01.qcow2 image: /ssd840pool/ssd840_vmpool/CentOS-7-x86_64-AtomicHost-20150228_01.qcow2 file format: qcow2 virtual size: 10G (10737418240 bytes) disk size: 777M cluster_size: 65536 Format specific information: compat: 0.10
I created the iso with user-data and meta-data as described in: http://www.projectatomic.io/docs/quickstart/ and other similar docs but it seems the image doesn't get parsed... (no hostname set and not able to ssh into the image). Do I have to pass any kernel command line when I start in virt-manager? I also found this "old" link to create the seed image: https://rwmj.wordpress.com/2013/12/10/creating-a-cloud-init-config-disk-for-...
but the virt-builder command is not able to extract kernel and initrd image from the qcow2 image. I get: virt-builder: error: get-kernel: no operating system found Here below the whole log of virt-builder run with -v and -x options: https://drive.google.com/file/d/0BwoPbcrMv8mvbm5lUk5rcFpVa0U/view?usp=sharin...
I don't know if it is expected that virt-builder gives error...
Thanks in advance
Gianluca