thr3ads.net - Xen users - Cannot create domU on Xen 4.1.2 [Feb 2012]

If this information is useful, please help other people find it:
Share via:

신용진

2012-Feb-13 08:32 UTC

Cannot create domU on Xen 4.1.2

Hi all,

 

I have installed xen 4.1.2. and libvirtd 0.8.4 on linux kernel 2.6.32.54. 

 

/var/log/xen/xend.log shows

==================================================================================
ERROR (SrvBase:88) Request wait_for_devices failed.

Traceback (most recent call last):

  File "/usr/lib64/python2.4/site-packages/xen/web/SrvBase.py", line
85, in
perform

    return op_method(op, req)

  File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomain.py",
line 85, in op_wait_for_devices

    return self.dom.waitForDevices()

  File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1237, in waitForDevices

    self.getDeviceController(devclass).waitForDevices()

  File "/usr/lib64/python2.4/site-
packages/xen/xend/server/DevController.py", line 140, in waitForDevices

    return map(self.waitForDevice, self.deviceIDs())

  File "/usr/lib64/python2.4/site-
packages/xen/xend/server/DevController.py", line 153, in waitForDevice

    raise VmError("Device %s (%s) could not be connected. "

VmError: Device 0 (vif) could not be connected. Hotplug scripts not working.

==================================================================================
 

When I googled about this, someone says that “not enough loopback device”.

So I enlarged number of loopback device from 8 to 128. 

But I faced same problem.

 

Is there anyone who have same problem with me? How can it be resolved?

 

And is there any recommendation for libvirtd version and kernel version?

 

If you need more information, please let me know!

 

Thanks in advance.



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

신용진

2012-Feb-13 10:42 UTC

head link

Cannot create domU on Xen 4.1.2

Hi all,

 

Sorry for duplicate message.

I wrote message with “wrong” e-mail address.

So I repeat this message again.

 

 

I have installed xen 4.1.2. and libvirtd 0.8.4 on linux kernel 2.6.32.54. 

 

/var/log/xen/xend.log shows

==================================================================================
ERROR (SrvBase:88) Request wait_for_devices failed.

Traceback (most recent call last):

  File "/usr/lib64/python2.4/site-packages/xen/web/SrvBase.py", line
85, in
perform

    return op_method(op, req)

  File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomain.py",
line 85, in op_wait_for_devices

    return self.dom.waitForDevices()

  File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1237, in waitForDevices

    self.getDeviceController(devclass).waitForDevices()

  File "/usr/lib64/python2.4/site-
packages/xen/xend/server/DevController.py", line 140, in waitForDevices

    return map(self.waitForDevice, self.deviceIDs())

  File "/usr/lib64/python2.4/site-
packages/xen/xend/server/DevController.py", line 153, in waitForDevice

    raise VmError("Device %s (%s) could not be connected. "

VmError: Device 0 (vif) could not be connected. Hotplug scripts not working.

==================================================================================
 

When I googled about this, someone says that “not enough loopback device”.

So I enlarged number of loopback device from 8 to 128. 

But I faced same problem.

 

Is there anyone who have same problem with me? How can it be resolved?

 

And is there any recommendation for libvirtd version and kernel version?

 

If you need more information, please let me know!

 

Thanks in advance.

 



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mark van Dijk

2012-Feb-14 11:19 UTC

head link

Re: Cannot create domU on Xen 4.1.2

Hi,
> /var/log/xen/xend.log shows(..snip..)
> VmError: Device 0 (vif) could not be connected. Hotplug scripts not
> working.
This error usually occurs because the VM crashes before the vif can be
connected. So it''s probably not the real error.... usually something
else is up.

What are you trying to do? Show us your domU config please.

신용진

2012-Feb-14 11:32 UTC

head link

Re: Cannot create domU on Xen 4.1.2

I am using libvirtd to create domU

So I use "virsh create <xmlfile>" .

The xml file goes like this;
=====================================================================<domain
type="xen">
    <name>test</name>
    <clock offset="localtime" />
    <devices>
        <console></console>
        <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
        <graphics keymap="en-us" port="5901"
type="vnc" autoport="yes" />
        <disk type=''file''
device=''disk''>
            <driver name=''file'' />
            <source file=''/stg/test/test.vhd'' />
            <target dev=''hda'' />
        </disk>
        <disk type=''file''
device=''cdrom''>
            <readonly />
            <target dev=''hdc'' />
        </disk>
        <interface type="bridge">
            <mac address="00:16:3e:a2:c6:bd" />
            <source bridge="xenbr2" />
        </interface>
        <input type=''tablet''
bus=''usb''/>
    </devices>
    <features>
        <acpi></acpi>
        <apic></apic>
        <pae></pae>
    </features>
    <memory>2097152</memory>
    <on_crash>preserve</on_crash>
    <on_poweroff>destroy</on_poweroff>
    <on_reboot>restart</on_reboot>
    <os>
    <boot dev="hd" />
        <loader>/usr/lib/xen/boot/hvmloader</loader>
        <type>hvm</type>
    </os>
    <uuid>b1cd0781-e41d-4c37-897e-3ba2b1745f6e</uuid>
    <vcpu>2</vcpu>
</domain>

=====================================================================================
it is working under xen 3.4.2. 

I am trying to upgrade xen version from 3.4.2 to 4.1.2(or 4.X.X) 
FYI, I have "right" vhd file in "right" location
And I have enough memory, enough cpu and disk space


VHD and xml file is working well under xen 3.4.2.

Thank you for your attention !

> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> bounces@lists.xensource.com] On Behalf Of Mark van Dijk
> Sent: Tuesday, February 14, 2012 8:19 PM
> To: xen-users@lists.xensource.com
> Subject: Re: [Xen-users] Cannot create domU on Xen 4.1.2
> 
> Hi,
> 
> > /var/log/xen/xend.log shows
> (..snip..)
> 
> > VmError: Device 0 (vif) could not be connected. Hotplug scripts not
> > working.
> 
> This error usually occurs because the VM crashes before the vif can be
> connected. So it''s probably not the real error.... usually
something
> else is up.
> 
> What are you trying to do? Show us your domU config please.
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

신용진

2012-Feb-15 07:55 UTC

head link

Re: Cannot create domU on Xen 4.1.2

Oh, I found something interest.

In my xml configuration,

When I removed network interface, it works!

         <interface type="bridge">
             <mac address="00:16:3e:a2:c6:bd" />
             <source bridge="xenbr2" />
         </interface>

I can make domU.

Maybe there should be some problem in
"/etc/xen/scripts/vif-bridge"
I think. 

Does anyone know about this?

> -----Original Message-----
> From: 신용진 [mailto:akayong@gmail.com]
> Sent: Tuesday, February 14, 2012 8:32 PM
> To: 'mark+lists@internecto.net';
'xen-users@lists.xensource.com'
> Subject: RE: [Xen-users] Cannot create domU on Xen 4.1.2
> 
> 
> I am using libvirtd to create domU
> 
> So I use "virsh create <xmlfile>" .
> 
> The xml file goes like this;
> =====================================================================>
<domain type="xen">
>     <name>test</name>
>     <clock offset="localtime" />
>     <devices>
>         <console></console>
>         <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
>         <graphics keymap="en-us" port="5901"
type="vnc" autoport="yes" />
>         <disk type='file' device='disk'>
>             <driver name='file' />
>             <source file='/stg/test/test.vhd' />
>             <target dev='hda' />
>         </disk>
>         <disk type='file' device='cdrom'>
>             <readonly />
>             <target dev='hdc' />
>         </disk>
>         <interface type="bridge">
>             <mac address="00:16:3e:a2:c6:bd" />
>             <source bridge="xenbr2" />
>         </interface>
>         <input type='tablet' bus='usb'/>
>     </devices>
>     <features>
>         <acpi></acpi>
>         <apic></apic>
>         <pae></pae>
>     </features>
>     <memory>2097152</memory>
>     <on_crash>preserve</on_crash>
>     <on_poweroff>destroy</on_poweroff>
>     <on_reboot>restart</on_reboot>
>     <os>
>     <boot dev="hd" />
>         <loader>/usr/lib/xen/boot/hvmloader</loader>
>         <type>hvm</type>
>     </os>
>     <uuid>b1cd0781-e41d-4c37-897e-3ba2b1745f6e</uuid>
>     <vcpu>2</vcpu>
> </domain>
> 
>
=========================================================================>
============>
> it is working under xen 3.4.2.
> 
> I am trying to upgrade xen version from 3.4.2 to 4.1.2(or 4.X.X)
> FYI, I have "right" vhd file in "right" location
> And I have enough memory, enough cpu and disk space
> 
> 
> VHD and xml file is working well under xen 3.4.2.
> 
> Thank you for your attention !
> 
> 
> > -----Original Message-----
> > From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> > bounces@lists.xensource.com] On Behalf Of Mark van Dijk
> > Sent: Tuesday, February 14, 2012 8:19 PM
> > To: xen-users@lists.xensource.com
> > Subject: Re: [Xen-users] Cannot create domU on Xen 4.1.2
> >
> > Hi,
> >
> > > /var/log/xen/xend.log shows
> > (..snip..)
> >
> > > VmError: Device 0 (vif) could not be connected. Hotplug scripts
not
> > > working.
> >
> > This error usually occurs because the VM crashes before the vif can be
> > connected. So it's probably not the real error.... usually
something
> > else is up.
> >
> > What are you trying to do? Show us your domU config please.
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

신용진

2012-Feb-16 07:40 UTC

head link

Cannot find network interface while creating domU and what is virbr?. (xen 4.1.2)

Hi all,

I found one more clue.

When I checked xen-hotplug.log

It says "bridge pbond2 does not exist!"

My system uses bonding interface.


"brctl show" result
bridge name     bridge id               STP enabled     interfaces
virbr0          8000.000000000000       yes
xenbr0          8000.xxxxxxxxxxxx       no              peth0
xenbr1          8000.xxxxxxxxxxxx       no              peth1
xenbr2          8000.xxxxxxxxxxxx       no              pbond2
xenbr4          8000.xxxxxxxxxxxx       no              peth4

in here, 
1) what is virbr in here?
Why virbr0 comes up? That naming rule is used in KVM, as I Know...

ifconfig pbond2 result

pbond2    Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
          inet6 addr: fe80::21b:21ff:fe5b:badc/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:128243 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5212 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11757059 (11.2 MiB)  TX bytes:1211197 (1.1 MiB)


Anyway, I tried to find which script or source write logs "bridge pbond2
does not exist!", however, I could not find it.
(I found every python source(/usr/lib64/python2.4/site-packages/xen/xend/),
and every xen scripts(/etc/xen/scripts/))

So, my 2nd question is..
2) which script makes that log? 


And finally.
What is the problem? That I cannot make domU? : (

This is the xend.log which shows the error.

ERROR (SrvBase:88) Request wait_for_devices failed.
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/web/SrvBase.py", line
85, in
perform
    return op_method(op, req)
  File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomain.py",
line 85, in op_wait_for_devices
    return self.dom.waitForDevices()
  File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1237, in waitForDevices
    self.getDeviceController(devclass).waitForDevices()
  File "/usr/lib64/python2.4/site-
packages/xen/xend/server/DevController.py", line 140, in waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib64/python2.4/site-
packages/xen/xend/server/DevController.py", line 153, in waitForDevice
    raise VmError("Device %s (%s) could not be connected. "
VmError: Device 0 (vif) could not be connected. Hotplug scripts not working.



Thanks in advance.

> -----Original Message-----
> From: 신용진 [mailto:akayong@gmail.com]
> Sent: Wednesday, February 15, 2012 4:56 PM
> To: 'mark+lists@internecto.net';
'xen-users@lists.xensource.com'
> Subject: RE: [Xen-users] Cannot create domU on Xen 4.1.2
> 
> 
> Oh, I found something interest.
> 
> In my xml configuration,
> 
> When I removed network interface, it works!
> 
>          <interface type="bridge">
>              <mac address="00:16:3e:a2:c6:bd" />
>              <source bridge="xenbr2" />
>          </interface>
> 
> I can make domU.
> 
> Maybe there should be some problem in
> "/etc/xen/scripts/vif-bridge"
> I think.
> 
> Does anyone know about this?
> 
> 
> > -----Original Message-----
> > From: 신용진 [mailto:akayong@gmail.com]
> > Sent: Tuesday, February 14, 2012 8:32 PM
> > To: 'mark+lists@internecto.net';
'xen-users@lists.xensource.com'
> > Subject: RE: [Xen-users] Cannot create domU on Xen 4.1.2
> >
> >
> > I am using libvirtd to create domU
> >
> > So I use "virsh create <xmlfile>" .
> >
> > The xml file goes like this;
> >
=====================================================================> >
<domain type="xen">
> >     <name>test</name>
> >     <clock offset="localtime" />
> >     <devices>
> >         <console></console>
> >         <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
> >         <graphics keymap="en-us" port="5901"
type="vnc" autoport="yes"
/>> >         <disk type='file' device='disk'>
> >             <driver name='file' />
> >             <source file='/stg/test/test.vhd' />
> >             <target dev='hda' />
> >         </disk>
> >         <disk type='file' device='cdrom'>
> >             <readonly />
> >             <target dev='hdc' />
> >         </disk>
> >         <interface type="bridge">
> >             <mac address="00:16:3e:a2:c6:bd" />
> >             <source bridge="xenbr2" />
> >         </interface>
> >         <input type='tablet' bus='usb'/>
> >     </devices>
> >     <features>
> >         <acpi></acpi>
> >         <apic></apic>
> >         <pae></pae>
> >     </features>
> >     <memory>2097152</memory>
> >     <on_crash>preserve</on_crash>
> >     <on_poweroff>destroy</on_poweroff>
> >     <on_reboot>restart</on_reboot>
> >     <os>
> >     <boot dev="hd" />
> >         <loader>/usr/lib/xen/boot/hvmloader</loader>
> >         <type>hvm</type>
> >     </os>
> >     <uuid>b1cd0781-e41d-4c37-897e-3ba2b1745f6e</uuid>
> >     <vcpu>2</vcpu>
> > </domain>
> >
> >
>
=========================================================================>
> ============> >
> > it is working under xen 3.4.2.
> >
> > I am trying to upgrade xen version from 3.4.2 to 4.1.2(or 4.X.X)
> > FYI, I have "right" vhd file in "right" location
> > And I have enough memory, enough cpu and disk space
> >
> >
> > VHD and xml file is working well under xen 3.4.2.
> >
> > Thank you for your attention !
> >
> >
> > > -----Original Message-----
> > > From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> > > bounces@lists.xensource.com] On Behalf Of Mark van Dijk
> > > Sent: Tuesday, February 14, 2012 8:19 PM
> > > To: xen-users@lists.xensource.com
> > > Subject: Re: [Xen-users] Cannot create domU on Xen 4.1.2
> > >
> > > Hi,
> > >
> > > > /var/log/xen/xend.log shows
> > > (..snip..)
> > >
> > > > VmError: Device 0 (vif) could not be connected. Hotplug
scripts not
> > > > working.
> > >
> > > This error usually occurs because the VM crashes before the vif
can be
> > > connected. So it's probably not the real error.... usually
something
> > > else is up.
> > >
> > > What are you trying to do? Show us your domU config please.
> > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Feb 2012 - Cannot create domU on Xen 4.1.2

Cannot create domU on Xen 4.1.2

Cannot create domU on Xen 4.1.2

Re: Cannot create domU on Xen 4.1.2

Re: Cannot create domU on Xen 4.1.2

Re: Cannot create domU on Xen 4.1.2

Cannot find network interface while creating domU and what is virbr?. (xen 4.1.2)