Benjamin Budts wrote:
> Hi,
>
> I'm running debian, installed kvm-18 from source, it installed fine...
>
> I have an intel s5000pal motherboard with dual core xeon 64bit,
> virtualization enabled in my bios.
>
> question 1 : is it normal i dont have this file : qemu-system-x86_64 , i
> only have
Gregory Haskins wrote:
> I am seeing this:
>
> [EMAIL PROTECTED]:~/sandbox> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm- userspace.git
> Initialized empty Git repository in /home/ghaskins/sandbox/kvm-
> userspace/.git/
> fatal: The remote end hung up unexpectedly
> fetch-pac
Andrew Walrond wrote:
> On Wednesday 18 April 2007 16:50:00 Avi Kivity wrote:
>
>> What's your VM HAL
>> (http://kvm.qumranet.com/kvmwiki/Windows_ACPI_Workaround step 5)?
>>
>
> MPS Uniprocessor PC
>
> And after following those instructions, it now works fine under version 19,
> and
On Wednesday 18 April 2007 16:50:00 Avi Kivity wrote:
>
> What's your VM HAL
> (http://kvm.qumranet.com/kvmwiki/Windows_ACPI_Workaround step 5)?
MPS Uniprocessor PC
And after following those instructions, it now works fine under version 19,
and at lightning speed :)
Thanks for the point
I am seeing this:
[EMAIL PROTECTED]:~/sandbox> git clone
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm- userspace.git
Initialized empty Git repository in /home/ghaskins/sandbox/kvm- userspace/.git/
fatal: The remote end hung up unexpectedly
fetch-pack from 'git://git.kernel.org/pub/scm/l
--- Begin Message ---
Hi,
I'm running debian, installed kvm-18 from source, it installed fine...
I have an intel s5000pal motherboard with dual core xeon 64bit,
virtualization enabled in my bios.
question 1 : is it normal i dont have this file : qemu-system-x86_64 , i
only have the qemu fil
Hi,
I'm running debian, installed kvm-18 from source, it installed fine...
I have an intel s5000pal motherboard with dual core xeon 64bit,
virtualization enabled in my bios.
question 1 : is it normal i dont have this file : qemu-system-x86_64 , i
only have the qemu file in my /bin
kvm and kv
> Great, that increases the probability that the patch is a net gain.
>
> I don't think you need to run the SLES installer as both Sergey and me
> have it working. Instead, running with your regular workload (possibly
> stressing it) would be a good test.
Okay yeah I don't seem to have problems a
Kiselev, Sergey wrote:
> Hi,
>
> Any plans to add support for guests with more than 2GB RAM?
No immediate plans, but of course I'd like to have that limitation lifted.
>
> I tried to fix obvious limitations, e.g. to change ram_size and
> phys_ram_size variables from 'int' to 'unsigned long'
Andrew Walrond wrote:
> Should images created with older version in general work with newer versions?
>
Yes.
> Anyhow, my XP vm just sits at a black screen with or without the modules
> loaded (I using those built installed from the package, not the old ones
> installed with my Feisty instal
Hi,
Any plans to add support for guests with more than 2GB RAM?
I tried to fix obvious limitations, e.g. to change ram_size and
phys_ram_size variables from 'int' to 'unsigned long' type.
Now I am getting 'init_rmode_tss: gfn_to_page failed' error from KVM, so
probably KVM kernel module needs t
Should images created with older version in general work with newer versions?
Anyhow, my XP vm just sits at a black screen with or without the modules
loaded (I using those built installed from the package, not the old ones
installed with my Feisty installation).
Reverting to kvm-16, again with
David Brown wrote:
>>
>> I see. Consider it pushed. I'll send it linuswards if there's no
>> negative feedback in a day or two.
>>
>
> Oooo, patch!
>
> What was the method for reproduction? since I was unable to reproduce
> the bug maybe I could with your method.
>
It was the SLES 9 installer/in
It fixes the problem, at least for me...
Thanks,
Sergey
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Avi Kivity
Sent: 18 April 2007 11:22
To: David Brown
Cc: [email protected]
Subject: Re: [kvm-devel] Oopse in kvm
Avi Kivity wrote:
> Da
>
> I see. Consider it pushed. I'll send it linuswards if there's no
> negative feedback in a day or two.
>
Oooo, patch!
What was the method for reproduction? since I was unable to reproduce
the bug maybe I could with your method.
Don't worry I'll be on this thread until the problem is fixed,
Thomas Glanzmann wrote:
>
>> Ok. You mean you're running linus -rc?
>>
>
> In fact I do. But I didn't meant that upstream. I was talking about your
> repository[1]. But it isn't in the kvm kernel repository yet. So I commited it
> local. And thanks to git if you commit it, it will merge th
Thomas Glanzmann wrote:
> Hello,
> with VMWare ESX Server you have VMware Consolidated Backup. Which
> basically does the following:
>
> - Do a Snapshot.
> - Pull an atomic state of the disks.
> - Delete the Snapshot.
>
> Does somone does that with kvm or qemu already and ma
Hello Avi,
> hehe, the 4g4g patch.
I see. I thought noone would use that anymore because of the overhead
during context switches.
> It's the same bug.
perfect.
> Ok. You mean you're running linus -rc?
In fact I do. But I didn't meant that upstream. I was talking about your
repository[1]. But
Thomas Glanzmann wrote:
> Hello Avi,
> I had an kernel OOPS that morning with RHEL_5_ it isn't reproducable.
>
> Apr 18 08:57:42 thinkpad kernel: BUG: unable to handle kernel NULL pointer
> dereference at virtual address 0024
> Apr 18 08:57:42 thinkpad kernel: printing eip:
> Apr 18 08:57:42
Hello,
with VMWare ESX Server you have VMware Consolidated Backup. Which
basically does the following:
- Do a Snapshot.
- Pull an atomic state of the disks.
- Delete the Snapshot.
Does somone does that with kvm or qemu already and maybe has a script
for me or points me to
Hello Avi,
I had an kernel OOPS that morning with RHEL_5_ it isn't reproducable.
Apr 18 08:57:42 thinkpad kernel: BUG: unable to handle kernel NULL pointer
dereference at virtual address 0024
Apr 18 08:57:42 thinkpad kernel: printing eip:
Apr 18 08:57:42 thinkpad kernel: 78351d8c
Apr 18 08:5
Avi Kivity wrote:
David Brown wrote:
I was wondering of anyone could help out on this, just found an oopse
when trying to start rhel4 on i386 box. I was wondering if anyone else
has seen this with kvm-18 and if I should submit a bug for it.
[10937.52] BUG: unable to handle kernel NULL po
22 matches
Mail list logo
