Re: [kvm-devel] kvm-18 breaks Cisco VPN on WinXP SP1
Leslie Mann wrote: Avi Kivity [EMAIL PROTECTED] writes: Can you run qemu under strace -ttT? Be prepared for a long log. Also, checking with the -no-kvm option is worthwhile. Avi: Can't run under strace. XP starts to boot then blue screens complaining of an infinite loop in the cirrus driver. I have attached the tail of the strace log. I have been running display at max, tried dropping resolution to 800x600, 16 bit but same problem. Runs fine without kvm modules loaded. Ah, Windows sets a timeout when loading drivers, and of course strace slows down the initial screen clear. You can try attaching strace with the '-p' option, just before connecting. This will reduce the log size greatly. I should have thought of it before. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] portability layer?
Hollis Blanchard wrote: No, I'm saying that some #ifdeffery in both libkvm and the ioctl interface is unavoidable. If by #ifdeffery you mean having per-architecture definitions of structures like kvm_regs, absolutely. If you mean literal #ifdefs in the middle a header file, I believe that can and should be avoided. If it can be avoided I'm all for it. Right now this is handled by qemu, which means our higher level tools are _already_ nonportable. Yes, but not *all* the higher level tools are. At some point you have a common interface, and at this point I think I've answered my own question: the qemu monitor connection is the portable interface. That means everything layered above qemu, such as libvirt and thus virt-manager, should work on all architectures +/- without changes. Lower-level software, such as GDB, would need per-architecture support. Ah, _those_ higher layer tools. Each of these interfaces needs to be stabilized for different reasons: - the kernel ABI allows the kernel and userspace to be upgraded independently - libkvm is mainly for when we've merged all our changes into mainline qemu, and for the theoretical second user - the qemu monitor is for the higher level tools Note that the qemu monitor (and commandline) interface is under the control of the qemu maintainers, not us. So far it has been steadily improving. [I have a feeling we're talking a little past each other, probably due to me not knowing ppc at any level of detail. No doubt things will become clearer when the code arrives] I don't have any code for you, but you will be the first to know when I do. :) Right now I'm just trying to make sure we don't accidentally paint ourselves into a corner with a stable ABI. The stable ABI here is just the support baseline, not a freeze. We know for certain that changes are needed for smp, paravirt drivers, new hardware virtualization extensions, and new archs. And of course it only holds for x86; other archs will stabilize when they are ready. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Physical memory read: word crosses page boundary + host kernel oops
Hi
1. It seems that first problem happens because this particular
double-word (address 0x9FFFD) is located on the boundary between regular
memory and video memory. Probably this address accessed because some bug
in that old kernel (I don't see any good reason to read this location).
But it will be nice to check for reads/writes to such addresses.
2. Problem (oops) is gone away in rev 4571. Not sure why. Still it can
be repeatedly reproduced on kvm-18.
If needed, I can upload an image that reproduces these problems (~150MB
compressed size).
Thanks,
Sergey
-Original Message-
From: Avi Kivity [mailto:[EMAIL PROTECTED]
Sent: 27 March 2007 16:45
To: Kiselev, Sergey
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] Physical memory read: word crosses page
boundary + host kernel oops
Kiselev, Sergey wrote:
Hi,
1. When booting old Linux (RH7.1 based, 2.4.9, 32bit) guest on kvm-18,
kvm userspace process crashes with 'Bus error' (last output on guest's
screen is Uncompressing Linux...).
I did some debugging and found that kvm_readl() function calls
ldl_phys() with address 0x9FFFD, so resulting double-word read crosses
page boundary.
After looking at qemu/exec.c it seems that ld*_phys and st*_phys
functions not really care about crossing page boundary (even there is
a comment sayng warning: addr must be aligned). So either
qemu/exec.c should be updated to check such condition or (more logical
place) qemu/qemu-kvm.c should take care of it.
gdb backtrace:
(gdb) bt
#0 ldl_phys (addr=4093) at ../cpu-all.h:322
#1 0x0047e08d in kvm_readl (opaque=0x9f, addr=159,
data=0x2b63605a5030) at /srv/src/kvm-18/qemu/qemu-kvm.c:543
This is quite surprising. I agree that hacking kvm_readl() is the best
fix.
2. After working-around the first issue, I have following problem: at
some point of guest's Linux boot sequence (after running
microcode_ctl, before running kudzu) following oops happens:
Mar 27 12:10:39 itstl140 kernel: Code: 4c 8b 08 41 0f 18 09 48 8d 70
d8 31 c0 e9 39 ff ff ff 48 63
Mar 27 12:10:39 itstl140 kernel: RIP
88366aa6{:kvm:mmu_page_remove_parent_pte+225} RSP
81014e34f938
Mar 27 12:10:39 itstl140 kernel: CR2: 00030593a563
I tried to disable both microcode_ctl and kudzu, in this case oops h
Strangely, I've seen this exact oops somewhere booting Windows XP in
safe mode. I haven't been able to reproduce it, though.
If this is reproducible, it may be debugged by turning on audit
(s/#undef AUDIT/#define AUDIT/ in mmu.c). Audit slows the guest down,
but is a little faster if you reduce the amount of guest memory. If
this is reproducible using a publicly available image, I may have a go
at it too.
--
error compiling committee.c: too many arguments to function
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] APIC model in kernel
Hi Guys, My team currently has interests in both the PV work, and the SMP work. It seems in both cases a significant gating factor is the APIC modeling. Avi, Dor, and others have mentioned that this would probably be best served by the KVM kernel code, and I agree that this seems logical. I figured I could take a stab at this task unless anyone objects? -Greg - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] APIC model in kernel
Hi Guys, My team currently has interests in both the PV work, and the SMP work. It seems in both cases a significant gating factor is the APIC modeling. Avi, Dor, and others have mentioned that this would probably be best served by the KVM kernel code, and I agree that this seems logical. I figured I could take a stab at this task unless anyone objects? It would be wonderful! Actually Ingo Molnar was sniffing around this area too. Ingo, do you have any news in that field or you were tied up with the other, many Linux issues that you support? Actually you can get initial kick start in two places: 1. I had a working in-kernel-apic KVM version. It's quite old release of the KVM, before the SVM support but it was working back then. The reason we didn't merged it was that we managed to run Windows with qemu's apic. You can get the 'apic' branch from the kvm svn. 2. Get an updated version from Xen and make the necessary changes for KVM. This is what I have done in the above apic implementation. I had to choose between implementation from scratch, ripping qemu, ripping Xen and I decided to pick Xen. Please keep us uptodate about the progress, if possible by sending small cumulative patches each time. Cheers, Dor. -Greg --- -- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVD EV ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm-18 breaks Cisco VPN on WinXP SP1
Avi Kivity [EMAIL PROTECTED] writes:
Ah, Windows sets a timeout when loading drivers, and of course strace
slows down the initial screen clear.
You can try attaching strace with the '-p' option, just before
connecting. This will reduce the log size greatly. I should have
thought of it before.
Avi:
That works. Here is the last 100 lines from the strace capture. Letme know if
there is anything else you need.
Les
21:05:48.713254 ioctl(10, 0xae80, 0)= 0 0.22
21:05:48.713314 ioctl(10, 0xae80, 0)= 0 0.22
21:05:48.713374 ioctl(10, 0xae80, 0)= 0 0.22
21:05:48.713442 ioctl(10, 0xae80, 0)= 0 0.28
21:05:48.713508 ioctl(10, 0xae80, 0)= 0 0.28
21:05:48.713573 ioctl(10, 0xae80, 0)= 0 0.27
21:05:48.713638 ioctl(10, 0xae80, 0)= 0 0.27
21:05:48.713703 ioctl(10, 0xae80, 0)= 0 0.29
21:05:48.713781 ioctl(10, 0xae80, 0)= 0 0.23
21:05:48.713841 ioctl(10, 0xae80, 0)= 0 0.23
21:05:48.713902 ioctl(10, 0xae80, 0)= 0 0.22
21:05:48.713962 ioctl(10, 0xae80, 0)= 0 0.23
21:05:48.714023 ioctl(10, 0xae80, 0)= 0 0.29
21:05:48.714094 --- SIGIO (I/O possible) @ 0 (0) ---
21:05:48.714117 clock_gettime(CLOCK_MONOTONIC, {1334, 948044221}) = 0 0.09
21:05:48.714165 sigreturn() = ? (mask now []) 0.08
21:05:48.714242 ioctl(10, 0xae80, 0)= 0 0.000290
21:05:48.714571 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.714628 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.714685 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.714743 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.714832 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.714889 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.714946 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.715003 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.715066 --- SIGIO (I/O possible) @ 0 (0) ---
21:05:48.715089 clock_gettime(CLOCK_MONOTONIC, {1334, 949016131}) = 0 0.10
21:05:48.715138 sigreturn() = ? (mask now []) 0.08
21:05:48.715214 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.715272 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.715329 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.715387 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.715454 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.715512 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.715569 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.715626 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.715683 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.715740 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.715796 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.715853 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.715910 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.715966 ioctl(10, 0xae80, 0)= 0 0.29
21:05:48.716029 --- SIGIO (I/O possible) @ 0 (0) ---
21:05:48.716052 clock_gettime(CLOCK_MONOTONIC, {1334, 950502633}) = 0 0.000604
21:05:48.716734 sigreturn() = ? (mask now []) 0.25
21:05:48.716853 ioctl(10, 0xae80, 0)= 0 0.31
21:05:48.716925 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.716983 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.717038 --- SIGIO (I/O possible) @ 0 (0) ---
21:05:48.717064 clock_gettime(CLOCK_MONOTONIC, {1334, 950992080}) = 0 0.10
21:05:48.717114 sigreturn() = ? (mask now []) 0.000977
21:05:48.719489 --- SIGIO (I/O possible) @ 0 (0) ---
21:05:48.719522 clock_gettime(CLOCK_MONOTONIC, {1334, 953451331}) = 0 0.10
21:05:48.719574 sigreturn() = ? (mask now []) 0.08
21:05:48.719652 ioctl(10, 0xae80, 0)= 0 0.38
21:05:48.719728 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.719786 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.719844 ioctl(10, 0xae80, 0)= 0 0.18
21:05:48.719900 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.719961 --- SIGIO (I/O possible) @ 0 (0) ---
21:05:48.719985 clock_gettime(CLOCK_MONOTONIC, {1334, 953911724}) = 0 0.09
21:05:48.720033 sigreturn() = ? (mask now []) 0.08
21:05:48.720110 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.720167 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.720224 ioctl(10, 0xae80, 0)= 0 0.000118
21:05:48.720379 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.720546 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.720604 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.720996 --- SIGIO (I/O possible) @ 0 (0) ---
21:05:48.721019 clock_gettime(CLOCK_MONOTONIC, {1334, 954945934}) = 0 0.09
21:05:48.721066 sigreturn() = ? (mask now []) 0.09
21:05:48.721241 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.721396 ioctl(10, 0xae80, 0)= 0 0.27
21:05:48.721463 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.721542 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.721600 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.721656 ioctl(10, 0xae80, 0)= 0 0.19
21:05:48.721713 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.721796 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.721862 ioctl(10, 0xae80, 0)= 0 0.20
21:05:48.721917 --- SIGIO (I/O possible) @ 0
[kvm-devel] kvm-18 compilation error
hi,
I am having trouble compiling kvm-18 on suse10.2. 'make' is giving the
following error:
/opt/gcc33/bin/gcc-3.3 -I /root/kvm-18/qemu/../user -Wall -O2 -g
-fno-strict-aliasing -I /root/kvm-18/kernel/include -I. -I..
-I/root/kvm-18/qemu/target-i386 -I/root/kvm-18/qemu -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D__user= -I/root/kvm-18/qemu/fpu
-DHAS_AUDIO -I/root/kvm-18/qemu/slirp -c -o exec.o /root/kvm-18/qemu/exec.c
/root/kvm-18/qemu/exec.c: In function `cpu_breakpoint_insert':
/root/kvm-18/qemu/exec.c:1055: warning: implicit declaration of function
`kvm_update_debugger'
/root/kvm-18/qemu/exec.c: In function `cpu_physical_memory_set_dirty_tracking':
/root/kvm-18/qemu/exec.c:1436: warning: implicit declaration of function
`kvm_physical_memory_set_dirty_tracking'
/opt/gcc33/bin/gcc-3.3 -I /root/kvm-18/qemu/../user -Wall -O2 -g
-fno-strict-aliasing -I /root/kvm-18/kernel/include -I. -I..
-I/root/kvm-18/qemu/target-i386 -I/root/kvm-18/qemu -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D__user= -I/root/kvm-18/qemu/fpu
-DHAS_AUDIO -I/root/kvm-18/qemu/slirp -c -o kqemu.o /root/kvm-18/qemu/kqemu.c
/opt/gcc33/bin/gcc-3.3 -I /root/kvm-18/qemu/../user -Wall -O2 -g
-fno-strict-aliasing -I /root/kvm-18/kernel/include -fomit-frame-pointer -I.
-I.. -I/root/kvm-18/qemu/target-i386 -I/root/kvm-18/qemu -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D__user= -I/root/kvm-18/qemu/fpu
-DHAS_AUDIO -I/root/kvm-18/qemu/slirp -c -o qemu-kvm.o /root/kvm-18/qe
mu/qemu-kvm.c
/root/kvm-18/qemu/qemu-kvm.c: In function `kvm_cpu_exec':
/root/kvm-18/qemu/qemu-kvm.c:447: warning: implicit declaration of
function `exit'
/root/kvm-18/qemu/qemu-kvm.c: In function `kvm_shutdown':
/root/kvm-18/qemu/qemu-kvm.c:599: warning: implicit declaration of
function `qemu_system_reset_request'
/root/kvm-18/qemu/qemu-kvm.c: In function `kvm_qemu_init_env':
/root/kvm-18/qemu/qemu-kvm.c:732: error: unable to find a register to
spill in class `SIREG'
/root/kvm-18/qemu/qemu-kvm.c:732: error: this is the insn:
(insn:HI 37 35 38 0 0x4074ab00 (parallel [
(set (reg:SI 1 edx [67])
(const_int 0 [0x0]))
(set (reg/f:SI 0 eax [64])
(plus:SI (ashift:SI (reg:SI 2 ecx [66])
(const_int 2 [0x2]))
(reg/f:SI 0 eax [64])))
(set (reg/f:SI 2 ecx [65])
(plus:SI (ashift:SI (reg:SI 2 ecx [66])
(const_int 2 [0x2]))
(reg/v/f:SI 59)))
(set (mem/s:BLK (reg/f:SI 0 eax [64]) [0 copy+0 S25712 A128])
(mem/s:BLK (reg/v/f:SI 59) [0 S25712 A128]))
(use (reg:SI 2 ecx [66]))
(use (reg:SI 19 dirflag))
]) 454 {rep_movsi} (insn_list 3 (insn_list 32 (insn_list 34 (insn_list
35 (nil)
(expr_list:REG_DEAD (reg:SI 19 dirflag)
(expr_list:REG_DEAD (reg:SI 2 ecx [66])
(expr_list:REG_UNUSED (reg:SI 1 edx [67])
(expr_list:REG_UNUSED (reg/f:SI 0 eax [64])
(expr_list:REG_UNUSED (reg/f:SI 2 ecx [65])
(nil)))
/root/kvm-18/qemu/qemu-kvm.c:732: confused by earlier errors, bailing out
make[2]: *** [qemu-kvm.o] Error 1
make[2]: Leaving directory `/root/kvm-18/qemu/i386-softmmu'
make[1]: *** [subdir-i386-softmmu] Error 2
make[1]: Leaving directory `/root/kvm-18/qemu'
make: *** [qemu] Error 2
any ideas what might be going wrong?
Omar
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm-18 breaks Cisco VPN on WinXP SP1
Leslie Mann wrote:
That works. Here is the last 100 lines from the strace capture. Letme know if
there is anything else you need.
[...]
21:05:48.736568 clock_gettime(CLOCK_MONOTONIC, {1334, 970496230}) = 0
0.10
21:05:48.736618 sigreturn() = ? (mask now []) 0.08
21:05:48.736707 ioctl(10, 0xae80, 0)= 0 0.22
21:05:48.736767 ioctl(10, 0xae80, 0)= 0 0.000544
21:05:48.744119 --- SIGIO (I/O possible) @ 0 (0) ---
21:05:48.744146 clock_gettime(CLOCK_MONOTONIC, {1334, 978076521}) = 0
0.10
21:05:48.744200 sigreturn() = ? (mask now [INT QUIT TRAP FPE KILL
SEGV TSTP URG SYS RTMIN]) 0.10
21:05:48.744285 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
The SIGIO means some I/O has occured, but what exactly, we don't know.
Can you generate a core, attach it with gdb, and generate a backtrace?
Check the backtrace for signs of your password and delete them if
found. It shouldn't be there, but then it shouldn't crash either.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm-18 compilation error
Omar Khan wrote:
hi,
I am having trouble compiling kvm-18 on suse10.2. 'make' is giving the
following error:
/opt/gcc33/bin/gcc-3.3 -I /root/kvm-18/qemu/../user -Wall -O2 -g
-fno-strict-aliasing -I /root/kvm-18/kernel/include -fomit-frame-pointer -I.
-I.. -I/root/kvm-18/qemu/target-i386 -I/root/kvm-18/qemu -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D__user= -I/root/kvm-18/qemu/fpu
-DHAS_AUDIO -I/root/kvm-18/qemu/slirp -c -o qemu-kvm.o /root/kvm-18/qe
mu/qemu-kvm.c
/root/kvm-18/qemu/qemu-kvm.c: In function `kvm_cpu_exec':
/root/kvm-18/qemu/qemu-kvm.c:447: warning: implicit declaration of
function `exit'
/root/kvm-18/qemu/qemu-kvm.c: In function `kvm_shutdown':
/root/kvm-18/qemu/qemu-kvm.c:599: warning: implicit declaration of
function `qemu_system_reset_request'
/root/kvm-18/qemu/qemu-kvm.c: In function `kvm_qemu_init_env':
/root/kvm-18/qemu/qemu-kvm.c:732: error: unable to find a register to
spill in class `SIREG'
/root/kvm-18/qemu/qemu-kvm.c:732: error: this is the insn:
(insn:HI 37 35 38 0 0x4074ab00 (parallel [
(set (reg:SI 1 edx [67])
(const_int 0 [0x0]))
(set (reg/f:SI 0 eax [64])
(plus:SI (ashift:SI (reg:SI 2 ecx [66])
(const_int 2 [0x2]))
(reg/f:SI 0 eax [64])))
(set (reg/f:SI 2 ecx [65])
(plus:SI (ashift:SI (reg:SI 2 ecx [66])
(const_int 2 [0x2]))
(reg/v/f:SI 59)))
(set (mem/s:BLK (reg/f:SI 0 eax [64]) [0 copy+0 S25712 A128])
(mem/s:BLK (reg/v/f:SI 59) [0 S25712 A128]))
(use (reg:SI 2 ecx [66]))
(use (reg:SI 19 dirflag))
]) 454 {rep_movsi} (insn_list 3 (insn_list 32 (insn_list 34 (insn_list
35 (nil)
(expr_list:REG_DEAD (reg:SI 19 dirflag)
(expr_list:REG_DEAD (reg:SI 2 ecx [66])
(expr_list:REG_UNUSED (reg:SI 1 edx [67])
(expr_list:REG_UNUSED (reg/f:SI 0 eax [64])
(expr_list:REG_UNUSED (reg/f:SI 2 ecx [65])
(nil)))
/root/kvm-18/qemu/qemu-kvm.c:732: confused by earlier errors, bailing out
make[2]: *** [qemu-kvm.o] Error 1
make[2]: Leaving directory `/root/kvm-18/qemu/i386-softmmu'
make[1]: *** [subdir-i386-softmmu] Error 2
make[1]: Leaving directory `/root/kvm-18/qemu'
make: *** [qemu] Error 2
any ideas what might be going wrong?
You might try with gcc 3.4.6, which most people are using for qemu.
Alternatively, ./configure --qemu-cc=gcc --disable-gcc-check, but then
you lose the ability to run with the -no-kvm switch.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
