Errors in my `dmesg`
...
[ 0.000000] efi: EFI_MEMMAP is not enabled.
[ 0.000000] esrt: ESRT header is not in the memory map.
...
[ 17.560906] Could not initialize VPMU for cpu 0, error -38
...
[ 20.600298] systemd[1]: Failed to start Load Kernel Modules.
...
[ 21.293191] Error: Driver 'processor_aggregator' is already
registered, aborting...
...
[ 21.639418] Error: Driver 'processor_aggregator' is already
registered, aborting...
...
[ 23.021708] BTRFS error (device sda2): could not find root 8
[ 23.021791] BTRFS error (device sda2): could not find root 8
...
On 10-02-16 15:47, Folatt wrote:
I just tried systemd-networkd. I can finally access both my Dom0
and DomU at the same time :).
It now looks like this:
[code]
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
fq_codel master xenbr0 state UP group default qlen 1000
link/ether d0:50:99:8f:1e:31 brd ff:ff:ff:ff:ff:ff
inet6 2001:983:8610:1:d250:99ff:fe8f:1e31/64 scope global
noprefixroute dynamic
valid_lft 5831sec preferred_lft 3322sec
inet6 fe80::ebb8:6b64:34bf:49de/64 scope link
valid_lft forever preferred_lft forever
4: xenbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP group default qlen 1000
link/ether d0:50:99:8f:1e:31 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.113/24 brd 192.168.178.255 scope global
dynamic xenbr0
valid_lft 860091sec preferred_lft 860091sec
inet6 2001:983:8610:1:d250:99ff:fe8f:1e31/64 scope global
noprefixroute dynamic
valid_lft 5831sec preferred_lft 3322sec
inet6 2001:983:8610:1:6424:4bff:feb3:ea82/64 scope global
deprecated noprefixroute dynamic
valid_lft 2231sec preferred_lft 0sec
inet6 fe80::6424:4bff:feb3:ea82/64 scope link
valid_lft forever preferred_lft forever
5: vif2.0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
fq_codel master xenbr0 state UP group default qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcff:ffff:feff:ffff/64 scope link
valid_lft forever preferred_lft forever
[/code]
"Did you happen to specify the address d0:50:99:8f:1e:31
explicitly in your config anywhere?"
No.
"Use `netstat -l -p` on Dom0 to verify qemu is listening for VNC
clients."
I used `nmap localhost` and `ss -lnpt` and got this:
[code]
PORT STATE SERVICE
22/tcp open ssh
5900/tcp open vnc
State Recv-Q Send-Q Local
Address:Port
Peer Address:Port
LISTEN 0
1
*:5900
*:*
LISTEN 0
128
:::22
:::*
[/code]
"Do a simple connectivity test using netcat from the remote
machine to local Dom0."
Never used it before. I typed `nc hypervisor 5900` and got this:
[code]
RFB 003.008
[/code]
"Try connecting to the VNC server"
I typed `vncviewer hypervisor`
and got a window with a black screen where my mouse pointer turns
into an open dot. The window has the title: TightVNC: QEMU
(ArkOS_Dev)
"see if `dmesg` provides any helpful information"
I see a cpu and filesystem error, but nothing serious. I probably
need to recheck my xen configurations, because I changed
computers.
"Could not initialize VPMU for cpu 0, error -38"
https://gist.github.com/Folatt/ff48d2d9b0509d27a448
"Check /var/log/xen/qemu-dm-<name>.log for qemu errors."
[code]
(process:4053): GLib-WARNING **: gmem.c:482: custom memory
allocation vtable not supported
[/code]
There's also systemd-networkd, which personally I find
easiest to use for bridges and other virtual devices (just not
for wireless). It coexists with netctl just fine, and iproute2
with some additional care. See
https://wiki.archlinux.org/index.php/systemd-networkd
https://www.freedesktop.org/software/systemd/man/systemd-networkd.service.html
I don't think the bridge itself (xenbr0) actually needs an IP
address, since enp3s0 and vif2.0 are both slaves of the
bridge. One problem I do see is that enp3s0 and xenbr0 both
have the same MAC address, which I think is incorrect
(although I could be wrong). Did you happen to specify the
address d0:50:99:8f:1e:31 explicitly in your config anywhere?
Also note that unless you installed a VNC server inside the
guest yourself, the guest doesn't even need a network adapter
in order for VNC to work. The qemu process inside Dom0 is what
listens for VNC clients (with "vnc = 1" or "vfb = ['vnc=1']"
in xl.cfg(5)). Make sure you specified "vnclisten=0.0.0.0" in
your xl config, as qemu only listens for VNC clients on
localhost by default. This applies to xen vfb (PV) and the
qemu emulated graphics cards (HVM), but with a different
syntax, see http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html
Here are some general recommendations: Use `netstat -l -p` on
Dom0 to verify qemu is listening for VNC clients. Do a simple
connectivity test using netcat from the remote machine to
local Dom0. Make sure there's no firewall interfering (i.e.
unknowingly filtering link-layer frames). Try connecting to
the VNC server and see if `dmesg` provides any helpful
information. Check /var/log/xen/qemu-dm-<name>.log for
qemu errors.
Quoting "Daniel E. Shub" <daniel.e.shub@xxxxxxxxx>:
You can setup a bridge in Arch in a number of ways. I
personally think
doing it with iproute2, like you are, is more difficult than
with
netctl (which is also part of base). With iproute2 you have
to write
your own systemd service and make sure you get the right
load order.
For example, I think you want the bridge service to start
before the
network comes up. With netctl you just need to create a
configuration
file in /etc/netctl/ and then you can enable it on boot with
"netctl
enable". The Arch Wiki has a pretty good walk through:
https://wiki.archlinux.org/index.php/Bridge_with_netctl.
On Tue, Feb 9, 2016 at 12:38 PM, Simon Hobson <linux@xxxxxxxxxxxxxxxx>
wrote:
Folatt <folatt@xxxxxxxxxxxx>
wrote:
Arch Linux
Not familiar with that one. In Debian it's as simple as
putting this stanza in /etc/network/interfaces
auto br0
iface br0 inet static
bridge_ports eth0
address 192.168.xxx.yyy
netmask 255.255.255.0
I see from https://wiki.archlinux.org/index.php/Network_bridge
that this isn't an option for Arch.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxx.orghttp://lists.xen.org/xen-users
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator™ to keep your
email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
No Bandwidth Quotas! 15GB disk space!
Commercial and Bulk Mail Options!
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
|
