[Qemu-discuss] qemu does not show any output on windows
Hi, I downloaded the qemu binary file and installed on my win7 64-bit machine. I can run qemu-system-i386.exe to load my own disk image. It seems to be working. One strange thing is that the console window (cmd) does not give me any output or error message if I typed some invalid options. It just does not show anything to me. The qemu-system-i386.exe -h does not have any output either. Did I forget any settings? Thanks. Best regards, Kai
[Qemu-discuss] passthrough keyboard/mouse
Hi, I'm running Fedora 21 Alpha with qemu version 2.1.2 and linux kernel 3.16 an a notebook with intel VT-d. Forwarding the graphics card is working really well. The guest system is Windows 7 x64. The only devices that are missing inside the VM are the internal keyboard and mouse. These devices are NOT connected via USB to the host instead they are connected via PS/2 [1.045386] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 [1.047179] i8042: Detected active multiplexing controller, rev 1.1 [1.048002] serio: i8042 KBD port at 0x60,0x64 irq 1 [1.048006] serio: i8042 AUX0 port at 0x60,0x64 irq 12 [1.048025] serio: i8042 AUX1 port at 0x60,0x64 irq 12 [1.048040] serio: i8042 AUX2 port at 0x60,0x64 irq 12 [1.048055] serio: i8042 AUX3 port at 0x60,0x64 irq 12 [1.048186] mousedev: PS/2 mouse device common for all mice Disabling legacy USB support in the BIOS doesn't change anything keyboard/mouse are still connected via PS/2. The PS/2 controller is directly connected to the chipset which appears on the host as an PCI device: 00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) I could imagine that it is not possible to passthrough the chipset to the virtual machine. I want to use the internal keyboard/mouse inside the virtual machine because I wont to use the notebook without the need for an external keyboard. Does qemu provide a possibility to share the host keyboard and mouse with a guest when not using a virtual display? Regards, Tobias
[Qemu-discuss] How to change a VM vcpu core frequency?
Hello, I want to change the vm vcpu core frequency, the vm now is same as host, like 2.8Ghz. Is there is a way to change it, even it just for display. thanks. xuanmao_001
[Qemu-discuss] Memory range addresses involved in qemu
Hello I am new to qemu development. I wanted to print the corresponding addresses involved when a memory has been assigned to a virtual machine. For example, when i invoke the following command qemu-system-i386 ubuntu.img -m 1G I need to be able to print the virtual addresses and physical addresses involved. Like above 1G memory involved: Guest VirtualAddr = 0x12345678..to 0x87654321.. Guest Physical Addr = 0x23456781..to 0x74536733..(This is the one that gets mapped to host virtual memory if my understanding is right). Note: Above numbers are just for explanation. When I looked into the source code of qemu, I see that this size whatever we are mentioning here is assigned as a part of |ram_addr_t| block. But I am not able to find as how to proceed to find the offset for this size.Kindly help me in this regard at the earliest.
[Qemu-discuss] Re (2): running a system installer under QEMU
P.s. ... From: wor...@alum.mit.edu (Dale R. Worley) Date: Thu, 30 Oct 2014 11:58:29 -0400 > The problem that I most expect is the matter of disk interfaces. The > boot loader for reading a SCSI disk might be quite different from the > boot loader for reading an IDE disk. Debian Wheezy denotes an ATA disk as /dev/sdx. https://wiki.debian.org/Persistent_disk_names Likewise for a USB flash store. This QEMU assumes my /dev/sda is a SCSI? Certainly a possible explanation. In my imagination, the Debian port of QEMU recognizes Debian naming conventions. Perhaps not but a solution using "-disk" will help. Thanks, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +1 360 639 0202 http://carnot.yi.org/ Bcc: peter at easthope. ca
Re: [Qemu-discuss] remote 'g' packet reply is too long
Hi, I have solved this problem by modify the GDB source. Download the gdb-7.8 source code, and modify the gdb/remote.c, At 2014-10-31 10:07:49, "孙贝磊" wrote: Hi, I am trying to debug the Linux-64 bit kernel with Qemu, but meet the following problems: Remote 'g' packet reply is too long: 286360816cca690100fc0900685f5481f9774a8136636081b85f5481a05f54810081985f5481d03101006a925d8146001000180018001800180018007f03801f (gdb) I used the latest Qemu version ,Qemu-2.1.2, that I compiled and installed manually. I referred to the solution in http://augustl.com/blog/2014/gdb_progress/ , "set architecture i386:x86-64:intel", but it didn't work. Did any one meet similar problems? And advice is appreciated... Thank you
[Qemu-discuss] Re (2): running a system installer under QEMU
From: wor...@alum.mit.edu (Dale R. Worley) Date: Thu, 30 Oct 2014 11:58:29 -0400 > I suspect what you mean is, "Having loaded the hard drive within the > virtual machine, I can't boot the physical machine off the hard > drive." Exactly. > Also, I note at the URL you provided the statement "These instructions > are tentative and do not yet yield a working Oberon system." Well, I wrote that section. When the instructions work, the notice will be removed. > The problem that I most expect is the matter of disk interfaces. The > boot loader for reading a SCSI disk might be quite different from the > boot loader for reading an IDE disk. Nice insight! Thanks! > You can adjust the disk interface that the virtual machine sees by > using the if= parameter of the -disk option rather than the -hda > option. Google "site:qemu.org -disk" doesn't pan out. "-disk" is a new option not yet documented? Thanks again, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +1 360 639 0202 http://carnot.yi.org/ Bcc: peter at easthope. ca
[Qemu-discuss] Print Memory Address Range
Hello I am new to qemu development. I wanted to print the corresponding addresses involved when a memory has been assigned to a virtual machine. For example, when i invoke the following command qemu-system-i386 ubuntu.img -m 1G I need to be able to print the virtual addresses and physical addresses involved. Like above 1G memory involved: Guest Virtual Addr = 0x12345678..to 0x87654321.. Guest Physical Addr = 0x23456781..to 0x74536733..(This is the one that gets mapped to host virtual memory if my understanding is right). Note: Above numbers are just for explanation. When I looked into the source code of qemu, I see that this size whatever we are mentioning in the command here is assigned as a part of |ram_addr_t| block. But I am not able to find as how to proceed to find the corresponding addresses for this size. Once I find the addresses, I need to perform the encryption of the contents present at this location. Kindly help me in this regard at the earliest.
Re: [Qemu-discuss] running a system installer under QEMU
> From: pe...@easthope.ca > I've installed a system to /dev/sda6 with the machine booted from > the installer diskette. That system boots as expected. > > Also attempted to install the system to /dev/sda5 with the diskette > content running under QEMU as described here. > http://www.ocp.inf.ethz.ch/wiki/Documentation/Installation#toc23 > No problem is evident in the installation process but that system > will not boot. What do you mean by "the system will not boot"? You've set up a virtual machine, and within it, run an installer diskette which set up a hard drive. If you reboot the virtual machine, does it boot correctly? I suspect what you mean is, "Having loaded the hard drive within the virtual machine, I can't boot the physical machine off the hard drive." The problem is probably that the characteristics of the physical machine are different from those of the virtual machine, sufficiently different that the boot code cannot locate the proper drive within the physical machine. Also, I note at the URL you provided the statement "These instructions are tentative and do not yet yield a working Oberon system." > I don't understand how the installer produces such different boot > sectors in the two cases. How can an installer run under QEMU to > obtain a result just as if it was running from the boot device? The problem that I most expect is the matter of disk interfaces. The boot loader for reading a SCSI disk might be quite different from the boot loader for reading an IDE disk. You can adjust the disk interface that the virtual machine sees by using the if= parameter of the -disk option rather than the -hda option. Dale
[Qemu-discuss] remote 'g' packet reply is too long
Hi, I am trying to debug the Linux-64 bit kernel with Qemu, but meet the following problems: Remote 'g' packet reply is too long: 286360816cca690100fc0900685f5481f9774a8136636081b85f5481a05f54810081985f5481d03101006a925d8146001000180018001800180018007f03801f (gdb) I used the latest Qemu version ,Qemu-2.1.2, that I compiled and installed manually. I referred to the solution in http://augustl.com/blog/2014/gdb_progress/ , "set architecture i386:x86-64:intel", but it didn't work. Did any one meet similar problems? And advice is appreciated... Thank you
[Qemu-discuss] Re (2): running a system installer under QEMU
From: wor...@alum.mit.edu (Dale R. Worley) Date: Thu, 30 Oct 2014 11:58:29 -0400 > If you reboot the virtual machine, does it boot correctly? Yes. > You can adjust the disk interface that the virtual machine sees by > using the if= parameter of the -disk option rather than the -hda > option. http://comments.gmane.org/gmane.comp.emulators.qemu/20760 has "-disk file[,if=type][,index=i][,bus=n][,unit=m][,media=d][,cyls=c,heads=h,secs=s[,trans=t]][snapshot=on|off] where: file is the disk image type is the interface type (ide, scsi, floppy, pflash, mtd, sd) i is the index of the disk on the interface (0, 1, 2, ...) n is the bus number of the given type m is the unit number on the the given bus d is the type of the media (disk, cdrom)" Rather than a disk image I aim for a real device. sudo qemu-system-i386 -boot a -fda /home/user/Oberon0.Dsk -disk /dev/sdd,if=ide,media=disk -vga std Is that plausable? Is the "media=disk" suboption necessary? Thanks, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +1 360 639 0202 http://carnot.yi.org/ Bcc: peter at easthope. ca
Re: [Qemu-discuss] qemu does not show any output on windows
On 31 October 2014 14:46, Kai Liu wrote: > Hi, > I downloaded the qemu binary file and installed on my win7 64-bit machine. I > can run qemu-system-i386.exe to load my own disk image. It seems to be > working. One strange thing is that the console window (cmd) does not give me > any output or error message if I typed some invalid options. It just does > not show anything to me. The qemu-system-i386.exe -h does not have any > output either. Did I forget any settings? I think that windows binary is built such that it sends stdout to a file stdout.txt and stderr to a stderr.txt; check whether it's written the help output to those files. -- PMM
[Qemu-discuss] Any way to set boot priority of individual NICs?
Hi, I'm using a system where I need to be able to netboot via eth1. Under virtualbox I can use the "VBoxManage modifyvm --nicbootprio2 1" command to make it attempt to netboot over eth1 before any of the other nics. Is there a way to do anything similar with qemu? Thanks, Chris
Re: [Qemu-discuss] passthrough keyboard/mouse
On 31/10/2014 16:13, Tobias Specht wrote: Hi, I'm running Fedora 21 Alpha with qemu version 2.1.2 and linux kernel 3.16 an a notebook with intel VT-d. Forwarding the graphics card is working really well. The guest system is Windows 7 x64. The only devices that are missing inside the VM are the internal keyboard and mouse. These devices are NOT connected via USB to the host instead they are connected via PS/2 [1.045386] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 [1.047179] i8042: Detected active multiplexing controller, rev 1.1 [1.048002] serio: i8042 KBD port at 0x60,0x64 irq 1 [1.048006] serio: i8042 AUX0 port at 0x60,0x64 irq 12 [1.048025] serio: i8042 AUX1 port at 0x60,0x64 irq 12 [1.048040] serio: i8042 AUX2 port at 0x60,0x64 irq 12 [1.048055] serio: i8042 AUX3 port at 0x60,0x64 irq 12 [1.048186] mousedev: PS/2 mouse device common for all mice Disabling legacy USB support in the BIOS doesn't change anything keyboard/mouse are still connected via PS/2. The PS/2 controller is directly connected to the chipset which appears on the host as an PCI device: 00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) I could imagine that it is not possible to passthrough the chipset to the virtual machine. I want to use the internal keyboard/mouse inside the virtual machine because I wont to use the notebook without the need for an external keyboard. Does qemu provide a possibility to share the host keyboard and mouse with a guest when not using a virtual display? As a more obvious alternative: Does qemu provide a way to pass the host attachedPS/2 keyboard/mouse through to the virtual PS/2 keyboard/mouse of the virtualPC chipset? Note that these areessentially character devices, although only the mouse may bedirectly exposed (as /dev/psaux) by the host kernel. Perhaps some of the options used when qemu powers the XEN Dom0 handling of XEN DomUI/O can do this? Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may contain errors. WiseMo - Remote Service Management for PCs, Phones and Embedded
[Qemu-discuss] Re: running a system installer under QEMU
From: wor...@alum.mit.edu (Dale R. Worley) Date: Thu, 30 Oct 2014 11:58:29 -0400 > You can adjust the disk interface that the virtual machine sees by > using the if= parameter of the -disk option rather than the -hda > option. The problem might be just a disk acess limitation and no problem with QEMU. http://www.ethoberon.ethz.ch/bios.html http://www.ethoberon.ethz.ch/install.html#E3 Although I don't understand why booting from IDE0#6 works while IDE0#5 fails. After November 8 I'll review the problem and post an update. Thanks for the help, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +1 360 639 0202 http://carnot.yi.org/ Bcc: peter at easthope. ca
