Re: [Openstack] Error mounting disk with libguestfs (child process died unexpectedly)

2014-03-04 Thread Parthipan, Loganathan
Arindam,

What happens if you 'apt-get remove python-guestfs' and try? I'd expect it to 
fallback to nbdmount.


From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 04 March 2014 10:40
To: openstack@lists.openstack.org
Subject: [Openstack] Error mounting disk with libguestfs (child process died 
unexpectedly)

Hi,
I have a working Openstack Grizzly setup with nova-network on Scientific Linux. 
As, SL comes with a old qemu:

qemu-kvm-0.12.1.2-2.355.el6_4.6.x86_64

I am trying to upgrade it to qemu-1.7.0 from source.

The configuration output.

As, openstack use /usr/libexec/qemu-kvm to start up VM, i linked
qemu-kvm to qemu-system-x86_64:
ls -l /usr/libexec/qemu-kvm lrwxrwxrwx 1 root root 33 Feb 19 15:25 
/usr/libexec/qemu-kvm -> /usr/local/bin/qemu-system-x86_64

But when I try to start VM, I get following error:

WARNING nova.virt.disk.api [req-7dfd6cf1-db21-403d-abbf-ccb5f0273a6a
b829b65d0675416198f9e4838b5009e2 9a2e060772204260b53b52ea1c12db97]
Ignoring error injecting data into image
(Error mounting 
/var/lib/nova/instances/07c0898e-7d75-448d-b4fe-2c37f681b846/disk
with libguestfs (child process died unexpectedly))

The full error log is here.

Output of libguestfs-test-tool is here.

Regards,
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] Error mounting disk with libguestfs (child process died unexpectedly)

2014-03-04 Thread Parthipan, Loganathan
Reading your log, I don't think the problem is due to injection failure at 
libguestfs. It's a warning and is ignored.

Seems more like a network setup issue. Are you using neutron? Is the 
network/subnet etc setup properly?

From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 04 March 2014 11:50
To: Parthipan, Loganathan; openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Hi Parthipan,

When I try to do yum remove python-libguestfs.
It also wants to remove openstack-nova-compute. So, I can not.

Regards,
Arindam


From: parthi...@hp.com
To: arin...@live.com; openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
Date: Tue, 4 Mar 2014 11:23:50 +
Arindam,

What happens if you 'apt-get remove python-guestfs' and try? I'd expect it to 
fallback to nbdmount.


From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 04 March 2014 10:40
To: openstack@lists.openstack.org
Subject: [Openstack] Error mounting disk with libguestfs (child process died 
unexpectedly)

Hi,
I have a working Openstack Grizzly setup with nova-network on Scientific Linux. 
As, SL comes with a old qemu:

qemu-kvm-0.12.1.2-2.355.el6_4.6.x86_64

I am trying to upgrade it to qemu-1.7.0 from source.

The configuration output<http://pastebin.com/raw.php?i=geEEXm79>.

As, openstack use /usr/libexec/qemu-kvm to start up VM, i linked
qemu-kvm to qemu-system-x86_64:
ls -l /usr/libexec/qemu-kvm lrwxrwxrwx 1 root root 33 Feb 19 15:25 
/usr/libexec/qemu-kvm -> /usr/local/bin/qemu-system-x86_64

But when I try to start VM, I get following error:

WARNING nova.virt.disk.api [req-7dfd6cf1-db21-403d-abbf-ccb5f0273a6a
b829b65d0675416198f9e4838b5009e2 9a2e060772204260b53b52ea1c12db97]
Ignoring error injecting data into image
(Error mounting 
/var/lib/nova/instances/07c0898e-7d75-448d-b4fe-2c37f681b846/disk
with libguestfs (child process died unexpectedly))

The full error log is here<http://pastebin.com/raw.php?i=FD8N47mk>.

Output of libguestfs-test-tool is here<http://pastebin.com/raw.php?i=EKWQWH1y>.

Regards,
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] Error mounting disk with libguestfs (child process died unexpectedly)

2014-03-05 Thread Parthipan, Loganathan
Seems like qemu doesn't have the privileges to read 
/sys/kernel/debug/tracing/tracing_on



From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 04 March 2014 15:15
To: Parthipan, Loganathan; openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Hi,
both
/sys/kernel/debug/tracing/tracing_on
/sys/kernel/debug/tracing/events/kvm/enable is 1.

The logs are:

libvirtd-debug<http://paste.openstack.org/raw/72197/> (sorry for lots of 
garbage in this file)

/var/log/messages<http://paste.openstack.org/raw/72198/>

instance.log<http://paste.openstack.org/raw/72205/>

After disabling tracing_on and tracing kvm events, it gave the same error.

Regards,
Arindam


