[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Basic Question: Accessing the console on Dom0 (Xen4.5-Ubuntu1504)
Hi Jeff, On Mon, 17 Aug 2015 03:45:34 +0000 Jeff Murdoch <dochsavage@xxxxxxxxx> wrote: > Many thanks. That helped a bit. I'm able to switch to tty1 and > tty2, etc which gives some flexibility. > Going back to the UI via startx is another issue; just getting a blank > screen with a cursor. Still, an improvement. > Meanwhile, in Xen-land, I've been able to set up the usual networking > in /etc/network/interfaces. > That is, I can ping external sites. > The indications I'm seeing here seem to indicate that the dom0 (Ubuntu > 15.04) O/S is having trouble touching the hardware. > The most lowlevel messages seem to be coming from "mcelog", like so: > > mcelog --client > mcelog: client connect: No such file or directory > mcelog: client command write: Transport endpoint is not connected. > mcelog: client read: Invalid argument Xen is working fine for me in Xubuntu 15.04 with kernel 4.1.5 http://linuxg.net/install-kernel-4-1-x-on-ubuntu/ I recommend http://xubuntu.org/ . # uname -a Linux planb 4.1.5-040105-generic #201508101730 SMP Mon Aug 10 21:44:30 UTC 2015 i686 i686 i686 GNU/Linux # xl list Name ID Mem VCPUs Domain-0 0 4094 4 freebsd-11.hvm 1 2048 2 > I see a lot of rss-counter state errors and and "Segmentation fault > (core dumped)" messages, which just can't be good. > The rss messages look thus: > [timestamp] BUG: Bad rss-counter state mm:ffff880415295180 idx:1 > val: 2 (idx and val values vary) > Segmentation fault (core dumped) > When I use startx to bring up a new UI and start a terminal, I was > able to try to start firefox: > > firefox & > GLib -CRITICAL **: g_slice_set_config: assertion 'sys_page_slice=0' > failed. Chrome is working fine for me. # dpkg -l | grep google-chrome ii google-chrome-stable 44.0.2403.155-1 i386 The web browser I recommend chrome. http://aosabook.org/en/posa/high-performance-networking-in-chrome.html Tuning improves the performance # grep -r GRUB_CMDLINE_XEN_DEFAULT /etc/default/grub GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=4096M,max:4096M" http://wiki.xenproject.org/wiki/Xen_Project_Best_Practices http://wiki.xenproject.org/wiki/Tuning_Xen_for_Performance > And in desperation, I consulted "top" to see what is running. I see > a lot of error handling. > - apport > - oopsie > - upstart > - update-manager (?) > I'm obviously not sure about the details, but this collection of > messages seems to point to a serious disconnect between dom0 (Ubuntu > 15.04) and my hardware: Asus Formula V (latest 2012 BIOS). > Hopefully, the above info will ring some bells. Is trying a full > re-install with Ubuntu 14.04 LTS something I should consider here? I'm running it on Lenovo E130 with 8GB memory. Bridge is working fine with openvswitch and disabled NetworkManager https://help.ubuntu.com/community/NetworkManager#Disabling_NetworkManager "Using Open vSwitch" https://help.ubuntu.com/community/Xen # dpkg -l | grep openvswitch ii openvswitch-common 2.3.1-0ubuntu1 i386 Open vSwitch common ii openvswitch-switch 2.3.1-0ubuntu1 i386 Open vSwitch switch # cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual allow-hotplug ovsbr0 iface ovsbr0 inet dhcp bridge_ports eth0 # ovs-vsctl show b170c8d6-642a-4deb-adbc-3333331e6df7 Bridge "ovsbr0" Port "ovsbr0" Interface "ovsbr0" type: internal Port "eth0" Interface "eth0" ovs_version: "2.3.1" HTH, Cheers -vlado > Best regards, > Doch > > On Thu, Aug 13, 2015 at 6:35 AM, Matthias Hoffmann > <debian@xxxxxxxxxxxxxxxx> wrote: > > Hi, > > > Here's the newbie bit: I can't open the console. I have to kill > > > GNOME > > to get a CLI. > > > If I try the usual Control-Alt-T method or even the > > > right-click-menu to > > open a console, the session quickly slows to a crawl then halts. A > > hard restart is only way out at this point. > > Sounds really strange, open a CLI should not be a problem at this > > point. > > Afaik you could use Control+Alt+F2 [Or F3, F4, etc.] to switch to > > tty2 [3, 4 ..] with Gnome installed. BTW maybe this helps: > > http://askubuntu.com/questions/403819/ctrlaltt-not-working > > Best regards, > > Matthias > > > > *Von:* xen-users-bounces@xxxxxxxxxxxxx [mailto: > > xen-users-bounces@xxxxxxxxxxxxx] *Im Auftrag von *Jeff Murdoch > > *Gesendet:* Donnerstag, 13. August 2015 04:31 > > *An:* xen-users@xxxxxxxxxxxxx > > *Betreff:* [Xen-users] Basic Question: Accessing the console on Dom0 > > (Xen4.5-Ubuntu1504) > > Hi, > > I'm something of a Xen padawan, but I've jumped in both feet, and > > so, of course, I'm stuck. > > I've installed Ubuntu 15.04 on LVM, > > followed by the usual apt-get update-of-everthing, > > followed by the installation of the Xen 4.5 hypervisor package. > > So far, so good, as I can boot easily via Grub2 into the Xen > > hypervisor O/S (dom0). > > My next step would be to open a console and configure networking > > (bridge). > > Here's the newbie bit: I can't open the console. I have to kill > > GNOME to get a CLI. > > If I try the usual Control-Alt-T method or even the > > right-click-menu to open a console, the session quickly slows to a > > crawl then halts. A hard restart is only way out at this point. > > I saw a reference regarding tty2 being the dom0 console location. > > What have I missed here? Hopefully, something obvious. > > Best regards, > > Doch Attachment:
pgph9hBNgMKAU.pgp _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |