Re: [openstack-dev] [nova] FFE Request: image-multiple-location support
On Thu, Sep 12, 2013 at 9:43 PM, Thierry Carrez thie...@openstack.org wrote: lzy@gmail.com wrote: BP: https://blueprints.launchpad.net/nova/+spec/image-multiple-location Since a dependent patch getting merger delay (https://review.openstack.org/#/c/44316/), so the main patch https://review.openstack.org/#/c/33409/ been hold by FF. It's very close to get merger and waited about 3 months, could you pls take a look and let it go in H? So, this is a significant feature... which paradoxically is a good reason to accept it *and* to deny it. On one hand it would be nice to complete this (with Glance support for it being landed), but on the other it's not really a self-contained feature and I could see it have bugs (or worse, create regressions). Hello Thierry Carrez, two questions, whether we pass FFE or not. 1. why you think it's not a self-contained feature/patch, do you think the patch miss something? 2. I'd very like to know what's wrong in current patch # 33409, can you point the bugs out which you mentioned above? My answer would probably have been different if this request had been posted a week ago, but at this point, I would lean towards -1. I have two points here: 1. The dependent patch #44316 just been merged on this Monday so I could not send this FFE request out early. 2. I have committed the patch #33409 on June and followed up any comments on time, so at this point I can only say the review progress let down me TBH. -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Thanks for you input ttx. zhiyan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] FFE Request: read-only-volumes feature
Hello, The feature BP at https://blueprints.launchpad.net/cinder/+spec/read-only-volumes. The Cinder server side change (https://review.openstack.org/#/c/38322/) was done and merged, but since there was a delay of a few weeks on the Cinder side while team debated between some design options, and I couldn't submit Nova side patchs until the corresponding Cinder patch was merged. So the follow Nova side changes need to request FFE, I need those changes to make the feature workable fully: https://review.openstack.org/#/c/44455/ https://review.openstack.org/#/c/44817/(depends on cinderclient change https://review.openstack.org/#/c/44672/ ) https://review.openstack.org/#/c/45171/ thanks, zhiyan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [Openstack] Image filtering
Try this: /images/detail?changes-since=2013-07-18T17:01:22Z thanks, zhiyan On Mon, Jul 22, 2013 at 5:06 PM, Narayanan, Krishnaprasad naray...@uni-mainz.de wrote: Hallo Stackers, In continuation of my earlier email, I found a filter called “changes-since” that is supported by the “index” command in Glance. Can somebody tell me the format of it? Regards, Krishnaprasad From: Openstack [mailto:openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] On Behalf Of Narayanan, Krishnaprasad Sent: Sonntag, 21. Juli 2013 18:38 To: openstack@lists.launchpad.net Subject: [Openstack] Image filtering Hallo All, Can somebody guide me how to filter images based on start and end date using the nova cli? What is the command that I should use in order to perform this filtering? Thanks Krishnaprasad ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [openstack-dev] [nova] Nova API extensions NOT to be ported to v3
Hi Chris, thank you for the response. Replied by inline comments. On Mon, Jul 1, 2013 at 9:01 AM, Christopher Yeoh cbky...@gmail.com wrote: Hi Zhiyan, On Sat, Jun 29, 2013 at 6:25 PM, lzy@gmail.com lzy@gmail.com wrote: On Fri, Jun 28, 2013 at 8:31 PM, Christopher Yeoh cbky...@gmail.com wrote: Hi Chris, for extended_virtual_interfaces_net extension, actually it is based on 'virtual_interfaces', but I saw they are in different part in NovaV3ExtensionPortWorkList. And our product using those extension currently, so if you can port them to v3 it will be very grateful. Just to be clear, the v2 version will remain in Havana so it will be only an issue for your product if you are porting it to the v3 API. As os-virtual-interfaces doesn't support Quantum I guess you're only using it when openstack is setup with nova-network? Yes, in current version our product using nova-network, and planned to migrate to Neutron. It looks to me that it should be possible to get the same information through the quantum API (and nova-network is going away in the nearish future). Can you see any reason that might not be possible? Ok, I have not checked that yet but seems we need implement a new extension/change in Neutron API layer to cover our requirement what 'extended_virtual_interfaces' current did, maybe. It looks like extended_virtual_interfaces should be on that list of extensions not to port since it is directly dependent on os-virtual-interfaces Yes, I think so, if you no plan to port 'os-virtual-interfaces'. Regards, Chris zhiyan Also I'd like to propose that after H2 any new API extension submitted HAS to have a v3 version. That will give us enough time to ensure that the V3 API in Havana can do everything that the V2 one except where we explicitly don't want to support something. For developers who have had new API extensions merged in H2 but haven't submitted a v3 version, I'd appreciate it if you could check the following etherpad to see if your extension is on the list and put it on there ASAP if it isn't there already: https://etherpad.openstack.org/NovaV3ExtensionPortWorkList I've tried to keep track of new API extensions to make sure we do v3 ports but may have missed some. Chris ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)
Can you check the backing file: /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96 is in normal? On Wed, May 15, 2013 at 3:16 PM, Nikhil Mittal mittalnik...@gmail.com wrote: Any suggestions on debugging this issue ? As I mentioned below, the command qemu-img shows information where the file format is qcow2 whereas the image used in this instance is ISO. Is this a bug or am I missing something ? Thanks, -Nikhil On Tue, May 14, 2013 at 3:30 PM, Nikhil Mittal mittalnik...@gmail.com wrote: Here it is: === image: /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk file format: qcow2 virtual size: 160G (171798691840 bytes) disk size: 200K cluster_size: 65536 backing file: /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96 === BTW, I launched the instance with ISO image format NOT qcow2. Don't know why it is showing the format as qcow2. On Tue, May 14, 2013 at 3:23 PM, lzy@gmail.com lzy@gmail.com wrote: Nikhil What the 'qemu-img info /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk' command say? Zhi Yan On Tue, May 14, 2013 at 5:43 PM, Nikhil Mittal mittalnik...@gmail.com wrote: Wang, I guess you are referring to to the instance specific XML file under /etc/libvirt/qemu. It has the following section having 'vda': === devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'/ target dev='vda' bus='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /disk === Can you specify what exactly I need to change ? Thanks, Nikhil On Tue, May 14, 2013 at 1:45 PM, Wangpan hzwang...@corp.netease.com wrote: seems like the roog disk is not a bootable device, you may need to check the vda/xvda device in libvirt XML config file is bootable or not. 2013-05-14 Wangpan 发件人：Nikhil Mittal 发送时间：2013-05-14 15:59 主题：[Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04) 收件人：openstackopenstack@lists.launchpad.net 抄送： Hello, I recently installed Grizzly (single-node) on Ubuntu 13.04 on x86 64 bit having two physical NICs. I posted about the networking issues that I was facing after the installation in an earlier post. Well, while I was debugging the networking issue, I came across a more serious issue -- my host machine got rebooted (power-cycle) and on reboot I see that my two VMs are shown in shut-off Status and shut-down Power state in the Dashboard GUI. The options available to me are only soft reboot, hard reboot, terminate instance, Disassociate Floating IP and Edit Instance. I did first soft reboot and the console shows No bootable device. Then i tried Hard reboot and again the same message No bootable device. I checked that all services are running fine and there are no error messages in the logs for nova, quantum, etc. I followed installation instructions based on the following link: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_SingleNode/OpenStack_Grizzly_Install_Guide.rst Thanks, Nikhil ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)
Nikhil What the 'qemu-img info /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk' command say? Zhi Yan On Tue, May 14, 2013 at 5:43 PM, Nikhil Mittal mittalnik...@gmail.com wrote: Wang, I guess you are referring to to the instance specific XML file under /etc/libvirt/qemu. It has the following section having 'vda': === devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'/ target dev='vda' bus='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /disk === Can you specify what exactly I need to change ? Thanks, Nikhil On Tue, May 14, 2013 at 1:45 PM, Wangpan hzwang...@corp.netease.com wrote: seems like the roog disk is not a bootable device, you may need to check the vda/xvda device in libvirt XML config file is bootable or not. 2013-05-14 Wangpan 发件人：Nikhil Mittal 发送时间：2013-05-14 15:59 主题：[Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04) 收件人：openstackopenstack@lists.launchpad.net 抄送： Hello, I recently installed Grizzly (single-node) on Ubuntu 13.04 on x86 64 bit having two physical NICs. I posted about the networking issues that I was facing after the installation in an earlier post. Well, while I was debugging the networking issue, I came across a more serious issue -- my host machine got rebooted (power-cycle) and on reboot I see that my two VMs are shown in shut-off Status and shut-down Power state in the Dashboard GUI. The options available to me are only soft reboot, hard reboot, terminate instance, Disassociate Floating IP and Edit Instance. I did first soft reboot and the console shows No bootable device. Then i tried Hard reboot and again the same message No bootable device. I checked that all services are running fine and there are no error messages in the logs for nova, quantum, etc. I followed installation instructions based on the following link: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_SingleNode/OpenStack_Grizzly_Install_Guide.rst Thanks, Nikhil ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Libguestfs] libguestfs-test-tool say child process died on ubuntu 11.10 x64
On Fri, Dec 30, 2011 at 3:38 PM, Wanlong Gao wanlong@gmail.com wrote: On 12/30/2011 03:29 PM, Wanlong Gao wrote: On 12/30/2011 03:25 PM, lzy@gmail.com wrote: On Fri, Dec 30, 2011 at 2:58 PM, Wanlong Gao wanlong@gmail.com wrote: On 12/30/2011 09:57 AM, lzy@gmail.com wrote: Hi all, As title, thanks a lot. My test host configurations: Linux desktop 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux The test tool output as following: xxx@desktop:~$ sudo libguestfs-test-tool [sudo] password for xxx: = Test starts here = LIBGUESTFS_DEBUG=1 TMPDIR=(not set) libguestfs: new guestfs handle 0x16cd0f0 library version: 1.15.11 guestfs_get_append: (null) guestfs_get_attach_method: appliance guestfs_get_autosync: 1 guestfs_get_direct: 0 guestfs_get_memsize: 500 guestfs_get_network: 0 guestfs_get_path: /usr/lib/guestfs guestfs_get_pgroup: 0 guestfs_get_qemu: /usr/bin/kvm guestfs_get_recovery_proc: 1 guestfs_get_selinux: 0 guestfs_get_smp: 1 guestfs_get_trace: 0 guestfs_get_verbose: 1 host_cpu: x86_64 Launching appliance, timeout set to 600 seconds. libguestfs: [0ms] febootstrap-supermin-helper --verbose -f checksum '/usr/lib/guestfs/supermin.d' x86_64 supermin helper [0ms] whitelist = (not specified), host_cpu = x86_64, kernel = (null), initrd = (null), appliance = (null) supermin helper [0ms] inputs[0] = /usr/lib/guestfs/supermin.d checking modpath /lib/modules/3.0.0-13-generic is a directory picked vmlinuz-3.0.0-13-generic because modpath /lib/modules/3.0.0-13-generic exists checking modpath /lib/modules/3.0.0-14-generic is a directory picked vmlinuz-3.0.0-14-generic because modpath /lib/modules/3.0.0-14-generic exists supermin helper [0ms] finished creating kernel supermin helper [0ms] visiting /usr/lib/guestfs/supermin.d supermin helper [0ms] visiting /usr/lib/guestfs/supermin.d/base.img supermin helper [1ms] visiting /usr/lib/guestfs/supermin.d/daemon.img supermin helper [1ms] visiting /usr/lib/guestfs/supermin.d/hostfiles supermin helper [00031ms] visiting /usr/lib/guestfs/supermin.d/init.img Here missed add kernel modules. Did you test 1.15.11-1 here http://libguestfs.org/download/binaries/ubuntu1110-packages/ ? I just tested on ubuntu-11.10 x86_64, but didn't see this error, can you test with the 1.15.11-1 package again and send the result here? Thanks -Wanlong Gao Hi, The version of libguestfs I have tested is 1.15.11-1. And there deb packages are all download from that official site. Thanks. You can see this error every time? And can you tell me the version of your febootstrap? ## febootstrap -V Thanks -Wanlong Gao Zhi Yan, Liu Hi, 1. Yes, I can reproduce this error every time. 2. the febootstrap version is 3.7. Thanks. Zhi Yan, Liu ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] libguestfs-test-tool say child process died on ubuntu 11.10 x64
On Fri, Dec 30, 2011 at 5:53 PM, Richard W.M. Jones rjo...@redhat.com wrote: On Fri, Dec 30, 2011 at 09:57:36AM +0800, lzy@gmail.com wrote: library version: 1.15.11 [...] [17614ms] /usr/bin/kvm \ -drive file=/tmp/libguestfs-test-tool-sda-6OA3hT,cache=off,format=raw,if=virtio \ -nodefconfig \ -machine accel=kvm:tcg \ -nodefaults \ -nographic \ -m 500 \ -no-reboot \ -no-hpet \ -device virtio-serial \ -serial stdio \ -chardev socket,path=/tmp/libguestfsJF88Lr/guestfsd.sock,id=channel0 \ -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \ -kernel /var/tmp/.guestfs-0/kernel.17521 \ -initrd /var/tmp/.guestfs-0/initrd.17521 \ -append 'panic=1 console=ttyS0 udevtimeout=300 no_timer_check acpi=off printk.time=1 cgroup_disable=memory selinux=0 guestfs_verbose=1 TERM=xterm ' \ -drive file=/var/tmp/.guestfs-0/root.17521,snapshot=on,if=virtio,cache=unsafeSupported machines are: pc Standard PC (alias of pc-0.14) pc-0.14 Standard PC (default) pc-0.13 Standard PC pc-0.12 Standard PC pc-0.11 Standard PC, qemu 0.11 pc-0.10 Standard PC, qemu 0.10 isapc ISA-only PC This is a bug in qemu 0.15, fixed in qemu 1.0 (although 1.0 introduced another bug which prevents libguestfs from working out of the box there too). If you recompile libguestfs from source then it will detect this qemu problem at ./configure time and add some code to work around it. However the binaries on the website weren't compiled this way. In Fedora we patch around many qemu bugs, so it's worth keeping an eye on our qemu packages: http://pkgs.fedoraproject.org/gitweb/?p=qemu.git Here is the patch you need to qemu 0.15 which fixes the above bug: http://pkgs.fedoraproject.org/gitweb/?p=qemu.git;a=blob;f=qemu-Allow-to-leave-type-on-default-in-machine.patch;h=e4a8e6ddc6ce825517836c8d595c06584c3126f0;hb=refs/heads/f16 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top Thanks Rich and Gao. I have solved this issue by update qemu-kvm from 0.15 to 1.0 version. Zhi Yan, Liu ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
subscription
subscription -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
