LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 03-04-2005, 04:51 AM   #1
bitpicker
Member
 
Registered: Jul 2003
Location: Germany
Distribution: Xubuntu, Ubuntu
Posts: 416
Blog Entries: 14

Rep: Reputation: 35
qemu: qemu stopped right after command exec


I have recently tried to boot a Knoppix CD with qemu - I've done it before, and it always worked. However, I seem to have made an error in the parameters then, and that time it failed. Now the problem is that since then, qemu only opens the emulator window with a blank, black screen, and in the window title there appears 'qemu stopped'. This only happens when I try to use it as the user who made the error, as root it works as usual, and with the same command. The stopped window does not react to attempts of starting the console (ctrl + 2) either, so I have no idea how to restart the emulation. There seems to be some kind of temp file or config file which prompts qemu to stop immediately, as this behaviour also survives a reboot, but I cannot find any in either the home directory or /tmp.

The command I am using is

qemu -cdrom /dev/cdrom -boot d -snapshot -m 256

It doesn't matter which bootable CD I put in the drive, the behaviour is always the same. Does anyone know how to change this setting or how to unfreeze qemu?

Robin
 
Old 03-04-2005, 11:25 PM   #2
bigrigdriver
LQ Addict
 
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian Squeeze
Posts: 5,783

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
It sometimes happens, rarely, but sometimes, that an error condition can be preserved in a file which is essentially a temporary file. The file is preserved if the error causes the program to terminate abnormally, or if the program is closed improperly. Such files names usually end with ~ (tilde) or _ (underscore).
What I suggest is a tedious, time-consuming solution. But, it may solve your problem.
Use 'find' to search for filenames ending with ~ or _. Such as: find *.*~ or find *.*_. Redirect the output to a text file ( > find.txt) to study at your convenience. Depending on the size of your OS, it will take a long time.
Look for files ending with ~ or _, especially those relative to gemu and cdrom. You may have an error condition trapped in a temporary file which will plague you until you remove it.

To reduce the time required to find the offending file, use 'find' on the following directories: /etc, /home, /var, and /tmp. They are the most likely locations for such a file.

Last edited by bigrigdriver; 03-04-2005 at 11:28 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
QEmu mtecknology Linux - Software 5 09-14-2007 05:30 AM
qemu paul_mat Linux - General 3 12-09-2005 12:48 PM
qemu gaah Linux - Newbie 6 10-19-2005 05:22 AM
Qemu BarfBag Linux - Software 3 06-03-2005 01:06 PM
qemu RySk8er30 Linux - Software 1 06-01-2005 07:23 PM


All times are GMT -5. The time now is 07:04 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration