9:56 p.m.
Hi
I have a question about specifications of virsh start.
It is necessary to remove "type=ioemu" from the configuration file of Xen,
when HVM domain installed Para Virtualized Driver use unmodified driver
on Xen 3.0.3.
But,libvirt always adds "type=ioemu" to vif of HVM domain in xm_internal.c.
Therefore virsh start cannot start correctly HVM domain installed
Para Virtualized Driver.
Could you teach why does libvirt disregard setting of configuration
file and set type=ioemu ?
Thanks,
Masayuki Sunou.
7:32 a.m.
Masayuki Sunou wrote:
Hi
I have a question about specifications of virsh start.
It is necessary to remove "type=ioemu" from the configuration file of Xen,
when HVM domain installed Para Virtualized Driver use unmodified driver
on Xen 3.0.3.
But,libvirt always adds "type=ioemu" to vif of HVM domain in xm_internal.c.
Therefore virsh start cannot start correctly HVM domain installed
Para Virtualized Driver.
Could you teach why does libvirt disregard setting of configuration
file and set type=ioemu ?
This is surely a bug in libvirt, src/xm_internal.c, xenXMParseXMLVif:
if (hvm) {
strcat(buf, ",type=ioemu");
}
Do you know what we can use to determine if the PV drivers are installed
in a domain? I don't think there is anything extrinsic, so perhaps we
need to add something to the XML domain description.
Rich.
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
1:54 a.m.
Thanks for answering.
Do you know what we can use to determine if the PV drivers are
installed
in a domain? I don't think there is anything extrinsic, so perhaps we
need to add something to the XML domain description.
I also do not know a method to distinguish whether PV drivers are installed
in a domain.
I think that there is only a method of changing XML to fix it,
if libvirt supports starting of a domain which installed PV drivers.
However, it is not a proper idea.
Thanks,
Masayuki Sunou
In message <4731BE88.3090207(a)redhat.com>
"Re: [Libvir] Question about specifications of virsh start"
""Richard W.M. Jones" <rjones(a)redhat.com>" wrote:
> Masayuki Sunou wrote:
> > Hi
> >
> > I have a question about specifications of virsh start.
> >
> > It is necessary to remove "type=ioemu" from the configuration file of
Xen,
> > when HVM domain installed Para Virtualized Driver use unmodified driver
> > on Xen 3.0.3.
> >
> > But,libvirt always adds "type=ioemu" to vif of HVM domain in
xm_internal.c.
> > Therefore virsh start cannot start correctly HVM domain installed
> > Para Virtualized Driver.
> >
> > Could you teach why does libvirt disregard setting of configuration
> > file and set type=ioemu ?
>
> This is surely a bug in libvirt, src/xm_internal.c, xenXMParseXMLVif:
>
> if (hvm) {
> strcat(buf, ",type=ioemu");
> }
>
Do you know what we can use to determine if the PV drivers are
installed
in a domain? I don't think there is anything extrinsic, so perhaps we
need to add something to the XML domain description.
> Rich.
>
> --
> Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
> Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
> England and Wales under Company Registration No. 03798903
>
8:14 a.m.
On Wed, Nov 07, 2007 at 12:56:29PM +0900, Masayuki Sunou wrote:
Hi
I have a question about specifications of virsh start.
It is necessary to remove "type=ioemu" from the configuration file of Xen,
when HVM domain installed Para Virtualized Driver use unmodified driver
on Xen 3.0.3.
Xen 3.0.3 is broken. Only Xen 3.1.0 works sanely wrt to PV drivers in HVM
If you leave off the 'type=ioemu' Xen 3.1.0 always sets up networking
so that both QEMU & PV drivers work.
But,libvirt always adds "type=ioemu" to vif of HVM domain
in xm_internal.c.
Therefore virsh start cannot start correctly HVM domain installed
Para Virtualized Driver.
Could you teach why does libvirt disregard setting of configuration
file and set type=ioemu ?
This whole rationale of changing the config file in order to setup PV
drivers is wrong. The person in charge of admin for DomU will often
not have any access to Dom0 at all. So if the DomU admin wants to install
PV drivers, how can they change the config file ? Well they can't. Any
need to change the config file prior to install PV drivers is broken.
Hence why XenD was fixed in 3.1.0 to not be stupid.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
1:54 a.m.
Thanks for answering.
I understand as follows.
- Libvirt cannot support a domain installed Para Virtualized Driver on Xen 3.0.3 .
(because of the breakdown of Xen 3.0.3)
Thanks,
Masayuki Sunou
In message <20071107141434.GA1769(a)redhat.com>
"Re: [Libvir] Question about specifications of virsh start"
""Daniel P. Berrange" <berrange(a)redhat.com>" wrote:
On Wed, Nov 07, 2007 at 12:56:29PM +0900, Masayuki Sunou wrote:
> Hi
>
> I have a question about specifications of virsh start.
>
> It is necessary to remove "type=ioemu" from the configuration file of
Xen,
> when HVM domain installed Para Virtualized Driver use unmodified driver
> on Xen 3.0.3.
Xen 3.0.3 is broken. Only Xen 3.1.0 works sanely wrt to PV drivers in HVM
If you leave off the 'type=ioemu' Xen 3.1.0 always sets up networking
so that both QEMU & PV drivers work.
> But,libvirt always adds "type=ioemu" to vif of HVM domain in
xm_internal.c.
> Therefore virsh start cannot start correctly HVM domain installed
> Para Virtualized Driver.
>
> Could you teach why does libvirt disregard setting of configuration
> file and set type=ioemu ?
This whole rationale of changing the config file in order to setup PV
drivers is wrong. The person in charge of admin for DomU will often
not have any access to Dom0 at all. So if the DomU admin wants to install
PV drivers, how can they change the config file ? Well they can't. Any
need to change the config file prior to install PV drivers is broken.
Hence why XenD was fixed in 3.1.0 to not be stupid.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
6219
days inactive
6224
days old
4 comments
3 participants
participants (3)
-
Daniel P. Berrange -
Masayuki Sunou -
Richard W.M. Jones