[pve-devel] training week : students features request

Alexandre DERUMIER aderumier at odiso.com
Thu Mar 22 08:37:59 CET 2018


>>But after install last deb, Alexandre, the qemu broke. So I need to return 
>>to previously version. 

>>qm start 100 
>>/usr/bin/qemu-img: symbol lookup error: /usr/bin/qemu-img: undefined 
>>symbol: rbd_aio_writev 

sorry, my build environnement use last ceph librbd dev library...
(if you want to test, you can install last pve ceph luminous repo)


----- Mail original -----
De: "Gilberto Nunes" <gilberto.nunes32 at gmail.com>
À: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mercredi 21 Mars 2018 13:16:37
Objet: Re: [pve-devel] training week : students features request

He 

Cloud-init up and running. 
But after install last deb, Alexandre, the qemu broke. So I need to return 
to previously version. 

qm start 100 
/usr/bin/qemu-img: symbol lookup error: /usr/bin/qemu-img: undefined 
symbol: rbd_aio_writev 
Total translation table size: 0 
Total rockridge attributes bytes: 417 
Total directory bytes: 0 
Path table size(bytes): 10 
qemu-img: symbol lookup error: qemu-img: undefined symbol: rbd_aio_writev 
command 'set -o pipefail && genisoimage -R -V cidata 
/run/pve/cloudinit/100/ | qemu-img dd -f raw -O raw 'isize=0' 'osize=0' 
'of=/dev/zvol/rpool/data/vm-100-cloudinit'' failed: exit code 127 

Now it run with pve-qemu-vm version 2.9.1-9. Works fine. 

Thanks 

--- 
Gilberto Nunes Ferreira 

(47) 3025-5907 
(47) 99676-7530 - Whatsapp / Telegram 

Skype: gilberto.nunes36 




2018-03-21 1:57 GMT-03:00 Alexandre DERUMIER <aderumier at odiso.com>: 

> Hi Gilberto, 
> maybe related, you need last pve-qemu package too, to have last qemu-img 
> bin (which is need to generate the drive) 
> 
> http://odisoweb1.odiso.net/pve-qemu-kvm_2.11.1-3_amd64.deb 
> 
> ----- Mail original ----- 
> De: "Gilberto Nunes" <gilberto.nunes32 at gmail.com> 
> À: "pve-devel" <pve-devel at pve.proxmox.com> 
> Envoyé: Mardi 20 Mars 2018 14:37:43 
> Objet: Re: [pve-devel] training week : students features request 
> 
> Oh! I see! 
> 
> So this the correct steps: 
> 1 - generate the cloud-init image 
> 2 - install my favorite distro 
> 3 - install the cloud-init into the vm with my fav distro 
> 4 - when boot the fav distro, cloud-init will get the information from that 
> cloud-init image and set the IP, user, password and so on... 
> 
> That's the general idea? Correct if I wrong please! 
> 
> --- 
> Gilberto Nunes Ferreira 
> 
> (47) 3025-5907 
> (47) 99676-7530 - Whatsapp / Telegram 
> 
> Skype: gilberto.nunes36 
> 
> 
> 
> 
> 2018-03-20 10:09 GMT-03:00 Wolfgang Bumiller <w.bumiller at proxmox.com>: 
> 
> > On Tue, Mar 20, 2018 at 09:49:05AM -0300, Gilberto Nunes wrote: 
> > > That's was nice! Thanks Dietmar 
> > > 
> > > Meanwhile, I get some errors here... Certain because I am doing 
> something 
> > > pretty ugly. 
> > > 
> > > So, this is my steps: 
> > > 
> > > 1 - I alreay have a KVM VM with Alpine Linux in it. The VMID is 101. 
> > > 2 - I add a cloud disk to VM 101. I add it to ZFS local storage... I 
> > local 
> > > storage I get this error [1] 
> > (...) 
> > > kvm: -drive 
> > > file=/var/lib/vz/images/101/vm-101-cloudinit.qcow2,if= 
> > none,id=drive-ide2,format=qcow2,cache=none,aio=native,detect-zeroes=on: 
> > > file system may not support O_DIRECT 
> > > kvm: -drive 
> > > file=/var/lib/vz/images/101/vm-101-cloudinit.qcow2,if= 
> > none,id=drive-ide2,format=qcow2,cache=none,aio=native,detect-zeroes=on: 
> > > Could not open '/var/lib/vz/images/101/vm-101-cloudinit.qcow2': 
> Invalid 
> > > argument 
> > 
> > You can't use cache=none with _files_ on ZFS. 
> > 
> > > 3 - I went to Cloud-init, fill all information, such user and password 
> > bla 
> > > bla bla... Click Regenerate Image 
> > > 4 - I created a new VM, attached the cloud-init and try to boot over it 
> > - I 
> > > use qm set VMID -ide2 local-zfs:vm-101-cloudinit and try it also with 
> > -scsi1 
> > > 5 - I get a not bootable disk 
> > 
> > Well of course, you're not supposed to boot from the disk, the disks is 
> > just data for the OS to load and use. You need an already-installed OS 
> > with cloud-init starting at boot (either from a fixed 
> > cloud-image/template, or by insstalling your favorite distro and 
> > installing the cloud-init package into it) 
> > 
> > 
> _______________________________________________ 
> pve-devel mailing list 
> pve-devel at pve.proxmox.com 
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
> 
> _______________________________________________ 
> pve-devel mailing list 
> pve-devel at pve.proxmox.com 
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
> 
_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 



More information about the pve-devel mailing list