how to determine CPU Slice
by Manogna Ramakrishna Chebiyyam
Hi,
Some one please give me a pointer as to how to determine the CPU Slice
of a domain U
Thanks in advance
"If we knew what it was we were doing, it would not be called research,
would it?" Albert Einstien
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
17 years, 7 months
Exception when starting xend: error while reading /vm/00000000-0000-0000-0000-000000000000/ssidref
by Daniele Sgandurra
I've been using Xen for 3 months, but now I've
problems when starting xend: I'm using Fedora 5 with
Xen installed from binaries (I have also tried with
compiled versions but it doesn't work either):
$ uname -a
Linux localhost.localdomain 2.6.16-xen #1 SMP Mon Jul
3 18:18:42 CEST 2006 i686 i686 i386 GNU/Linux
$ python -V
Python 2.4.3
# xend start
# xm list
Error: Error connecting to xend: No such file or
directory. Is xend running?
This is the output from /var/log/xend.log:
--------------------------------------------
[2006-09-08 13:42:05 xend] INFO (SrvDaemon:278) Xend
Daemon started
[2006-09-08 13:42:05 xend] INFO (SrvDaemon:282) Xend
changeset: Thu Apr 13 15:18:37 2006 +0100
9617:5802713c159b.
[2006-09-08 13:42:05 xend.XendDomainInfo] DEBUG
(XendDomainInfo:200)
XendDomainInfo.recreate({'paused': 0, 'cpu_time':
30441112756L, 'ssidref': 65537, 'handle': [0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb':
429056, 'maxmem_kb': -4, 'max_vcpu_id': 0, 'crashed':
0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1,
'blocked': 0})
[2006-09-08 13:42:05 xend.XendDomainInfo] INFO
(XendDomainInfo:212) Recreating domain 0, UUID
00000000-0000-0000-0000-000000000000.
[2006-09-08 13:42:05 xend.XendDomainInfo] WARNING
(XendDomainInfo:234) (5, 'Input/output error, while
reading
/vm/00000000-0000-0000-0000-000000000000/ssidref')
[2006-09-08 13:42:05 xend] ERROR (SrvDaemon:292)
Exception starting xend ((5, 'Input/output error,
while reading
/vm/00000000-0000-0000-0000-000000000000/ssidref'))
Traceback (most recent call last):
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/server/SrvDaemon.py",
line 286, in run
servers = SrvServer.create()
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/server/SrvServer.py",
line 108, in create
root.putChild('xend', SrvRoot())
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/server/SrvRoot.py",
line 40, in __init__
self.get(name)
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/web/SrvDir.py",
line 82, in get
val = val.getobj()
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/web/SrvDir.py",
line 52, in getobj
self.obj = klassobj()
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/server/SrvDomainDir.py",
line 39, in __init__
self.xd = XendDomain.instance()
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomain.py",
line 582, in instance
inst.init()
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomain.py",
line 77, in init
True))
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
line 236, in recreate
vm = XendDomainInfo(xeninfo, domid, dompath, True,
priv)
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
line 435, in __init__
self.augmentInfo(priv)
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
line 520, in augmentInfo
self.readVMDetails(entries))
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
line 463, in readVMDetails
return self.gatherVm(*params)
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
line 606, in gatherVm
return xstransact.Gather(self.vmpath, *args)
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py",
line 305, in Gather
return complete(path, lambda t: t.gather(*args))
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py",
line 325, in complete
result = f(t)
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py",
line 305, in <lambda>
return complete(path, lambda t: t.gather(*args))
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py",
line 179, in gather
val = self._read(key)
File
"/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py",
line 49, in _read
'%s, while reading %s' % (ex.args[1], path))
RuntimeError: (5, 'Input/output error, while reading
/vm/00000000-0000-0000-0000-000000000000/ssidref')
--------------------------------------------
I've tried to re-install Xen from binary or from
source but I cannot get it work.
Any ideas/suggestions?
Thank you very much.
__________________________________________________
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi
http://mail.yahoo.it
17 years, 7 months
multiple nic's with vlan -> bridge or bridge -> vlan
by Thomas von Steiger
Hello,
Whats the experience with multiple nic's and vlan's/bridge's for xen guests
?
Is it better to build network configs for xen guest's with:
eth0 - vlan's - bridge's - domU's
eth1 - vlan's - bridge's - domU's
or
eth0 - bridge - vlan's -domU's
eth1 - bridge - vlan's -domU's
regards,
Thomas
17 years, 7 months
interface tun0 does not exist!
by Thomas von Steiger
Hello,
I can not setup any guest's becose of missing interfaces.
/var/log/xend-debug.log:
Link veth0 is missing.
This may be because you have reached the limit of the number of
interfaces that the loopback driver supports. If the loopback driver is
a module, you may raise this limit by passing it as a parameter
(nloopbacks=<N>); if the driver is compiled statically into the kernel,
then you may set the parameter using loopback.nloopbacks=<N> on the
domain 0 kernel command line.
interface tun0 does not exist!
interface tun0 does not exist!
interface tun0 does not exist!
interface tun0 does not exist!
>From dmesg:
bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex
bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex
bnx2: eth2 NIC Link is Up, 1000 Mbps full duplex
bnx2: eth3 NIC Link is Up, 1000 Mbps full duplex
/etc/grub.conf:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/fcvg/slash
# initrd /initrd-version.img
#boot=/dev/cciss/c0d0
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title Fedora Core (2.6.17-1.2174_FC5xen)
root (hd0,0)
kernel /xen.gz-2.6.17-1.2174_FC5-PAE dom0_mem=512000
loopback.nloopbacks=128
module /vmlinuz-2.6.17-1.2174_FC5xen ro root=/dev/fcvg/slash
module /initrd-2.6.17-1.2174_FC5xen.img
title Fedora Core (2.6.17-1.2174_FC5smp)
root (hd0,0)
kernel /vmlinuz-2.6.17-1.2174_FC5smp ro root=/dev/fcvg/slash
initrd /initrd-2.6.17-1.2174_FC5smp.img
title Fedora Core 5 (2.6.15-1.2054_FC5smp)
root (hd0,0)
kernel /vmlinuz-2.6.15-1.2054_FC5smp ro root=/dev/fcvg/slash
initrd /initrd-2.6.15-1.2054_FC5smp.img
Hardware: HP DL380 G5, 16G memory, 4 nic's from type bnx2, eth0 - eth3 are
all there.
ifconfig -a prints eth0,eth1,eth2,eth3,lo
With kernel parameter "loopback.nloopbacks=128" i have the same problem.
Again with loopback.nloopbacks= .32,48,128,164,256. always no tun0 or
xenbr0.
What can be wrong here ?
Many thanks for any help.
Thomas
17 years, 7 months
Re: rawhide report: 20060906 changes
by Jeremy Katz
On Wed, 2006-09-06 at 06:51 -0400, buildsys(a)redhat.com wrote:
> xen-3.0.2-33
> ------------
> * Tue Sep 05 2006 Jeremy Katz <katzj(a)redhat.com> - 3.0.2-33
> - update pvfb patch based on upstream feedback
Heads up that this also requires the 2627 kernel in guests using the
paravirt framebuffer. The last round of upstream review had some minor
protocol changes, but hopefully those are all behind us now.
Unfortunately, the kernel build finished at 4:02 am (the rawhide compose
starts at 4 am). So for now, I've put the previous tools package (-32)
at http://people.redhat.com/~katzj/xen/
Jeremy
17 years, 7 months
vif not being created for domU - possible hotplug problem?
by Hilton Day
Hi,
I'm running with fc5, kernel-xen0-2.6.17-1.2174.
Yesterday I had a working Xen installation with a domU also running FC5,
same kernel, udev, xen, libvirt, and same hardware.
Following a rebuild of the host and reinstall/update of FC5 to same
update levels, I'm now hitting a problem installing a domU, where it
appears its not setting up a bridged interface for the domU. I think it
might be hotplug related?
I've got the same udev, and its running, and I can see the rules files
in /etc/udev/rules.d.
Below is the output of several logs and commands.. as far as I can see,
the network-bridge script is good, and its set up my interfaces
correctly. One minor complication is that my bridged ethernet card is
on device eth2, but I've got the amendment in xend-config.sxp to call
"(network-script 'network-bridge netdev=eth2')".
I checked the kernel-xen list in bugzilla but couldn't find anything
there on hotplug problems.
Any help in figuring out the root cause would be much appreciated!
Having gone from working to not-working in a reinstall of the same setup
has me very confused.
#### brctl show ####
bridge name bridge id STP enabled interfaces
xenbr2 8000.feffffffffff no peth2
vif0.2
#### ifconfig ####
eth2 Link encap:Ethernet HWaddr 00:14:6C:8C:2E:25
inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::214:6cff:fe8c:2e25/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:353 errors:0 dropped:0 overruns:0 frame:0
TX packets:396 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:42427 (41.4 KiB) TX bytes:97320 (95.0 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:660 errors:0 dropped:0 overruns:0 frame:0
TX packets:660 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3375221 (3.2 MiB) TX bytes:3375221 (3.2 MiB)
peth2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:362 errors:0 dropped:0 overruns:0 frame:0
TX packets:457 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:43683 (42.6 KiB) TX bytes:104598 (102.1 KiB)
Interrupt:18
vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:396 errors:0 dropped:0 overruns:0 frame:0
TX packets:354 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:97320 (95.0 KiB) TX bytes:42517 (41.5 KiB)
xenbr2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:62 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9920 (9.6 KiB) TX bytes:468 (468.0 b)
#### /var/log/xen-hotplug.log ####
interface vif1.0 does not exist!
#### /var/log/xend.log ####
[2006-08-30 11:17:25 xend] INFO (SrvDaemon:283) Xend Daemon started
[2006-08-30 11:17:25 xend] INFO (SrvDaemon:287) Xend changeset:
unavailable .
[2006-08-30 11:17:25 xend.XendDomainInfo] DEBUG (XendDomainInfo:207)
XendDomainInfo.recreate({'paused': 0, 'cpu_time': 10867218609L,
'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 961860,
'maxmem_kb': -4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1,
'shutdown': 0, 'online_vcpus': 1, 'blocked': 0})
[2006-08-30 11:17:25 xend.XendDomainInfo] INFO (XendDomainInfo:219)
Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2006-08-30 11:17:25 xend.XendDomainInfo] WARNING (XendDomainInfo:241)
No vm path in store for existing domain 0
[2006-08-30 11:17:25 xend.XendDomainInfo] DEBUG (XendDomainInfo:701)
Storing VM details: {'name': 'Domain-0', 'on_reboot': 'restart',
'on_poweroff': 'destroy', 'uuid':
'00000000-0000-0000-0000-000000000000', 'on_crash': 'restart', 'vcpus':
'1', 'vcpu_avail': '1', 'memory': '940', 'maxmem': '940'}
[2006-08-30 11:17:25 xend.XendDomainInfo] DEBUG (XendDomainInfo:736)
Storing domain details: {'cpu/0/availability': 'online',
'memory/target': '962560', 'name': 'Domain-0', 'console/limit':
'1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'}
[2006-08-30 11:17:25 xend] DEBUG (XendDomain:153) number of vcpus to use
is 0
[2006-08-30 11:17:25 xend.XendDomainInfo] DEBUG (XendDomainInfo:919)
XendDomainInfo.handleShutdownWatch
[2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:185)
XendDomainInfo.create(['vm', ['name', 'xen-www'], ['memory', '256'],
['maxmem', '256'], ['vcpus', '1'], ['on_poweroff', 'destroy'],
['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['linux',
['kernel', '/var/lib/xen/vmlinuz.1WDQ9c'], ['ramdisk',
'/var/lib/xen/initrd.img.jBbqHv'], ['args', ' root=/dev/xvd
method=ftp://virtual/pub ']]], ['device', ['vbd', ['dev', '/dev/xvda'],
['uname', 'file:/dev/raid/xen_www'], ['mode', 'w']]], ['device', ['vif',
['mac', '00:16:3e:11:48:67'], ['bridge', 'xenbr0'], ['script',
'/etc/xen/scripts/vif-bridge']]]])
[2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:291)
parseConfig: config is ['vm', ['name', 'xen-www'], ['memory', '256'],
['maxmem', '256'], ['vcpus', '1'], ['on_poweroff', 'destroy'],
['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['linux',
['kernel', '/var/lib/xen/vmlinuz.1WDQ9c'], ['ramdisk',
'/var/lib/xen/initrd.img.jBbqHv'], ['args', ' root=/dev/xvd
method=ftp://virtual/pub ']]], ['device', ['vbd', ['dev', '/dev/xvda'],
['uname', 'file:/dev/raid/xen_www'], ['mode', 'w']]], ['device', ['vif',
['mac', '00:16:3e:11:48:67'], ['bridge', 'xenbr0'], ['script',
'/etc/xen/scripts/vif-bridge']]]]
[2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:390)
parseConfig: result is {'uuid': None, 'on_crash': 'destroy',
'on_reboot': 'destroy', 'image': ['linux', ['kernel',
'/var/lib/xen/vmlinuz.1WDQ9c'], ['ramdisk',
'/var/lib/xen/initrd.img.jBbqHv'], ['args', ' root=/dev/xvd
method=ftp://virtual/pub ']], 'on_poweroff': 'destroy',
'bootloader_args': None, 'cpus': None, 'name': 'xen-www', 'backend': [],
'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None,
'memory': 256, 'device': [('vbd', ['vbd', ['dev', '/dev/xvda'],
['uname', 'file:/dev/raid/xen_www'], ['mode', 'w']]), ('vif', ['vif',
['mac', '00:16:3e:11:48:67'], ['bridge', 'xenbr0'], ['script',
'/etc/xen/scripts/vif-bridge']])], 'bootloader': None, 'cpu': None,
'maxmem': 256}
[2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:1216)
XendDomainInfo.construct: None
[2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:1248)
XendDomainInfo.initDomain: 1 1.0
[2006-08-30 11:22:23 xend] DEBUG (balloon:134) Balloon: free 62; need
257; retries: 10.
[2006-08-30 11:22:23 xend] DEBUG (balloon:143) Balloon: setting dom0
target to 745.
[2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:987)
Setting memory target of domain Domain-0 (0) to 745 MiB.
[2006-08-30 11:22:23 xend] DEBUG (balloon:128) Balloon: free 257; need
257; done.
[2006-08-30 11:22:23 xend] INFO (image:134) buildDomain os=linux dom=1
vcpus=1
[2006-08-30 11:22:23 xend] DEBUG (image:177) dom = 1
[2006-08-30 11:22:23 xend] DEBUG (image:178) image =
/var/lib/xen/vmlinuz.1WDQ9c
[2006-08-30 11:22:23 xend] DEBUG (image:179) store_evtchn = 1
[2006-08-30 11:22:23 xend] DEBUG (image:180) console_evtchn = 2
[2006-08-30 11:22:23 xend] DEBUG (image:181) cmdline =
root=/dev/xvd method=ftp://virtual/pub
[2006-08-30 11:22:23 xend] DEBUG (image:182) ramdisk =
/var/lib/xen/initrd.img.jBbqHv
[2006-08-30 11:22:23 xend] DEBUG (image:183) vcpus = 1
[2006-08-30 11:22:23 xend] DEBUG (image:184) features =
[2006-08-30 11:22:23 xend] DEBUG (blkif:24) exception looking up device
number for /dev/xvda: [Errno 2] No such file or directory: '/dev/xvda'
[2006-08-30 11:22:23 xend] DEBUG (DevController:110) DevController:
writing {'virtual-device': '51712', 'backend-id': '0', 'state': '1',
'backend': '/local/domain/0/backend/vbd/1/51712'} to
/local/domain/1/device/vbd/51712.
[2006-08-30 11:22:23 xend] DEBUG (DevController:112) DevController:
writing {'domain': 'xen-www', 'frontend':
'/local/domain/1/device/vbd/51712', 'dev': '/dev/xvda', 'state': '1',
'params': '/dev/raid/xen_www', 'mode': 'w', 'frontend-id': '1', 'type':
'file'} to /local/domain/0/backend/vbd/1/51712.
[2006-08-30 11:22:23 xend] DEBUG (DevController:110) DevController:
writing {'backend-id': '0', 'mac': '00:16:3e:11:48:67', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/1/0'} to
/local/domain/1/device/vif/0.
[2006-08-30 11:22:23 xend] DEBUG (DevController:112) DevController:
writing {'bridge': 'xenbr0', 'domain': 'xen-www', 'handle': '0',
'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend':
'/local/domain/1/device/vif/0', 'mac': '00:16:3e:11:48:67',
'frontend-id': '1'} to /local/domain/0/backend/vif/1/0.
[2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:701)
Storing VM details: {'uuid': '5b6415d8-f3a6-d64b-67c8-d8f7afb98e95',
'on_reboot': 'destroy', 'start_time': '1156900943.67', 'on_poweroff':
'destroy', 'name': 'xen-www', 'vcpus': '1', 'vcpu_avail': '1', 'memory':
'256', 'on_crash': 'destroy', 'image': "(linux (kernel
/var/lib/xen/vmlinuz.1WDQ9c) (ramdisk /var/lib/xen/initrd.img.jBbqHv)
(args ' root=/dev/xvd method=ftp://virtual/pub '))", 'maxmem': '256'}
[2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:736)
Storing domain details: {'console/ring-ref': '237071', 'console/port':
'2', 'name': 'xen-www', 'console/limit': '1048576', 'vm':
'/vm/5b6415d8-f3a6-d64b-67c8-d8f7afb98e95', 'domid': '1',
'cpu/0/availability': 'online', 'memory/target': '262144',
'store/ring-ref': '237072', 'store/port': '1'}
[2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:919)
XendDomainInfo.handleShutdownWatch
[2006-08-30 11:22:23 xend] DEBUG (DevController:143) Waiting for devices
vif.
[2006-08-30 11:22:23 xend] DEBUG (DevController:149) Waiting for 0.
[2006-08-30 11:22:23 xend] DEBUG (DevController:449)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2006-08-30 11:22:23 xend] DEBUG (DevController:449)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2006-08-30 11:22:23 xend] DEBUG (DevController:463)
hotplugStatusCallback 2.
[2006-08-30 11:22:23 xend] ERROR (SrvBase:87) Request wait_for_devices
failed.
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 85,
in perform
return op_method(op, req)
File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomain.py",
line 72, in op_wait_for_devices
return self.dom.waitForDevices()
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1511, in waitForDevices
self.waitForDevices_(c)
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1063, in waitForDevices_
return self.getDeviceController(deviceClass).waitForDevices()
File
"/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py",
line 145, in waitForDevices
return map(self.waitForDevice, self.deviceIDs())
File
"/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py",
line 161, in waitForDevice
raise VmError("Device %s (%s) could not be connected. "
VmError: Device 0 (vif) could not be connected. Backend device not found.
[2006-08-30 11:22:24 xend] INFO (XendDomain:365) Domain xen-www (1)
unpaused.
#### /var/log/messages ####
Aug 30 11:17:26 virtual kernel: Bridge firewalling registered
Aug 30 11:17:26 virtual kernel: device vif0.2 entered promiscuous mode
Aug 30 11:17:26 virtual NET[2453]: /sbin/dhclient-script : updated
/etc/resolv.conf
Aug 30 11:17:26 virtual kernel: audit(1156900646.201:3): dev=vif0.2
prom=256 old_prom=0 auid=4294967295
Aug 30 11:17:26 virtual kernel: xenbr2: port 1(vif0.2) entering learning
state
Aug 30 11:17:26 virtual dhclient: bound to 192.168.0.10 -- renewal in
43167 seconds.
Aug 30 11:17:26 virtual kernel: xenbr2: topology change detected,
propagating
Aug 30 11:17:26 virtual kernel: xenbr2: port 1(vif0.2) entering
forwarding state
Aug 30 11:17:26 virtual kernel: r8169: peth2: link up
Aug 30 11:17:26 virtual kernel: device peth2 entered promiscuous mode
Aug 30 11:17:26 virtual kernel: audit(1156900646.249:4): dev=peth2
prom=256 old_prom=0 auid=4294967295
Aug 30 11:17:26 virtual kernel: xenbr2: port 2(peth2) entering learning
state
Aug 30 11:17:26 virtual kernel: xenbr2: topology change detected,
propagating
Aug 30 11:17:26 virtual kernel: xenbr2: port 2(peth2) entering
forwarding state
Aug 30 11:20:37 virtual ntpd[2004]: synchronized to LOCAL(0), stratum 10
Aug 30 11:20:37 virtual ntpd[2004]: kernel time sync disabled 0041
Aug 30 11:21:40 virtual ntpd[2004]: kernel time sync enabled 0001
Aug 30 11:22:23 virtual logger: /etc/xen/scripts/vif-bridge: brctl addif
xenbr0 vif1.0 failed
Aug 30 11:22:46 virtual ntpd[2004]: synchronized to 192.231.203.132,
stratum 2
17 years, 7 months
Xen VT Notebooks
by MJang
Folks,
Hoping for advice on notebooks suited to Xen. If you've had success
enabling VT, what notebook model are you using?
I've asked on the Xen mailing list as well - am considering a new
notebook, and have heard that HP has disabled VT on all of their Dual
Core and AMD X2 TL-50 (and above) notebooks. I know, I know, avoid the
T2300E (and below), the Core 2 Duo T5500, and anything less than TL-50.
I gather from some messages that some notebooks allow end-users to
enable it via the BIOS, others (namely HP) do not.
Don't know if that's true, but HP pre-sales support says that they don't
have any documentation on the issue. So much for HP sales . . . Still
awaiting a reply from Dell.
Thanks,
Mike
17 years, 8 months
cdrom cannot be found in xen0
by Eric Benton
I'd compiled the sources of xen3 unstable and booted successfuly into
xen0, where xend is working and everything is ok.
The only problem is, I can't find my cdrom under /dev. I'm running FC5
and when not at xen0, my cdrom is at /dev/hdc
Is it something related to udev? or the initrd?
Thanks in advance,
Eric.
17 years, 8 months
PAE confusion using FC5 kernel-xen - is it PAE or not?
by Hilton Day
Hi,
I've been playing around with FC5 and Xen, using kernel-xen0 and
kernel-xenU for dom0 and domU's respectively..
Unfortunately I hit a snag in that I can't get pci pass-through for
ethernet cards to a xenU kernel as there's no support for ethernet card
drivers.. so I had a look at the new kernel-xen.
And I've hit a confusing snag, to do with PAE where I get conflicting
messages in xend-debug.log.
Two scenarios give different PAE messages:
Scenario 1:
dom0: kernel-xen-2.6.17-1.2174
domU: kernel-xen-2.6.17-1.2174
This gives the xend-debug.log messages:
ERROR: Non PAE-kernel on PAE host.
ERROR: Error constructing guest OS
Which I thought was odd, as they're the same kernel?
So I tried switching dom0 back to a non-PAE kernel build.. xen0
Scenario 2:
dom0: kernel-xen0-2.6.17-1.2174
domU: kernel-xen-2.6.17-1.2174
However, when I try to "xm create" the domU this gives me:
ERROR: PAE-kernel on non-PAE host.
ERROR: Error constructing guest OS
So my confusion is that I'm being told that kernel-xen is a PAE kernel
by the debug, *and* that its a non-PAE kernel by the debug. I'd have
thought that scenario 1 above would work.
I checked the files in kernel-xenU and kernel-xen with an "rpm -ql", and
can't see any conflicts in /boot - they have separate
filenames for config, initrd, system.map, vmlinuz kernel etc.
Anyone have any idea whats up here, and how I can get kernel-xen to boot
on the DomU so I can get the pass-through working? (I want to set up one
of the domU's as a gateway/proxy/firewall for the others) I can't use
FC6 currently - it has no support for combined software RAID5/LVM2
setups which is what I'm running for dom0.
My grub.conf on the domU is:
#boot=/dev/xvda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.17-1.2174_FC5xen)
root (hd0,0)
kernel /vmlinuz-2.6.17-1.2174_FC5xen ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.17-1.2174_FC5xen.img
title Fedora Core (2.6.17-1.2174_FC5xenU)
root (hd0,0)
kernel /vmlinuz-2.6.17-1.2174_FC5xenU ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.17-1.2174_FC5xenU.img
title Fedora Core (2.6.15-1.2054_FC5xenU)
root (hd0,0)
kernel /vmlinuz-2.6.15-1.2054_FC5xenU ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.15-1.2054_FC5xenU.img
17 years, 8 months
