Built a xen server and went with the desktop, kde I think it was. Anyhow, created a couple of guests, both CentOS, all went well. Rebooting the host, servers came back, no problems. Decided to change startup init level to 3 and bypass desktop coming up. Now one guest comes up fine, the other came up in read only mode. Rebooted it and now it''s not coming up at all. Yet, checking on it, host says it''s running; virsh # dominfo crm-logi-192-59 Id: 4 Name: crm-logi-192-59 UUID: 01690336-0d39-fafb-ebf3-3c904b1925c6 OS Type: linux State: blocked CPU(s): 2 CPU time: 3.2s Max memory: 1048576 kB Used memory: 786432 kB Seems that it''s running but it''s lost it''s network connection as well now? But, even if it is running, something has gone weird. What should I be looking for next? /var/log/xen logs aren''t showing anything obvious either. There are some things in the debug log but there''s nothing which says anything about the particular guest so figure it''s unrelated. Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Forgot to add, ''xm console'' into the domain is not showing anything obvious. It seems to be stalling as it''s coming up. Here''s a snippet of the console login. 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 Xen virtual console successfully installed as xvc0 Event-channel device installed. Console: switching to colour frame buffer device 100x37 input: Xen Virtual Keyboard/Mouse as /class/input/input0 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new driver hiddev usbcore: registered new 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 md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered 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/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 176k freed Write protecting the kernel read-only data: 380k USB Universal Host Controller Interface driver v3.0 Registering block device major 202 xvda: xvda1 xvda2 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. audit(1234073445.344:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 audit(1234073445.676:3): policy loaded auid=4294967295 ses=4294967295 Anyone have any thoughts on what else I can do? Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Feb 8, 2009 at 12:56 PM, lists@grounded.net <lists@grounded.net> wrote:> Built a xen server and went with the desktop, kde I think it was. > Anyhow, created a couple of guests, both CentOS, all went well. Rebooting the host, servers came back, no problems. > Decided to change startup init level to 3 and bypass desktop coming up. Now one guest comes up fine, the other came up in read only mode. Rebooted it and now it''s not coming up at all.What dom0 is it? Is it Centos as well? What do you use as domU''s backend disk? Is it iscsi or remote storage? I seem to recall having a similar problem a long time ago. Turned out it was SAN problem (either storage or switches or fibers). Dom0 doesn''t experience this problem since on my case it was located on local drives. Try fsck domUs storage and mount it on dom0, see if it comes up with something. Regards Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Fajar,> What dom0 is it? Is it Centos as well?Yes, Centos, 2.6.18-92.1.22.el5xen, SMP on an HP multi-processor.> What do you use as domU''s backend disk? Is it iscsi or remote storage?The guest is a Centos 5.2 also, local storage only, nothing over the network right now. I''ve been putting the hardware together for this project and am using this server to build a few servers onto xen, then will migrate them over to a replacement server for production as each guest is tested and running as it should be.> Try fsck domUs storage and mount it on dom0, see if it comes up with > something.Ran it on local drive on reboot, no problems but guest still not showing up. # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 10908 8 r----- 119.0 crm-logi-192-59 2 768 2 -b---- 15.4 dns2-192-33 1 511 1 -b---- 14.7 Yes, xm shows that it''s running. When I console into the guest, still locked up; **SNIP** md: bitmap version 4.39 TCP bic registered 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/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 176k freed Write protecting the kernel read-only data: 380k USB Universal Host Controller Interface driver v3.0 Registering block device major 202 xvda: xvda1 xvda2 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. audit(1234110643.032:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 audit(1234110643.500:3): policy loaded auid=4294967295 ses=4294967295 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
When I do a xm list --long domain;
(state -b----)
(shutdown_reason poweroff)
(cpu_time 17.136254798)
(online_vcpus 2)
(up_time 1252.65520096)
(start_time 1234110635.1)
(store_mfn 359668)
(console_mfn 359667)
This is exactly the same as another guest which is running fine on the same
server.
This would be a pretty stressful time if this happened in production.
Mike
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> Hehehe. So I was right about the problem was in storage :DI didn''t say it wasn''t storage, I thought you asked if it was network storage :).> How did you find out it was corrupted? fsck -f SHOULD be able to > identify SOME problems, which is why I asked to fsck and mount domU''s > disk earlier.Well, here''s the weirdness. Trying to console into the guest got me nowhere and all I could see is what I posted. So I decided to go into init mode 5, desktop, then looked at the guest as it was booting and saw that it hung on a disk problem, requiring fsck. Fine, but, what''s weird to me is that rebooting the host, nothing was wrong with the local storage, it looked just fine but the guest''s storage, which is on the host, was messed up? I realize that the guest is in it''s own world for the most part but I didn''t expect this.> If both domU and dom0 located on the same drive, yet only domU is > corrupted, there is a possibility that somehow you may have mounted it > twice at the sametime: on dom0 and domU, or on two domUs. Xen (on > linux anyway) should prevent this, but if you force it to (like > putting phy://...,w! instead of just w) or if you''re on a shared-disk > setup (two dom0s accessing the same shared storage) it can happen.Don''t recall doing anything special but, there is something I did do with this particular guest. As I''ve been setting up hardware, I did try a few manual commands to see if I could migrate it to another machine. I wonder if I messed it up when I was doing that. Interesting but I sure wish there was a way of getting more info from command line when something goes wrong. Every xm and virsh information test I looked up returned nothing wrong with the guest, yet there it was, but it took desktop to see it. I''ve not found any info on where you automate turning on guests when the host boots and what I''ve done so far is to have virsh start in the rc.local. Bet that might be a problem if I accidentally have guests being turned on somewhere else when the host boots. Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users