Can't text install DomU
by Lars Bjørndal
My approach is to install a DomU on top of a Fedora 16, 32 bit machine.
I don't have any X running, so I need a real text install. Anaconda
starts, but nothing happens after that. Below is the output. Hope
someone can help.
--------------------
[root@fox ~]# virt-install -l http://download.fedoraproject.org/pub/fedora/linux /releases/16/Fedora/i386/os --ram 512 --disk /var/lib/libvirt/images/f16.img,siz e=4 -n f16 --graphic none
Starting install...
Retrieving file .treeinfo...
Retrieving file vmlinuz-
Retrieving file initrd-PA
Creating domain...
Connected to domain f16
Escape character is ^]
[ 0.000000] Reserving virtual address space above 0xf5800000
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.1.0-7.fc16.i686.PAE (mockbuild(a)x86-11.phx2.fedoraproject.org) (gcc version 4.6.2 20111027 (Red Hat 4.6.2-1) (GCC) ) #1 SMP Tue Nov 1 20:53:45 UTC 2011
[ 0.000000] ACPI in unprivileged domain disabled
[ 0.000000] released 0 pages of unused memory
[ 0.000000] Set 0 page(s) to 1-1 mapping.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 00000000000a0000 (usable)
[ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 0000000020000000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI not present or invalid.
[ 0.000000] last_pfn = 0x20000 max_arch_pfn = 0x1000000
[ 0.000000] init_memory_mapping: 0000000000000000-0000000020000000
[ 0.000000] RAMDISK: 00eca000 - 08f57000
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 512MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 20000000
[ 0.000000] low ram: 0 - 20000000
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x00020000
[ 0.000000] HighMem empty
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x000000a0
[ 0.000000] 0: 0x00000100 -> 0x00020000
[ 0.000000] Using APIC driver default
[ 0.000000] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org
[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
[ 0.000000] APIC: disable apic facility
[ 0.000000] APIC: switched to apic NOOP
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000)
[ 0.000000] Booting paravirtualized kernel on Xen
[ 0.000000] Xen version: 4.1.2 (preserve-AD)
[ 0.000000] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 13 pages/cpu @dfbee000 s32000 r0 d21248 u53248
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129936
[ 0.000000] Kernel command line: method=http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fed...
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Initializing CPU#0
[ 0.000000] allocated 2096896 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Initializing HighMem for node 0 (00000000:00000000)
[ 0.000000] Memory: 375456k/524288k available (4278k kernel code, 148384k reserved, 2724k data, 612k init, 0k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xf5295000 - 0xf57ff000 (5544 kB)
[ 0.000000] pkmap : 0xf4e00000 - 0xf5000000 (2048 kB)
[ 0.000000] vmalloc : 0xe0800000 - 0xf4dfe000 ( 325 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] .init : 0xc0ad7000 - 0xc0b70000 ( 612 kB)
[ 0.000000] .data : 0xc082d816 - 0xc0ad6840 (2724 kB)
[ 0.000000] .text : 0xc0400000 - 0xc082d816 (4278 kB)
[ 0.000000] SLUB: Genslabs=15, HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] NR_IRQS:1280
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] console [hvc0] enabled
[ 0.000000] installing Xen timer for CPU 0
[ 0.000000] Detected 3000.144 MHz processor.
[ 0.000999] Calibrating delay loop (skipped), value calculated using timer frequency.. 6000.28 BogoMIPS (lpj=3000144)
[ 0.001045] pid_max: default: 32768 minimum: 301
[ 0.001373] Security Framework initialized
[ 0.001514] SELinux: Initializing.
[ 0.001868] Mount-cache hash table entries: 512
[ 0.002761] Initializing cgroup subsys cpuacct
[ 0.002961] Initializing cgroup subsys memory
[ 0.002999] Initializing cgroup subsys devices
[ 0.002999] Initializing cgroup subsys freezer
[ 0.002999] Initializing cgroup subsys net_cls
[ 0.002999] Initializing cgroup subsys blkio
[ 0.003034] Initializing cgroup subsys perf_event
[ 0.003333] CPU: Physical Processor ID: 0
[ 0.003460] CPU: Processor Core ID: 0
[ 0.003829] SMP alternatives: switching to UP code
[ 0.005311] Freeing SMP alternatives: 12k freed
[ 0.005517] ftrace: allocating 24660 entries in 49 pages
[ 0.007181] Performance Events: unsupported Netburst CPU model 4 no PMU driver, software events only.
[ 0.008787] NMI watchdog disabled (cpu0): hardware events not enabled
[ 0.008894] Brought up 1 CPUs
[ 0.009721] devtmpfs: initialized
[ 0.012825] atomic64 test passed for i586+ platform with CX8 and with SSE
[ 0.012916] Grant table initialized
[ 0.031893] RTC time: 165:165:165, date: 165/165/65
[ 0.032094] NET: Registered protocol family 16
[ 0.034997] PCI: setting up Xen PCI frontend stub
[ 0.038731] bio: create slab <bio-0> at 0
[ 0.039179] ACPI: Interpreter disabled.
[ 0.040964] xen/balloon: Initialising balloon driver.
[ 0.040991] last_pfn = 0x20000 max_arch_pfn = 0x1000000
[ 0.050377] xen-balloon: Initialising balloon driver.
[ 0.051831] vgaarb: loaded
[ 0.052121] SCSI subsystem initialized
[ 0.052457] usbcore: registered new interface driver usbfs
[ 0.052516] usbcore: registered new interface driver hub
[ 0.052708] usbcore: registered new device driver usb
[ 0.052995] PCI: System does not support PCI
[ 0.052995] PCI: System does not support PCI
[ 0.053035] NetLabel: Initializing
[ 0.053057] NetLabel: domain hash size = 128
[ 0.053077] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.053121] NetLabel: unlabeled traffic allowed by default
[ 0.053152] Switching to clocksource xen
[ 0.053995] Switched to NOHz mode on CPU #0
[ 0.076539] pnp: PnP ACPI: disabled
[ 0.084678] NET: Registered protocol family 2
[ 0.085081] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.086163] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.086893] TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.087070] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.087070] TCP reno registered
[ 0.087070] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.087070] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.087070] NET: Registered protocol family 1
[ 0.088629] Unpacking initramfs...
[ 1.385540] Freeing initrd memory: 131636k freed
[ 1.482913] platform rtc_cmos: registered platform RTC device (no PNP device found)
[ 1.483446] apm: BIOS not found.
[ 1.483754] Intel AES-NI instructions are not detected.
[ 1.484230] audit: initializing netlink socket (disabled)
[ 1.484276] type=2000 audit(1336972488.808:1): initialized
[ 1.517251] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 1.521353] VFS: Disk quotas dquot_6.5.2
[ 1.521587] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.523240] msgmni has been set to 990
[ 1.524571] alg: No test for stdrng (krng)
[ 1.524609] NET: Registered protocol family 38
[ 1.524751] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 1.524888] io scheduler noop registered
[ 1.524906] io scheduler deadline registered
[ 1.524954] io scheduler cfq registered (default)
[ 1.525152] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 1.525238] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 1.525260] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 1.525530] isapnp: Scanning for PnP cards...
[ 1.885464] isapnp: No Plug & Play device found
[ 1.886695] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.888191] Non-volatile memory driver v1.3
[ 1.888218] Linux agpgart interface v0.103
[ 1.891628] loop: module loaded
[ 1.891987] Fixed MDIO Bus: probed
[ 1.892240] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.892308] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.892365] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.892540] usbcore: registered new interface driver usbserial
[ 1.892586] USB Serial support registered for generic
[ 1.892643] usbcore: registered new interface driver usbserial_generic
[ 1.892668] usbserial: USB Serial Driver core
[ 1.892766] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 1.893837] mousedev: PS/2 mouse device common for all mice
[ 1.934410] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[ 1.934570] rtc_cmos: probe of rtc_cmos failed with error -38
[ 1.934849] device-mapper: uevent: version 1.0.3
[ 1.935180] device-mapper: ioctl: 4.21.0-ioctl (2011-07-06) initialised: dm-devel(a)redhat.com
[ 1.935427] EFI Variables Facility v0.08 2004-May-17
[ 1.935895] usbcore: registered new interface driver usbhid
[ 1.935919] usbhid: USB HID core driver
[ 1.936148] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 1.936209] TCP cubic registered
[ 1.936229] Initializing XFRM netlink socket
[ 1.936623] NET: Registered protocol family 10
[ 1.937123] Mobile IPv6
[ 1.937140] NET: Registered protocol family 17
[ 1.937186] Registering the dns_resolver key type
[ 1.937250] Using IPI No-Shortcut mode
[ 1.937542] registered taskstats version 1
[ 1.937567] IMA: No TPM chip found, activating TPM-bypass!
[ 1.937680] XENBUS: Device with no driver: device/vbd/51712
[ 1.937699] XENBUS: Device with no driver: device/vif/0
[ 1.937716] XENBUS: Device with no driver: device/console/0
[ 1.937765] Magic number: 1:252:3141
[ 1.937809] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 1.937876] Initializing network drop monitor service
[ 1.938729] Freeing unused kernel memory: 612k freed
[ 1.942723] Write protecting the kernel text: 4280k
[ 1.944461] Write protecting the kernel read-only data: 2064k
[ 1.944487] NX-protecting the kernel data: 3912k
[ 2.088215] dracut: dracut-013-18.fc16
[ 2.109377] dracut: root was live:/squashfs.img, liveroot is now live:/squashfs.img
[ 2.144554] udevd[65]: starting version 173
[ 2.455170] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 2.667001] EXT4-fs (dm-0): warning: checktime reached, running e2fsck is recommended
[ 2.669876] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 2.688729] dracut: Mounted root filesystem /dev/mapper/live-rw
[ 2.788224] dracut: Switching root
[ 3.588479] type=1403 audit(1336972490.912:2): policy loaded auid=4294967295 ses=4294967295
[ 3.604555] systemd[1]: Successfully loaded SELinux policy in 311ms 966us.
[ 3.753016] systemd[1]: Successfully loaded SELinux database in 147ms 59us, size on heap is 362K.
[ 4.066382] systemd[1]: Relabelled /dev and /run in 290ms 464us.
[ 4.079236] systemd[1]: systemd 36 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora)
Welcome to [0;34mFedora release 16 (Verne)[0m!
[ 4.093558] systemd[1]: No hostname configured.
[ 4.096337] systemd[1]: Initializing machine ID from random generator.
[ 4.250819] systemd[1]: Failed to fully start up daemon: No such file or directory
[ 4.251155] systemd[1]: Cannot add dependency job for unit fedora-storage-init.service, ignoring: Unit fedora-storage-init.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-storage-init.service' for details.
[ 4.251288] systemd[1]: Cannot add dependency job for unit fedora-wait-storage.service, ignoring: Unit fedora-wait-storage.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-wait-storage.service' for details.
[ 4.251405] systemd[1]: Cannot add dependency job for unit systemd-remount-api-vfs.service, ignoring: Unit systemd-remount-api-vfs.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-remount-api-vfs.service' for details.
[ 4.251516] systemd[1]: Cannot add dependency job for unit fedora-readonly.service, ignoring: Unit fedora-readonly.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-readonly.service' for details.
[ 4.251647] systemd[1]: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
[ 4.251979] systemd[1]: Cannot add dependency job for unit rpcbind.socket, ignoring: Unit rpcbind.socket failed to load: No such file or directory. See system logs and 'systemctl status rpcbind.socket' for details.
[ 4.252139] systemd[1]: Cannot add dependency job for unit dm-event.socket, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
[ 4.252242] systemd[1]: Cannot add dependency job for unit avahi-daemon.socket, ignoring: Unit avahi-daemon.socket failed to load: No such file or directory. See system logs and 'systemctl status avahi-daemon.socket' for details.
[ 4.252432] systemd[1]: Cannot add dependency job for unit ip6tables.service, ignoring: Unit ip6tables.service failed to load: No such file or directory. See system logs and 'systemctl status ip6tables.service' for details.
[ 4.253495] systemd[1]: Cannot add dependency job for unit iptables.service, ignoring: Unit iptables.service failed to load: No such file or directory. See system logs and 'systemctl status iptables.service' for details.
Starting Collect Read-Ahead Data...
Started Replay Read-Ahead Data.
Started Lock Directory.
Starting Initialize storage subsystems (RAID, LVM, etc.)...
Starting Software RAID Monitor Takeover...
Starting Security File System...
Starting Debug File System...
Starting Huge Pages File System...
Starting POSIX Message Queue File System...
Starting udev Coldplug all Devices...
Starting udev Kernel Device Manager...
Starting Syslog Kernel Log Buffer Bridge...
Started Syslog Kernel Log Buffer Bridge.
Starting Runtime Directory...
Started Collect Read-Ahead Data.
[ 4.812765] systemd[1]: fedora-storage-init-late.service: main process exited, code=exited, status=203
Starting Initialize storage subsystems (RAID, LVM, etc.) [1;31mfailed[0m, see 'systemctl status fedora-storage-init-late.service' for details.
[ 4.815369] systemd[1]: Unit fedora-storage-init-late.service entered failed state.
Started Software RAID Monitor Takeover.
Started Security File System.
Started Debug File System.
Started Huge Pages File System.
Started POSIX Message Queue File System.
Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Started Load legacy module configuration.
Starting File System Check on Root Device...
Started Load Kernel Modules.
Started Configuration File System.
Started FUSE Control File System.
Starting Setup Virtual Console...
Started Set Up Additional Binary Formats.
Starting Apply Kernel Variables...
Starting STDOUT Syslog Bridge...
Started STDOUT Syslog Bridge.
Started Runtime Directory.
[ 5.140020] systemd-fsck[194]: Root directory is writable, skipping check.
Started File System Check on Root Device.
Starting Remount Root FS...
[ 5.197725] systemd-vconsole-setup[195]: /bin/loadkeys failed with error code 1.
[ 5.198839] systemd-vconsole-setup[195]: /bin/setfont failed with error code 1.
Started Setup Virtual Console.
Started Apply Kernel Variables.
[ 5.257727] mount[201]: warning: can't open /etc/fstab: No such file or directory
[ 5.294187] EXT4-fs (dm-0): re-mounted. Opts: user_xattr,acl,barrier=1,data=ordered
Started Remount Root FS.
Started udev Kernel Device Manager.
[ 5.598173] udevd[188]: starting version 173
Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization...
[ 6.113732] lvm[192]: No volume groups found
Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Started Reconfigure the system on administrator request.
Started Relabel all filesystems, if necessary.
Started Mark the need to relabel after reboot.
Starting Load Random Seed...
Starting Recreate Volatile Files and Directories...
Started Load Random Seed.
[ 6.616135] systemd-tmpfiles[229]: Successfully loaded SELinux database in 367ms 792us, size on heap is 363K.
[ 6.821216] Initialising Xen virtual ethernet driver.
[ 6.903454] blkfront: xvda: flush diskcache: enabled
[ 6.909609] xvda: unknown partition table
Started Recreate Volatile Files and Directories.
Started udev Wait for Complete Device Initialization.
Started anaconda performance monitor.
Starting System Logging Service...
Starting Shell on tty2...
Started Shell on tty2.
Starting Shell on hvc1...
[ 8.831724] udevd[208]: setfilecon /dev/vcs2 failed: No such file or directory
Started Shell on hvc1.
Starting Anaconda version 16.25.
11 years, 3 months
Fedora 17 testing as Xen VM / Xorg issue
by Pasi Kärkkäinen
Hello,
I just did some installs with F17 RC4 (the GA version) as a Xen VM.
Xen host/dom0: RHEL 5.8 x86_64 with the included Xen rpms.
Tested F17 RC4 VMs:
- 32bit F17 PV domU: graphical GUI install works OK using the Xen vfb/pvfb
but Xorg fails to start during normal boot after installation.
- 64bit F17 PV domU: graphical GUI install works OK using the Xen vfb/pvfb
but Xorg fails to start during normal boot after installation.
- 32bit F17 PVHVM guest: X fails to start so VNC install must be used, install works OK thru VNC.
Xorg fails to start during normal boot after installation.
- 64bit F17 PVHVM guest: X fails to start so VNC install must be used, install works OK thru VNC.
Xorg fails to start during normal boot after installation.
(PVHVM == HVM fully virtualized guest with optimized Xen PV drivers.
Optimized Xen PVHVM drivers are nowadays included and used as a default with
recent upstream Linux kernel versions (2.6.36+), so disk/net IO doesn't have to be emulated by Xen Qemu-dm.)
I wonder if the problem with X failing to start is related to:
http://fedoraproject.org/wiki/Features/DRI2DriversOnly
Xen HVM guests have Qemu-dm emulated Cirrus VGA adapter (or stdvga) visible to the VM..
which doesn't have DRM/KMS drivers, and I think it's the same for xen-fbfront.
I think I saw Cirrus (Qemu) DRM/KMS driver being worked on dri-devel mailinglist..
Any ideas/comments?
-- Pasi
11 years, 3 months
Kernel Update for Xen Dom0
by Steven Smith
Hi,
Is there a "best practices" procedure for updating the xen Dom0 environment
(kernel)? The installation of Fedora 16 with xen 4 was a breeze and it has
been running and performing well for ~ eight Months. Performing an update
on the Dom0 kernel, however, does not seem to be covered in the standard
documentation. Using Yum to update the kernel does not rebuild or change the
xen.gz and the new kernel will not boot the xen dom0. Does anyone have any
experience with this?
Best Regards,
Steven
11 years, 3 months
Boot errors
by Chris Jones
I installed Fedora 16 and then ran:
sudo yum install xen
Xen installed without errors and I rebooted. In the Grub2 list I selected
Xen 4.1.2 and then selected the option:
Fedora Linux, with Xen 4.1.2 and Linux 3.3.0-4.fc16.x86_64
The boot process starts (i notice that loading ramdisk is very short) and
then shortly thereafter the boot fails and the system reboots without any
error.
I tried checking the boot log but I'm not sure I'm looking at the right
log.
The only problem I see in the boot is
Started SYSV: sandbox, xguest and other apps that want to use pam_names$
Failed to start Xenstored - daemon managing xenstore file system
11 years, 4 months
Change xen package owner away from xen-maint?
by Cole Robinson
Hey folks.
Right now the package owner for xen in fedora is the xen-maint alias account.
Originally this was an alias that was mapped to various @redhat folks who were
doing xen development, and was used for both fedora and internal RHEL stuff.
Nowadays it's not really used in upstream/fedora land and fedora-virt-maint is
a better suited alias. Additionally @redhat isn't doing much xen work these
days so we should just have a single package owner which reflects reality.
So I propose we drop xen-maint as the package owner, and Michael can
'officially' take on package ownership. If that sounds fine I'll file a ticket
with fedora infrastructure to make the change (required AFAIK for alias
account changes).
Michael, does that sound good to you?
Thanks,
Cole
11 years, 4 months
DomU nat router fails when DomUs on same host
by Virgil
Hi List,
I have a strange issue someone, hopefully, can advise me on.
I have two external connections into a host: em1 is behind a firewall machine
which is connected to an internet backbone link, while em2 is an adsl all-u-
can-eat deal with a cheap router.
Both are bridged. So there's pem1 and pem2 which are connected to the em1 and
em2 bridges respectively.
There is a domU router which nats (and is connected to both bridges).
Some domU servers (a variety of fc6 to fc16 32 and 64) default route to the
domU router and go out the all-u-can-eat link.
The issue is, I recent upgraded the host from Fedora8 to Fedora16, and now the
domU machines that once happily used the all-u-can-eat link, no longer can.
However, in an act of desperation, I moved one of the domUs to a backup
machine. Nothing else changed. Bingo. That domU works. All resources are still
on the original machine (i.e. the DB servers, the router, etc. etc.).
It seems that the router does't seem to nat domUs on the same host. You move
the domU off with comms going via em1 to another host and it works.
Iptraf tracing seems to indicate that the TCP connection is setup. The first
packet goes off and is acked. Then everything stops and eventually the tcp
connection closes on the router, but the domU and the remote computer think
the link is still up (at least that's what I think is happening). The domU's
send queue ends up with lots of data in it according to 'netstat -ant'
Only nat'd tcp connections are effected. Connections to machines on the same
bridge work fine.
Does this sound familiar to anyone?
Thanks in advance
Virgil
11 years, 4 months
Dom0 and colord
by Lars Bjørndal
I'm testing Xen dom0 on a Fedora 16 i686 box. I notice a process called
/usr/libexec/colord, that leads to high cpu load, resulting in a
spinning cpu fan. The process also runs when Xen is not running, but then
the TIME reported by 'ps ax' is 0:00.
As I'm blind and don't use any X or GUI, I think I don't need the colord
process, so I did 'killall -9 /usr/libexec/colord'. However, this
doesn't work from a script, like /etc/rc.d/rc.local, and I need to do it
manually after every reboot.
Where is colord started, and how can I get rid of the process?
Thanks and regards,
Lars
11 years, 4 months
