David Brown wrote:
Host cpu type, host bitness, guest bitness, and qemu command line
please.
Oh sorry, forgot about that stuff.
model name : Genuine Intel(R) CPU U2500 @ 1.20GHz
Ugh, a Core-not-2. I'll see if I can find one here.
qemu -kernel
Anthony Liguori wrote:
Thomas Glanzmann wrote:
Hello,
when I try to start a SLES 10 Guest, I get a OPPS:
This is probably the infamous big real mode VT issue. You should be
able to find instructions for starting SLES without the graphical splash
screen either on the KVM
Paul Brook wrote:
On Monday 30 April 2007, Nakajima, Jun wrote:
We found a way to get 32-bit Vista up on KVM by fixing bios.bin. And I
think it should be helpful to qemu as well. However, I'm not sure if the
binary file has been created simply by applying bios.diff to the latest
bochs CVS
Hollis Blanchard wrote:
I think we can start the syscall based API (with compatibility ioctls
for x86), now that we have all four archs looking at it.
It would probably make sense for the IA64 and S390 folks, who already have
syscall-based implementations, to put up a straw man
Thomas Glanzmann wrote:
Hello,
when I try to start a SLES 10 Guest, I get a OPPS:
What kvm version are you using? If you're using git, please provide the
output of 'git describe'.
--
error compiling committee.c: too many arguments to function
I'll try to answer the open questions.
Btw, libvirt is a great project and a very good option for managing kvm.
In the future use plain text for the list messages.
From: jd [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 28, 2007 8:12 AM
To: Daniel P.
Avi Kivity wrote:
Thomas Glanzmann wrote:
Hello,
when I try to start a SLES 10 Guest, I get a OPPS:
May 1 00:36:07 thinkpad kernel: Code: 08 eb 71 83 fe 20 0f 87 57 01
00 00 8b 0c b5 00 05 4c 78 85 c9 0f 84 48 01 00 00 89 ea 89 f8 ff d1
85 c0 89 c3 0f 8e 4b 01 00 00 64 a1 08 00 00 00 8b
Howdie,
Nakajima, Jun wrote:
We found a way to get 32-bit Vista up on KVM by fixing bios.bin. And I
think it should be helpful to qemu as well. However, I'm not sure if the
binary file has been created simply by applying bios.diff to the latest
bochs CVS tree (actually I doubt it). Can
Hello,
as soon as SLES 10 switches the first time to X the screen is frozen and
I can't press any keys or move the virtual mouse. But I can switch to
the qemu console using ctrl-alt-2 and back.
Thomas
-
This SF.net
Thomas Glanzmann wrote:
Hello,
as soon as SLES 10 switches the first time to X the screen is frozen and
I can't press any keys or move the virtual mouse. But I can switch to
the qemu console using ctrl-alt-2 and back.
Is this a regression from a previous kvm version?
Does this happen
Omar Khan wrote:
hi,
I am measuring the VM enty/exit time on the following two machines by
recording the time it takes to make n number of vmcalls :
1. Lenovo Think Centre, Intel Pentium D, 2 Cores, 3GHz with 3G of memory
2. Dell Inspiron 6400 , Intel Core Duo, 2 Cores, 2 GHz with 1G of
Shuveb Hussain wrote:
Hi,
I see that the user tests are for 64 bit guests. Anything for good ol'
32-bit available?
Trunk has a few tests for 32-bit (the only one I remember offhand is
user/test/vmexit.c)
--
error compiling committee.c: too many arguments to function
qemu -kernel /root/boot/vmlinuz-${KVER} \
-initrd /root/boot/${INITRD_BASE}${INITRD_APPEND}-${KVER} \
-append ${APPEND} \
-m 512 --no-rtc \
\
-usb \
-soundhw es1370 \
-net nic,vlan0,macaddr=52:54:56:34:12:00 \
-net tap,vlan=0,ifname=tap0 \
-hdb
Bugs item #1710701, was opened at 2007-05-01 16:38
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1710701group_id=180599
Please note that this message will contain a full copy of
On Tuesday 01 May 2007 13:38:15 SourceForge.net wrote:
the video corrupts slightly (black vertical bars) and the (USB) mouse gets
stuck to the left border of the screen. It can be moved away very slowly,
Got the almost the same exact behaviour here with kvm 21 and core2duo E6600
processor.
Andreas Hasenack wrote:
On Tuesday 01 May 2007 13:38:15 SourceForge.net wrote:
the video corrupts slightly (black vertical bars) and the (USB) mouse gets
stuck to the left border of the screen. It can be moved away very slowly,
Got the almost the same exact behaviour here with kvm
On Sunday 29 April 2007, Heiko Carstens wrote:
Is this data structure extensible? If it is, you probably need
some sort of versioning information to make sure that user space
doesn't rely on fields that the kernel doesn't know about.
I don't think we can put in some versioning
How big is your initrd image ? There was a QEMU bug which causes the
end of the initrd to be overwritten by the kernel if the initd was
larger than 1 MB IIRC. Upstream QEMU CVS has the patch, but the current
KVM SVN repo does not seem to have it. I'm attaching the patch we applied
to
Arnd Bergmann wrote:
On Sunday 29 April 2007, Heiko Carstens wrote:
Is this data structure extensible? If it is, you probably need
some sort of versioning information to make sure that user space
doesn't rely on fields that the kernel doesn't know about.
I don't think we can put
19 matches
Mail list logo
