OK I am back from vacation and have started up this project again. I am taking old xen images from Fedora Core 4 and upgrading them to 7 on a new server. Here is what I have done so far and have run into a problem. I installed Fedora Core 7 on the new server and has new xen and kernel. I transferred the old images and files from the old server to the new one. I then went in to the old config file - and changed the kernel from FC4 to the new vmlinuz FC7. I then created a new initrd with xenblk with the following command: mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd-2.6.20-2925.13.fc7xen.img 2.6.20-2925.13.fc7-1xen. I put that in the config file under ramdisk. Now when I run the command xm create -c xmconfig I get this: Using config file "./xmconfig". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. I looked at the archives and tried many suggestions, however none of them have worked - Anything else I could do to get by this error?> yes,> you also need to create a new initrd for domU''s with xenblk module.> OK I am going to install Fedora Core 7 on the new server (it has 6 now). > > I will install the latest Xen 3.1 and the *13* kernel. > > After that I will transfer all the stuff from the older server to the new > one. > > Then do I go into the xmconfig and change the kernel name? So here is the > xmconfig for the sec-int-dns vm. > > # Kernel image file. > kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU" > > Do I go and switch that line to kernel = (new xen kernel)? > > I am trying to understand that part - thanks for all your help!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.
I looked at the config file again and it stated under vif: # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''mac=aa:00:00:00:00:11, bridge=xen-br0'' ] vif = [ ''mac=aa:00:00:00:01:04'' ] I changed it to: vif = ['' ''] I then did the xm create and got this error: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Here is the entire log file: #===========================================================================# Python configuration setup for ''xm create''. # This script sets the parameters used when a domain is created using ''xm create''. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #=========================================================================== #---------------------------------------------------------------------------- # Kernel image file. #kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU" kernel = "/boot/vmlinuz-2.6.20-2925.13.fc7xen" # Optional ramdisk. ramdisk = "/boot/initrd-2.6.20-2925.13.fc7xen.img" # The domain build function. Default is ''linux''. #builder=''linux'' # Initial memory allocation (in megabytes) for the new domain. memory = 32 # A name for your domain. All domains must have different names. name = "sec-int-dns" # Which CPU to start domain on? #cpu = -1 # leave to Xen to pick #---------------------------------------------------------------------------- # Define network interfaces. # Number of network interfaces. Default is 1. #nics=1 # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''mac=aa:00:00:00:00:11, bridge=xen-br0'' ] #vif = [ ''mac=aa:00:00:00:01:04'' ] vif = ['' ''] #---------------------------------------------------------------------------- # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. disk = [ ''file:/xen/sec-int-dns/root.img,sda1,w'', ''file:/xen/sec-int-dns/swap.img,sda2,w'' ] #---------------------------------------------------------------------------- # Set the kernel command line for the new domain. # You only need to define the IP parameters and hostname if the domain''s # IP config doesn''t, e.g. in ifcfg-eth0 or via DHCP. # You can use ''extra'' to set the runlevel and custom environment # variables used by custom rc scripts (e.g. VMID=, usr= ). # Set if you want dhcp to allocate the IP address. dhcp="dhcp" #ip="172.20.1.88" # Set netmask. netmask="255.255.255.0" # Set default gateway. gateway="172.20.1.1" # Set the hostname. hostname= "sec-int-dns" # Set root device. root = "/dev/sda1 ro" # Root device for nfs. #root = "/dev/nfs" # The nfs server. #nfs_server = ''169.254.1.0'' # Root directory on the nfs server. #nfs_root = ''/full/path/to/root/directory'' # Sets runlevel 4. extra = "4" #---------------------------------------------------------------------------- # Set according to whether you want the domain restarted when it exits. # The default is ''onreboot'', which restarts the domain when it shuts down # with exit code reboot. # Other values are ''always'', and ''never''. #restart = ''onreboot'' #=========================================================================== Here is the xen log file: [2007-08-08 04:53:01 25349] DEBUG (XendDomainInfo:957) XendDomainInfo.handleShutdownWatch [2007-08-08 04:53:02 25349] DEBUG (DevController:148) Waiting for devices vif. [2007-08-08 04:53:02 25349] DEBUG (DevController:153) Waiting for 0. [2007-08-08 04:53:02 25349] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vif/16/0/hotplug-status. [2007-08-08 04:53:02 25349] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vif/16/0/hotplug-status. [2007-08-08 04:53:02 25349] DEBUG (DevController:570) hotplugStatusCallback 1. [2007-08-08 04:53:02 25349] DEBUG (DevController:148) Waiting for devices usb. [2007-08-08 04:53:02 25349] DEBUG (DevController:148) Waiting for devices vbd. [2007-08-08 04:53:02 25349] DEBUG (DevController:153) Waiting for 2049. [2007-08-08 04:53:02 25349] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vbd/16/2049/hotplug-status. [2007-08-08 04:54:42 25349] DEBUG (XendDomainInfo:1709) XendDomainInfo.destroy: domid=16 [2007-08-08 04:54:42 25349] DEBUG (XendDomainInfo:1726) XendDomainInfo.destroyDomain(16) Log file for hotplug: Nothing to flush. xenstore-read: couldn''t read path backend/vbd/16/2049/node xenstore-read: couldn''t read path backend/vbd/16/2050/node Hope this helps to determine the problem. Thanks> OK I am back from vacation and have started up this project again. I am > > taking old xen images from Fedora Core 4 and upgrading them to 7 on a new > server. Here is what I have done so far and have run into a problem.> I installed Fedora Core 7 on the new server and has new xen and kernel. I > transferred the old images and files from the old server to the new one.> I then went in to the old config file - and changed the kernel from FC4 to > the new vmlinuz FC7. I then created a new initrd with xenblk with the > following command: mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd- > 2.6.20-2925.13.fc7xen.img 2.6.20-2925.13.fc7-1xen. I put that in the config file under ramdisk.> Now when I run the command xm create -c xmconfig I get this:> Using config file "./xmconfig". > Error: Device 0 (vif) could not be connected. Hotplug scripts not working.> I looked at the archives and tried many suggestions, however none of them > have worked -> Anything else I could do to get by this error?> yes,> you also need to create a new initrd for domU''s with xenblk module.> OK I am going to install Fedora Core 7 on the new server (it has 6 now). > > I will install the latest Xen 3.1 and the *13* kernel. > > After that I will transfer all the stuff from the older server to the new > one. > > Then do I go into the xmconfig and change the kernel name? So here is the > xmconfig for the sec-int-dns vm. > > # Kernel image file. > kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU" > > Do I go and switch that line to kernel = (new xen kernel)? > > I am trying to understand that part - thanks for all your help!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. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen 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.
Update: I disabled my firewall and selinux and now get it to start to boot, but then this comes up: 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: 180k freed Write protecting the kernel read-only data: 759k USB Universal Host Controller Interface driver v3.0 SCSI subsystem initialized Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com Registering block device major 8 register_blkdev: cannot get major 8 for sd xen_blk: can''t get major 8 with name sd vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/9/2049 Registering block device major 8 register_blkdev: cannot get major 8 for sd xen_blk: can''t get major 8 with name sd vbd vbd-2050: 19 xlvbd_add at /local/domain/0/backend/vbd/9/2050 XENBUS: Timeout connecting to device: device/vbd/2049 (state 6) XENBUS: Timeout connecting to device: device/vbd/2050 (state 6) Kernel panic - not syncing: Attempted to kill init! Thanks> I looked at the config file again and it stated under vif:> # Optionally define mac and/or bridge for the network interfaces. > # Random MACs are assigned if not given. > #vif = [ ''mac=aa:00:00:00:00:11, bridge=xen-br0'' ] > vif = [ ''mac=aa:00:00:00:01:04'' ]> I changed it to:> vif = ['' '']> I then did the xm create and got this error:> Error: Device 2049 (vbd) could not be connected. Hotplug scripts not > working.> snipThis 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.
Update on this issue and need some help. I am trying to get an old FC4 image booted up on my new FC7 xen box so that I can upgrade the old FC4 machine to FC7 - however I am having trouble booting it up. I will place the config file after explanation. The situation is as follows: I have 2 old P3 boxes with xen images on them. We now have a new Power Edge server and I installed Fedora Core 7 on it. I then transferred over all the files from the old boxes to the new FC7 box and have the same directory structures. (All the files were in the /xen directory and a bunch of sub-directories with the xen images.) I am trying to get one of the old FC4 xen images to boot with an xm create -c (config file name) - however when I do that - it will not boot and giving me errors. I did a few things listed below: (Itamar on the mailing list guided me in this direction) I created a new initrd with this command: mkinitrd --preload=xenblk --preload=xennet -f -v /boot/initrd-2.6.20-2925.13.fc7xen.guest.img 2.6.20-2925.13.fc7xen I then had my new initrd img with xenblk and xennet. Now in the config file I had to change the kernel from: #kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU" kernel = "/boot/vmlinuz-2.6.20-2925.13.fc7xen" So that I can get the old machine to boot up in the FC7 environment. When I go to boot the machine I get this: xm create -c xmconfig 4gb seg fixup, process S28autofs (pid 825), cs:ip 73:0092914b printk: 197950 messages suppressed. 4gb seg fixup, process egrep (pid 973), cs:ip 73:008e8149 printk: 116932 messages suppressed. 4gb seg fixup, process sendmail (pid 962), cs:ip 73:004d675f printk: 15 messages suppressed. 4gb seg fixup, process dhcpd (pid 941), cs:ip 73:00d20d7f printk: 108 messages suppressed. 4gb seg fixup, process sendmail (pid 962), cs:ip 73:004d675f printk: 15 messages suppressed. 4gb seg fixup, process named (pid 752), cs:ip 73:002f775f This just keeps repeating and going and never stops and I can not do anything with the machine except kill it. I googled for these errors and tried just about everything I could find and nothing worked. It all comes back to this repeating. I really would like to get this FC4 image up and running so I can go in and then update it to FC7 as I have to do this with 4 of our old images. Here is the full config file. If you guys have any ideas of what I could do please let me know. # -*- mode: python; -*- #===========================================================================# Python configuration setup for ''xm create''. # This script sets the parameters used when a domain is created using ''xm create''. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #=========================================================================== #---------------------------------------------------------------------------- # Kernel image file. #kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU" kernel = "/boot/vmlinuz-2.6.20-2925.13.fc7xen" # Optional ramdisk. #ramdisk = "/boot/initrd.gz" ramdisk = "/boot/initrd-2.6.20-2925.13.fc7xen.guest.img" # The domain build function. Default is ''linux''. #builder=''linux'' # Initial memory allocation (in megabytes) for the new domain. memory = 128 # A name for your domain. All domains must have different names. name = "sec-int-dns" # Which CPU to start domain on? #cpu = -1 # leave to Xen to pick #---------------------------------------------------------------------------- # Define network interfaces. # Number of network interfaces. Default is 1. #nics=1 # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''mac=aa:00:00:00:00:11, bridge=xen-br0'' ] vif = [ ''mac=aa:00:00:00:01:04'' ] #---------------------------------------------------------------------------- # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. disk = [ ''file:/xen/sec-int-dns/root.img,sda1,w'', ''file:/xen/sec-int-dns/swap.img,sda2,w'' ] #---------------------------------------------------------------------------- # Set the kernel command line for the new domain. # You only need to define the IP parameters and hostname if the domain''s # IP config doesn''t, e.g. in ifcfg-eth0 or via DHCP. # You can use ''extra'' to set the runlevel and custom environment # variables used by custom rc scripts (e.g. VMID=, usr= ). # Set if you want dhcp to allocate the IP address. dhcp="dhcp" #ip="17x.2x.x.xx" # Set netmask. #netmask="255.255.255.0" # Set default gateway. #gateway="17x.xx.x.x" # Set the hostname. hostname= "sec-int-dns" # Set root device. root = "/dev/sda1 ro" # Root device for nfs. #root = "/dev/nfs" # The nfs server. #nfs_server = ''xxx.xxx.x.0'' # Root directory on the nfs server. #nfs_root = ''/full/path/to/root/directory'' # Sets runlevel 4. extra = "4" #---------------------------------------------------------------------------- # Set according to whether you want the domain restarted when it exits. # The default is ''onreboot'', which restarts the domain when it shuts down # with exit code reboot. # Other values are ''always'', and ''never''. #restart = ''onreboot'' #=========================================================================== 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.
Here is the complete boot up process with the 4gb seg fixup problem if that
helps to diagnose the problem. Thank you!
Started domain sec-int-dns
Linux version 2.6.20-2925.13.fc7xen
(kojibuilder@xenbuilder2.fedora.redhat.com) (gcc version 4.1.2 20070502 (Red Hat
4.1.2-12)) #1 SMP Tue Jul 17 10:38:27 EDT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize bail 0
copy_e820_map() start: 0000000000000000 size: 0000000008800000 end:
0000000008800000 type: 1
Xen: 0000000000000000 - 0000000008800000 (usable)
0MB HIGHMEM available.
136MB LOWMEM available.
NX (Execute Disable) protection: active
Zone PFN ranges:
DMA 0 -> 34816
Normal 34816 -> 34816
HighMem 34816 -> 34816
early_node_map[1] active PFN ranges
0: 0 -> 34816
ACPI in unprivileged domain disabled
Built 1 zonelists. Total pages: 34544
Kernel command line: root=/dev/sda1 ro ip=:1.2.3.4:::sec-int-dns:eth0:dhcp 4
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c135d000 soft=c133d000
PID hash table entries: 1024 (order: 10, 4096 bytes)
Xen reported: 3000.104 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: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Software IO TLB disabled
vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000
Memory: 114332k/139264k available (2023k kernel code, 16588k reserved, 1077k
data, 180k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xf5315000 - 0xf57fe000 (5028 kB)
pkmap : 0xf5000000 - 0xf5200000 (2048 kB)
vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB)
lowmem : 0xc0000000 - 0xc8800000 ( 136 MB)
.init : 0xc130c000 - 0xc1339000 ( 180 kB)
.data : 0xc11f9fe5 - 0xc1307714 (1077 kB)
.text : 0xc1000000 - 0xc11f9fe5 (2023 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 7504.32 BogoMIPS (lpj=15008654)
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: 2048K
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: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 6, 262144 bytes)
TCP bind hash table entries: 4096 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 8192 bind 4096)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 8752k freed
IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
audit: initializing netlink socket (disabled)
audit(1187228011.247: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/2049
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vif/0
Freeing unused kernel memory: 180k freed
Write protecting the kernel read-only data: 759k
Registering block device major 8
blkfront: sda1: barriers enabled
blkfront: sda2: barriers enabled
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has copying receive path.
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
4gb seg fixup, process init (pid 1), cs:ip 73:0092da56
4gb seg fixup, process init (pid 1), cs:ip 73:0099e2ee
4gb seg fixup, process init (pid 1), cs:ip 73:0092c75f
4gb seg fixup, process init (pid 1), cs:ip 73:0092c76d
4gb seg fixup, process init (pid 1), cs:ip 73:008e8b6b
4gb seg fixup, process init (pid 1), cs:ip 73:0092c75f
4gb seg fixup, process init (pid 1), cs:ip 73:0092c76d
4gb seg fixup, process init (pid 1), cs:ip 73:00901d7f
4gb seg fixup, process init (pid 1), cs:ip 73:0092c75f
4gb seg fixup, process init (pid 1), cs:ip 73:0092c76d
SELinux: Disabled at runtime.
SELinux: Unregistering netfilter hooks
audit(1187228019.543:2): selinux=0 auid=4294967295
audit(1187228073.382:3): audit_backlog_limit=256 old=64 by auid=4294967295
audit(1187228073.774:4): audit_pid=778 old=0 by auid=4294967295
4gb seg fixup, process S28autofs (pid 804), cs:ip 73:0092914b
printk: 129366 messages suppressed.
4gb seg fixup, process newaliases (pid 954), cs:ip 73:00217ce7
printk: 191711 messages suppressed.
4gb seg fixup, process sendmail (pid 962), cs:ip 73:0020d75f
printk: 18 messages suppressed.
4gb seg fixup, process sendmail (pid 962), cs:ip 73:0020d75f
printk: 41 messages suppressed.
4gb seg fixup, process sendmail (pid 962), cs:ip 73:0020d75f
printk: 15 messages suppressed.
4gb seg fixup, process sendmail (pid 962), cs:ip 73:0020d75f
(Right here it keeps repeating the 4gb seg fixup.)
> snip
> When I go to boot the machine I get this: xm create -c xmconfig
> 4gb seg fixup, process S28autofs (pid 825), cs:ip 73:0092914b
> printk: 197950 messages suppressed.
> 4gb seg fixup, process egrep (pid 973), cs:ip 73:008e8149
> printk: 116932 messages suppressed.
> 4gb seg fixup, process sendmail (pid 962), cs:ip 73:004d675f
> printk: 15 messages suppressed.
> 4gb seg fixup, process dhcpd (pid 941), cs:ip 73:00d20d7f
> printk: 108 messages suppressed.
> 4gb seg fixup, process sendmail (pid 962), cs:ip 73:004d675f
> printk: 15 messages suppressed.
> 4gb seg fixup, process named (pid 752), cs:ip 73:002f775f
> snip
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.