Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qemu is broken if configured without --enable-debug option #1

Open
aszeszo opened this issue Sep 8, 2011 · 4 comments
Open

Qemu is broken if configured without --enable-debug option #1

aszeszo opened this issue Sep 8, 2011 · 4 comments

Comments

@aszeszo
Copy link

aszeszo commented Sep 8, 2011

Hi Joyent!

Qemu seems to be broken when configured without --enable-debug option. It is broken for me on two different machines one with dual E5620 CPUs the other one with single i7-2600K CPU.

The easiest way to replicate the problem is to try booting 64-bit CentOS 6 iso. It is booting OK when qemu is configured with --enable-debug. It fails to boot when Qemu is compiled without this option. See the screenshot here: http://i.imgur.com/3oAkc.png

Please fix! :D

Andrzej

@rmustacc
Copy link
Contributor

rmustacc commented Sep 8, 2011

Hi,

We've been able to boot several 64-bit Linux images without using the enable-debug option and the failure you have there is generally seen when Linux can't find a device for the root filesystem.

For starters, what system are you running this on? SmartOS, OI, something else? Where did you get the kvm driver from? Did you build it yourself or are you using it from one of the distributions mentioned above?

It sounds like you're compiling from source, can you verify that for me? If so, are you using ./build.sh or are you manually running configure. If the latter, what configure options are you using?

From there, how are you invoking qemu, what are the arguments that you are using?

Thanks.

@aszeszo
Copy link
Author

aszeszo commented Sep 8, 2011

Hi Robert

I am running OI + recent illumos. Everything is built from source. I
have tried OI packages also and they behave in the same way.

CentOS 6 64-bit ISO + qemu built using default build.sh script is booting fine
CentOS 6 64-bit ISO + qemu built using build.sh script with
--enable-debug removed fails to boot with the "uncompression error"
like in the screenshot.

Ubuntu 11.04 is always booting fine. Doesn't matter if it is
configured with --enable-debug or not.

Andrzej

On 8 September 2011 16:07, Robert Mustacchi
[email protected]
wrote:

Hi,

We've been able to boot several 64-bit Linux images without using the enable-debug option and the failure you have there is generally seen when Linux can't find a device for the root filesystem.

For starters, what system are you running this on? SmartOS, OI, something else? Where did you get the kvm driver from? Did you build it yourself or are you using it from one of the distributions mentioned above?

It sounds like you're compiling from source, can you verify that for me? If so, are you using ./build.sh or are you manually running configure. If the latter, what configure options are you using?

From there, how are you invoking qemu, what are the arguments that you are using?

Thanks.

Reply to this email directly or view it on GitHub:
#1 (comment)

@rmustacc
Copy link
Contributor

rmustacc commented Sep 8, 2011

Andrzej, can you share what arguments you're using to invoke QEMU for both the Ubuntu and CentOS case?

@aszeszo
Copy link
Author

aszeszo commented Sep 8, 2011

Here are the command lines I have been using for testing:

pfexec /opt/qemu/bin/qemu-system-x86_64
-vnc 0.0.0.0:1
-enable-kvm
-smp 2
-m 2048
-no-hpet
-localtime
-drive file=/export/isos/ubuntu-11.04-desktop-amd64.iso,media=cdrom,if=ide,index=2
-vga std

pfexec /opt/qemu/bin/qemu-system-x86_64
-vnc 0.0.0.0:1
-enable-kvm
-smp 2
-m 2048
-no-hpet
-localtime
-drive file=/export/isos/CentOS-6.0-x86_64-minimal.iso,media=cdrom,if=ide,index=2
-vga std

citrus-it pushed a commit to citrus-it/illumos-kvm-cmd that referenced this issue Feb 22, 2019
OS-7566 Clean up qemu use of old CTF tools
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants