[Qemu-devel] Weird Issue with IDE
I am doing something specific and slightly different than normal uses. Would appreciate if someone can help me with a pointer as to what I can do next. I am kinda stuck at this point. My experiment is trying to move the PIIX4 chipset (which currently resides on dev 1, func 0/1/2/3/) to dev 2 (same function sequence). I have modified the ACPI tables to report the IRQ mapping accordingly, which is probably not useful for IDE anyway as it just uses the legacy IRQ14/15 interrupts. Unfortunately, my Linux kernel fail to find the IDE device when I do this simple change. I have compiled the kernel to dump code from its ATA driver and it does tell me that the interrupt handler is invoked for IRQ14 and IRQ15, so this may not be an interrupt routing issue (which is what I first assumed it to be). Is there some other code in qemu that resides on PCI slot location of the IDE controller? My current modification to change the PCI slot is very simple (I just change the pci_create_simple_multifunction call in i440fx_init to put that on devfn 0x10, instead of default). I am comparing the dmesg dump for normal kernel boot (with default PIIX4 on dev 1) vs modified qemu boot (which just lands me to initramfs shell if I choose console to ttyS0, as it complains it could not find IDE disk). I tried to attach the the console output and the dmesg output for the both cases, but the mail bounced back on me, perhaps it does not accept 250K attachment. In the latter case, the ports are disabled after recovery and validate routines are called in ata driver code in the kernel. I would appreciate if someone can give any pointers on what may be going wrong with this simple change? And what more may be required in qemu to change the PCI slot of the PIIX4 controller. I assumed this should be a simple change, but apparently not so simple :-( -- Adhyas Two types have compatible type if their types are the same. — ANSI C Standard, 3.1.2.6.
[Qemu-devel] PS2 Mouse/Kbd do not work with qemu-0.13.0
I have issues with both PS2 Mouse and Keyboard working out of the box with virgin qemu-0.13.0 code base. The host is Ubuntu 10.04 x86_64 and I am making a 64-bit build for x86_64-softmmu Sometimes (for some guest environments, e.g. Ubuntu 10.10. x86_64) the mouse does not work within the guest, while the keyboard does. In some other environments, the keyboard does not work as well. Has anyone else witnessed the same issue? Are there any known workarounds I can use to move ahead? USB keyboard/mouse do work, but I cannot use that workaround for the work I am doing as I don't have USB drivers in my BIOS yet. I will appreciate any responses that can help me get unblocked. Thanks, Adhyas Two types have compatible type if their types are the same. — ANSI C Standard, 3.1.2.6.
[Qemu-devel] Re: PS2 Mouse/Kbd do not work with qemu-0.13.0
I am trying to use it on my custom build of open source EFI BIOS (which does not use interrupts, and uses only polling) and this does not work. Also, PS2 Mouse does not work for Ubuntu 10.10. x86_64 guest for me. Oh, and the same BIOS (and its driver) work just fine for 0.12.5 and 0.12.3, but does not work for 0.13.0 If that helps prove my case further. I am trying to debug more. Thanks, Adhyas On Tue, Nov 16, 2010 at 1:52 PM, Adhyas Avasthi adh...@gmail.com wrote: I have issues with both PS2 Mouse and Keyboard working out of the box with virgin qemu-0.13.0 code base. The host is Ubuntu 10.04 x86_64 and I am making a 64-bit build for x86_64-softmmu Sometimes (for some guest environments, e.g. Ubuntu 10.10. x86_64) the mouse does not work within the guest, while the keyboard does. In some other environments, the keyboard does not work as well. Has anyone else witnessed the same issue? Are there any known workarounds I can use to move ahead? USB keyboard/mouse do work, but I cannot use that workaround for the work I am doing as I don't have USB drivers in my BIOS yet. I will appreciate any responses that can help me get unblocked. Thanks, Adhyas Two types have compatible type if their types are the same. — ANSI C Standard, 3.1.2.6. -- Adhyas Two types have compatible type if their types are the same. — ANSI C Standard, 3.1.2.6.
Re: [Qemu-devel] Issue with compiling qemu-0.13.0.-rc1
Anthony Are you sure that this error is because the make version is not similar to yours? As I said, I cannot even make the rc1 image. The last stable image I can make is qemu-0.12.5 Even 0.12.5 also gives the make output initially that says could not find -include but continues to build without any issues. Maybe we decided to break build on this warning for 0.13 rc? I guess I am still stuck at this error and cannot compile qemu on my box. As for compiling with different targets, I am getting similar behavior for the following targets specifically i386-softmmu, x86_64-softmmu, ppc-softmmu If I give the target as x86_64-linux-user I get a different error (output reproduced below): bash-3.2$ make Makefile:331: no file name for `-include' GEN config-host.h GEN trace.h Makefile:23: no file name for `-include' make-3.79.1-p7[1]: *** No rule to make target `i386-dis.o', needed by `all'. Stop. make-3.79.1-p7: *** [subdir-libdis-user] Error 2 Any pointers to unblock me will be very helpful. Thanks, Adhyas
Re: [Qemu-devel] Issue with compiling qemu-0.13.0.-rc1
Alright, so I updated the version of make to what you have(3.81 GNU Make built for x86_64-redhat-linux-gnu) When I build the RC1 image now, I get a bunch of compile time errors (different than what I saw before). Reproduced below. Not sure if this is because RC1 code has issues or something to do with my environment. GEN libhw64/qemu-options.def CClibhw64/vl.o CClibhw64/loader.o /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.c:45:16: error: hw.h: No such file or directory In file included from /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.c:46: /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/disas.h:28: error: expected declaration specifiers or '...' before 'target_phys_addr_t' In file included from /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.c:50: /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:7: error: expected declaration specifiers or '...' before 'target_phys_addr_t' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:12: error: expected declaration specifiers or '...' before 'target_phys_addr_t' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:13: error: expected declaration specifiers or '...' before 'target_phys_addr_t' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:14: error: expected declaration specifiers or '...' before 'target_phys_addr_t' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:15: error: expected declaration specifiers or '...' before 'target_phys_addr_t' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:18: error: expected declaration specifiers or '...' before 'target_phys_addr_t' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:20: error: expected declaration specifiers or '...' before 'target_phys_addr_t' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:25: error: expected declaration specifiers or '...' before 'target_phys_addr_t' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:27: error: expected declaration specifiers or '...' before 'target_phys_addr_t' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:30: error: expected declaration specifiers or '...' before 'target_phys_addr_t' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.h:31: error: expected ')' before 'addr' /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.c:51:20: error: fw_cfg.h: No such file or directory /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.c:53: error: stray '##' in program /auto/cats5/adavasth/svn/qemu-0.13.0-rc1/loader.c:53: error: expected '=', ',', ';', 'asm' or '__attribute__' before '' token (and the errors follow). Thanks, Adhyas
Re: [Qemu-devel] Issue with compiling qemu-0.13.0.-rc1
The OS is RedHat Thanks, Adhyas
Re: [Qemu-devel] Issue with compiling qemu-0.13.0.-rc1
Seems like my toolchain set up was not proper. Resolved the build environment and it seems to build RC1 (target x86_64-softmmu) for me now. Will let you know if I can repro the issue again. I will try to build the other targets now. - Adhyas
Re: [Qemu-devel] Issue with compiling qemu-0.13.0.-rc1
Thanks for the response. I tried './configure' without any arguments and still the same issue. Find the output from ./configure and make attached. Thanks, Adhyas On Sat, Sep 11, 2010 at 10:37 AM, Anthony Liguori anth...@codemonkey.ws wrote: Please include the full output of configure. Why are you explicitly using --disable-kvm and --disable-xen? Regards, Anthony Liguori out_configure Description: Binary data out_make Description: Binary data
Re: [Qemu-devel] Issue with compiling qemu-0.13.0.-rc1
bash-3.2$ make --version GNU Make version 3.79.1-p7, by Richard Stallman and Roland McGrath. Built for i686-pc-linux-gnu Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 2000 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This is really blocking my work at this point as I cannot even compile. Is there a workaround that can unblock me for the time being ? Thanks, Adhyas On Sun, Sep 12, 2010 at 12:26 PM, Anthony Liguori anth...@codemonkey.ws wrote: What's the output of 'make --version'?
Re: [Qemu-devel] Issue with compiling qemu-0.13.0.-rc1
I tried qemu-0.13.0-rc1 and it has the same issues on this machine. Let me try what you suggest. Thanks, Adhyas On Sun, Sep 12, 2010 at 3:21 PM, Andreas Färber andreas.faer...@web.de wrote: Try giving an explicit --target-list= to configure, to narrow down what build step causes this. There may be subtle dependency issues, cf. my recent patch trace: Fix user emulator dependency on trace objects which fixes a similar issue. As for blocking your work, just try the last stable version.
[Qemu-devel] Issue with compiling qemu-0.13.0.-rc1
When I try to run the following commands on rc1 or fresh git (synced 5 minutes back), I get the following error: bash-3.2$ ./configure --disable-kvm --disable-xen bash-3.2$ make Makefile:24: no file name for `-include' make-3.79.1-p7[1]: *** No rule to make target `loader.o', needed by `all'. Stop. make-3.79.1-p7: *** [subdir-libhw32] Error 2 Any pointers as to what might be causing it? -- Adhyas Two types have compatible type if their types are the same. — ANSI C Standard, 3.1.2.6.
[Qemu-devel] PCIe Qemu changes for Q35
Hi Isaku I believe you were working on the Q35 chipset and PCIe emulation for the same, and planned to check your code in to the main git. I can use some of that work for something I am working on. I have not been too active on the mailing list, and might have missed your reviews if you have sent already. In that case, please disregard my email (and let me know privately). Otherwise, If you can share your plan of sending the review and checking the code, it would give me some idea of when I can expect the PCIe changes in the git. I am mostly interested in your PCIe code (and not Q35) for now. My apologies if I am sounding pushy, I just want to see if your plan falls within my requirement schedule and I can use your code. Awaiting your response. Thanks, Adhyas Two types have compatible type if their types are the same. — ANSI C Standard, 3.1.2.6.
[Qemu-devel] Graphics Device Passthrough
Hello (newbie hacker to qemu community, so please excuse novice ignorances) I wish to pass-through a graphics controller to my Windows 7 VM running on qemu-kvm. I would like it to be PCI-Express (if that works, that is). Are there any recommended devices that I should purchase for this experiment? I would like the device to also be accessible from my Fedora Core 10 host. Basically, I wish to have the device pass-through when I run the VM, I then wish to eject the device out of the VM (hot-remove), and then give it back to Fedora Core 10 to use. This is how my experiment is defined. I am looking for suggestions on graphics controllers I should think of purchasing for this experiment. Any help would be appreciated. Thanks, Adhyas
