[Qemu-discuss] windows 7 guest deactivated after qemu update from 2.0.0 to 2.3.0
after upgradeing my qemu installation from 2.0.0 to 2.3.0 my windows 7 guest installation bacame deactivated. If I run the same disk image with the same parameters in qemu 2.0.0 again windows 7 is still activated. Are there any changes in hardware presented to the guest between qemu versions? The only difference I can see in windows hardware manager is the CPU name. It contains the quemu version number. I tried to use another type of cpu (-cpu kvm64) windows 7 is still deactivated (in qemu 2.0.0). I tried other versions of qemu too. The only way to have an activated windows 7 is to run it in qemu 2.0.0. It's important to know that I used qemu 2.0.0 when activating the installation with an unused OEM key. There must be a difference in hardware seen by windows 7. What hardware cold that be?
Re: [Qemu-discuss] windows 7 guest deactivated after qemu update from 2.0.0 to 2.3.0
Am 09.08.2015 12:50, schrieb Stefan Treuheit: after upgradeing my qemu installation from 2.0.0 to 2.3.0 my windows 7 guest installation bacame deactivated. If I run the same disk image with the same parameters in qemu 2.0.0 again windows 7 is still activated. Are there any changes in hardware presented to the guest between qemu versions? The only difference I can see in windows hardware manager is the CPU name. It contains the quemu version number. I tried to use another type of cpu (-cpu kvm64) windows 7 is still activated (in qemu 2.0.0). I tried other versions of qemu too. The only way to have an activated windows 7 is to run it in qemu 2.0.0. It's important to know that I used qemu 2.0.0 when activating the installation with an unused OEM key. There must be a difference in hardware seen by windows 7. What hardware cold that be? of course the other cpu did not deactivate windows. It must besomething other.
Re: [Qemu-discuss] help using qemu to emulate raspberry pi2
mar.krzeminski writes: > > Hello, > > It seems that it stucks at console opning, is this console is same as in > raspberry? > I do not have raspberry to check it, but I think you do not have ttyAMA0 > in your filesystem... My raspberry doesn't boot so I'm trying to use qemu before I reflash it. The console I run qemu from says: Raspbian GNU/Linux 7 (none) ttyAMA0 and it doesn't loop. sudo mount -o loop,offset=62914560 2015-05-05-raspbian-wheezy.img tmp $ ls tmp bin dev home lost+found mnt proc run selinux sys usr boot etc lib media opt root sbin srv tmp var What am looking for?
Re: [Qemu-discuss] help using qemu to emulate raspberry pi2
This is what the console on the host says (it doesn't loop): Uncompressing Linux... done, booting the kernel. Raspbian GNU/Linux 7 (none) ttyAMA0 (none) login: pi Password: Linux (none) 3.2.0 #1 Sun Jan 29 03:14:15 CST 2012 armv6l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. NOTICE: the software on this Raspberry Pi has not been fully configured. Please run 'sudo raspi-config' Raspbian GNU/Linux 7 (none) ttyAMA0 (none) login:
Re: [Qemu-discuss] help using qemu to emulate raspberry pi2
>init: Id "1" respawning too fast: disabled for 5 minutes. https://wiki.gentoo.org/wiki/Raspberry_Pi/Quick_Install_Guide#Configuring_inittab_and_rc.conf >Comment out the s0 Serial console to stop "INIT: Id "s0" respawning too fast" messages on the console. I have a feeling it has something to do with that error line. And i think the console= kernel parameter needs a baudrate setting, like "console=ttyAMA0,115200". I have little experience with rpi and raspbian, but i've got gentoo running on a physical rpi.
Re: [Qemu-discuss] help using qemu to emulate raspberry pi2
On 09/08/2015 15:34, James wrote: This is what the console on the host says (it doesn't loop): Uncompressing Linux... done, booting the kernel. Raspbian GNU/Linux 7 (none) ttyAMA0 (none) login: pi Password: Linux (none) 3.2.0 #1 Sun Jan 29 03:14:15 CST 2012 armv6l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. NOTICE: the software on this Raspberry Pi has not been fully configured. Please run 'sudo raspi-config' Raspbian GNU/Linux 7 (none) ttyAMA0 (none) login: The following assumes Raspian 7 uses a traditional sysv init process, just like Debian 7. From the emulated ttyAMA0, try looking at the contents of /etc/inittab and try to see which line looks most like it could have "Id 1" . That is the process that keeps failing to run so fast that /sbin/init refuses to relaunch it until a 5 minute cool off period. Then look in /var/log/syslog, /var/log/messages etc. for reasons why that process refuses to run. Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. https://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
