Domain blocked
by Roger Grosswiler
Hei,
got xen installed, client runs, but xm top often show state blocked. Why
is this? What does this mean?
gollum --b---
Thanks,
Roger
17 years, 8 months
Fedora-xen-ia64 test status
by Akio Takebe
Hi, Aron, Juan, all
We could not boot dom0 with kernel-xen-2.6.17-1.2488.fc6 on Tiger4.
So I and Kouya debuged it, and found kernel text area is cleared.
Isuku make a patch which resolve the issue.
And I tested booting dom0 with Isuku's patch.
So My test results is below.
I used the below as dom0 kernel
http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora
＋kernel-2.6.17-ia64-xen.config＋rsvd_region.patch
And I used the latest xen-ia64-unstable.hg and xen-unstable.
With the dom0 and the xen, I can boot dom0.
Then I research the recently cset, I found the following mismatch.
http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora have vDSO linux-2.6-
saparse changes, but Hypervisor don't have the changes.
changeset: 10703:8d501f39286c
user: awilliam(a)xenbuild.aw
date: Mon Jul 24 13:43:35 2006 -0600
summary: [IA64] vDSO paravirtualization: paravirtualize vDSO
changeset: 10702:614deef19299
user: awilliam(a)xenbuild.aw
date: Mon Jul 24 13:04:40 2006 -0600
summary: [IA64] vDSO paravirtualization: import linux files
I think we need to update Hypervisor.
Is this possible?
Best Regards,
Akio Takebe
17 years, 8 months
CUPS crashes Xen kernel
by J.L. Coenders
Hi,
Has anyone tried printing with CUPS on the fc5 Xen kernel
(2.6.17-1.2157_FC5xen0)?
I was trying out Xen and it seems to crash my system.
Regards,
Jeroen
17 years, 8 months
First VM error: No such domain vmguest1
by Peter Guthrie
Can anyone help with the following error I get when trying to create my
first VM.
Xen0 host is FC5 x86_64 on a dual cpu, dual core opteron 275 with 4Gb of
memory up to date with patches.
# uname -a
Linux dhcp-201.local.net 2.6.17-1.2157_FC5xen0 #1 SMP Tue Jul 11
23:30:05 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
# xenguest-install.py
What is the name of your virtual machine? vmguest1
How much RAM should be allocated (in megabytes)? 512
What would you like to use as the disk (path)? /var/tmp/vmguest1-disk
How large would you like the disk to be (in gigabytes)? 8
What is the install location?
http://zeniiia.linux.org.uk/pub/distributions/fedora/linux/core/5/i386/os/
Starting install...
libvir: Xen Daemon error : POST operation failed: No such domain vmguest1
Failed to get devices for domain vmguest1
Traceback (most recent call last):
File "/usr/sbin/xenguest-install.py", line 460, in ?
main()
File "/usr/sbin/xenguest-install.py", line 451, in main
start_paravirt_install(name, ram, disk, mac, uuid, src, options.extra)
File "/usr/sbin/xenguest-install.py", line 331, in start_paravirt_install
dom = conn.createLinux(cfgxml, 0)
File "/usr/lib64/python2.4/site-packages/libvirt.py", line 233, in
createLinux if ret is None:raise libvirtError('virDomainCreateLinux()
failed')
libvirt.libvirtError: virDomainCreateLinux() failed
Here's the output from 'xm log':
[2006-08-10 16:47:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:1216)
XendDomainInfo.construct: None
[2006-08-10 16:47:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:1248)
XendDomainInfo.initDomain: 1 1.0
[2006-08-10 16:47:50 xend] DEBUG (balloon:134) Balloon: free 128; need
513; retries: 10.
[2006-08-10 16:47:50 xend] DEBUG (balloon:143) Balloon: setting dom0
target to 3393.
[2006-08-10 16:47:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:987)
Setting memory target of domain Domain-0 (0) to 3393 MiB.
[2006-08-10 16:47:50 xend] DEBUG (balloon:128) Balloon: free 513; need
513; done.
[2006-08-10 16:47:50 xend] INFO (image:134) buildDomain os=linux dom=1
vcpus=1
[2006-08-10 16:47:50 xend] DEBUG (image:177) dom = 1
[2006-08-10 16:47:50 xend] DEBUG (image:178) image =
/var/lib/xen/vmlinuz.i0GIQN
[2006-08-10 16:47:50 xend] DEBUG (image:179) store_evtchn = 1
[2006-08-10 16:47:50 xend] DEBUG (image:180) console_evtchn = 2
[2006-08-10 16:47:50 xend] DEBUG (image:181) cmdline =
root=/dev/xvd
method=http://zeniiia.linux.org.uk/pub/distributions/fedora/linux/core/5/i386/os/
[2006-08-10 16:47:50 xend] DEBUG (image:182) ramdisk =
/var/lib/xen/initrd.img.4rNZB1
[2006-08-10 16:47:50 xend] DEBUG (image:183) vcpus = 1
[2006-08-10 16:47:50 xend] DEBUG (image:184) features =
[2006-08-10 16:47:50 xend.XendDomainInfo] ERROR (XendDomainInfo:197)
Domain construction failed
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 190, in create
vm.initDomain()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1311, in initDomain
raise VmError(str(exn))
VmError: (9, \047Bad file descriptor\047)
[2006-08-10 16:47:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:1397)
XendDomainInfo.destroy: domid=1
[2006-08-10 16:47:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:1405)
XendDomainInfo.destroyDomain(1)
[2006-08-10 16:47:50 xend] ERROR (SrvBase:87) Request create failed.
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/web/SrvBase.py", line 85,
in perform
return op_method(op, req)
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomainDir.py",
line 82, in op_create
raise XendError("Error creating domain: " + str(ex))
XendError: Error creating domain: (9, \047Bad file descriptor\047)
Looks like some sort of path error creating one of the files.
Peter
17 years, 8 months
FC5 problem with vif, udev and HAL
by Tomáš Kouba
Hello,
I have a problem with domU starting. I use
vif=['']
configuration option for setting network.
When the domain starts it hangs for a while and then
ends with an error:
[root@fik ~]# xm create -c vmid=1
Using config file "/etc/xen/xmdefconfig".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
I have googled some pieces of advice but nothing applies for me
(I have enough loop devices, I cannot install hotplug package since it is
no longer used in FC5).
Does anybody have a hint what can be wrong?
Some (hopefully) useful logs:
xend.log:
[2006-08-11 10:28:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:185)
XendDomainInfo.create(['vm', ['name', 'ce'], ['memory', 256], ['vcpus',
1], ['image', ['linux', ['kernel',
'/boot/vmlinuz-2.6.17-1.2157_FC5xen'], ['ip',
'192.168.1.101/24:1.2.3.4:192.168.1.128::ce:eth0:dhcp'], ['root',
'/dev/sda1'], ['args', 'fastboot ro']]], ['device', ['vbd', ['uname',
'phy:vgpool/ce'], ['dev', 'sda1'], ['mode', 'w']]], ['device', ['vbd',
['uname', 'phy:vgpool/ceswap'], ['dev', 'sda2'], ['mode', 'w']]],
['device', ['vif', ['ip', '10.0.9.1/16'], ['mac', '00:16:3E:47:A1:09'],
['vifname', 'cevif']]]])
[2006-08-11 10:28:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:291)
parseConfig: config is ['vm', ['name', 'ce'], ['memory', 256], ['vcpus',
1], ['image', ['linux', ['kernel',
'/boot/vmlinuz-2.6.17-1.2157_FC5xen'], ['ip',
'192.168.1.101/24:1.2.3.4:192.168.1.128::ce:eth0:dhcp'], ['root',
'/dev/sda1'], ['args', 'fastboot ro']]], ['device', ['vbd', ['uname',
'phy:vgpool/ce'], ['dev', 'sda1'], ['mode', 'w']]], ['device', ['vbd',
['uname', 'phy:vgpool/ceswap'], ['dev', 'sda2'], ['mode', 'w']]],
['device', ['vif', ['ip', '10.0.9.1/16'], ['mac', '00:16:3E:47:A1:09'],
['vifname', 'cevif']]]]
[2006-08-11 10:28:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:390)
parseConfig: result is {'uuid': None, 'on_crash': None, 'on_reboot':
None, 'image': ['linux', ['kernel',
'/boot/vmlinuz-2.6.17-1.2157_FC5xen'], ['ip',
'192.168.1.101/24:1.2.3.4:192.168.1.128::ce:eth0:dhcp'], ['root',
'/dev/sda1'], ['args', 'fastboot ro']], 'on_poweroff': None,
'bootloader_args': None, 'cpus': None, 'name': 'ce', 'backend': [],
'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None,
'memory': 256, 'device': [('vbd', ['vbd', ['uname', 'phy:vgpool/ce'],
['dev', 'sda1'], ['mode', 'w']]), ('vbd', ['vbd', ['uname',
'phy:vgpool/ceswap'], ['dev', 'sda2'], ['mode', 'w']]), ('vif', ['vif',
['ip', '10.0.9.1/16'], ['mac', '00:16:3E:47:A1:09'], ['vifname',
'cevif']])], 'bootloader': None, 'cpu': None, 'maxmem': None}
[2006-08-11 10:28:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:1216)
XendDomainInfo.construct: None
[2006-08-11 10:28:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:1248)
XendDomainInfo.initDomain: 2 1.0
[2006-08-11 10:28:50 xend] DEBUG (balloon:128) Balloon: free 261; need
261; done.
[2006-08-11 10:28:50 xend] INFO (image:134) buildDomain os=linux dom=2
vcpus=1
[2006-08-11 10:28:50 xend] DEBUG (image:177) dom = 2
[2006-08-11 10:28:50 xend] DEBUG (image:178) image =
/boot/vmlinuz-2.6.17-1.2157_FC5xen
[2006-08-11 10:28:50 xend] DEBUG (image:179) store_evtchn = 1
[2006-08-11 10:28:50 xend] DEBUG (image:180) console_evtchn = 2
[2006-08-11 10:28:50 xend] DEBUG (image:181) cmdline =
ip=192.168.1.101/24:1.2.3.4:192.168.1.128::ce:eth0:dhcp root=/dev/sda1
fastboot ro
[2006-08-11 10:28:50 xend] DEBUG (image:182) ramdisk =
[2006-08-11 10:28:50 xend] DEBUG (image:183) vcpus = 1
[2006-08-11 10:28:50 xend] DEBUG (image:184) features =
[2006-08-11 10:28:50 xend] DEBUG (blkif:24) exception looking up device
number for sda1: [Errno 2] No such file or directory: '/dev/sda1'
[2006-08-11 10:28:50 xend] DEBUG (DevController:110) DevController:
writing {'virtual-device': '2049', 'backend-id': '0', 'state': '1',
'backend': '/local/domain/0/backend/vbd/2/2049'} to
/local/domain/2/device/vbd/2049.
[2006-08-11 10:28:50 xend] DEBUG (DevController:112) DevController:
writing {'domain': 'ce', 'frontend': '/local/domain/2/device/vbd/2049',
'dev': 'sda1', 'state': '1', 'params': 'vgpool/ce', 'mode': 'w',
'frontend-id': '2', 'type': 'phy'} to /local/domain/0/backend/vbd/2/2049.
[2006-08-11 10:28:50 xend] DEBUG (blkif:24) exception looking up device
number for sda2: [Errno 2] No such file or directory: '/dev/sda2'
[2006-08-11 10:28:50 xend] DEBUG (DevController:110) DevController:
writing {'virtual-device': '2050', 'backend-id': '0', 'state': '1',
'backend': '/local/domain/0/backend/vbd/2/2050'} to
/local/domain/2/device/vbd/2050.
[2006-08-11 10:28:50 xend] DEBUG (DevController:112) DevController:
writing {'domain': 'ce', 'frontend': '/local/domain/2/device/vbd/2050',
'dev': 'sda2', 'state': '1', 'params': 'vgpool/ceswap', 'mode': 'w',
'frontend-id': '2', 'type': 'phy'} to /local/domain/0/backend/vbd/2/2050.
[2006-08-11 10:28:50 xend] DEBUG (DevController:110) DevController:
writing {'backend-id': '0', 'mac': '00:16:3E:47:A1:09', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/2/0'} to
/local/domain/2/device/vif/0.
[2006-08-11 10:28:50 xend] DEBUG (DevController:112) DevController:
writing {'domain': 'ce', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'ip': '10.0.9.1/16', 'state': '1',
'frontend': '/local/domain/2/device/vif/0', 'mac': '00:16:3E:47:A1:09',
'vifname': 'cevif', 'frontend-id': '2'} to /local/domain/0/backend/vif/2/0.
[2006-08-11 10:28:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:701)
Storing VM details: {'uuid': '082c2415-8bfc-e14e-22f0-29c452b9be24',
'on_reboot': 'restart', 'start_time': '1155284930.3', 'on_poweroff':
'destroy', 'name': 'ce', 'vcpus': '1', 'vcpu_avail': '1', 'memory':
'256', 'on_crash': 'restart', 'image': "(linux (kernel
/boot/vmlinuz-2.6.17-1.2157_FC5xen) (ip
192.168.1.101/24:1.2.3.4:192.168.1.128::ce:eth0:dhcp) (root /dev/sda1)
(args 'fastboot ro'))", 'maxmem': '256'}
[2006-08-11 10:28:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:736)
Storing domain details: {'console/ring-ref': '69352', 'console/port':
'2', 'name': 'ce', 'console/limit': '1048576', 'vm':
'/vm/082c2415-8bfc-e14e-22f0-29c452b9be24', 'domid': '2',
'cpu/0/availability': 'online', 'memory/target': '262144',
'store/ring-ref': '69353', 'store/port': '1'}
[2006-08-11 10:28:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:919)
XendDomainInfo.handleShutdownWatch
[2006-08-11 10:28:50 xend] DEBUG (DevController:143) Waiting for devices
vif.
[2006-08-11 10:28:50 xend] DEBUG (DevController:149) Waiting for 0.
[2006-08-11 10:28:50 xend] DEBUG (DevController:449)
hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2006-08-11 10:29:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:1397)
XendDomainInfo.destroy: domid=2
[2006-08-11 10:29:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:1405)
XendDomainInfo.destroyDomain(2)
/var/log/messages (with udev logging set to info):
Aug 11 10:28:50 fik udevd[477]: udev_event_run: seq 783 forked, pid
[4566], 'add' 'xen-backend', 0 seconds old
Aug 11 10:28:50 fik udevd-event[4566]: wait_for_sysfs: file
'/sys/devices/xen-backend/vbd-2-2049/bus' appeared after 0 loops
Aug 11 10:28:50 fik udevd-event[4566]: pass_env_to_socket: passed -1
bytes to socket '/org/kernel/udev/monitor',
Aug 11 10:28:50 fik udevd-event[4566]: run_program:
'/lib/udev/udev_run_hotplugd'
Aug 11 10:28:50 fik udevd-event[4566]: run_program:
'/lib/udev/udev_run_hotplugd' returned with status 0
Aug 11 10:28:50 fik udevd-event[4566]: run_program:
'/lib/udev/udev_run_devd'
Aug 11 10:28:50 fik udevd-event[4566]: run_program:
'/lib/udev/udev_run_devd' returned with status 0
Aug 11 10:28:50 fik udevd-event[4566]: pass_env_to_socket: passed 240
bytes to socket '/org/freedesktop/hal/udev_event',
Aug 11 10:28:50 fik udevd-event[4566]: run_program:
'/etc/xen/scripts/block add'
Aug 11 10:28:50 fik udevd[477]: udev_event_run: seq 784 forked, pid
[4570], 'add' 'xen-backend', 0 seconds old
Aug 11 10:28:50 fik udevd-event[4570]: wait_for_sysfs: file
'/sys/devices/xen-backend/vbd-2-2050/bus' appeared after 0 loops
Aug 11 10:28:50 fik udevd-event[4570]: pass_env_to_socket: passed -1
bytes to socket '/org/kernel/udev/monitor',
Aug 11 10:28:50 fik udevd-event[4570]: run_program:
'/lib/udev/udev_run_hotplugd'
Aug 11 10:28:50 fik udevd-event[4570]: run_program:
'/lib/udev/udev_run_hotplugd' returned with status 0
Aug 11 10:28:50 fik udevd-event[4570]: run_program:
'/lib/udev/udev_run_devd'
Aug 11 10:28:50 fik udevd-event[4570]: run_program:
'/lib/udev/udev_run_devd' returned with status 0
Aug 11 10:28:50 fik udevd-event[4570]: pass_env_to_socket: passed 240
bytes to socket '/org/freedesktop/hal/udev_event',
Aug 11 10:28:50 fik udevd[477]: udev_event_run: seq 785 forked, pid
[4578], 'add' 'xen-backend', 0 seconds old
Aug 11 10:28:50 fik udevd-event[4578]: wait_for_sysfs: file
'/sys/devices/xen-backend/vif-2-0/bus' appeared after 0 loops
Aug 11 10:28:50 fik udevd-event[4578]: pass_env_to_socket: passed -1
bytes to socket '/org/kernel/udev/monitor',
Aug 11 10:28:50 fik udevd-event[4578]: run_program:
'/lib/udev/udev_run_hotplugd'
Aug 11 10:28:50 fik udevd-event[4578]: run_program:
'/lib/udev/udev_run_hotplugd' returned with status 0
Aug 11 10:28:50 fik udevd-event[4578]: run_program:
'/lib/udev/udev_run_devd'
Aug 11 10:28:50 fik udevd-event[4570]: run_program:
'/etc/xen/scripts/block add'
Aug 11 10:28:50 fik udevd-event[4578]: run_program:
'/lib/udev/udev_run_devd' returned with status 0
Aug 11 10:28:50 fik udevd-event[4578]: pass_env_to_socket: passed 231
bytes to socket '/org/freedesktop/hal/udev_event',
Aug 11 10:28:50 fik udevd-event[4578]: udev_event_run: seq 785 finished
Aug 11 10:28:50 fik udevd[477]: udev_done: seq 785, pid [4578] exit with
0, 0 seconds old
Aug 11 10:28:50 fik udevd-event[4566]: run_program:
'/etc/xen/scripts/block' returned with status 0
Aug 11 10:28:50 fik udevd-event[4566]: udev_event_run: seq 783 finished
Aug 11 10:28:50 fik udevd[477]: udev_done: seq 783, pid [4566] exit with
0, 0 seconds old
Aug 11 10:28:51 fik udevd-event[4570]: run_program:
'/etc/xen/scripts/block' returned with status 0
Aug 11 10:28:51 fik udevd-event[4570]: udev_event_run: seq 784 finished
Aug 11 10:28:51 fik udevd[477]: udev_done: seq 784, pid [4570] exit with
0, 1 seconds old
both xend-debug.log and xen-hotplug.log are empty :(
--
Tomas Kouba
17 years, 8 months
[BUG] dmidecode in DomU throws thousands of xen printk's
by Matt C
Hi All
One more bug... in a seperate email so they don't get confused.
System is kernel-xen-2.6.17-1.2157_FC5 on a 2p opteron (older
non-hardware-virt). This happens when I try to run the 'dmidecode' tool
from within a non-privileged guest. The guest is running the same kernel
as above. One other note is that the console on this system is serial,
ttyS0 at 9600bps... which may have something to do with the CPU lockup
bugs below.
I basically get thousands of the following printk messages, starting with:
(XEN) DOM4: (file=mm.c, line=578) Non-privileged attempt to map I/O space
000000f0
and counting up and ending with:
(XEN) DOM4: (file=mm.c, line=578) Non-privileged attempt to map I/O space
000000ff
Then, some of the time, the kernel throws a spinlock timer at the end of
all of these printks:
Timer ISR/1: Time went backwards: delta=-46186990 delta_cpu=-42186990
shadow=2112479126776 off=466807746 processed=2112992120678
cpu_processed=2112988120678
BUG: spinlock lockup on CPU#0, swapper/0, c06e9284 (Not tainted)
<c04e74b0> __spin_lock_debug+0x7b/0x85 <c04e7514>
_raw_spin_lock+0x5a/0x69
<c061eedb> _spin_lock+0x6/0x8 <c0407d80> timer_interrupt+0x40/0x563
<c0434533> ktime_get_ts+0x4b/0x51 <c0434484> ktime_get+0x10/0x3a
<c0442fe3> handle_IRQ_event+0x40/0x82 <c04430b0> __do_IRQ+0x8b/0xdf
<c0406336> do_IRQ+0x1a/0x25 <c054c937> evtchn_do_upcall+0x84/0xb8
<c0404c71> hypervisor_callback+0x3d/0x48 <c04087da> safe_halt+0x1a/0x2f
<c0402b98> kernel_thread_helper+0x0/0xb <c04028a9> xen_idle+0x45/0x4d
<c0402945> cpu_idle+0x94/0xad <c07047cf> start_kernel+0x1c1/0x1c5
0: 2112992120678
1: 2112988120678
BUG: soft lockup detected on CPU#1!
<c0442e2d> softlockup_tick+0x9a/0xab <c040825d>
timer_interrupt+0x51d/0x563
<c0442fe3> handle_IRQ_event+0x40/0x82 <c04430b0> __do_IRQ+0x8b/0xdf
<c0406336> do_IRQ+0x1a/0x25 <c054c937> evtchn_do_upcall+0x84/0xb8
<c0404c71> hypervisor_callback+0x3d/0x48 <c054c8b1>
force_evtchn_callback+0xa/0xc
<c04248cf> __do_softirq+0x67/0xee <c0424995> do_softirq+0x3f/0x63
<c040633b> do_IRQ+0x1f/0x25 <c054c937> evtchn_do_upcall+0x84/0xb8
<c0404c71> hypervisor_callback+0x3d/0x48 <c04087da> safe_halt+0x1a/0x2f
<c04028a9> xen_idle+0x45/0x4d <c0402945> cpu_idle+0x94/0xad
BUG: soft lockup detected on CPU#0!
<c0442e2d> softlockup_tick+0x9a/0xab <c040825d>
timer_interrupt+0x51d/0x563
<c0434533> ktime_get_ts+0x4b/0x51 <c0442fe3> handle_IRQ_event+0x40/0x82
<c04430b0> __do_IRQ+0x8b/0xdf <c0406336> do_IRQ+0x1a/0x25
<c054c937> evtchn_do_upcall+0x84/0xb8 <c0404c71>
hypervisor_callback+0x3d/0x48
<c04087da> safe_halt+0x1a/0x2f <c0402b98> kernel_thread_helper+0x0/0xb
<c04028a9> xen_idle+0x45/0x4d <c0402945> cpu_idle+0x94/0xad
<c07047cf> start_kernel+0x1c1/0x1c5
Once, I even had the storage controller (3ware 9500) barf on me due to an
I/O timeout that it couldn't recover from. I didn't have my console
capture setup for that one, unfortunately.
I assume that this is the smbios hardware address space that dmidecode is
trying to access via the guest kernel. I'm also guessing that the printk
has interrupts disabled or something similarly funky, so the flood of them
causes the CPU lockup messages as well as probably the I/O problems.
I saw some patches on the xen-devel list about adding real smbios data to
the HVM virtual hosts, but it seemed to be very HVM-specific code, and I'm
running paravirts. The thread from that is here:
http://lists.xensource.com/archives/html/xen-devel/2006-07/msg00416.html
I'd be happy if dmidecode just returned nothing but the console didn't
spew messages like this. As you can imagine, the whole system (all virts)
is unuseable while this is happening, and it runs for minutes at a time.
Thanks again
-Matt
17 years, 8 months
How to boot in a non-existing guest via cdrom
by Roger Grosswiler
Hello,
I would like to try to install FreeBSD on to a guest on FC5-Dom0.
Therefore, i would need some help.
1) I think i need to create an image using dd?
2) How can i then tell this image (which still is quite empty) to boot
from cd-rom?
Anybody tried this already? How do i have to do this the easiest way?
Thanks,
Roger
17 years, 8 months
Fedora, xen and Windoze
by Christian Schuermann
Hi all!
Has actually somebody managed to run Windows as domU? I'm asking because
setup dies here just after "Setup is starting Windows 2000/XP". I've
also tested FC6test2 but it doesn't even boot there.
Regards, Chris
17 years, 8 months
domU network problems
by Karl J South
Hi,
I have three xen installations, two servers and one laptop. The laptop
install was done about half a year ago but the server installs are new. The
laptop install is working flawlessly but the two servers have the same domU
network problems. I have been pulling my hair for a while now but got stuck,
so I'm turning to you for help.
All installations has been done with help from the FedoraXenQuickstartFC5
howto. Both servers are fresh minimum installs of Fedora Core 5, updated via
yum and they use the latest xen0 kernel - 2.6.17-1.2157_FC5xen0. When trying
to install a domU client with xenguest-install.py or try to startup an
existing domU image I get no network connection.
xm create -c fedora2.cfg
Using config file "/etc/xen/fedora2.cfg".
Going to boot Fedora Core (2.6.17-1.2157_FC5xenU)
kernel: /vmlinuz-2.6.17-1.2157_FC5xenU
initrd: /initrd-2.6.17-1.2157_FC5xenU.img
Error: Device 0 (vif) could not be connected. Backend device not found.
When running xenguest-install.py I get to the point where I configure the
network and get stuck there.
On my laptop ifconfig shows me the interfaces, eth0, lo, peth0, vif0.0 and
xenbr0. On the servers the peth0, vif0.0 and xenbr0 interfaces doesn't
exist.
The domain0 logs tells me:
cat messages |grep xen
Aug 10 11:58:34 XD0-01 logger: /etc/xen/scripts/vif-bridge: Could not find
bridge, and none was specified
Aug 10 12:09:27 XD0-01 kernel: Linux version 2.6.17-1.2157_FC5xen0 (
brewbuilder(a)ls20-bc2-14.build.redhat.com) (gcc version 4.1.1 20060525 (Red
Hat 4.1.1-1)) #1 SMP Wed Jul 12 00:28:36 EDT 2006
Aug 10 12:09:27 XD0-01 kernel: xen_mem: Initialising balloon driver.
Aug 10 12:09:27 XD0-01 kernel: IA-32 Microcode Update Driver: v1.14-xen <
tigran(a)veritas.com>
Aug 10 12:09:33 XD0-01 xenstored: Checking store ...
Aug 10 12:09:33 XD0-01 xenstored: Checking store complete.
Aug 10 12:09:33 XD0-01 xenstored: Checking store ...
Aug 10 12:09:33 XD0-01 xenstored: Checking store complete.
Aug 10 12:23:05 XD0-01 logger: /etc/xen/scripts/vif-bridge: Could not find
bridge, and none was specified
cat xend-debug.log
Link veth0
1 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.
cat xend.log
<snip>
[2006-08-10 12:23:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:919)
XendDomainInfo.handleShutdownWatch
[2006-08-10 12:23:05 xend] DEBUG (DevController:143) Waiting for devices
vif.
[2006-08-10 12:23:05 xend] DEBUG (DevController:149) Waiting for 0.
[2006-08-10 12:23:05 xend] DEBUG (DevController:449) hotplugStatusCallback
/local/domain/0/backend/vif/1/0/hotplug-status.
[2006-08-10 12:23:05 xend] DEBUG (DevController:449) hotplugStatusCallback
/local/domain/0/backend/vif/1/0/hotplug-status.
[2006-08-10 12:23:05 xend] DEBUG (DevController:463) hotplugStatusCallback
2.
[2006-08-10 12:23:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:1397)
XendDomainInfo.destroy: domid=1
[2006-08-10 12:23:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:1405)
XendDomainInfo.destroyDomain(1)
Does anyone of you have any ideas on how to get the network working?
All help is appreciated,
Thanks in advance,
/KJS
17 years, 8 months
