Error bringing up VMs with Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0

Error bringing up VMs with Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0

[AP Xen]

[-- Attachment #1.1: Type: text/plain, Size: 9958 bytes --]

I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built
and installed the Xen binaries from source. The systems boot successfully
however I am having issues bring up DomUs. Here is config:

 

name = 'xyz'

memory = 256

vcpus = 1

pae = 1

vnc = 1

vncunused = 1

disk = [ 'phy:/dev/vg1/xyz,hda,w' ]

vif = [ 'type=netfront,bridge=xenbr0,mac=04:01:3e:00:04:62' ]

builder = 'hvm'

kernel = '/usr/sbin/hvmloader'

boot = 'c'

device_model = '/usr/sbin/qemu-dm'

 

When I do an xm create on the config, I get the following error:

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

 

It looks like there is some configuration issue with the backend devices and
the hotplug scrips. Do I need to do anything special to have a
2.6.18-194.32.1.el5xen CentOS Dom0 kernel working with Xen 4.0.1?

 

Thanks,

AP

 

Xend.log

Here is the xend.log output:

 

[2011-01-17 15:43:47 3368] DEBUG (XendDomainInfo:101)
XendDomainInfo.create(['vm', ['name', 'xyz'], ['memory', 256],
['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash',
'restart'], ['on_xend_st

art', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', 1], ['oos', 1],
['image', ['hvm', ['kernel', '/usr/sbin/hvmloader'], ['videoram', 4],
['acpi', 1], ['apic', 1], ['boot', 'c'], ['cpuid', []], ['cpuid_che

ck', []], ['device_model', '/usr/sbin/qemu-dm'], ['fda', ''], ['fdb', ''],
['guest_os_type', 'default'], ['hap', 1], ['hpet', 0], ['isa', 0],
['keymap', ''], ['localtime', 0], ['nographic', 0], ['oos', 1], ['

pae', 1], ['pci', []], ['pci_msitranslate', 1], ['pci_power_mgmt', 0],
['rtc_timeoffset', 0], ['soundhw', ''], ['stdvga', 0], ['timer_mode', 1],
['usb', 0], ['usbdevice', ''], ['vcpus', 1], ['vnc', 1], ['vncu

nused', 1], ['viridian', 0], ['vpt_align', 1], ['xauthority',
'/root/.Xauthority'], ['xen_platform_pci', 1], ['memory_sharing', 0],
['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd',

['uname', 'phy:/dev/vg1/xyz'], ['dev', 'hda'], ['mode', 'w']]], ['device',
['vif', ['bridge', 'xenbr0'], ['mac', '04:01:3e:00:04:62'], ['type',
'netfront']]]])

[2011-01-17 15:43:47 3368] DEBUG (XendDomainInfo:2508)
XendDomainInfo.constructDomain

[2011-01-17 15:43:47 3368] DEBUG (balloon:220) Balloon: 144863028 KiB free;
need 16384; done.

[2011-01-17 15:43:47 3368] DEBUG (XendDomain:464) Adding Domain: 4

[2011-01-17 15:43:47 3368] DEBUG (XendDomainInfo:2818)
XendDomainInfo.initDomain: 4 256

[2011-01-17 15:43:47 3368] DEBUG (image:339) No VNC passwd configured for
vfb access

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: boot, val: c

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: fda, val: None

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: fdb, val: None

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: soundhw, val: None

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: localtime, val: 0

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: serial, val: None

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: std-vga, val: 0

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: isa, val: 0

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: acpi, val: 1

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: usb, val: 0

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: usbdevice, val: None

[2011-01-17 15:43:47 3368] DEBUG (image:891) args: gfx_passthru, val: None

[2011-01-17 15:43:47 3368] INFO (image:822) Need to create platform
device.[domid:4]

[2011-01-17 15:43:47 3368] DEBUG (XendDomainInfo:2845)
_initDomain:shadow_memory=0x0, memory_static_max=0x10000000,
memory_static_min=0x0.

[2011-01-17 15:43:47 3368] INFO (image:182) buildDomain os=hvm dom=4 vcpus=1

[2011-01-17 15:43:47 3368] DEBUG (image:949) domid          = 4

[2011-01-17 15:43:47 3368] DEBUG (image:950) image          =
/usr/sbin/hvmloader

[2011-01-17 15:43:47 3368] DEBUG (image:951) store_evtchn   = 2

[2011-01-17 15:43:47 3368] DEBUG (image:952) memsize        = 256

[2011-01-17 15:43:47 3368] DEBUG (image:953) target         = 256

[2011-01-17 15:43:47 3368] DEBUG (image:954) vcpus          = 1

[2011-01-17 15:43:47 3368] DEBUG (image:955) vcpu_avail     = 1

[2011-01-17 15:43:47 3368] DEBUG (image:956) acpi           = 1

[2011-01-17 15:43:47 3368] DEBUG (image:957) apic           = 1

[2011-01-17 15:43:47 3368] INFO (XendDomainInfo:2367) createDevice: vfb :
{'vncunused': 1, 'other_config': {'vncunused': 1, 'vnc': '1'}, 'vnc': '1',
'uuid': '69eb706c-3ad6-cfb2-b1b4-56eb4a8fbb32'}

[2011-01-17 15:43:47 3368] DEBUG (DevController:95) DevController: writing
{'state': '1', 'backend-id': '0', 'backend':
'/local/domain/0/backend/vfb/4/0'} to /local/domain/4/device/vfb/0.

[2011-01-17 15:43:47 3368] DEBUG (DevController:97) DevController: writing
{'vncunused': '1', 'domain': 'xyz', 'frontend':
'/local/domain/4/device/vfb/0', 'uuid':
'69eb706c-3ad6-cfb2-b1b4-56eb4a8fbb32', 'fron

tend-id': '4', 'state': '1', 'online': '1', 'vnc': '1'} to
/local/domain/0/backend/vfb/4/0.

[2011-01-17 15:43:47 3368] INFO (XendDomainInfo:2367) createDevice: vbd :
{'uuid': '3d3ace2a-4a69-f13c-943b-db32d1142796', 'bootable': 1, 'driver':
'paravirtualised', 'dev': 'hda', 'uname': 'phy:/dev/vg1/xyz'

, 'mode': 'w'}

[2011-01-17 15:43:47 3368] DEBUG (DevController:95) DevController: writing
{'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state':
'1', 'backend': '/local/domain/0/backend/vbd/4/768'} to

/local/domain/4/device/vbd/768.

[2011-01-17 15:43:47 3368] DEBUG (DevController:97) DevController: writing
{'domain': 'xyz', 'frontend': '/local/domain/4/device/vbd/768', 'uuid':
'3d3ace2a-4a69-f13c-943b-db32d1142796', 'bootable': '1', 'dev

': 'hda', 'state': '1', 'params': '/dev/vg1/xyz', 'mode': 'w', 'online':
'1', 'frontend-id': '4', 'type': 'phy'} to
/local/domain/0/backend/vbd/4/768.

[2011-01-17 15:43:47 3368] INFO (XendDomainInfo:2367) createDevice: vif :
{'bridge': 'xenbr0', 'mac': '04:01:3e:00:04:62', 'type': 'netfront', 'uuid':
'ab489b98-fbfe-0f67-9aa1-53d4f922f808'}

[2011-01-17 15:43:47 3368] DEBUG (DevController:95) DevController: writing
{'backend-id': '0', 'mac': '04:01:3e:00:04:62', 'handle': '0', 'state': '1',
'backend': '/local/domain/0/backend/vif/4/0'} to /local/

domain/4/device/vif/0.

[2011-01-17 15:43:47 3368] DEBUG (DevController:97) DevController: writing
{'bridge': 'xenbr0', 'domain': 'xyz', 'handle': '0', 'uuid':
'ab489b98-fbfe-0f67-9aa1-53d4f922f808', 'script': '/etc/xen/scripts/vif-

bridge', 'mac': '04:01:3e:00:04:62', 'frontend-id': '4', 'state': '1',
'online': '1', 'frontend': '/local/domain/4/device/vif/0', 'type':
'netfront'} to /local/domain/0/backend/vif/4/0.

[2011-01-17 15:43:47 3368] INFO (image:418) spawning device models:
/usr/sbin/qemu-dm ['/usr/sbin/qemu-dm', '-d', '4', '-domain-name', 'xyz',
'-videoram', '4', '-vnc', '0.0.0.0:0', '-vncunused', '-vcpus', '1'

, '-vcpu_avail', '0x1', '-boot', 'c', '-acpi', '-net', 'none', '-M',
'xenfv']

[2011-01-17 15:43:47 3368] INFO (image:467) device model pid: 20674

[2011-01-17 15:43:47 3368] INFO (image:590) waiting for sentinel_fifo

[2011-01-17 15:43:47 3368] DEBUG (XendDomainInfo:3400) Storing VM details:
{'on_xend_stop': 'ignore', 'shadow_memory': '3', 'uuid':
'b4e4814f-c4d7-2bb4-6eba-02a436353121', 'on_reboot': 'restart', 'start_time'

: '1295307827.36', 'on_poweroff': 'destroy', 'bootloader_args': '',
'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0',
'vcpus': '1', 'vcpu_avail': '1', 'bootloader': '', 'image': '(h authority
/root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)))', 'name': 'xyz'}

e': 'ioemu', 'name': 'xyz'}

[2011-01-17 15:43:47 3368] DEBUG (DevController:95) DevController: writing
{'state': '1', 'backend-id': '0', 'backend':
'/local/domain/0/backend/console/4/0'} to /local/domain/4/device/console/0.

'state': '1', 'location': '3', 'online': '1', 'protocol': 'vt100'} to
/local/domain/0/backend/console/4/0.

[2011-01-17 15:43:47 3368] DEBUG (XendDomainInfo:1891)
XendDomainInfo.handleShutdownWatch

[2011-01-17 15:43:47 3368] DEBUG (DevController:139) Waiting for devices
vif2.

[2011-01-17 15:43:47 3368] DEBUG (DevController:139) Waiting for devices
vif.

[2011-01-17 15:43:47 3368] DEBUG (DevController:144) Waiting for 0.

[2011-01-17 15:43:47 3368] DEBUG (DevController:628) hotplugStatusCallback
/local/domain/0/backend/vif/4/0/hotplug-status.

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:3053)
XendDomainInfo.destroy: domid=4

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2411) Destroying device
model

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2418) Releasing devices

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2424) Removing vif/0

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2424) Removing vbd/768

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2424) Removing vfb/0

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0

[2011-01-17 15:45:27 3368] INFO (image:615) xyz device model terminated

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2424) Removing console/0

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2416) No device model

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2418) Releasing devices

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2424) Removing vif/0

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2424) Removing vbd/768

[2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768

(END)

 

 

 


[-- Attachment #1.2: Type: text/html, Size: 21649 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Error bringing up VMs with Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0

[Konrad Rzeszutek Wilk]

On Tue, Jan 18, 2011 at 11:00:18AM -0800, AP Xen wrote:
> I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built
> and installed the Xen binaries from source. The systems boot successfully
> however I am having issues bring up DomUs. Here is config:
> 
>  
> 
> name = 'xyz'
> 
> memory = 256
> 
> vcpus = 1
> 
> pae = 1
> 
> vnc = 1
> 
> vncunused = 1
> 
> disk = [ 'phy:/dev/vg1/xyz,hda,w' ]
> 
> vif = [ 'type=netfront,bridge=xenbr0,mac=04:01:3e:00:04:62' ]
> 
> builder = 'hvm'
> 
> kernel = '/usr/sbin/hvmloader'
> 
> boot = 'c'
> 
> device_model = '/usr/sbin/qemu-dm'
> 
>  
> 
> When I do an xm create on the config, I get the following error:
> 
> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

Does the 'xenbr0' interface exist?

Have you tried to contact the xen-users mailing list instead of xen-devel?

RE: Error bringing up VMs with Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0

[AP Xen]

> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Tuesday, January 18, 2011 11:24 AM
> To: AP Xen
> Cc: 'Xen-Devel'
> Subject: Re: [Xen-devel] Error bringing up VMs with Xen 4.0.1 + 2.6.18-
> 194.32.1.el5xen CentOS Dom0
> 
> On Tue, Jan 18, 2011 at 11:00:18AM -0800, AP Xen wrote:
> > I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I
> built
> > and installed the Xen binaries from source. The systems boot
> successfully
> > however I am having issues bring up DomUs. Here is config:
> >
> >
> >
> > name = 'xyz'
> >
> > memory = 256
> >
> > vcpus = 1
> >
> > pae = 1
> >
> > vnc = 1
> >
> > vncunused = 1
> >
> > disk = [ 'phy:/dev/vg1/xyz,hda,w' ]
> >
> > vif = [ 'type=netfront,bridge=xenbr0,mac=04:01:3e:00:04:62' ]
> >
> > builder = 'hvm'
> >
> > kernel = '/usr/sbin/hvmloader'
> >
> > boot = 'c'
> >
> > device_model = '/usr/sbin/qemu-dm'
> >
> >
> >
> > When I do an xm create on the config, I get the following error:
> >
> > Error: Device 0 (vif) could not be connected. Hotplug scripts not
> working.
> 
> Does the 'xenbr0' interface exist?

Here is the output of "brctl show"
bridge name	bridge id		STP enabled	interfaces
br2026b		8000.001b2147d86c	no		eth2.2026
br2026f		8000.003048f5af19	no		eth1.2026
eth0		8000.003048f5af18	no		peth0
virbr0		8000.000000000000	yes		

> Have you tried to contact the xen-users mailing list instead of xen-
> devel?

I did and waited for 24 hrs and received no reply.

I also tried bringing up the VM without the "vif" parameter in the config.
The VM kernel panicked because it couldn't find the boot device.

Thanks,
AP

Re: Error bringing up VMs with Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0

[Pasi Kärkkäinen]

On Tue, Jan 18, 2011 at 11:54:42AM -0800, AP Xen wrote:
> > -----Original Message-----
> > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > Sent: Tuesday, January 18, 2011 11:24 AM
> > To: AP Xen
> > Cc: 'Xen-Devel'
> > Subject: Re: [Xen-devel] Error bringing up VMs with Xen 4.0.1 + 2.6.18-
> > 194.32.1.el5xen CentOS Dom0
> > 
> > On Tue, Jan 18, 2011 at 11:00:18AM -0800, AP Xen wrote:
> > > I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I
> > built
> > > and installed the Xen binaries from source. The systems boot
> > successfully
> > > however I am having issues bring up DomUs. Here is config:
> > >
> > >
> > >
> > > name = 'xyz'
> > >
> > > memory = 256
> > >
> > > vcpus = 1
> > >
> > > pae = 1
> > >
> > > vnc = 1
> > >
> > > vncunused = 1
> > >
> > > disk = [ 'phy:/dev/vg1/xyz,hda,w' ]
> > >
> > > vif = [ 'type=netfront,bridge=xenbr0,mac=04:01:3e:00:04:62' ]
> > >
> > > builder = 'hvm'
> > >
> > > kernel = '/usr/sbin/hvmloader'
> > >
> > > boot = 'c'
> > >
> > > device_model = '/usr/sbin/qemu-dm'
> > >
> > >
> > >
> > > When I do an xm create on the config, I get the following error:
> > >
> > > Error: Device 0 (vif) could not be connected. Hotplug scripts not
> > working.
> > 
> > Does the 'xenbr0' interface exist?
> 
> Here is the output of "brctl show"
> bridge name	bridge id		STP enabled	interfaces
> br2026b		8000.001b2147d86c	no		eth2.2026
> br2026f		8000.003048f5af19	no		eth1.2026
> eth0		8000.003048f5af18	no		peth0
> virbr0		8000.000000000000	yes		
> 

Well, you don't have a bridge called 'xenbr0'.
So it won't work, like you noticed.

You seem to have a bridge called 'eth0' - use that instead in the domU cfg.


> > Have you tried to contact the xen-users mailing list instead of xen-
> > devel?
> 
> I did and waited for 24 hrs and received no reply.
> 
> I also tried bringing up the VM without the "vif" parameter in the config.
> The VM kernel panicked because it couldn't find the boot device.
> 

This question is not suitable for xen-devel mailinglist.

-- Pasi

RE: Error bringing up VMs with Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0

[AP Xen]

> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
> Sent: Tuesday, January 18, 2011 11:58 AM
> To: AP Xen
> Cc: 'Konrad Rzeszutek Wilk'; 'Xen-Devel'
> Subject: Re: [Xen-devel] Error bringing up VMs with Xen 4.0.1 + 2.6.18-
> 194.32.1.el5xen CentOS Dom0
> 
> On Tue, Jan 18, 2011 at 11:54:42AM -0800, AP Xen wrote:
> > > -----Original Message-----
> > > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > > Sent: Tuesday, January 18, 2011 11:24 AM
> > > To: AP Xen
> > > Cc: 'Xen-Devel'
> > > Subject: Re: [Xen-devel] Error bringing up VMs with Xen 4.0.1 +
> 2.6.18-
> > > 194.32.1.el5xen CentOS Dom0
> > >
> > > On Tue, Jan 18, 2011 at 11:00:18AM -0800, AP Xen wrote:
> > > > I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0.
> I
> > > built
> > > > and installed the Xen binaries from source. The systems boot
> > > successfully
> > > > however I am having issues bring up DomUs. Here is config:
> > > >
> > > >
> > > >
> > > > name = 'xyz'
> > > >
> > > > memory = 256
> > > >
> > > > vcpus = 1
> > > >
> > > > pae = 1
> > > >
> > > > vnc = 1
> > > >
> > > > vncunused = 1
> > > >
> > > > disk = [ 'phy:/dev/vg1/xyz,hda,w' ]
> > > >
> > > > vif = [ 'type=netfront,bridge=xenbr0,mac=04:01:3e:00:04:62' ]
> > > >
> > > > builder = 'hvm'
> > > >
> > > > kernel = '/usr/sbin/hvmloader'
> > > >
> > > > boot = 'c'
> > > >
> > > > device_model = '/usr/sbin/qemu-dm'
> > > >
> > > >
> > > >
> > > > When I do an xm create on the config, I get the following error:
> > > >
> > > > Error: Device 0 (vif) could not be connected. Hotplug scripts not
> > > working.
> > >
> > > Does the 'xenbr0' interface exist?
> >
> > Here is the output of "brctl show"
> > bridge name	bridge id		STP enabled	interfaces
> > br2026b		8000.001b2147d86c	no		eth2.2026
> > br2026f		8000.003048f5af19	no		eth1.2026
> > eth0		8000.003048f5af18	no		peth0
> > virbr0		8000.000000000000	yes
> >
> 
> Well, you don't have a bridge called 'xenbr0'.
> So it won't work, like you noticed.
> 
> You seem to have a bridge called 'eth0' - use that instead in the domU
> cfg.

I tried using eth0, br2026b, br2026f but got the same error. The same
configuration works if I use the Xen version packaged with CentOS 5.5. 

> > > Have you tried to contact the xen-users mailing list instead of
> xen-
> > > devel?
> >
> > I did and waited for 24 hrs and received no reply.
> >
> > I also tried bringing up the VM without the "vif" parameter in the
> config.
> > The VM kernel panicked because it couldn't find the boot device.
> >
> 
> This question is not suitable for xen-devel mailinglist.

Sorry about that. I only posted on xen-devel when I received no reply from
xen-users. Should I try posting again on xen-users?

Thanks,
AP
 
> -- Pasi