Brian J. Johnson wrote:
> Is anyone working on KVM for IA64?
Not that I know of. I'm very interested in additional kvm ports.
> Does the current architecture have
> any fundamental issues which would prevent it being ported to IA64?
>
I don't know enough about ia64 (or VT-i) to say for ce
Finally I got some time and played with this some
more. The unresolved symbols are caused by the fact
that the kvm module fails to load:
FATAL: Error inserting kvm
(/lib/modules/2.6.20/extra/kvm.ko): Device or resource
busy
I narrowed it down the following:
r = register_filesystem(&kvm_fs_type);
On Thu, 2007-03-01 at 17:07 +0200, Avi Kivity wrote:
> I'd like to add a signal mask to kvm, so that when the guest executes,
> the signal mask is temporarily set to some user specified value. This
> allows signals to be used as a way to interrupt the guest, but without
> requiring signal deliv
On Tue, Feb 27, 2007 at 09:08:50AM +0200, Avi Kivity wrote:
> Aurelien Jarno wrote:
> >Hi all,
> >
> >While I am able to run a 64-bit FreeBSD under a 64-bit KVM perfectly, I
> >am having problems with running a 32-bit FreeBSD under the same KVM:
> >
> >INIT: version 2.86 booting
> >INIT: PANIC: seg
Is anyone working on KVM for IA64? Does the current architecture have
any fundamental issues which would prevent it being ported to IA64?
Thanks,
Brian J. Johnson
-
Take Surveys. Earn Cash. Influence the Future of IT
Join S
I'd like to add a signal mask to kvm, so that when the guest executes,
the signal mask is temporarily set to some user specified value. This
allows signals to be used as a way to interrupt the guest, but without
requiring signal delivery to the userspace handler (which is what makes
signals ex
> > If it does not increase memory usage, then possibly:
> >
> > __register_chrdev_region(major, 0, (~0U) & MINORMASK, name);
> > or (1< clear
> >
> >
>
> I'm more worried about something in the chardev bowels not supporting
> >8bit minors well.
>
I was under
Jan Engelhardt wrote:
> On Mar 1 2007 13:58, Avi Kivity wrote:
>
>> fs/char_dev.c:
>>
>>> int register_chrdev(unsigned int major, const char *name,
>>>const struct file_operations *fops)
>>> {
>>> struct char_device_struct *cd;
>>> struct cdev *cdev;
>>> char *s;
>>> int err = -
On Mar 1 2007 13:58, Avi Kivity wrote:
>
> fs/char_dev.c:
>> int register_chrdev(unsigned int major, const char *name,
>>const struct file_operations *fops)
>> {
>> struct char_device_struct *cd;
>> struct cdev *cdev;
>> char *s;
>> int err = -ENOMEM;
>>
>> cd = __register_chrdev_regi
Avi Kivity wrote:
> Linus,
>
> The following changes since commit
> 2ff7354fe888f46f6629b57e463b0a1eb956c02b:
> Eric W. Biederman (1):
>x86_64/i386 irq: Fix !CONFIG_SMP compilation
>
> are found in the git repository at:
>
> git://kvm.qumranet.com/kvm.git#linus
Oops. git://kvm.qumranet
Linus,
The following changes since commit 2ff7354fe888f46f6629b57e463b0a1eb956c02b:
Eric W. Biederman (1):
x86_64/i386 irq: Fix !CONFIG_SMP compilation
are found in the git repository at:
git://kvm.qumranet.com/kvm.git#linus
The changes fall into three broad categories:
- initial kv
Mathiasen, Torben wrote:
>> 10 charNon-serial mice, misc features
>> nnn = /dev/kvm kernel-based virtual machine (hardware
>> virtualization extensions)
>>
>>
>
> Major 10, minor 256 has been assigned to /dev/kvm. Let me know if this is nok
> okay.
>
>
It doesn't work. The
[EMAIL PROTECTED] wrote:
> Hello,
> I'd like to know smp guests are supported (I read the answer is not in
> the FAQ but the smp support is not specified in the TODO )
>
>
SMP guests are not supported at present. We plan to support SMP guests
in the future.
> I heard something about kvm par
Hello,
I'd like to know smp guests are supported (I read the answer is not in
the FAQ but the smp support is not specified in the TODO )
I heard something about kvm paravirtualization like xen but in the FAQ
I read is not supported ? Is it still true ?
Many thanks and Regards
Ignazio
---
14 matches
Mail list logo
