Domain 0 reboot when network flow is heavy
by Xin Chen
Hi All,
I am not sure about this, just wondering anyone has the similar
situation with me::
I was using scp command on a remote server, copying a 20G file into
Domain 0 server.
the speed displayed is around 8Mb/s
waiting...
waiting...
at 67%, it stopped, why? because Domain 0 reboot.....
I check the log, nothing useful. I guess it is because the network flowing,
because the domain 0 has been running for 3 weeks until today I do the
copying.
I attached some info, please give me some advice, thanks a lot!!
xin
[root@XenServer xen]# uname -a
Linux XenServer 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 15:11:19 EDT 2006
i686 i686 i386 GNU/Linux
[root@XenServer xen]# xm info
host : XenServer
release : 2.6.18-1.2798.fc6xen
version : #1 SMP Mon Oct 16 15:11:19 EDT 2006
machine : i686
nr_cpus : 4
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 1600
hw_caps :
bfebfbff:20100000:00000000:00000140:0004e33d:00000000:00000001
total_memory : 4094
free_memory : 0
xen_major : 3
xen_minor : 0
xen_extra : .3-rc3-1.2798.f
xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
xen_pagesize : 4096
platform_params : virt_start=0xf5800000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)
cc_compile_by : brewbuilder
cc_compile_domain : build.redhat.com
cc_compile_date : Mon Oct 16 14:34:31 EDT 2006
xend_config_format : 2
/var/log/xend.log
[2007-06-24 01:08:55 xend 3125] DEBUG (DevController:149) Waiting for 51712.
[2007-06-24 01:08:55 xend 3125] DEBUG (DevController:472)
hotplugStatusCallback
/local/domain/0/backend/tap/6/51712/hotplug-status.
[2007-06-24 01:08:55 xend 3125] DEBUG (DevController:486)
hotplugStatusCallback
1.
[2007-06-24 01:08:55 xend 3125] DEBUG (DevController:143) Waiting for
devices vt
pm.
[2007-06-24 01:08:55 xend 3125] INFO (XendDomain:370) Domain stimpy (6)
unpaused
.
*[2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:283) Xend Daemon
started -> here is the place reboot.*
[2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:287) Xend changeset:
unavailable
.
[2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG
(XendDomainInfo:212) XendDo
mainInfo.recreate({'paused': 0, 'cpu_time': 29578464995L, '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': 4012156, 'maxmem_kb': -4, 'max_vcpu_id': 3,
'crashed':
0, 'running': 1, 'shutdown': 0, 'online_vcpus': 4, 'blocked': 0})
[2007-06-26 17:18:55 xend.XendDomainInfo 3154] INFO (XendDomainInfo:224)
Recreat
ing domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2007-06-26 17:18:55 xend.XendDomainInfo 3154] WARNING
(XendDomainInfo:246) No v
m path in store for existing domain 0
[2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG
(XendDomainInfo:715) Storin
g VM details: {'shadow_memory': '0', 'uuid':
'00000000-0000-0000-0000-0000000000
00', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name':
'Domain-0', 'xend
/restart_count': '0', 'vcpus': '4', 'vcpu_avail': '15', 'memory':
'3919', 'on_cr
ash': 'restart', 'maxmem': '3919'}
[2007-06-26 17:18:56 xend.XendDomainInfo 3154] DEBUG
(XendDomainInfo:750) Storin
g domain details: {'cpu/1/availability': 'online', 'cpu/3/availability':
'online
', 'name': 'Domain-0', 'console/limit': '1048576', 'cpu/2/availability':
'online
', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
'cpu/0/availa
bility': 'online', 'memory/target': '4013056'}
[2007-06-26 17:18:56 xend 3154] DEBUG (XendDomain:153) number of vcpus
to use is
0
[2007-06-26 17:18:56 xend 3154] INFO (SrvServer:116) unix
path=/var/lib/xend/xen
d-socket
/var/log/message:
Jun 26 17:14:58 XenServer kernel: peth1: received packet with own
address as so
urce address
Jun 26 17:15:57 XenServer last message repeated 2 times
Jun 26 17:15:57 XenServer kernel: peth0: received packet with own
address as so
urce address
Jun 26 17:16:01 XenServer kernel: peth1: received packet with own
address as so
urce address
Jun 26 17:17:00 XenServer kernel: peth1: received packet with own
address as so
urce address
*Jun 26 17:18:38 XenServer syslogd 1.4.1: restart. --> here is the place
reboot*
Jun 26 17:18:38 XenServer kernel: klogd 1.4.1, log source = /proc/kmsg
started.
Jun 26 17:18:38 XenServer kernel: Linux version 2.6.18-1.2798.fc6xen
(brewbuilde
r(a)hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat
4.1.1-30)) #
1 SMP Mon Oct 16 15:11:19 EDT 2006
Jun 26 17:18:38 XenServer kernel: BIOS-provided physical RAM map:
Jun 26 17:18:38 XenServer kernel: Xen: 0000000000000000 -
00000000f575f000 (usa
ble)
Jun 26 17:18:38 XenServer kernel: 3199MB HIGHMEM available.
Jun 26 17:18:38 XenServer kernel: 727MB LOWMEM available.
Jun 26 17:18:38 XenServer kernel: NX (Execute Disable) protection: active
Jun 26 17:18:38 XenServer kernel: found SMP MP-table at 000f5f20
Jun 26 17:18:38 XenServer kernel: DMI present.
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x00]
lapic_id[0x00] enab
led)
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x01]
lapic_id[0x01] enab
led)
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x02]
lapic_id[0x02] enab
led)
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x03]
lapic_id[0x03] enab
led)
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high
edge lint[
0x1])
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high
edge lint[
0x1])
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high
edge lint[
0x1])
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high
edge lint[
0x1])
Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x04]
address[0xfec00000] gsi
_base[0])
Jun 26 17:18:38 XenServer kernel: IOAPIC[0]: apic_id 4, version 32,
address 0xfe
c00000, GSI 0-23
Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x05]
address[0xfec80000] gsi
_base[24])
attach the network details of domain 0:
[root@XenServer ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:30:48:32:4F:94
inet addr:192.168.200.120 Bcast:192.168.200.255
Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe32:4f94/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2286450 errors:0 dropped:0 overruns:0 frame:0
TX packets:1118771 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3457059468 (3.2 GiB) TX bytes:74013507 (70.5 MiB)
eth1 Link encap:Ethernet HWaddr 00:30:48:32:4F:95
inet addr:192.168.200.121 Bcast:192.168.200.255
Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe32:4f95/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4211 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:410017 (400.4 KiB) TX bytes:8485 (8.2 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:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1008 (1008.0 b) TX bytes:1008 (1008.0 b)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:2282062 errors:0 dropped:0 overruns:0 frame:0
TX packets:1116125 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3458070625 (3.2 GiB) TX bytes:78308773 (74.6 MiB)
Base address:0x2000 Memory:d8400000-d8420000
peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:7627 errors:0 dropped:0 overruns:0 frame:0
TX packets:4103 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:893944 (872.9 KiB) TX bytes:523855 (511.5 KiB)
Base address:0x2020 Memory:d8420000-d8440000
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1118785 errors:0 dropped:0 overruns:0 frame:0
TX packets:2286472 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:74014879 (70.5 MiB) TX bytes:3457092776 (3.2 GiB)
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:39 errors:0 dropped:0 overruns:0 frame:0
TX packets:4211 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8485 (8.2 KiB) TX bytes:410017 (400.4 KiB)
vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:4100 errors:0 dropped:0 overruns:0 frame:0
TX packets:5265 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:440557 (430.2 KiB) TX bytes:652881 (637.5 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:472 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:59881 (58.4 KiB) TX bytes:0 (0.0 b)
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1348 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:96255 (93.9 KiB) TX bytes:0 (0.0 b)
16 years, 10 months
32bit guests on 64bit FC7
by thewird
FC7 64bit doesn't work with 32bit guests yet even
though it was supposed to. Does anyone know when a yum
update will be possible to make it work? I'm currently
building a machine with 32GB of ram and need to run
32bit guests. I have about 4-5 weeks before the server
needs to go live so will it be updated by then? Thanks.
16 years, 10 months
FC6 guest save/restore: serious clock drift...
by Mike Carney
Hi folks,
I had a FC6 guest which was doing a kernel build while running on a F7
system. Due to a power outage and waning UPS battery capacity, I saved
the FC6 image. Once power was restored a few hours later, I restored the
FC6 guest, and observed it picked up in its build right were it left
off. Cool, I thought - until the build crashed because the FC6 guest's
clock was almost 24 hours in the past when compared to the correct time
on the F7 system it was hosted on.
Has anyone else observed this guest clock drift behavior with save/restore?
TIA,
Mike
16 years, 10 months
FWIW: Howto for building F7 and FC6 xen kernels + xen w/o PAE ...
by Mike Carney
Hi All,
I've successfully built the F7 source RPMS for the xen kernel + xen 3.1
w/o PAE, and it works ok on my PAE-capable dual Xeon w/ 1GB ram. I'm
able to run the following non-pae guests: freeBSD, NetBSD, as well as my
non-PAE F6 and F7 Guests of course.
I followed the wiki instructions here:
http://fedoraproject.org/wiki/Docs/CustomKernel
With the following modifications:
F7:
Using kernel-xen-2.6-2.6.20-2925.11.fc7.src.rpm:
a) with menuconfig, in "processor type and features", "High Memory
Support", I selected "off" (I only have 1GB of memory. Selecting "4GB"
would also work just as well). I also turned off "64 bit Memory and IO
resources (EXPERIMENTAL)".
b) Just before starting the final rpmbuild, I edited the spec file and
set pae=n. The difference between the standard xen spec file and mine were:
591B> diff kernel-xen.spec *pae*
35c35
< %define release %(R="$Revision: 2925.11 $"; RR="${R##: }"; echo
${RR%%?})%{?dist}
---
> %define release %(R="$Revision: 2925.11 $"; RR="${R##: }"; echo
${RR%%?}).NO_PAE%{?dist}
97,98c97,98
< # we build always xen HV with pae
< %define xen_flags verbose=y crash_debug=y pae=y
---
> # we build always xen HV with pae - No we don't.
> %define xen_flags verbose=y crash_debug=y pae=n
I installed the resultant RPM on Dom0 and my F7 guests. Note you'll need
to specify --oldpackage, since rpm thinks the currently installed,
redhat-built 2925.11 version is newer for some reason. Reboot ... Now
you're non-PAE, and can utilize all those non-PAE guests out there. And
you can switch back and forth between PAE/non-PAE, by choosing the
appropriate versions of the kernel on dom0 and guests.
FC6 (built for use by my FC6 guest):
Just like F7, with the following exceptions:
a) I used kernel-2.6.20-1.2962.fc6.src.rpm
b) Spec file changes (kernel-2.6.spec) look like:
36c36,37
< %define with_xenonly %{?_with_xenonly: 1} %{?!_with_xenonly: 0}
---
> #%define with_xenonly %{?_with_xenonly: 1} %{?!_with_xenonly: 0}
> %define with_xenonly 1
64c65
< %define release %(R="$Revision: 1.2962 $"; RR="${R##: }"; echo
${RR%%?})%{?dist}%{?buildid}
---
> %define release %(R="$Revision: 1.2962 $"; RR="${R##: }"; echo
> ${RR%%?}).NO_PAE.%{?dist}%{?buildid}
178,179c179,180
< # we build always xen i686 HV with pae
< %define xen_flags verbose=y crash_debug=y pae=y
---
> # we build always xen i686 HV with pae - No we don't.
> %define xen_flags verbose=y crash_debug=y pae=n
I haven't tried to see if FC5 guests work - I suspect they will.
Enjoy,
Mike
16 years, 10 months
Problem installing xen guest on Fedora Core 7
by Formoso, Travis
All,
I am trying to do a guest install using virt-install on Fedora Core 7. This is a fresh install of 7. Here is what I am getting when I try to do the install:
What is the name of your virtual machine? www
How much RAM should be allocated (in megabytes)? 256
What would you like to use as the disk (path)? /xen/www
How large would you like the disk (/xen/www) to be (in gigabytes)? 40
Would you like to enable graphics support? (yes or no) no
What is the install location? nfs:172.20.1.138:/data/network-install/RPM
Starting install...
libvir: Xen Daemon error : GET operation failed:
libvir: Xen Daemon error : GET operation failed:
Creating storage file... 100% |=========================| 40 GB 00:00
Creating domain... 0 B 00:00
Linux version 2.6.20-2925.9.fc7xen (kojibuilder(a)xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 08:53:03 EDT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize bail 0
copy_e820_map() start: 0000000000000000 size: 0000000010800000 end: 0000000010800000 type: 1
Xen: 0000000000000000 - 0000000010800000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
Using x86 segment limits to approximate NX protection
Zone PFN ranges:
DMA 0 -> 67584
Normal 67584 -> 67584
HighMem 67584 -> 67584
early_node_map[1] active PFN ranges
0: 0 -> 67584
ACPI in unprivileged domain disabled
Built 1 zonelists. Total pages: 67056
Kernel command line: method=nfs:172.20.1.138:/data/network-install/RPM
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c135f000 soft=c133f000
PID hash table entries: 2048 (order: 11, 8192 bytes)
Xen reported: 2800.092 MHz processor.
Console: colour dummy device 80x25
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES: 8
... MAX_LOCK_DEPTH: 30
... MAX_LOCKDEP_KEYS: 2048
... CLASSHASH_SIZE: 1024
... MAX_LOCKDEP_ENTRIES: 8192
... MAX_LOCKDEP_CHAINS: 16384
... CHAINHASH_SIZE: 8192
memory used by lock dependency info: 1064 kB
per task-struct memory footprint: 1200 bytes
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Software IO TLB disabled
vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000
Memory: 245120k/270336k available (2030k kernel code, 16724k reserved, 1079k data, 180k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xf5315000 - 0xf57fe000 (5028 kB)
pkmap : 0xf5000000 - 0xf5200000 (2048 kB)
vmalloc : 0xd1000000 - 0xf4ffe000 ( 575 MB)
lowmem : 0xc0000000 - 0xd0800000 ( 264 MB)
.init : 0xc130e000 - 0xc133b000 ( 180 kB)
.data : 0xc11fb8b9 - 0xc1309714 (1079 kB)
.text : 0xc1000000 - 0xc11fb8b9 (2030 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 7007.88 BogoMIPS (lpj=14015769)
Security Framework v1.0.0 initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 11k freed
Brought up 1 CPUs
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: Fatal: No config space access function found
PCI: setting up Xen PCI frontend stub
Setting up standard PCI resources
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 7, 524288 bytes)
TCP bind hash table entries: 8192 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 7264k freed
IA-32 Microcode Update Driver: v1.14-xen <tigran(a)veritas.com>
audit: initializing netlink socket (disabled)
audit(1182440856.653:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
input: Macintosh mouse button emulation as /class/input/input0
Xen virtual console successfully installed as xvc0
Event-channel device installed.
usbcore: registered new interface driver libusual
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP bic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
Freeing unused kernel memory: 180k freed
Write protecting the kernel read-only data: 762k
After the Write protecting it jams up and does not go any further.
Anyone else run into this problem?
Thanks
________________________________
Travis Formoso | Blue Slate Solutions
Infrastructure Specialist | www.blueslate.net
|518.810.0377| travis.formoso(a)blueslate.net
.
This e-mail and any files transmitted with it are for the sole use of
Blue Slate Solutions and the intended recipient(s) and may contain
confidential and privileged information. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
or any action taken in reliance on this e-mail is strictly prohibited
and may be unlawful.
16 years, 10 months
Confused on how to have each guest reach a VLAN
by Juan Carlos Castro y Castro
Both my host and guests are Fedora 6. My first, naive thought, was to
just configure eth0.N within each guest OS.
For testing purposes, I created eth0.69 both within guest01 and guest02,
with addresses 10.11.12.101 and 10.1.12.102 respectively. But guest01
and guest02 can't ping one another through these new addresses.
I read http://wiki.xensource.com/xenwiki/XenNetworking and, in its last
paragraph, it suggests I have to configure VLAN in the host OS, and add
virtual interfaces to a bridge. But I'm confused about how to do that.
Which interfaces do I have to create? Do I have to add them to the
xenbr0 bridge? Can I have this start automagically upon "xm create"?
Below are my ifconfig on the host machine, and the config files for the
two guests (they have IDs 5 and 6):
----------------------------------------------------------------------
eth0 Link encap:Ethernet HWaddr 00:15:17:23:7D:6D
inet addr:192.168.0.195 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::215:17ff:fe23:7d6d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:159825 errors:0 dropped:0 overruns:0 frame:0
TX packets:62265 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:41732783 (39.7 MiB) TX bytes:61710095 (58.8 MiB)
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:4123270 errors:0 dropped:0 overruns:0 frame:0
TX packets:4123270 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:377591540 (360.0 MiB) TX bytes:377591540 (360.0 MiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1552519 errors:0 dropped:0 overruns:0 frame:0
TX packets:324298 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2101900272 (1.9 GiB) TX bytes:84510344 (80.5 MiB)
Base address:0x2000 Memory:48180000-481a0000
tap0 Link encap:Ethernet HWaddr CA:C9:C4:AB:3E:A6
inet6 addr: fe80::c8c9:c4ff:feab:3ea6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:349 errors:0 dropped:0 overruns:0 frame:0
TX packets:1710 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:104729 (102.2 KiB) TX bytes:928665 (906.8 KiB)
tap1 Link encap:Ethernet HWaddr 0E:3E:CA:31:FB:7A
inet6 addr: fe80::c3e:caff:fe31:fb7a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37 errors:0 dropped:0 overruns:0 frame:0
TX packets:1195 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:2922 (2.8 KiB) TX bytes:874780 (854.2 KiB)
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:62278 errors:0 dropped:0 overruns:0 frame:0
TX packets:159837 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:61715017 (58.8 MiB) TX bytes:41733575 (39.8 MiB)
vif5.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif6.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:6844 (6.6 KiB)
xenbr0 Link encap:Ethernet HWaddr 0E:3E:CA:31:FB:7A
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:97424 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:25040439 (23.8 MiB) TX bytes:0 (0.0 b)
----------------------------------------------------------------------
name = "guest01"
uuid = "6ab45a27-0718-5dc1-d235-1704e4273870"
maxmem = 192
memory = 192
vcpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 0
apic = 0
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib/xen/bin/qemu-dm"
sdl = 0
vnc = 1
vncunused = 1
disk = [ "file:/var/lib/xen/images/guest01,hda,w" ]
vif = [ "mac=00:16:3e:13:61:c3,bridge=xenbr0,type=ioemu" ]
serial = "pty"
----------------------------------------------------------------------
name = "guest02"
uuid = "6ab45a27-0718-5dc1-d235-1704e4273871"
maxmem = 192
memory = 192
vcpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 0
apic = 0
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib/xen/bin/qemu-dm"
sdl = 0
vnc = 1
vncunused = 1
disk = [ "file:/var/lib/xen/images/guest02,hda,w" ]
vif = [ "mac=00:16:3e:13:61:c4,bridge=xenbr0,type=ioemu" ]
serial = "pty"
----------------------------------------------------------------------
16 years, 10 months
f7 trunk dom0 ifcfg startup creates 2 bridge no vlan int
by Dale Bewley
I'm trying to configure Fedora 7 to support a 802.1q trunk
in dom0 using
https://www.redhat.com/archives/fedora-xen/2007-June/msg00008.html
and
http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_lib...
for clues.
Since the network-bridge script doesn't seem capable of doing to VLAN work
and I prefer the normal OS scripts, I have the following in xend-config.sxp:
(network-script /bin/true)
(vif-script /bin/true)
It seems that the Fedora goal is to take the original name for an
interface, in this case eth0.6 and make that a bridge and move its
guts to something like peth0.6.
I don't wanna be deprecated so I tried to play along and setup
the ifcfg files like so:
[root@helix network-scripts]# cat ifcfg-eth0
# Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
DEVICE=eth0
MTU=1504
BOOTPROTO=dhcp
ONBOOT=yes
[root@helix network-scripts]# cat ifcfg-vlan6br
DEVICE=eth0.6
TYPE=Bridge
BOOTPROTO=static
ONBOOT=yes
IPADDR=19.27.25.134
NETMASK=255.255.255.192
NETWORK=19.27.25.128
BROADCAST=19.27.25.191
[root@helix network-scripts]# cat ifcfg-vlan6phy
DEVICE=peth0.6
BRIDGE=eth0.6
VLAN=yes
ONBOOT=yes
BOOTPROTO=none
But, this creates a bridge under both names and no vlan interface
[root@helix ~]# brctl show
bridge name bridge id STP enabled interfaces
eth0.6 8000.000000000000 no
peth0.6 8000.000000000000 no
[root@helix network-scripts]# ls /proc/net/vlan
ls: cannot access /proc/net/vlan: No such file or directory
I'll dissect the ifup scripts when I get a second, but am I swimming
upstream or just making a dumb mistake somewhere?
--
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
16 years, 10 months
resizing Xen para-virtualized guest partition
by runmd
I would like to know if it is possible to resizing Xen para-virtualized
guest partition. For example,
I created a para-virtualized guest as 10GB. Later down the road I would
like to grow it to 20GB. Can I do this with it being just a file on Dom0.
The only possible solution I can think of is creating a new domU as 20GB and
then doing a dd command and copying one virutal disk to another. But I
would like to just grow the guest, if possible.
Thanks
Terry
16 years, 10 months
CentOS 4.5 domU on FC6 dom0 won't boot
by Ranbir
Hi,
I'm running some test to see if I can take a physical CentOS 4.5 server
and convert it to a domU on a FC6 dom0 machine - a completely different
server.
I created a LV for the domU, and restored the CentOS 4.5 system from a
backup on the LV - that was the basic install. I then cleaned
up /etc/fstab accordingly (on the domU), and made sure the domU's /boot
was set up properly.
When I run "xm create -c webster" or "virsh start webster", the boot
process gets to the point where SElinux starts, but than freezes. I've
let the domU sit there for 2 hours, but it won't continue booting. I've
tried setting SElinux in the domU to disabled or permissive, but neither
have helped fix the boot issue.
I'm not sure what's wrong. Searching for similar problems hasn't turned
anything up either. Does anyone have an idea about what the problem
could be?
Here's the domU's config:
name = "webster"
bootloader = "/usr/bin/pygrub"
memory = 256
disk = [ "phy:vg00/webster,sda1,w","phy:vg00/swap2,sda2,w" ]
vif = [ '' ]
#vnc = "1"
#vncunused = "1"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
And here's the boot log:
[root@xenmaster ~]# xm create -c webster
Using config file "/etc/xen/webster".
Going to boot CentOS (2.6.9-55.ELxenU)
kernel: /boot/vmlinuz-2.6.9-55.ELxenU
initrd: /boot/custom-initrd-2.6.9-55.ELxenU.img
Started domain webster
Linux version 2.6.9-55.ELxenU (mockbuild(a)builder6.centos.org) (gcc
version 3.4.6 20060404 (Red Hat 3.4.6-8)) #1 SMP Wed May 2 14:49:26 EDT
2007
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000010000000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
Using x86 segment limits to approximate NX protection
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line: ro root=/dev/sda1 3
Initializing CPU#0
CPU 0 irqstacks, hard=c0338000 soft=c0318000
PID hash table entries: 2048 (order: 11, 32768 bytes)
Xen reported: 2392.028 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
vmalloc area: d1000000-f4ffe000, maxmem 2d800000
Memory: 253728k/270336k available (1450k kernel code, 8388k reserved,
539k data, 124k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Security Scaffold v1.0.0 initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
There is already a security framework initialized, register_security
failed.
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
Brought up 1 CPUs
checking if image is initramfs... it is
Freeing initrd memory: 1189k freed
Grant table initialized
NET: Registered protocol family 16
Brought up 1 VCPUs
xen_mem: Initialising balloon driver.
audit: initializing netlink socket (disabled)
audit(1182637492.361:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key FBAD6F8AE400BF26
- User ID: CentOS (Kernel Module GPG key)
rtc: IRQ 8 is not free.
i8042.c: No controller found.
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as xvc0
Linux version 2.6.9-55.ELxenU (mockbuild(a)builder6.centos.org) (gcc
version 3.4.6 20060404 (Red Hat 3.4.6-8)) #1 SMP Wed May 2 14:49:26 EDT
2007
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000010000000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
Using x86 segment limits to approximate NX protection
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line: ro root=/dev/sda1 3
Initializing CPU#0
CPU 0 irqstacks, hard=c0338000 soft=c0318000
PID hash table entries: 2048 (order: 11, 32768 bytes)
Xen reported: 2392.028 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
vmalloc area: d1000000-f4ffe000, maxmem 2d800000
Memory: 253728k/270336k available (1450k kernel code, 8388k reserved,
539k data, 124k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Security Scaffold v1.0.0 initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
There is already a security framework initialized, register_security
failed.
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
Brought up 1 CPUs
checking if image is initramfs... it is
Freeing initrd memory: 1189k freed
Grant table initialized
NET: Registered protocol family 16
Brought up 1 VCPUs
xen_mem: Initialising balloon driver.
audit: initializing netlink socket (disabled)
audit(1182637492.361:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key FBAD6F8AE400BF26
- User ID: CentOS (Kernel Module GPG key)
rtc: IRQ 8 is not free.
i8042.c: No controller found.
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device installed.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 5, 196608 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vif/0
Freeing unused kernel memory: 124k freed
Red Hat nash version 4.2.1.10 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Loading xenblk.ko module
Registering block device major 8
Using cfq io scheduler
Loading jbd.ko module
Loading ext3.ko module
Creating root device
Mounting root filesystem
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
mount: error 2 mounting none
Switching to new root
security: 3 users, 4 roles, 355 types, 26 bools
security: 55 classes, 22610 rules
SELinux: Completing initialization.
SELinux: Setting up existing superblocks.
SELinux: initialized (dev sda1, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev selinuxfs, type selinuxfs), uses
genfs_contexts
SELinux: initialized (dev mqueue, type mqueue), not configured for
labeling
SELinux: initialized (dev devpts, type devpts), uses transition SIDs
SELinux: initialized (dev eventpollfs, type eventpollfs), uses
genfs_contexts
SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
Thanks,
Ranbir
--
Kanwar Ranbir Sandhu
Linux 2.6.20-1.2944.fc6 i686 GNU/Linux
18:25:35 up 14 days, 9:12, 2 users, load average: 0.18, 0.47, 0.46
16 years, 10 months
Re: [Fedora-xen] F7 x86_64 Xen - Can't start xend - wrong ELF class
by Chris Tyler
> ImportError: /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so: wrong
> ELF class: ELFCLASS32
> -----------------------------------------------------------------
>
> Looks like that file is expected to be a 64-bit binary but is 32-bit
> (?). Not sure how to get a 64-bit version; the file is owned by package
> 'xen' (3.1.0-0.rc7.1.fc7) but the only version available appears to be
> i386.
Solved - problem with a local repo mirror (red face!).
--
Chris Tyler
16 years, 10 months