From: parthi...@hp.com
To: arin...@live.com
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
Date: Tue, 4 Mar 2014 14:07:31 +
If you can that'll be great. Thanks.

Also what's in

/sys/kernel/debug/tracing/tracing_on
/sys/kernel/debug/tracing/events/kvm/enable

Try running after
echo 0 > /sys/kernel/debug/tracing/tracing_on

If there's no improvement try - although I don't know what it really does (I 
need to read the code)
echo 0 > /sys/kernel/debug/tracing/events/kvm/enable

I'm just wondering if it's due to some permission/ACL issues when trying to 
write into debugfs using ftrace, given your observation on different tracing 
backends.

Thanks for reporting and spending time on this.

Cheers
~parthi


From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 04 March 2014 13:27
To: Parthipan, Loganathan
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Hi,

Its a multi-node deployment with nova-network.

If you want I can recreate the error and send you the logs.

Regards,

From: parthi...@hp.com
To: arin...@live.com
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
Date: Tue, 4 Mar 2014 13:21:24 +
Interesting...

Is it a single node deployment? Do you have any other log data such as 
libvirt_debug.log, libvirt/qemu/instance-.log? Any errors/warnings during 
the time of instance creation in syslog?

From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 04 March 2014 12:56
To: Parthipan, Loganathan
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)


it only happens when I enable

--enable-trace-backend=ftrace

with
--enable-trace-backend=simple

works fine.


From: parthi...@hp.com
To: arin...@live.com
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
Date: Tue, 4 Mar 2014 12:33:55 +
Also check if it's a cgroups issue since the binary location changed. You could 
look at the syslog and kern.log


From: Parthipan, Loganathan
Sent: 04 March 2014 12:15
To: 'Arindam Choudhury'; openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Reading your log, I don't think the problem is due to injection failure at 
libguestfs. It's a warning and is ignored.

Seems more like a network setup issue. Are you using neutron? Is the 
network/subnet etc setup properly?

From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 04 March 2014 11:50
To: Parthipan, Loganathan; openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Hi Parthipan,

When I try to do yum remove python-libguestfs.
It also wants to remove openstack-nova-compute. So, I can not.

Regards,
Arindam

From: parthi...@hp.com
To: arin...@live.com; openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
Date: Tue, 4 Mar 2014 11:23:50 +
Arindam,

What happens if you 'apt-get remove python-guestfs' and try? I'd expect it to 
fallback to nbdmount.


From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 04 March 2014 10:40
To: openstack@lists.openstack.org
Subject: [Openstack] Error mounting disk with libguestfs (child process died 
unexpectedly)

Hi,
I have a working Openstack Grizzly setup with nova-network on Scientific Linux. 
As, SL comes with a old qemu:

qemu-kvm-0.12.1.2-2.355.el6_4.6.x86_64

I am trying to upgrade it to qemu-1.7.0 from source.

The configuration output<http://pastebin.com/raw.php?i=geEEXm79>.

As, openstack use /usr/libexec/qemu-kvm to start up VM, i linked
qemu-kvm to qemu-system-x86_64:
ls -l /usr/libexec/qemu-kvm lrwxrwxrwx 1 root root 33 Feb 19 15:25 
/usr/libexec/qemu-kvm -> /usr/local/bin/qemu-system-x86_64

But when I try to start VM, I get following error:

WARNING nova.virt.disk.api [req-7dfd6cf1-db21-403d-abbf-ccb5f0

Re: [Openstack] Error mounting disk with libguestfs (child process died unexpectedly)

2014-03-06 Thread Parthipan, Loganathan
Arindam,

If you don’t want to see the error in the logs you can configure 
/etc/nova/nova.conf to

[libvirt]
inject_partition = -2

The guest can then inject files and metadata after it starts up, which is more 
preferable.

~parthi

From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 06 March 2014 09:48
To: 黎林果; openstack@lists.openstack.org
Subject: Re: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Hi,

It will be very helpful if you can share your procedure. My libguestfs version 
is libguestfs-1.16.34-2.el6.x86_64

Date: Thu, 6 Mar 2014 09:24:51 +0800
Subject: Re: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
From: lilinguo8...@gmail.com
To: arin...@live.com
I've been done. The guestfs's python file has a bug.
Bug I forget what is version of the guestfs. If you can't deal the problem, I 
can find out what I have done.

2014-03-05 23:30 GMT+08:00 Arindam Choudhury 
mailto:arin...@live.com>>:

Thanking a lot for helping me.

From: parthi...@hp.com<mailto:parthi...@hp.com>
To: arin...@live.com<mailto:arin...@live.com>
CC: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>

Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
Date: Wed, 5 Mar 2014 15:16:25 +
The guestfs error is due to a misconfiguration of guestfs and will only result 
in not having files injected before booting. Usually this is harmless as 
cloud-init like software will fix it after booting.

Glad the VM booted :)


From: Arindam Choudhury [mailto:arin...@live.com<mailto:arin...@live.com>]
Sent: 05 March 2014 15:10

To: Parthipan, Loganathan
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)


changing /etc/libvirt/qemu.conf helped [Image removed by sender. Image removed 
by sender. Emoji] . clear_emulator_capabilities=0 was already set.

VM boots up, but it still has the same error in log.

log <http://paste.openstack.org/raw/72621/>

instance-log<http://paste.openstack.org/raw/72622/>

ls -alh /var/lib/nova/instances/7d79e021-72a9-4e5c-b2e5-312e16355dcd/
total 52M
drwxr-xr-x 2 nova nova 4.0K Mar  5 15:50 .
drwxr-xr-x 5 nova nova 4.0K Mar  5 15:50 ..
-rw-rw 1 root root  25K Mar  5 15:51 console.log
-rw-r--r-- 1 root root  52M Mar  5 15:51 disk
-rw-r--r-- 1 nova nova 1.6K Mar  5 15:50 libvirt.xml



From: parthi...@hp.com<mailto:parthi...@hp.com>
To: arin...@live.com<mailto:arin...@live.com>; 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
Date: Wed, 5 Mar 2014 13:53:25 +
If that doesn’t work try setting clear_emulator_capabilities=0

From: Parthipan, Loganathan
Sent: 05 March 2014 13:37
To: 'Arindam Choudhury'; 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Try setting user and group to root in /etc/libvirt/qemu.conf

From: Arindam Choudhury [mailto:arin...@live.com<mailto:arin...@live.com>]
Sent: 05 March 2014 13:36
To: Parthipan, Loganathan; 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)


./configure --enable-trace-backend=ftrace --enable-kvm --enable-vhost-net 
--enable-virtfs --target-list=x86_64-linux-user,x86_64-softmmu
...

[邮件部分隐藏]
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

<>___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] [openstack-dev] booting VM with customized kernel and rootfs image

2014-05-13 Thread Parthipan, Loganathan
You can upload your custom kernel/rootdisk pair to glance and use the rootdisk 
uuid to boot an instance.

http://docs.openstack.org/user-guide/content/cli_manage_images.html


From: sonia verma [mailto:soniaverma9...@gmail.com]
Sent: 13 May 2014 06:33
To: OpenStack Development Mailing List (not for usage questions); 
openstack@lists.openstack.org
Subject: [openstack-dev] booting VM with customized kernel and rootfs image

Hi all
I have installed openstack using devstack.I'm able able to boot VM from the 
opebstack dashboard onto the compute node.
Now i need to boot VM from the openstack dashboard(controller node) onto 
compute node using customized kernel imae and rootfs.
Therefore my question is whether can we boot VM from controller node onto 
compute node using the customized kernel and rootfs image.
Please help regarding this.


Thanks
Sonia
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] instances stuck in "powering on"

2014-05-13 Thread Parthipan, Loganathan
Or rather, the compute cannot talk to the conductor. Try setting use_local=true 
in the compute nova.conf and restart nova-compute.

> -Original Message-
> From: Dimitri Maziuk [mailto:dmaz...@bmrb.wisc.edu]
> Sent: 12 May 2014 19:10
> To: openstack@lists.openstack.org
> Subject: [Openstack] instances stuck in "powering on"
> 
> Hi everyone,
> 
> I moved my bootable volumes to better storage (nfs backend) by copying
> files and editing provider_location in cinder db. The instances were
> shut off for that, of course.
> 
> Now when I power them on via dashboard, some (not all) of them get
> stuck in "powering on" for as long as I care to wait. On the compute
> host compute.log is full of
> 
> > TRACE nova.openstack.common.rpc.amqp
> > task run WARNING nova.openstack.common.loopingcall [-] outlasted
> > interval by 50.018454 sec ERROR nova.openstack.common.periodic_task
> [-] Error during ComputeManager._sync_power_states: Timeout while
> waiting on RPC response - topic: "conductor", RPC method:
> "object_class_action" info: ""
> 
> -- completely unhelpful since I'm getting tons of them during normal
> operation, too.
> 
> "virsh start instance-XX" works, "nova reset-state --active" clears
> up the "powering-on" but doesn't mark it "Running" regardless of
> instance's power state.
> 
> So it looks like dashboard can't talk to the compute. Any hints as to
> why & where to look?
> 
> (centos 6.current, rdo, havana, simple stupid setup w/ noop nova
> networking and bootable volumes.)
> 
> TIA
> --
> Dimitri Maziuk
> Programmer/sysadmin
> BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack