[Qemu-devel] kqemu version 1.3.0pre5 build failure on 2.6.16-1.2080_FC5

2006-08-20 Thread dragoran

Hello
I tryed to build kqemu on FC5 using 2.6.16-1.2080_FC5 and it fails 
because map_mem is undeclared.
The attached patch fixes it for me (remove to defines) but its likly to 
break older kernels. So a better one is needed.

Anyway I decided to report it here.
Patch is attached.
PS:
Please CC me as I am not suscribed to the list.
diff -ru kqemu-1.3.0pre5.org/kqemu-linux.c kqemu-1.3.0pre5/kqemu-linux.c
--- kqemu-1.3.0pre5.org/kqemu-linux.c	2006-03-27 22:58:01.0 +0200
+++ kqemu-1.3.0pre5/kqemu-linux.c	2006-04-12 09:20:10.0 +0200
@@ -22,12 +22,12 @@
 #if LINUX_VERSION_CODE  KERNEL_VERSION(2,4,19)
 #error Linux 2.4.19 or above needed
 #endif
-
+/*
 #ifndef page_to_pfn
 #define page_to_pfn(page) ((page) - mem_map)
 #define pfn_to_page(pfn) (mem_map + (pfn))
 #endif
-
+*/
 #ifdef PAGE_KERNEL_EXEC
 #if defined(__i386__)
 /* problem : i386 kernels usually don't export __PAGE_KERNEL_EXEC */
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-30 Thread Christian MICHON
I tried various guests today on winXP host.

* No crash and good speed for std kqemu (no kernel-kqemu)
* Crash of winXP host systematically on all guests (linux + ms)

It's hard to debug what is the problem. The only thing I have the
time to see is a BSOD (blue screen of d**th) and the error
message, informative ?

TRAP_CAUSE_UNKNOWN

Good job overall :) Kudos to the developpers.

Maybe we can make it a bartpe plugin one day, automatically
started with kqemu on ? That would be nice to promote
qemu virtualization features...

On 3/27/06, Fabrice Bellard [EMAIL PROTECTED] wrote:
 Hi,

 I just released a new version of kqemu which fixes some recently
 discovered issues. The fixes are the following:

 - Workaround for full virtualization on Windows host (more tests needed).


--
Christian


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-30 Thread denis . scheidt
Hello,

I have the same issues as Christian : I'm unable to get -kernel-kqemu option to
work.

My configuration :

Host : Windows XPpro SP2 on Intel P4HT

QEMU : 0.8.0 latest CVS version.
qemu.exe process' affinity set to second 'CPU' (with ImageCfg, but the result is
the same if set with ProcExp or with TaskMgr)

Guests :
* Windows 2000 SP4 : freezes just after loading splash screen...
* Ubuntu 5.10  : gives a kernel panic...

Procexp shows about 100% CPU usage in kernel mode... but it's possible to switch
to QEMU console and 'q'uit.

Everything works great when I don't use kernel-kqemu...

Am I missing something ?


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Brad Campbell

Fabrice Bellard wrote:

Hi,

I just released a new version of kqemu which fixes some recently 
discovered issues. The fixes are the following:


- Support for guest Linux kernels compiled with gcc = 3.3



Tested with 2.4.26  2.6.16 - gcc-3.2, gcc-3.3, gcc-3.4  gcc-4.0.2
Win2k-SP3, Win2k-SP4, WinXP-SP1, WinXP-SP2
AthlonXP, Sempron  PIII-M

and all combinations of.

Nice work :)

--
Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so. -- Douglas Adams


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Kazu
Sent: Tuesday, March 28, 2006 6:30 AM Fabrice Bellard wrote:

 Hi,

 I just released a new version of kqemu which fixes some recently
 discovered issues. The fixes are the following:

 - Support for guest Linux kernels compiled with gcc = 3.3

 - x86_64 host support is working again (only i386 on x86_64 full
 virtualization has been tested, x86_64 on x86_64 is implemented but not
 tested yet).

 - Workaround for full virtualization on Windows host (more tests needed).


I tested Linux guest/WinXP host but the host OS crashed.

Redhat 7.2 guest/Fedora Core 4 host with normal kqemu is slower
than -no-kqemu. Why ?

Regards,
Kazu



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Brad Campbell

Kazu wrote:


I tested Linux guest/WinXP host but the host OS crashed.


I believe -kernel-kqemu is still somewhat experimental on Windows host.


Redhat 7.2 guest/Fedora Core 4 host with normal kqemu is slower
than -no-kqemu. Why ?


Have you got your tmpfs set up correctly so qemu can place its memory swap file in a ramdisk rather 
than on disk?


/dev/hda1 4.6G  3.1G  1.4G  69% /
tmpfs 506M 0  506M   0% /dev/shm
/dev/hda2 4.6G  4.5G  103M  98% /home
/dev/hda6  44G   44G  424K 100% /tracks
none  768M  137M  632M  18% /tmp  -- not sure why it says 
none.. it's tmpfs

Regards,
Brad
--
Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so. -- Douglas Adams


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Marco Matthies

Brad Campbell wrote:
none  768M  137M  632M  18% /tmp  -- not sure why it 
says none.. it's tmpfs


change the none to tmpfs in /etc/fstab. normally the mount point goes 
there, but tmpfs (and proc, for example) don't have a mount point so you 
can put anything there.


marco


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread andrzej zaborowski
On 28/03/06, Marco Matthies [EMAIL PROTECTED] wrote:
 Brad Campbell wrote:
  none  768M  137M  632M  18% /tmp  -- not sure why it
  says none.. it's tmpfs

 change the none to tmpfs in /etc/fstab. normally the mount point goes
 there, but tmpfs (and proc, for example) don't have a mount point so you
 can put anything there.
You mean they don't have a device node. They do have mountpoints.

Regarding crashes of the host OS, that might have nothing to do with
QEMU. Ms Windows is known to be an experimental OS in general (by
experimental I mean that it crashes a lot) :-)
Normal Operating Systems don't crash no matter what program they are running.

 marco


 ___
 Qemu-devel mailing list
 Qemu-devel@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/qemu-devel



--
balrog 2oo6

Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Paul Brook
 Normal Operating Systems don't crash no matter what program they are
 running.

Except that kqemu is a kernel module (or windows equivalent). As such it is 
effectively part of the OS, and can easily crash the whole machine.

Paul


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Bruno Abinader
Works fine on my computer too!

OS: Ubuntu 5.10 (Breezy Badger)
CPU: Athlon XP 2000+ (with kernel 2.6.12-10-k7)
Using latest CVS version of QEMU with some USB patches from http://gnome.dnsalias.net/patches/On 3/28/06, 
Paul Brook [EMAIL PROTECTED] wrote:
 Normal Operating Systems don't crash no matter what program they are running.Except that kqemu is a kernel module (or windows equivalent). As such it iseffectively part of the OS, and can easily crash the whole machine.
Paul___Qemu-devel mailing listQemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel-- Bruno de Oliveira Abinader10LE/INdT
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Kazu
Sent: Tuesday, March 28, 2006 8:50 PM Brad Campbell wrote:


 Kazu wrote:

 I tested Linux guest/WinXP host but the host OS crashed.

 I believe -kernel-kqemu is still somewhat experimental on Windows host.

 Redhat 7.2 guest/Fedora Core 4 host with normal kqemu is slower
 than -no-kqemu. Why ?

 Have you got your tmpfs set up correctly so qemu can place its memory swap
file in a ramdisk rather
 than on disk?


I used tmpfs but the result is the same. Thanks, anyway.

Regards,
Kazu



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Ed Swierk
I'm still getting a kernel panic running a Linux guest kernel with
-kernel-qemu. I'm using kqemu-1.3.0pre5 and
qemu-snapshot-2006-03-27_23.

The guest kernel is a precompiled Fedora Core 4 kernel, version
2.6.14-1.1656_FC4. It works fine with kqemu in non-kernel-kqemu mode.

Any hints for how to track this problem down?

--Ed
Linux version 2.6.14-1.1656_FC4 ([EMAIL PROTECTED]) (gcc version 4.0.2 20051125 
(Red Hat 4.0.2-8)) #1 Thu Jan 5 22:13:22 EST 2006
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009fc00 (usable)
 BIOS-e820: 0010 - 1000 (usable)
0MB HIGHMEM available.
256MB LOWMEM available.
Using x86 segment limits to approximate NX protection
DMI not present.
ACPI: Unable to locate RSDP
Allocating PCI resources starting at 2000 (gap: 1000:f000)
Built 1 zonelists
Kernel command line: bootdev=hda1 bootnod=b,3,1 boottype=vfat 
bootdir=/swi/Aros-1.3.0 console=ttyS0 selinux=0
Initializing CPU#0
CPU 0 irqstacks, hard=c03f3000 soft=c03f2000
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 3000.676 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 254412k/262144k available (2099k kernel code, 7072k reserved, 718k 
data, 172k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 6043.49 BogoMIPS (lpj=12086981)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
monitor/mwait feature present.
using mwait in idle threads.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
mtrr: v2.0 (20020519)
CPU: Intel(R) Pentium(R) D CPU 3.00GHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
checking if image is initramfs... it is
Freeing initrd memory: 1232k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf9ce0, last bus=0
PCI: Using configuration type 1
ACPI: Subsystem revision 20050916
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router PIIX/ICH [8086/7000] at :00:01.0
PCI: BIOS reporting unknown device 01:00
PCI: BIOS reporting unknown device 01:00
PCI: BIOS reporting unknown device 01:00
PCI: BIOS reporting unknown device 01:00
PCI: BIOS reporting unknown device 01:00
PCI: Ignore bogus resource 6 [0:0] of :00:02.0
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
audit: initializing netlink socket (disabled)
audit(1143569137.708:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 86D1D7472B6BE898
- User ID: Red Hat, Inc. (Kernel Module GPG key)
PCI: PIIX3: Enabling Passive Release on :00:01.0
Limiting direct PCI/PCI transfers.
Activating ISA DMA hang workarounds.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
isapnp: Scanning for PnP cards...
isapnp: No Plug  Play device found
Real Time Clock Driver v1.12
Linux agpgart interface v0.101 (c) Dave Jones
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 32 ports, IRQ sharing enabled
invalid operand:  [#1]
Modules linked in:
CPU:0
EIP:0060:[c0101147]Not tainted VLI
EFLAGS: 00010246   (2.6.14-1.1656_FC4)
EIP is at mwait_idle+0x2f/0x41
eax: c03c1008   ebx: c03c1008   ecx:    edx: 
esi: c03c1000   edi: 0010   ebp:    esp: c03c1fc4
ds: 007b   es: 007b   ss: 0068
Process swapper (pid: 0, threadinfo=c03c1000 task=c0361c60)
Stack: 0800 c03c1000 c0113749 c03c1000 0800 00099100 c03bd800 00461007
   c01010a6 c03c270a 004c c03c22e9  c03f4e60 c0100199
Call Trace:
 [c0113749] apm_cpu_idle+0x5e/0x157
 [c01010a6] cpu_idle+0x34/0x4c
 [c03c270a] start_kernel+0x15f/0x1b9
 [c03c22e9] unknown_bootoption+0x0/0x1b6
Code: 00 f0 ff ff 21 e2 8b 42 08 a8 08 75 2d 0f ba 6a 08 10 89 d6 8d 5a 08 31 
c9 eb 0c 89 c8 0f 01 c9 8b 46 08 a8 08 75 0e 89 d8 89 ca 0f 01 c8 8b 46 08 a8 
08 74 e6 0f ba 76 08 10 5b 5e c3 83 ec 04
 0Kernel panic - not syncing: Attempted to kill the idle task!
 [c011a858] panic+0x45/0x1b4
 [c011baa0] profile_task_exit+0x30/0x43
 [c011d610] do_exit+0x375/0x3b8
 [c01037e7] do_divide_error+0x0/0xa8
 [c0103977] do_invalid_op+0x0/0xab
 [c0103a19] 

Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Brad Campbell

Ed Swierk wrote:

I'm still getting a kernel panic running a Linux guest kernel with
-kernel-qemu. I'm using kqemu-1.3.0pre5 and
qemu-snapshot-2006-03-27_23.

The guest kernel is a precompiled Fedora Core 4 kernel, version
2.6.14-1.1656_FC4. It works fine with kqemu in non-kernel-kqemu mode.

Any hints for how to track this problem down?


I was getting an almost _identical_ error on my laptop.. turned out I had forgot to copy the latest 
and greatest bios *.bin files to /usr/local/share/qemu


Updated the bios from the cvs source dir and it's all been peachy since..

Hope yours is similar..

You do need to be running the absolute latest cvs really for this to work 
properly..
My desktop was ok, but my laptop was a couple of days worth of commits out of 
date and *boom*

Brad
--
Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so. -- Douglas Adams


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Jens Axboe
On Tue, Mar 28 2006, Ed Swierk wrote:
 I'm still getting a kernel panic running a Linux guest kernel with
 -kernel-qemu. I'm using kqemu-1.3.0pre5 and
 qemu-snapshot-2006-03-27_23.
 
 The guest kernel is a precompiled Fedora Core 4 kernel, version
 2.6.14-1.1656_FC4. It works fine with kqemu in non-kernel-kqemu mode.
 
 Any hints for how to track this problem down?

[snip]

 monitor/mwait feature present.
 using mwait in idle threads.

[snip]

 invalid operand:  [#1]
 Modules linked in:
 CPU:0
 EIP:0060:[c0101147]Not tainted VLI
 EFLAGS: 00010246   (2.6.14-1.1656_FC4)
 EIP is at mwait_idle+0x2f/0x41

I don't think qemu supports PNI, which includes the monitor/mwait
additions. I wonder why Linux detects that. You can probably get around
it for now by either passing idle=poll as a boot parameter, or compile
your kernel for plain i586 for instance.

-- 
Jens Axboe



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Ed Swierk
On 3/28/06, Jens Axboe [EMAIL PROTECTED] wrote:
  monitor/mwait feature present.
  using mwait in idle threads.

 [snip]

  invalid operand:  [#1]
  Modules linked in:
  CPU:0
  EIP:0060:[c0101147]Not tainted VLI
  EFLAGS: 00010246   (2.6.14-1.1656_FC4)
  EIP is at mwait_idle+0x2f/0x41

 I don't think qemu supports PNI, which includes the monitor/mwait
 additions. I wonder why Linux detects that. You can probably get around
 it for now by either passing idle=poll as a boot parameter, or compile
 your kernel for plain i586 for instance.

It seems that with -kernel-kqemu, the guest kernel is seeing the CPUID
of the host machine rather than the one normally generated by qemu.

The workarounds you suggest do work--thanks for your help. However,
ideally kqemu would trap the CPUID instruction and mask the feature
bits for unsupported CPU features.

--Ed
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-28 Thread Fabrice Bellard

Ed Swierk wrote:

On 3/28/06, Jens Axboe [EMAIL PROTECTED] wrote:


monitor/mwait feature present.
using mwait in idle threads.


[snip]



invalid operand:  [#1]
Modules linked in:
CPU:0
EIP:0060:[c0101147]Not tainted VLI
EFLAGS: 00010246   (2.6.14-1.1656_FC4)
EIP is at mwait_idle+0x2f/0x41


I don't think qemu supports PNI, which includes the monitor/mwait
additions. I wonder why Linux detects that. You can probably get around
it for now by either passing idle=poll as a boot parameter, or compile
your kernel for plain i586 for instance.



It seems that with -kernel-kqemu, the guest kernel is seeing the CPUID
of the host machine rather than the one normally generated by qemu.

The workarounds you suggest do work--thanks for your help. However,
ideally kqemu would trap the CPUID instruction and mask the feature
bits for unsupported CPU features.


The problem is that it is not possible to trap on the CPUID instruction 
:-( So the only possible patch is to support PNI in QEMU. For 
monitor/mwait for example, doing nops should suffice...


Fabrice.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] kqemu version 1.3.0pre5

2006-03-27 Thread Fabrice Bellard

Hi,

I just released a new version of kqemu which fixes some recently 
discovered issues. The fixes are the following:


- Support for guest Linux kernels compiled with gcc = 3.3

- x86_64 host support is working again (only i386 on x86_64 full 
virtualization has been tested, x86_64 on x86_64 is implemented but not 
tested yet).


- Workaround for full virtualization on Windows host (more tests needed).

The documentation (http://bellard.org/qemu/kqemu1-doc.html) gives more 
information about the new full virtualization mode.


Fabrice.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kqemu version 1.3.0pre5

2006-03-27 Thread Pascal Terjan
On 3/27/06, Fabrice Bellard [EMAIL PROTECTED] wrote:
 Hi,

 I just released a new version of kqemu which fixes some recently
 discovered issues. The fixes are the following:

 - Support for guest Linux kernels compiled with gcc = 3.3

Hello,
I tried the Mandriva boot.iso and it now boots fine, thanks !


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel