From: Stefan Hajnoczi <stefanha@gmail.com>
To: arun.sasi1@wipro.com
Cc: libvirt-users@redhat.com, stefanha@linux.vnet.ibm.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qcow2
Date: Thu, 19 May 2011 09:22:37 +0100 [thread overview]
Message-ID: <BANLkTikTYV8Kr9GD+D=AtHkVo_Eh8sZV7A@mail.gmail.com> (raw)
In-Reply-To: <2E7A71644A98EC4983B36C4946F763F133F0AF@blr-mgr-msg.wipro.com>
On Wed, May 18, 2011 at 7:03 PM, <arun.sasi1@wipro.com> wrote:
> I was getting only the problem with audio(only Warning and error log) when I
> checking the logs
>
> {snip}
>
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
> HOME=/root USER=root LOGNAME=root TMPDIR=/tmp/root-tmp.2af1b17/files
> /usr/bin/kvm -S -M pc -m 512 -smp 4 -name sy0005embinf02 -uuid
> 9ddfc4b5-51bc-c3e9-3aea-59101bc15174 -monitor pty -pidfile
> /var/run/libvirt/qemu//sy0005embinf02.pid -boot c -drive
> file=,if=ide,media=cdrom,index=2 -drive
> file=/var/lib/libvirt/images/sy0005embinf02.img,if=virtio,index=0,boot=on
> -drive file=/var/lib/libvirt/images/sy0005embinf02_vdb.img,if=virtio,index=1
> -net nic,macaddr=00:16:36:1d:67:9e,vlan=0,model=virtio -net
> tap,fd=23,script=,vlan=0,ifname=vnet2 -serial pty -parallel none -usb -vnc
> 127.0.0.1:2 -k en-us -soundhw es1370
>
>
>
> cont
>
> oss: Could not initialize DAC
>
> oss: Failed to open `/dev/dsp'
>
> oss: Reason: No such file or directory
>
> oss: Could not initialize DAC
>
> oss: Failed to open `/dev/dsp'
>
> oss: Reason: No such file or directory
>
> audio: Failed to create voice `es1370.dac2'
>
> oss: Could not initialize ADC
>
> oss: Failed to open `/dev/dsp'
>
> oss: Reason: No such file or directory
>
> oss: Could not initialize ADC
>
> oss: Failed to open `/dev/dsp'
>
> oss: Reason: No such file or directory
>
> audio: Failed to create voice `es1370.adc'
These audio messages look like warnings, not fatal errors, but I am
not sure. I would view the VM details using virt-manager and remove
the sound card device from the VM if you don't need it.
> {snip}
There were no further error messages indicating that starting the VM failed?
>
>
>
> When it was not booting up I just given full permission
>
> -rw-r--r-- 1 root root 384M 2010-10-06 08:01 sy0005embinf01.img.gz
>
> -rw-rw-rw- 1 root root 45 2010-10-06 15:43 SLBTemplate.img
>
> -rw-r--r-- 1 root root 45 2010-10-14 11:44 sy0005embapp01.img
>
> -rw-r--r-- 1 root root 412K 2011-01-08 19:54 sy0005embinf02_vdd.img
>
> -rwxrwxrwx 1 root root 609G 2011-05-18 23:41 sy0005embinf02_vdb.img
>
> -rw-rw-rw- 1 root root 41G 2011-05-18 23:51 sy0005embinf02.img
>
> -rw-rw-rw- 1 root root 2.0G 2011-05-18 23:52 sy0005embinf01.img
>
> -rw-rw-rw- 1 root root 3.8G 2011-05-18 23:52 sy0005embldap01.img
>
>
>
> Note: it was not working after the full permission too...
>
>
>
> Was there any caching problem after the reboot…???
You mentioned using QCOW2. Use "qemu-img check
sy0005embinf02_vdb.img" to run a consistency check on the image file.
There should be no fatal errors.
Stefan
next prev parent reply other threads:[~2011-05-19 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2E7A71644A98EC4983B36C4946F763F133F099@blr-mgr-msg.wipro.com>
[not found] ` <20110518155803.GA23434@stefanha-thinkpad.localdomain>
2011-05-18 16:18 ` [Qemu-devel] Qcow2 arun.sasi1
2011-05-18 16:58 ` Stefan Hajnoczi
2011-05-18 18:03 ` arun.sasi1
2011-05-19 8:22 ` Stefan Hajnoczi [this message]
2011-05-19 14:24 ` arun.sasi1
2011-05-19 19:05 ` Stefan Hajnoczi
2011-05-30 8:53 ` arun.sasi1
2011-05-30 9:31 ` arun.sasi1
2011-06-07 17:10 ` arun.sasi1
2011-06-08 8:19 ` Stefan Hajnoczi
2011-06-08 9:02 ` arun.sasi1
2011-06-16 9:56 ` [Qemu-devel] Base server as file server arun.sasi1
2011-06-16 10:36 ` Stefan Hajnoczi
2011-06-16 10:46 ` arun.sasi1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTikTYV8Kr9GD+D=AtHkVo_Eh8sZV7A@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=arun.sasi1@wipro.com \
--cc=libvirt-users@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).