Hi, Im having a problem starting the domUs I have just built a new server running 3.4.2 and Jeremys pv_ops kernel which boot fine. When starting the domU i get this message Error: Device 0 (vif) could not be connected. Hotplug scripts not working. I have the HVM config set to vif = [ ''type=ioemu, bridge=xenbr0'' ] and running brctl show outputs bridge name bridge id STP enabled interfaces xenbr0 8000.001966ee28b4 no peth0 so i don''t understand what the issue is. Anyone got any ideas? Thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Jan 18, 2010 at 4:40 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Hi, > Im having a problem starting the domUs> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.> vif = [ ''type=ioemu, bridge=xenbr0'' ]try changing this to vif = [ ''bridge=xenbr0'' ] also check whether udev is running, and the logs on /var/log/xen/xend.log -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Fajar,
I have tried changing that but it still comes up with the same error
after hanging for a few mins.
I have also checked udev is running and the only error in the log that i
can see is
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 2228, in _releaseDevices
self.destroyDevice(true_devclass, dev, False);
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 1148, in destroyDevice
rc = self.getDeviceController(deviceClass).destroyDevice(devid,
force)
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 2249, in getDeviceController
raise XendError("Unknown device type: %s" % name)
XendError: Unknown device type: None
Not sure if that means anything to you?
Thanks
Ian
-----Original Message-----
From: Fajar A. Nugraha [mailto:fajar@fajar.net]
Sent: 18 January 2010 09:48
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Network problem
On Mon, Jan 18, 2010 at 4:40 PM, Ian Tobin <itobin@tidyhosts.com>
wrote:> Hi,
> Im having a problem starting the domUs
> Error: Device 0 (vif) could not be connected. Hotplug scripts not
working.
> vif = [ ''type=ioemu, bridge=xenbr0'' ]
try changing this to
vif = [ ''bridge=xenbr0'' ]
also check whether udev is running, and the logs on
/var/log/xen/xend.log
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Mon, Jan 18, 2010 at 5:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> I have also checked udev is running and the only error in the log that i > can see is > > Traceback (most recent call last): > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 2228, in _releaseDevices > self.destroyDevice(true_devclass, dev, False); > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 1148, in destroyDevice > rc = self.getDeviceController(deviceClass).destroyDevice(devid, > force) > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 2249, in getDeviceController > raise XendError("Unknown device type: %s" % name) > XendError: Unknown device type: None > > Not sure if that means anything to you? >Go back several lines (should be less than one hundred), start looking from the one where the domain is starting. There might be a more useful info there, like what it was doing before it throws the error vif not connected. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
This is what it says just before, i was tailing the log [2010-01-18 15:08:13 2917] DEBUG (XendDomainInfo:1709) XendDomainInfo.handleShutdownWatch [2010-01-18 15:08:13 2917] DEBUG (DevController:139) Waiting for devices vif. [2010-01-18 15:08:13 2917] DEBUG (DevController:144) Waiting for 0. [2010-01-18 15:08:13 2917] WARNING (image:493) domain testserver: device model failure: pid 2989: exited with nonzero status 1; see /var/log/xen/qemu-dm-testserver.log [2010-01-18 15:08:13 2917] WARNING (XendDomainInfo:1886) Domain has crashed: name=testserver id=1. [2010-01-18 15:08:13 2917] INFO (XendDomainInfo:2091) Preserving dead domain testserver (1). [2010-01-18 15:08:13 2917] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. -----Original Message----- From: Fajar A. Nugraha [mailto:fajar@fajar.net] Sent: 18 January 2010 13:57 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Network problem On Mon, Jan 18, 2010 at 5:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> I have also checked udev is running and the only error in the log that i > can see is > > Traceback (most recent call last): > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 2228, in _releaseDevices > self.destroyDevice(true_devclass, dev, False); > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 1148, in destroyDevice > rc = self.getDeviceController(deviceClass).destroyDevice(devid, > force) > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 2249, in getDeviceController > raise XendError("Unknown device type: %s" % name) > XendError: Unknown device type: None > > Not sure if that means anything to you? >Go back several lines (should be less than one hundred), start looking from the one where the domain is starting. There might be a more useful info there, like what it was doing before it throws the error vif not connected. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
This is the log from the qemu file domid: 1 qemu: the number of cpus is 1 /etc/xen/qemu-ifup: could not launch network script Could not initialize device ''tap'' Ian -----Original Message----- From: Fajar A. Nugraha [mailto:fajar@fajar.net] Sent: 18 January 2010 13:57 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Network problem On Mon, Jan 18, 2010 at 5:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> I have also checked udev is running and the only error in the log that i > can see is > > Traceback (most recent call last): > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 2228, in _releaseDevices > self.destroyDevice(true_devclass, dev, False); > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 1148, in destroyDevice > rc = self.getDeviceController(deviceClass).destroyDevice(devid, > force) > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 2249, in getDeviceController > raise XendError("Unknown device type: %s" % name) > XendError: Unknown device type: None > > Not sure if that means anything to you? >Go back several lines (should be less than one hundred), start looking from the one where the domain is starting. There might be a more useful info there, like what it was doing before it throws the error vif not connected. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Found the problem! For some reason the scripts had not fully copied into the directories so the script qemu-ifup was missing from the xen directory. I went back to the install directory and re ran the copy command which has now corrected the vif error. Thanks for pointing me in the direction of the log! Ian -----Original Message----- From: Fajar A. Nugraha [mailto:fajar@fajar.net] Sent: 18 January 2010 13:57 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Network problem On Mon, Jan 18, 2010 at 5:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> I have also checked udev is running and the only error in the log that i > can see is > > Traceback (most recent call last): > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 2228, in _releaseDevices > self.destroyDevice(true_devclass, dev, False); > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 1148, in destroyDevice > rc = self.getDeviceController(deviceClass).destroyDevice(devid, > force) > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 2249, in getDeviceController > raise XendError("Unknown device type: %s" % name) > XendError: Unknown device type: None > > Not sure if that means anything to you? >Go back several lines (should be less than one hundred), start looking from the one where the domain is starting. There might be a more useful info there, like what it was doing before it throws the error vif not connected. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Think i spoke to soon. The domU gets further in starting up now that you can see the main console start the virtual device but it still returns that error. Looking in the log file doesn''t really report any errors. If i comment out the networking in the config file the domU starts fine -----Original Message----- From: Fajar A. Nugraha [mailto:fajar@fajar.net] Sent: 18 January 2010 13:57 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Network problem On Mon, Jan 18, 2010 at 5:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> I have also checked udev is running and the only error in the log that i > can see is > > Traceback (most recent call last): > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 2228, in _releaseDevices > self.destroyDevice(true_devclass, dev, False); > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 1148, in destroyDevice > rc = self.getDeviceController(deviceClass).destroyDevice(devid, > force) > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > line 2249, in getDeviceController > raise XendError("Unknown device type: %s" % name) > XendError: Unknown device type: None > > Not sure if that means anything to you? >Go back several lines (should be less than one hundred), start looking from the one where the domain is starting. There might be a more useful info there, like what it was doing before it throws the error vif not connected. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Jan 18, 2010 at 09:16:15PM -0000, Ian Tobin wrote:> Think i spoke to soon. > > The domU gets further in starting up now that you can see the main console start the virtual device but it still returns that error. Looking in the log file doesn''t really report any errors. > > If i comment out the networking in the config file the domU starts fine >Please pastebin the domU configuration file from /etc/xen/ -- Pasi> > > -----Original Message----- > From: Fajar A. Nugraha [mailto:fajar@fajar.net] > Sent: 18 January 2010 13:57 > To: Ian Tobin > Cc: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Network problem > > On Mon, Jan 18, 2010 at 5:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > I have also checked udev is running and the only error in the log that i > > can see is > > > > Traceback (most recent call last): > > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > > line 2228, in _releaseDevices > > self.destroyDevice(true_devclass, dev, False); > > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > > line 1148, in destroyDevice > > rc = self.getDeviceController(deviceClass).destroyDevice(devid, > > force) > > File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", > > line 2249, in getDeviceController > > raise XendError("Unknown device type: %s" % name) > > XendError: Unknown device type: None > > > > Not sure if that means anything to you? > > > > Go back several lines (should be less than one hundred), start looking > from the one where the domain is starting. There might be a more > useful info there, like what it was doing before it throws the error > vif not connected. > > -- > Fajar > > > > _______________________________________________ > 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
Hi,
Here it is
# -*- mode: python; -*-
#===========================================================================#
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.
#===========================================================================
import os, re
arch_libdir = ''lib''
arch = os.uname()[4]
if os.uname()[0] == ''Linux'' and
re.search(''64'', arch):
arch_libdir = ''lib64''
#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/usr/lib/xen/boot/hvmloader"
# The domain build function. HVM domain uses ''hvm''.
builder=''hvm''
# Initial memory allocation (in megabytes) for the new domain.
#
# WARNING: Creating a domain with insufficient memory may cause out of
# memory errors. The domain needs enough memory to boot kernel
# and modules. Allocating less than 32MBs is not recommended.
memory = 128
# Shadow pagetable memory for the domain, in MB.
# If not explicictly set, xend will pick an appropriate value.
# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
# shadow_memory = 8
# A name for your domain. All domains must have different names.
name = "testserver"
# 128-bit UUID for the domain. The default behavior is to generate a new UUID
# on each call to ''xm create''.
#uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"
#-----------------------------------------------------------------------------
# The number of cpus guest platform has, default=1
#vcpus=1
# Enable/disable HVM guest PAE, default=1 (enabled)
#pae=1
# Enable/disable HVM guest ACPI, default=1 (enabled)
#acpi=1
# Enable/disable HVM APIC mode, default=1 (enabled)
# Note that this option is ignored if vcpus > 1
#apic=1
# Enable/disable extended power management support within HVM guest, i.e.,
beyond
# S3, S4, S5 within guest like exposing battery meter.
# 0 (default option, extended power management support disabled)
# 1 (pass-through mode; uses pass-through as needed; efficient but limited in
scope)
# 2 (non pass-through mode; extended scope, likely to work on all applicable
environment
# but comparitively less efficient than pass-through mode)
# xen_extended_power_mgmt=0
# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = "" # leave to Xen to pick
#cpus = "0" # all vcpus run on CPU0
#cpus = "0-3,5,^1" # all vcpus run on cpus 0,2,3,5
#cpus = ["2", "3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3
# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0,
model=ne2k_pci'' ]
# type=ioemu specify the NIC is an ioemu device not netfront
vif = [ ''type=ioemu, bridge=eth0 ]
#----------------------------------------------------------------------------
# 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 = [ ''phy:/dev/XEN/testserver,ioemu:hda,w'',
''file:/home/support/Win2008SP2_32bit.ISO,ioemu:hdc:cdrom,r'' ]
#disk = [ ''file:/var/images/min-el3-i386.img,hda,w'',
'',hdc:cdrom,r'' ]
#----------------------------------------------------------------------------
# Configure the behaviour when a domain exits. There are three
''reasons''
# for a domain to stop: poweroff, reboot, and crash. For each of these you
# may specify:
#
# "destroy", meaning that the domain is cleaned up as normal;
# "restart", meaning that a new domain is started in place of
the old
# one;
# "preserve", meaning that no clean-up is done until the
domain is
# manually destroyed (using xm destroy, for example); or
# "rename-restart", meaning that the old domain is not cleaned up,
but is
# renamed and a new domain started in its place.
#
# In the event a domain stops due to a crash, you have the additional options:
#
# "coredump-destroy", meaning dump the crashed domain''s
core and then destroy;
# "coredump-restart'', meaning dump the crashed domain''s
core and the restart.
#
# The default is
#
# on_poweroff = ''destroy''
# on_reboot = ''restart''
# on_crash = ''restart''
#
# For backwards compatibility we also support the deprecated option restart
#
# restart = ''onreboot'' means on_poweroff =
''destroy''
# on_reboot = ''restart''
# on_crash = ''destroy''
#on_poweroff = ''destroy''
#on_reboot = ''restart''
#on_crash = ''restart''
#===========================================================================
# Device Model to be used
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
#boot="cda"
#-----------------------------------------------------------------------------
# write to temporary files instead of disk image files
#snapshot=1
#----------------------------------------------------------------------------
# enable SDL library for graphics, default = 0
sdl=0
#----------------------------------------------------------------------------
# enable OpenGL for texture rendering inside the SDL window, default = 1
# valid only if sdl is enabled.
opengl=1
#----------------------------------------------------------------------------
# enable VNC library for graphics, default = 1
vnc=1
#----------------------------------------------------------------------------
# address that should be listened on for the VNC server if vnc is set.
# default is to use ''vnc-listen'' setting from
/etc/xen/xend-config.sxp
#vnclisten="127.0.0.1"
#----------------------------------------------------------------------------
# set VNC display number, default = domid
#vncdisplay=1
#----------------------------------------------------------------------------
# try to find an unused port for the VNC server, default = 1
#vncunused=1
#----------------------------------------------------------------------------
# set password for domain''s VNC console
# default is depents on vncpasswd in xend-config.sxp
vncpasswd=''''
#----------------------------------------------------------------------------
# no graphics, use serial port
#nographic=0
#----------------------------------------------------------------------------
# enable stdvga, default = 0 (use cirrus logic device model)
stdvga=0
#-----------------------------------------------------------------------------
# serial port re-direct to pty deivce, /dev/pts/n
# then xm console or minicom can connect
serial=''pty''
#-----------------------------------------------------------------------------
# Qemu Monitor, default is disable
# Use ctrl-alt-2 to connect
#monitor=1
#-----------------------------------------------------------------------------
# enable sound card support, [sb16|es1370|all|..,..], default none
#soundhw=''sb16''
#-----------------------------------------------------------------------------
# set the real time clock to local time [default=0 i.e. set to utc]
#localtime=1
#-----------------------------------------------------------------------------
# set the real time clock offset in seconds [default=0 i.e. same as dom0]
#rtc_timeoffset=3600
#-----------------------------------------------------------------------------
# start in full screen
#full-screen=1
#-----------------------------------------------------------------------------
# Enable USB support (specific devices specified at runtime through the
# monitor window)
#usb=1
# Enable USB mouse support (only enable one of the following, `mouse''
for
# PS/2 protocol relative mouse, `tablet''
for
# absolute mouse)
#usbdevice=''mouse''
#usbdevice=''tablet''
#-----------------------------------------------------------------------------
# Set keyboard layout, default is en-us keyboard.
#keymap=''ja''
#-----------------------------------------------------------------------------
# Enable/disable xen platform PCI device, default=1 (enabled)
#xen_platform_pci=1
Output of brctl
bridge name bridge id STP enabled interfaces
eth0 8000.001966ee28b4 no peth0
-----Original Message-----
From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
Sent: 18 January 2010 21:24
To: Ian Tobin
Cc: Fajar A. Nugraha; xen-users@lists.xensource.com
Subject: Re: [Xen-users] Network problem
On Mon, Jan 18, 2010 at 09:16:15PM -0000, Ian Tobin
wrote:> Think i spoke to soon.
>
> The domU gets further in starting up now that you can see the main console
start the virtual device but it still returns that error. Looking in the log
file doesn''t really report any errors.
>
> If i comment out the networking in the config file the domU starts fine
>
Please pastebin the domU configuration file from /etc/xen/
-- Pasi
>
>
> -----Original Message-----
> From: Fajar A. Nugraha [mailto:fajar@fajar.net]
> Sent: 18 January 2010 13:57
> To: Ian Tobin
> Cc: xen-users@lists.xensource.com
> Subject: Re: [Xen-users] Network problem
>
> On Mon, Jan 18, 2010 at 5:11 PM, Ian Tobin <itobin@tidyhosts.com>
wrote:
> > I have also checked udev is running and the only error in the log that
i
> > can see is
> >
> > Traceback (most recent call last):
> > File
"/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> > line 2228, in _releaseDevices
> > self.destroyDevice(true_devclass, dev, False);
> > File
"/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> > line 1148, in destroyDevice
> > rc = self.getDeviceController(deviceClass).destroyDevice(devid,
> > force)
> > File
"/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> > line 2249, in getDeviceController
> > raise XendError("Unknown device type: %s" % name)
> > XendError: Unknown device type: None
> >
> > Not sure if that means anything to you?
> >
>
> Go back several lines (should be less than one hundred), start looking
> from the one where the domain is starting. There might be a more
> useful info there, like what it was doing before it throws the error
> vif not connected.
>
> --
> Fajar
>
>
>
> _______________________________________________
> 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
On Mon, Jan 18, 2010 at 09:32:00PM -0000, Ian Tobin wrote:> Hi, > > Here it is > > > # Optionally define mac and/or bridge for the network interfaces. > # Random MACs are assigned if not given. > #vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] > # type=ioemu specify the NIC is an ioemu device not netfront > vif = [ ''type=ioemu, bridge=eth0 ] >You''re missing '' from the vif line. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sorry that was a typo, this is my vif line vif = [ ''type=ioemu, bridge=eth0'' ] -----Original Message----- From: Pasi Kärkkäinen [mailto:pasik@iki.fi] Sent: 18 January 2010 21:36 To: Ian Tobin Cc: Fajar A. Nugraha; xen-users@lists.xensource.com Subject: Re: [Xen-users] Network problem On Mon, Jan 18, 2010 at 09:32:00PM -0000, Ian Tobin wrote:> Hi, > > Here it is > > > # Optionally define mac and/or bridge for the network interfaces. > # Random MACs are assigned if not given. > #vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] > # type=ioemu specify the NIC is an ioemu device not netfront > vif = [ ''type=ioemu, bridge=eth0 ] >You''re missing '' from the vif line. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 19, 2010 at 4:16 AM, Ian Tobin <itobin@tidyhosts.com> wrote:> Think i spoke to soon. > > The domU gets further in starting up now that you can see the main console start the virtual device but it still returns that error. Looking in the log file doesn''t really report any errors. > > If i comment out the networking in the config file the domU starts fineWhat do you mean "you can see the main console"? Do you mean you can connect vncviewer and see domU booting? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sorry no, i mean on the actual physical server console, you can see the tap device being created, going into the forwarding state and then it just hangs, the console then reports that it is now in the disabled state. Ian -----Original Message----- From: Fajar A. Nugraha [mailto:fajar@fajar.net] Sent: 19 January 2010 03:22 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Network problem On Tue, Jan 19, 2010 at 4:16 AM, Ian Tobin <itobin@tidyhosts.com> wrote:> Think i spoke to soon. > > The domU gets further in starting up now that you can see the main console start the virtual device but it still returns that error. Looking in the log file doesn''t really report any errors. > > If i comment out the networking in the config file the domU starts fineWhat do you mean "you can see the main console"? Do you mean you can connect vncviewer and see domU booting? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 19, 2010 at 4:00 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Sorry no, i mean on the actual physical server console, you can see the tap device being created, going into the forwarding state and then it just hangs, the console then reports that it is now in the disabled state.What does "xm list" show? is the domU created? If not, there should be something in /var/log/xen/xend.log, recording when the domU failed to startup, or shutdown, or crashed. Also, since you say that some files failed to be copied earlier, the easiet way that can I suggest is to try known-good config first. For example, I''m using RHEL5.4 with Xen rpm from gitco. Once that works, you can start changing some elements (like replacing dom0 kernel with pv_ops). -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Xm list shows no creation.
Here is the entire log when xm create is issued
[2010-01-19 09:22:25 2894] DEBUG (XendDomainInfo:2304)
XendDomainInfo.constructDomain
[2010-01-19 09:22:25 2894] DEBUG (balloon:166) Balloon: 113092 KiB free;
need 4096; done.
[2010-01-19 09:22:25 2894] DEBUG (XendDomain:453) Adding Domain: 1
[2010-01-19 09:22:25 2894] DEBUG (XendDomainInfo:2505)
XendDomainInfo.initDomain: 1 256
[2010-01-19 09:22:25 2894] DEBUG (image:322) No VNC passwd configured
for vfb access
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: boot, val: c
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: fda, val: None
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: fdb, val: None
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: soundhw, val: None
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: localtime, val: 0
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: serial, val:
[''pty'']
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: std-vga, val: 0
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: isa, val: 0
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: acpi, val: 1
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: usb, val: 0
[2010-01-19 09:22:25 2894] DEBUG (image:813) args: usbdevice, val: None
[2010-01-19 09:22:25 2894] INFO (image:749) Need to create platform
device.[domid:1]
[2010-01-19 09:22:25 2894] DEBUG (XendDomainInfo:2529)
_initDomain:shadow_memory=0x0, memory_static_max=0x8000000,
memory_static_min=0x0.
[2010-01-19 09:22:25 2894] DEBUG (balloon:172) Balloon: 111808 KiB free;
0 to scrub; need 138240; retries: 20.
[2010-01-19 09:22:25 2894] DEBUG (balloon:187) Balloon: setting dom0
target to 1630 MiB.
[2010-01-19 09:22:25 2894] DEBUG (XendDomainInfo:1303) Setting memory
target of domain Domain-0 (0) to 1630 MiB.
[2010-01-19 09:22:25 2894] DEBUG (balloon:166) Balloon: 139068 KiB free;
need 138240; done.
[2010-01-19 09:22:25 2894] INFO (image:173) buildDomain os=hvm dom=1
vcpus=1
[2010-01-19 09:22:25 2894] DEBUG (image:866) domid = 1
[2010-01-19 09:22:25 2894] DEBUG (image:867) image
/usr/lib/xen/boot/hvmloader
[2010-01-19 09:22:25 2894] DEBUG (image:868) store_evtchn = 2
[2010-01-19 09:22:25 2894] DEBUG (image:869) memsize = 128
[2010-01-19 09:22:25 2894] DEBUG (image:870) target = 128
[2010-01-19 09:22:25 2894] DEBUG (image:871) vcpus = 1
[2010-01-19 09:22:25 2894] DEBUG (image:872) acpi = 1
[2010-01-19 09:22:25 2894] DEBUG (image:873) apic = 1
[2010-01-19 09:22:25 2894] INFO (XendDomainInfo:2168) createDevice: vfb
: {''vncunused'': 1, ''other_config'':
{''vncunused'': 1, ''vnc'':
''1''}, ''vnc'':
''1'', ''uuid'':
''70e019ed-9fef-d993-64f5-034348fddb7b''}
[2010-01-19 09:22:25 2894] DEBUG (DevController:95) DevController:
writing {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vfb/1/0''} to
/local/domain/1/device/vfb/0.
[2010-01-19 09:22:25 2894] DEBUG (DevController:97) DevController:
writing {''vncunused'': ''1'',
''domain'': ''testserver'',
''frontend'':
''/local/domain/1/device/vfb/0'', ''uuid'':
''70e019ed-9fef-d993-64f5-034348fddb7b'',
''frontend-id'': ''1'',
''state'':
''1'', ''online'': ''1'',
''vnc'': ''1''} to
/local/domain/0/backend/vfb/1/0.
[2010-01-19 09:22:25 2894] INFO (XendDomainInfo:2168) createDevice: vbd
: {''uuid'':
''ad665d18-f9c3-d70b-7e2a-fd913fc5e185'',
''bootable'': 1,
''driver'': ''ioemu'', ''dev'':
''ioemu:hda'', ''uname'':
''phy:/dev/XEN/testserver'', ''mode'':
''w''}
[2010-01-19 09:22:25 2894] DEBUG (DevController:95) DevController:
writing {''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'':
''disk'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/1/768''} to
/local/domain/1/device/vbd/768.
[2010-01-19 09:22:25 2894] DEBUG (DevController:97) DevController:
writing {''domain'': ''testserver'',
''frontend'':
''/local/domain/1/device/vbd/768'', ''uuid'':
''ad665d18-f9c3-d70b-7e2a-fd913fc5e185'',
''bootable'': ''1'', ''dev'':
''hda'',
''state'': ''1'', ''params'':
''/dev/XEN/testserver'', ''mode'':
''w'', ''online'':
''1'', ''frontend-id'': ''1'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/1/768.
[2010-01-19 09:22:25 2894] INFO (XendDomainInfo:2168) createDevice: vbd
: {''uuid'':
''c2cba0c1-47e4-934e-b905-957bce0d7c5e'',
''bootable'': 0,
''driver'': ''ioemu'', ''dev'':
''ioemu:hdc:cdrom'', ''uname'':
''file:/home/support/Win2008SP2_32bit.ISO'',
''mode'': ''r''}
[2010-01-19 09:22:25 2894] DEBUG (DevController:95) DevController:
writing {''backend-id'': ''0'',
''virtual-device'': ''5632'',
''device-type'':
''cdrom'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/1/5632''}
to /local/domain/1/device/vbd/5632.
[2010-01-19 09:22:25 2894] DEBUG (DevController:97) DevController:
writing {''domain'': ''testserver'',
''frontend'':
''/local/domain/1/device/vbd/5632'', ''uuid'':
''c2cba0c1-47e4-934e-b905-957bce0d7c5e'',
''bootable'': ''0'', ''dev'':
''hdc'',
''state'': ''1'', ''params'':
''/home/support/Win2008SP2_32bit.ISO'',
''mode'':
''r'', ''online'': ''1'',
''frontend-id'': ''1'',
''type'': ''file''} to
/local/domain/0/backend/vbd/1/5632.
[2010-01-19 09:22:25 2894] INFO (XendDomainInfo:2168) createDevice: vif
: {''bridge'': ''eth0'',
''mac'': ''00:16:3e:09:33:b7'',
''type'': ''ioemu'',
''uuid'':
''874b6ddc-613b-197c-26c1-1c0cc143274e''}
[2010-01-19 09:22:25 2894] DEBUG (DevController:95) DevController:
writing {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vif/1/0''} to
/local/domain/1/device/vif/0.
[2010-01-19 09:22:25 2894] DEBUG (DevController:97) DevController:
writing {''bridge'': ''eth0'',
''domain'': ''testserver'',
''handle'': ''0'',
''uuid'':
''874b6ddc-613b-197c-26c1-1c0cc143274e'',
''script'':
''/etc/xen/scripts/vif-bridge'', ''mac'':
''00:16:3e:09:33:b7'',
''frontend-id'': ''1'',
''state'': ''1'', ''online'':
''1'', ''frontend'':
''/local/domain/1/device/vif/0'', ''type'':
''ioemu''} to
/local/domain/0/backend/vif/1/0.
[2010-01-19 09:22:25 2894] INFO (image:394) spawning device models:
/usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'',
''-d'', ''1'',
''-domain-name'', ''testserver'',
''-videoram'', ''4'', ''-vnc'',
''0.0.0.0:0'',
''-vncunused'', ''-vcpus'',
''1'', ''-boot'', ''c'',
''-serial'', ''pty'', ''-acpi'',
''-net'',
''nic,vlan=1,macaddr=00:16:3e:09:33:b7,model=rtl8139'',
''-net'',
''tap,vlan=1,ifname=tap1.0,bridge=eth0'',
''-M'', ''xenfv'']
[2010-01-19 09:22:25 2894] INFO (image:443) device model pid: 2980
[2010-01-19 09:22:25 2894] INFO (image:531) waiting for sentinel_fifo
[2010-01-19 09:22:25 2894] DEBUG (XendDomainInfo:3060) Storing VM
details: {''on_xend_stop'': ''ignore'',
''shadow_memory'': ''2'',
''uuid'':
''e8bad567-b3d6-b45a-6b13-efa25ce55fff'',
''on_reboot'': ''restart'',
''start_time'': ''1263892945.57'',
''on_poweroff'': ''destroy'',
''bootloader_args'': '''',
''on_xend_start'': ''ignore'',
''on_crash'': ''restart'',
''xend/restart_count'': ''0'',
''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''bootloader'': '''', ''image'':
''(hvm (kernel ) (videoram 4) (hpet 0) (stdvga
0) (loader /usr/lib/xen/boot/hvmloader) (serial pty) (vncunused 1)
(xen_platform_pci 1) (opengl 1) (boot c) (rtc_timeoffset 0) (pci ())
(pae 1) (vpt_align 1) (hap 1) (viridian 0) (acpi 1) (localtime 0)
(timer_mode 1) (vnc 1) (nographic 0) (guest_os_type default)
(pci_msitranslate 1) (apic 1) (sdl 0) (monitor 0) (device_model
/usr/lib/xen/bin/qemu-dm) (pci_power_mgmt 0) (usb 0) (xauthority
/root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)))'',
''name'':
''testserver''}
[2010-01-19 09:22:25 2894] DEBUG (XendDomainInfo:1622) Storing domain
details: {''console/port'': ''3'',
''name'': ''testserver'',
''console/limit'':
''1048576'', ''store/port'':
''2'', ''vm'':
''/vm/e8bad567-b3d6-b45a-6b13-efa25ce55fff'',
''domid'': ''1'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
''memory/target'': ''131072'',
''control/platform-feature-multiprocessor-suspend'':
''1'',
''store/ring-ref'': ''1044476'',
''console/type'': ''ioemu''}
[2010-01-19 09:22:25 2894] DEBUG (DevController:95) DevController:
writing {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/console/1/0''} to
/local/domain/1/device/console/0.
[2010-01-19 09:22:25 2894] DEBUG (DevController:97) DevController:
writing {''domain'': ''testserver'',
''frontend'':
''/local/domain/1/device/console/0'', ''uuid'':
''9380cdf4-2b3d-c468-4d01-df014b42c4d6'',
''frontend-id'': ''1'',
''state'':
''1'', ''location'': ''3'',
''online'': ''1'', ''protocol'':
''vt100''} to
/local/domain/0/backend/console/1/0.
[2010-01-19 09:22:25 2894] DEBUG (XendDomainInfo:1709)
XendDomainInfo.handleShutdownWatch
[2010-01-19 09:22:25 2894] DEBUG (DevController:139) Waiting for devices
vif.
[2010-01-19 09:22:25 2894] DEBUG (DevController:144) Waiting for 0.
[2010-01-19 09:22:25 2894] DEBUG (DevController:629)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:2732)
XendDomainInfo.destroy: domid=1
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:2207) Destroying device
model
[2010-01-19 09:24:05 2894] INFO (image:556) testserver device model
terminated
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:2214) Releasing devices
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:2227) Removing vif/0
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:2227) Removing vbd/768
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = None, device = vbd/768
[2010-01-19 09:24:05 2894] ERROR (XendDomainInfo:2234) Device release
failed: testserver; None; vbd/768
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 2228, in _releaseDevices
self.destroyDevice(true_devclass, dev, False);
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 1148, in destroyDevice
rc = self.getDeviceController(deviceClass).destroyDevice(devid,
force)
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 2249, in getDeviceController
raise XendError("Unknown device type: %s" % name)
XendError: Unknown device type: None
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:2227) Removing vbd/5632
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = None, device = vbd/5632
[2010-01-19 09:24:05 2894] ERROR (XendDomainInfo:2234) Device release
failed: testserver; None; vbd/5632
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 2228, in _releaseDevices
self.destroyDevice(true_devclass, dev, False);
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 1148, in destroyDevice
rc = self.getDeviceController(deviceClass).destroyDevice(devid,
force)
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 2249, in getDeviceController
raise XendError("Unknown device type: %s" % name)
XendError: Unknown device type: None
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:2227) Removing vfb/0
[2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2010-01-19 09:24:06 2894] DEBUG (XendDomainInfo:2227) Removing
console/0
[2010-01-19 09:24:06 2894] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-01-19 09:24:06 2894] DEBUG (XendDomainInfo:2212) No device model
[2010-01-19 09:24:06 2894] DEBUG (XendDomainInfo:2214) Releasing devices
With regard to the Dom0. Im already using Jermeys kernel from his git
tree running pv_ops. The config is one of the example configs with just
the changes made to match the domU name etc.
Ian
-----Original Message-----
From: Fajar A. Nugraha [mailto:fajar@fajar.net]
Sent: 19 January 2010 09:12
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Network problem
On Tue, Jan 19, 2010 at 4:00 PM, Ian Tobin <itobin@tidyhosts.com>
wrote:> Sorry no, i mean on the actual physical server console, you can see
the tap device being created, going into the forwarding state and then
it just hangs, the console then reports that it is now in the disabled
state.
What does "xm list" show? is the domU created? If not, there should be
something in /var/log/xen/xend.log, recording when the domU failed to
startup, or shutdown, or crashed.
Also, since you say that some files failed to be copied earlier, the
easiet way that can I suggest is to try known-good config first. For
example, I''m using RHEL5.4 with Xen rpm from gitco. Once that works,
you can start changing some elements (like replacing dom0 kernel with
pv_ops).
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Tue, Jan 19, 2010 at 4:27 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Xm list shows no creation. > > Here is the entire log when xm create is issued> [2010-01-19 09:22:25 2894] INFO (XendDomainInfo:2168) createDevice: vbd > : {''uuid'': ''c2cba0c1-47e4-934e-b905-957bce0d7c5e'', ''bootable'': 0, > ''driver'': ''ioemu'', ''dev'': ''ioemu:hdc:cdrom'', ''uname'': > ''file:/home/support/Win2008SP2_32bit.ISO'', ''mode'': ''r''}Why are you still using ioemu? It''s not needed, neither in vif or disk. Also, do you have selinux enabled? It might prevent xen from reading files outside of /var/lib/xen. Try disabling selinux (if enabled), and also move the cdrom iso out of /home.> hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. > [2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:2732) > XendDomainInfo.destroy: domid=1this show the domain is destroyed. if you''re running on server''s GUI console, or have X forwarding enabled, it might be helpful to add vncconsole=1 or use sdl so that you could take a look at domU''s console, just in case it was started. FWIW, here''s my HVM domU config that I recently used to test opensuse installation #========================# cat opensuse memory = 2000 vif = [ ''mac=00:16:3E:C8:78:D8, bridge=br129, vifname=opensuse-eth0'' ] disk = [ ''file:/z/opensuse/hda.img,hda,w'', ''file:/z/opensuse/hdb.img,hdb,w'', ''file:/data/src/iso/opensuse.iso,hdc:cdrom,r'', ] boot="cd" device_model = ''/usr/lib64/xen/bin/qemu-dm'' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' sdl=0 vnc=1 vnclisten="0.0.0.0" #vncunused=0 vncpasswd='''' stdvga=0 serial=''pty'' localtime=0 usbdevice=''tablet'' acpi=1 apic=0 pae=1 vcpus=2 cpus="1-7" #================================= -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sorry i just used the example config in /etc/xen and changed the bits, i didn''t realise ioemu wasn''t needed. Have have tried your config and suggestions but still no good :( Im going to format the server and try again from scratch. Will update shortly thanks -----Original Message----- From: Fajar A. Nugraha [mailto:fajar@fajar.net] Sent: 19 January 2010 09:48 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Network problem On Tue, Jan 19, 2010 at 4:27 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Xm list shows no creation. > > Here is the entire log when xm create is issued> [2010-01-19 09:22:25 2894] INFO (XendDomainInfo:2168) createDevice:vbd> : {''uuid'': ''c2cba0c1-47e4-934e-b905-957bce0d7c5e'', ''bootable'': 0, > ''driver'': ''ioemu'', ''dev'': ''ioemu:hdc:cdrom'', ''uname'': > ''file:/home/support/Win2008SP2_32bit.ISO'', ''mode'': ''r''}Why are you still using ioemu? It''s not needed, neither in vif or disk. Also, do you have selinux enabled? It might prevent xen from reading files outside of /var/lib/xen. Try disabling selinux (if enabled), and also move the cdrom iso out of /home.> hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. > [2010-01-19 09:24:05 2894] DEBUG (XendDomainInfo:2732) > XendDomainInfo.destroy: domid=1this show the domain is destroyed. if you''re running on server''s GUI console, or have X forwarding enabled, it might be helpful to add vncconsole=1 or use sdl so that you could take a look at domU''s console, just in case it was started. FWIW, here''s my HVM domU config that I recently used to test opensuse installation #========================# cat opensuse memory = 2000 vif = [ ''mac=00:16:3E:C8:78:D8, bridge=br129, vifname=opensuse-eth0'' ] disk = [ ''file:/z/opensuse/hda.img,hda,w'', ''file:/z/opensuse/hdb.img,hdb,w'', ''file:/data/src/iso/opensuse.iso,hdc:cdrom,r'', ] boot="cd" device_model = ''/usr/lib64/xen/bin/qemu-dm'' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' sdl=0 vnc=1 vnclisten="0.0.0.0" #vncunused=0 vncpasswd='''' stdvga=0 serial=''pty'' localtime=0 usbdevice=''tablet'' acpi=1 apic=0 pae=1 vcpus=2 cpus="1-7" #================================= -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 19, 2010 at 6:20 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Sorry i just used the example config in /etc/xen and changed the bits, > i didn''t realise ioemu wasn''t needed.I''m not exactly sure whay ioemu does nowadays, but last time I check HVM domUs work just fine without it, and it causes problems when you use Windows domU + GPLPV.> > Have have tried your config and suggestions but still no good :( > > Im going to format the server and try again from scratch.If you''re going to format it anyway, I suggest starting with known good config (that you or others have tested). Like RHEL/Centos5, plus Gitco''s Xen rpm if you want. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Right, rebuilt, had some issues but got xen up. Ive now used the same config and it boots fine so what the issue was before is beyond me. Im still getting an error CDBOOT: Cannot boot from CD - Code: 1 When trying to boot from a Windows 2008 ISO. Any ideas? Ian -----Original Message----- From: Fajar A. Nugraha [mailto:fajar@fajar.net] Sent: 20 January 2010 01:57 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Network problem On Tue, Jan 19, 2010 at 6:20 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Sorry i just used the example config in /etc/xen and changed the bits, > i didn''t realise ioemu wasn''t needed.I''m not exactly sure whay ioemu does nowadays, but last time I check HVM domUs work just fine without it, and it causes problems when you use Windows domU + GPLPV.> > Have have tried your config and suggestions but still no good :( > > Im going to format the server and try again from scratch.If you''re going to format it anyway, I suggest starting with known good config (that you or others have tested). Like RHEL/Centos5, plus Gitco''s Xen rpm if you want. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Don''t worry, created a new iso from CD rather than downloading from Microsoft and it works now, very odd! Thanks again for the help Ian -----Original Message----- From: Fajar A. Nugraha [mailto:fajar@fajar.net] Sent: 20 January 2010 01:57 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Network problem On Tue, Jan 19, 2010 at 6:20 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Sorry i just used the example config in /etc/xen and changed the bits, > i didn''t realise ioemu wasn''t needed.I''m not exactly sure whay ioemu does nowadays, but last time I check HVM domUs work just fine without it, and it causes problems when you use Windows domU + GPLPV.> > Have have tried your config and suggestions but still no good :( > > Im going to format the server and try again from scratch.If you''re going to format it anyway, I suggest starting with known good config (that you or others have tested). Like RHEL/Centos5, plus Gitco''s Xen rpm if you want. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users