3:56 a.m.
Hi
I want to run netbsd 5.0 with kvm in virt-manager. It works with default
option but any network devices is recognized by the netbsd kernel.
To enable network with qemu-kvm, we had to disable the acpi and add other
options like -tdf, -localtime ... This is an an example who works :
http://ghantoos.org/2009/05/12/my-first-shot-of-netbsd/ (An explanation I found
is that the new scheduler in netbsd 5.0 cause some problems with
virtualization based on VT)
Currently, I have not found the way to do it with libvirt (and I don't think
it is possible with virt-manager).
It be very helpeful if these features can be add to libvirt.
Thanks
Fabien Georget
4:04 a.m.
On Sun, Jun 21, 2009 at 10:56:48AM +0200, Fabien Georget wrote:
Hi
I want to run netbsd 5.0 with kvm in virt-manager. It works with default
option but any network devices is recognized by the netbsd kernel.
To enable network with qemu-kvm, we had to disable the acpi and add other
options like -tdf, -localtime ... This is an an example who works :
http://ghantoos.org/2009/05/12/my-first-shot-of-netbsd/ (An explanation I found
is that the new scheduler in netbsd 5.0 cause some problems with
virtualization based on VT)
Hmm, I would not expect BSD to need 'localtime' - AFAIK, all UNIX OS will
prefer to have their RTC using UTC, with only Windows taking the crazy
option of storing localtime in the RTC. That said, you can set this in
libvirt if required
http://libvirt.org/formatdomain.html#elementsTime
You can turn off ACPI easily enough, by leaving out the '<acpi/>' flag in
the <features> section.
The -tdf flag isn't something we have support for. It is not in upstream QEMU,
only added in the KVM tree AFAIK, and is rather a hack. KVM should be fixed
to 'just work' by default either by fixing the bug that prevents BSD working,
or by making -tdf the global default.
Currently, I have not found the way to do it with libvirt (and I
don't think
it is possible with virt-manager).
virt-manager doesn't tend to expose this fine level of control over
individual features. Instead we have an OS type dictionary giving the
defaults for these kind of things, particularly the acpi/localtime
settings. I can't remember off hand if there is a Net BSD 5.0 OS
type or not - if not file a bug against virt-manager asking for one
to be added.
Regards,
Da niel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
5:12 a.m.
Le lundi 22 juin 2009 11:04:17, Daniel P. Berrange a écrit :
> To enable network with qemu-kvm, we had to disable the acpi and
add other
> options like -tdf, -localtime ...
Hmm, I would not expect BSD to need 'localtime' -...
yes, sorry, locatime is not what I meant. The other mandatory option is "-no-
kvm-pit".
You can turn off ACPI easily enough, by leaving out the
'<acpi/>' flag in
the <features> section.
The -tdf flag isn't something we have support for. It is not in upstream
QEMU, only added in the KVM tree AFAIK, and is rather a hack. KVM should be
fixed to 'just work' by default either by fixing the bug that prevents BSD
working, or by making -tdf the global default.
ACPI modification is done. But, the mandatory options "-tdf" and
"-no-kvm-pit"
cannot be add. And if you disable ACPI without these options the virtual
machine freeze.
I ask for a <netbsd/> flag in the <features> section for giving the good
arguments to qemu-kvm.
Libvirt is the frontend, so it have to adapt, isn't it ?
> Currently, I have not found the way to do it with libvirt (and I
don't
> think it is possible with virt-manager).
virt-manager doesn't tend to expose this fine level of control over
individual features. Instead we have an OS type dictionary giving the
defaults for these kind of things, particularly the acpi/localtime
settings. I can't remember off hand if there is a Net BSD 5.0 OS
type or not - if not file a bug against virt-manager asking for one
to be added.
No, there isn't a "NetBSD 5.0" type, but, currently, it is useless because
libvirt can't run NetBSD with kvm :(.
5632
days inactive
5633
days old
2 comments
2 participants
participants (2)
-
Daniel P. Berrange -
Fabien Georget