[Fedora-xen] RE: Upgrading Xen machines

Wed Aug 8 14:08:56 UTC 2007

I looked at the config file again and it stated under vif:

# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0' ]
vif = [ 'mac=aa:00:00:00:01:04'  ]

I changed it to:

vif = [' ']

I then did the xm create and got this error:

Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working.

Here is the entire log file:

#============================================================================
# Python configuration setup for 'xm create'.
# This script sets the parameters used when a domain is created using 'xm create'.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#============================================================================

#----------------------------------------------------------------------------
# Kernel image file.
#kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU"
kernel = "/boot/vmlinuz-2.6.20-2925.13.fc7xen"
# Optional ramdisk.
ramdisk = "/boot/initrd-2.6.20-2925.13.fc7xen.img"

# The domain build function. Default is 'linux'.
#builder='linux'

# Initial memory allocation (in megabytes) for the new domain.
memory = 32

# A name for your domain. All domains must have different names.
name = "sec-int-dns"

# Which CPU to start domain on?
#cpu = -1   # leave to Xen to pick

#----------------------------------------------------------------------------
# Define network interfaces.

# Number of network interfaces. Default is 1.
#nics=1

# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0' ]
#vif = [ 'mac=aa:00:00:00:01:04'  ]
vif = [' ']

#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.

disk = [ 'file:/xen/sec-int-dns/root.img,sda1,w', 'file:/xen/sec-int-dns/swap.img,sda2,w' ]

#----------------------------------------------------------------------------
# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the domain's
# IP config doesn't, e.g. in ifcfg-eth0 or via DHCP.
# You can use 'extra' to set the runlevel and custom environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).

# Set if you want dhcp to allocate the IP address.
dhcp="dhcp"
#ip="172.20.1.88"
# Set netmask.
netmask="255.255.255.0"
# Set default gateway.
gateway="172.20.1.1"
# Set the hostname.
hostname= "sec-int-dns"

# Set root device.
root = "/dev/sda1 ro"

# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = '169.254.1.0'
# Root directory on the nfs server.
#nfs_root   = '/full/path/to/root/directory'

# Sets runlevel 4.
extra = "4"

#----------------------------------------------------------------------------
# Set according to whether you want the domain restarted when it exits.
# The default is 'onreboot', which restarts the domain when it shuts down
# with exit code reboot.
# Other values are 'always', and 'never'.

#restart = 'onreboot'

#============================================================================

Here is the xen log file:

[2007-08-08 04:53:01 25349] DEBUG (XendDomainInfo:957) XendDomainInfo.handleShutdownWatch
[2007-08-08 04:53:02 25349] DEBUG (DevController:148) Waiting for devices vif.
[2007-08-08 04:53:02 25349] DEBUG (DevController:153) Waiting for 0.
[2007-08-08 04:53:02 25349] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vif/16/0/hotplug-status.
[2007-08-08 04:53:02 25349] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vif/16/0/hotplug-status.
[2007-08-08 04:53:02 25349] DEBUG (DevController:570) hotplugStatusCallback 1.
[2007-08-08 04:53:02 25349] DEBUG (DevController:148) Waiting for devices usb.
[2007-08-08 04:53:02 25349] DEBUG (DevController:148) Waiting for devices vbd.
[2007-08-08 04:53:02 25349] DEBUG (DevController:153) Waiting for 2049.
[2007-08-08 04:53:02 25349] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vbd/16/2049/hotplug-status.
[2007-08-08 04:54:42 25349] DEBUG (XendDomainInfo:1709) XendDomainInfo.destroy: domid=16
[2007-08-08 04:54:42 25349] DEBUG (XendDomainInfo:1726) XendDomainInfo.destroyDomain(16)

Log file for hotplug:

Nothing to flush.
xenstore-read: couldn't read path backend/vbd/16/2049/node
xenstore-read: couldn't read path backend/vbd/16/2050/node

Hope this helps to determine the problem.

Thanks

> OK I am back from vacation and have started up this project again. I am > > taking old xen images from Fedora Core 4 and upgrading them to 7 on a new > server. Here is what I have done so far and have run into a problem. 

> I installed Fedora Core 7 on the new server and has new xen and kernel. I > transferred the old images and files from the old server to the new one.

> I then went in to the old config file - and changed the kernel from FC4 to > the new vmlinuz FC7. I then created a new initrd with xenblk with the
> following command: mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd- > 2.6.20-2925.13.fc7xen.img 2.6.20-2925.13.fc7-1xen. I put that in the config file under ramdisk.

> Now when I run the command xm create -c xmconfig I get this:

> Using config file "./xmconfig".
> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

> I looked at the archives and tried many suggestions, however none of them > have worked -

> Anything else I could do to get by this error?

> yes,

> you also need to create a new initrd for domU's with xenblk module.

> OK I am going to install Fedora Core 7 on the new server (it has 6 now).
>
> I will install the latest Xen 3.1 and the *13* kernel.
>
> After that I will transfer all the stuff from the older server to the new
> one.
>
> Then do I go into the xmconfig and change the kernel name? So here is the
> xmconfig for the sec-int-dns vm.
>
> # Kernel image file.
> kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU"
>
> Do I go and switch that line to kernel = (new xen kernel)?
>
> I am trying to understand that part - thanks for all your help!

This e-mail and any files transmitted with it are for the sole use of
Blue Slate Solutions and the intended recipient(s) and may contain
confidential and privileged information. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
or any action taken in reliance on this e-mail is strictly prohibited
and may be unlawful.

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen

This e-mail and any files transmitted with it are for the sole use of
Blue Slate Solutions and the intended recipient(s) and may contain
confidential and privileged information. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
or any action taken in reliance on this e-mail is strictly prohibited
and may be unlawful.