Virtual Machine Console does not work neither VNC.


Cannot reach VM's console neither via VNC.

I've entered a new IP interval to be given to new VM's. However, i just cannot connect to them after i deploy them via Cloudmin.

OK.... Physical host is with a gateway A Xen host (working nicely) has ip.

A new Xen host with a new IP within the range with gateway cannot be reached after creation, neither via XM CONSOLE , neither VNC to VNC port .

Any clue ?




Does that new IP range perhaps need a different netmask?

Also, can you ping Xen instances on that IP range from the Xen host system?

I cannot reach any machine on that range.

And yes, different IP range takes a different gateway, not the one on the physical host, and since it is a 16 ip's network , it was a mask of 28 bits, i suppose.

Cheers Filipe

Wait, how many Xen host systems do you have here? Is it just one with two IP ranges, or two different systems?

If it is two, can you ping one of the Xen instances on the second host from the host itself?

It is a physical host with two ip ranges.... only one VM on first range, second VM's and new ones on the second one. I cannot ping from the physical host the VM's on the second IP RANGE, but i can reach and ping VM's on the first IP RANGE.


Also the Physical Host is on the first IP RANGE, and has no NIC configured on the second IP RANGE.

However i can ping the gateway of the second IP RANGE, provided by the datacenter supplier.

This may be a routing issue - it is possible that your system doesn't know how to route traffic to the second IP range.

Does it help if you add a route manually with a command like :

route add -net dev eth0

where XXX is the netmask given by your datacenter for the range.

I'll try to add that route

However, wouldn't XEN CONSOLE VM should work ?

because i do that like

>xen console suporte

and the shell hangs, or it seems to.... i can only get out using CTRL + 5 .

Strange isnt it? shouldn't I get sheel access to the VM directly ?


It still doesn't work

[root@hosting04 ~]# route add -net netmask dev eth0 [root@hosting04 ~]# ping PING ( 56(84) bytes of data.

--- ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3010ms

[root@hosting04 ~]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface * U 0 0 0 eth0 * U 0 0 0 eth0 * U 0 0 0 eth0 default UG 0 0 0 eth0 [root@hosting04 ~]#

using like you told me to, i get an error linke the one bellow.

[root@hosting04 ~]# route add -net dev eth0 Usage: inet_route [-vF] del {-host|-net} Target[/prefix] [gw Gw] [metric M] [[dev] If] inet_route [-vF] add {-host|-net} Target[/prefix] [gw Gw] [metric M] [netmask N] [mss Mss] [window W] [irtt I] [mod] [dyn] [reinstate] [[dev] If] inet_route [-vF] add {-host|-net} Target[/prefix] [metric M] reject inet_route [-FC] flush NOT supported

I did started the VM but, with XM LIST i get

[root@hosting04 ~]# xm list

Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 4242 8 r----- 17740.4 hosting03 1 3559 2 r----- 354357.8 suporte 8 255 1 -b---- 8.4

The suporte VM is still in b mode/state after more than 10 minutes ! a just installed machine should take that long.. should it?


Yeah, xm console not working is really odd..

What happens if you run :

cd /xen
xm destroy yoursystem
xm create -c  yoursystem.cfg

I get the console but then stops... no login shell, nothing!!!!

Check it

[root@hosting04 xen]# xm create -c dev.cfg Using config file "./dev.cfg". Started domain dev Bootdata ok (command line is root=/dev/sda1 ro) Linux version 2.6.18-92.el5xen ( (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Jun 10 19:20:18 EDT 2008 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) No mptable found. Built 1 zonelists. Total pages: 67584 Kernel command line: root=/dev/sda1 ro Initializing CPU#0 PID hash table entries: 2048 (order: 11, 16384 bytes) Xen reported: 2333.334 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Software IO TLB disabled Memory: 242868k/270336k available (2414k kernel code, 18952k reserved, 1349k data, 176k init) Calibrating delay using timer specific routine.. 5837.04 BogoMIPS (lpj=11674099) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 6144K CPU: Physical Processor ID: 1 CPU: Processor Core ID: 2 (SMP-)alternatives turned off Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1A7A0 could not acquire Mutex [2] [20060707] No dock devices found. ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1A7A0 could not acquire Mutex [2] [20060707] Brought up 1 CPUs PCI: Fatal: No PCI config space access function found PCI: setting up Xen PCI frontend stub 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 driver usbfs usbcore: registered new driver hub 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: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 8192 (order: 5, 131072 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered audit: initializing netlink socket (disabled) audit(1250112483.192:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 52394A11B61A91 - User ID: CentOS (Kernel Module GPG key) 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 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 XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vif/0 Write protecting the kernel read-only data: 461k Registering block device major 8 netfront: Initialising virtual ethernet driver. netfront: device eth0 has flipping receive path. USB Universal Host Controller Interface driver v3.0 SCSI subsystem initialized register_blkdev: cannot get major 8 for sd Adaptec aacraid driver 1.1-5[2453] Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: 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.

To get out of it I had to press Ctrl + 5


Ok, that looks like it did actually boot .. sometimes you don't get to see the init boot messages in the Xen console.

If you still can't ping the system, I would be happy to try SSHing in myself to see what is going wrong. It is almost certainly a networking issue, due to the second IP range being on a different subnet from eth0.