| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2020-01-17 | |||
| 11:58:51 | yoctozepto | what distro is this anyways? | |
| 11:59:02 | yoctozepto | (right time to ask that heh) | |
| 11:59:04 | admin0 | ubuntu 16.04 | |
| 11:59:06 | sean-k-mooney | admin0: i think you need to set up your experiment again clenly | |
| 11:59:11 | yoctozepto | quite an oldie there | |
| 11:59:46 | admin0 | ok.. then for the purpose of this, how do do virsh capabilities and edit hte nova file manually so that it just boots up, gets the IP and rsync, recovery is possible | |
| 11:59:47 | sean-k-mooney | the behavior you are seeing is not consitent with how nova operates | |
| 12:00:02 | admin0 | i undestand it may not boot in a very performant or optimal state, but the scope is recovery here | |
| 12:00:20 | sean-k-mooney | normally you would just do virsh start on the domains | |
| 12:00:25 | sean-k-mooney | no need to edit them | |
| 12:00:33 | admin0 | same would be if the virsh/os crashed and i manually had to copy the disk and xml to another (non-similar) compute node | |
| 12:00:41 | yoctozepto | admin0: is qemu-kvm installed? | |
| 12:01:01 | admin0 | qemu-kvm is already the newest version (1:2.10+dfsg-0ubuntu3.8~cloud1). | |
| 12:01:33 | admin0 | <type arch='x86_64' machine='pc-i440fx-artful'>hvm</type> | |
| 12:01:37 | yoctozepto | then I'm out of cards with this issue, really what comes to mind is some bug in ubuntu's libvirt that you have discovered | |
| 12:01:41 | admin0 | i guess that pc-* is the issue ? | |
| 12:01:56 | yoctozepto | well, you could try modifying that | |
| 12:02:31 | yoctozepto | pc-i440fx-xenial should be there | |
| 12:02:42 | yoctozepto | (at least that's what common sense suggests) | |
| 12:02:56 | admin0 | i see https://gist.github.com/a1git/f3696c126a732cda88757c09263bc2de in virsh capabilites related to x86_64 | |
| 12:03:16 | yoctozepto | nothing suspicious | |
| 12:03:37 | sean-k-mooney | the machine type is normal | |
| 12:03:45 | gibi | efried: I got pulled downstream this morning so my review on the provider config progressing slowly. sorry | |
| 12:03:53 | sean-k-mooney | it will now show up in the cpu feature list | |
| 12:04:00 | sean-k-mooney | *not | |
| 12:04:15 | sean-k-mooney | its basicaly the "motherboard" for lack of a better name the vm uses | |
| 12:09:34 | admin0 | i edited pc-i440fx-artful to pc-i440fx-xenial .. same error as invalid argument: could not find capabilities for arch=x86_64 . i have the virsh capabilities in full , lsmod and the vm definition here => https://gist.github.com/a1git/4528c53090f8934b9218586817c51911 | |
| 12:10:42 | sean-k-mooney | admin0: its not related to the model | |
| 12:11:10 | admin0 | ok .. but based on the output, there is no way this instance can boot up ? | |
| 12:11:12 | sean-k-mooney | admin0: you could set it to "pc" which is an aliase for the latest model supproted that is no q35 | |
| 12:11:55 | sean-k-mooney | admin0: the machine types are not listed in that output | |
| 12:12:15 | admin0 | how do i list them ? | |
| 12:13:08 | sean-k-mooney | its likely because the x68 emulator is also not listed | |
| 12:16:15 | sean-k-mooney | you shoudl have a section like this | |
| 12:16:19 | sean-k-mooney | <guest> | |
| 12:16:20 | sean-k-mooney | <os_type>hvm</os_type> | |
| 12:16:22 | sean-k-mooney | <arch name='x86_64'> | |
| 12:16:24 | sean-k-mooney | <wordsize>64</wordsize> | |
| 12:16:26 | sean-k-mooney | <emulator>/usr/local/bin/qemu-system-x86_64</emulator> | |
| 12:16:28 | sean-k-mooney | <machine maxCpus='255'>pc-i440fx-4.1</machine> | |
| 12:16:30 | sean-k-mooney | <machine canonical='pc-i440fx-4.1' maxCpus='255'>pc</machine> | |
| 12:16:34 | sean-k-mooney | in my case it extends quite far | |
| 12:17:09 | admin0 | i will try to remove the libvirt-bin package and reinstall it | |
| 12:17:19 | sean-k-mooney | its not libvirt that is the issue | |
| 12:17:31 | sean-k-mooney | it cant find the x86 qemu bindary | |
| 12:17:36 | stephenfin | sean-k-mooney: Any decisions on what we want to do about https://github.com/openstack/nova/blob/master/nova/virt/libvirt/vif.py#L299-L301 ? | |
| 12:17:42 | stephenfin | That function doesn't exist | |
| 12:17:44 | sean-k-mooney | so you need to reinstall qemu | |
| 12:18:28 | sean-k-mooney | set_vif_host_backedn_brdige_config? | |
| 12:18:34 | sean-k-mooney | stephenfin: what is the context? | |
| 12:18:43 | stephenfin | yes | |
| 12:18:53 | stephenfin | it hasn't existed since commit 92323586b5d03b31c18657ad64646a8ce3b8a742 | |
| 12:19:10 | stephenfin | ||
| 12:19:11 | stephenfin | <stephenfin> sean-k-mooney: fwiw, I'm running pytype over the code base to see what it reveals. That's one of two actual issues it has found so far | |
| 12:19:11 | stephenfin | <stephenfin> sean-k-mooney: so that means that code is not being called by anything yet. In either case, want to work on the fix or will I? | |
| 12:19:11 | stephenfin | <stephenfin> sean-k-mooney: but that function has existed since it was removed in commit 92323586b5d03b31c18657ad64646a8ce3b8a742 | |
| 12:19:45 | sean-k-mooney | oh you pinged me earlier i did not see it | |
| 12:20:20 | jawad_axd | Hi all! Question is: I want to move couple of vms from one openstack evn(with local storage) to another openstack env(with ceph backend). Both vms have 40G root disk and 100G ephemeral disk.I can not take snapshot of instances since they are using ephemeral disks. How can I take backup of these vms with ephemeral disks and boot those two instance in new environment(with ceph backend)? | |
| 12:20:53 | stephenfin | The easy fix would be to re-add the function, but if no one has hit this yet (it's been there since 18.0.0) perhaps we can remove the call | |
| 12:20:58 | sean-k-mooney | stephenfin: the only place that is called is here https://github.com/openstack/nova/blob/b44b540fc70504f3869ef23022642095de0ea99e/nova/virt/libvirt/vif.py#L611-L612 | |
| 12:20:59 | stephenfin | I call look into it if you don't have time | |
| 12:21:10 | stephenfin | yup | |
| 12:21:10 | sean-k-mooney | so it the non os-vif code path for linux bridge | |
| 12:21:22 | sean-k-mooney | i think that was there just for nova-net? | |
| 12:21:26 | admin0 | sean-k-mooney, i redid libvirt-bin , restarted libvirtd and now i see it | |
| 12:21:27 | admin0 | under hvm | |
| 12:21:36 | admin0 | trying to define the instance now | |
| 12:22:02 | admin0 | defined :) | |
| 12:22:28 | sean-k-mooney | stephenfin: i think we can remvoe that branch | |
| 12:22:32 | stephenfin | sean-k-mooney: aha, yes https://github.com/openstack/nova/blob/b44b540fc70504f3869ef23022642095de0ea99e/nova/network/os_vif_util.py#L527-L528 | |
| 12:22:35 | stephenfin | we sure can | |
| 12:22:39 | stephenfin | I'll go kill it | |
| 12:22:43 | stephenfin | thanks, sean-k-mooney | |
| 12:22:48 | sean-k-mooney | stephenfin: anything that would be taking it would be broken at the moment anyway | |
| 12:23:14 | stephenfin | but first, 🏊+🥪 | |
| 12:23:28 | admin0 | ok .. nova is taken care of .. neutron next i think: -> Cannot get interface MTU on 'brqb3371910-95': No such device | |
| 12:23:40 | yoctozepto | admin0: cool | |
| 12:23:54 | yoctozepto | so it's a bug in libvirt losing hvm | |
| 12:24:17 | admin0 | thanks yoctozepto, sean-k-mooney .. can i mention a thank you when i put put this article on my openstackfaq.com site | |
| 12:24:19 | sean-k-mooney | admin0: you might want to take this to #openstack by the way | |
| 12:24:33 | admin0 | i did started on kolla aio https://www.openstackfaq.com/openstack-kolla-all-in-one/ | |
| 12:24:45 | sean-k-mooney | admin0: sure if you want | |
| 12:25:03 | sean-k-mooney | jawad_axd: there is noe cross cloud migration support native to nova | |
| 12:25:03 | yoctozepto | admin0: /me appreciates appreciation | |
| 12:25:30 | sean-k-mooney | jawad_axd: so your best bet would be to do the backup from within the vm. | |
| 12:25:50 | sean-k-mooney | e.g. snapshot root disk | |
| 12:26:11 | sean-k-mooney | create a vm on the ohter cloud by downloand an uploadign the snap shot. | |
| 12:26:11 | jawad_axd | @sean-k-mooney : Not migration, just want to take snapshot of instance with ephemeral disk? | |
| 12:26:28 | sean-k-mooney | boot it in rescue mode and then rsync the contentes fo the ephemeral volumes | |
| 12:26:49 | admin0 | jawad_axd, or you can just boot 2 vms, rsync the data you need | |
| 12:26:49 | sean-k-mooney | you can take a snapshot but it will only snapshot the root disk | |
| 12:27:05 | sean-k-mooney | that is basicly what i was saying | |
| 12:27:36 | yoctozepto | (this is the point where one suggests using dd over socat) | |
| 12:27:47 | jawad_axd | Snapshot doest work with ephemeral disk[E.g flavor has root disk and ephemral disk], while snapshot works with just root disk when in flavor ephemeral disk=0 . | |
| 12:28:16 | jawad_axd | ah ok | |
| 12:28:22 | sean-k-mooney | really it should still work with the root disk. at least i taught it did | |
| 12:28:33 | sean-k-mooney | i just wont snapshot the ephemeral disks | |
| 12:28:58 | jawad_axd | Its not even snapshotting the root disk. | |
| 12:29:01 | sean-k-mooney | ephemeral disk are intened for fast local storage by the way. not data persitency | |
| 12:29:17 | sean-k-mooney | i see | |