mount -t 9p
by Frank Murphy
http://www.linux-kvm.org/page/9p_virtio
Can this setup be added to a guest
in /etc/fstab?
or verbatim in /etc/rc.d/rc.local
I would like a fallback on guest for when
the network goes down as it does in branched\rawhide.
--
Regards,
Frank
http//www.frankly3d.com
11 years
qemu-kvm 199.99% Host cpu
by Frank Murphy
What is the best to set guest CPU at,
as guest seem to be hogging it all.
Host CPU:
# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 21
Model: 2
Stepping: 0
CPU MHz: 1400.000
BogoMIPS: 7046.78
Virtualization: AMD-V
L1d cache: 16K
L1i cache: 64K
L2 cache: 2048K
L3 cache: 8192K
NUMA node0 CPU(s): 0-7
Guest CPU:
# lscpu
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 2
Vendor ID: AuthenticAMD
CPU family: 21
Model: 1
Stepping: 2
CPU MHz: 3523.504
BogoMIPS: 7047.00
Virtualization: AMD-V
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
set in Virt-Manager as OpteronG4, copied from host.
--
Regards,
Frank
http//www.frankly3d.com
11 years
Re: [fedora-virt] F18 Host Only one Guest (currently) cannot connect to host, ping, web anything
by Frank Murphy
On Sun, 24 Mar 2013 12:29:26 +0000
Frank Murphy <frankly3d(a)gmail.com> wrote:
Can now ping both nics in the host.
But that as far as it goes.
Update F18 with all virt\qemu updates-testing.
No joy am unsure if firewalld problem,
though I have a checkmark against libvirt in public zone.
~$ dmesg | grep virbr0
[ 54.567869] device virbr0-nic entered promiscuous mode
[ 54.688887] virbr0: topology change detected, propagating
[ 54.689764] virbr0: port 1(virbr0-nic) entered forwarding state
[ 54.690613] virbr0: port 1(virbr0-nic) entered forwarding state
[ 54.749869] virbr0: port 1(virbr0-nic) entered disabled state
Mar 24 23:45:45 testvm kernel: [ 54.567869] device virbr0-nic
entered promiscuous mode
Mar 24 23:45:45 testvm kernel: [ 54.688887] virbr0: topology change
detected, propagating
Mar 24 23:45:45 testvm kernel: [ 54.689764] virbr0: port
1(virbr0-nic) entered forwarding state
Mar 24 23:45:45 testvm kernel: [ 54.690613] virbr0: port
1(virbr0-nic) entered forwarding state
Mar 24 23:45:45 testvm avahi-daemon[808]: Joining mDNS multicast
group on interface virbr0.IPv4 with address 192.168.1.1.
Mar 24 23:45:45 testvm avahi-daemon[808]: New relevant interface
virbr0.IPv4 for mDNS.
Mar 24 23:45:45 testvm avahi-daemon[808]: Registering new address
record for 192.168.1.1 on virbr0.IPv4.
Mar 24 23:45:45 testvm kernel: [ 54.749869] virbr0: port
1(virbr0-nic) entered disabled state
--
Regards,
Frank
http//www.frankly3d.com
11 years
F18 Host Only one Guest (currently) cannot connect to host, ping, web anything
by Frank Murphy
Installed my first guest F16 Xfce 32bit (EOL, test)
No virt-preview installed standard repos only.
Virt-Manager in use.
The default "virt-network is there"
have tried it both NAT and routed,
deleted it, re-installed no joy.
Both eth0, eth1 show up in "Network Interfaces" tab
with their DHCP ipv4 info (ipv6 disabled on host by choice)
~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.6 netmask 255.255.255.0 broadcast
192.168.0.255 ether 90:2b:34:98:cb:28 txqueuelen 1000 (Ethernet)
RX packets 60 bytes 9351 (9.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 51 bytes 5856 (5.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.193 netmask 255.255.255.0 broadcast
192.168.0.255 ether a0:f3:c1:00:56:bb txqueuelen 1000 (Ethernet)
RX packets 138 bytes 75894 (74.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 165 bytes 15167 (14.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 0 (Local Loopback)
RX packets 12 bytes 840 (840.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12 bytes 840 (840.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.1.1 netmask 255.255.255.0 broadcast
192.168.1.255 ether 52:54:00:c6:4c:07 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 854 (854.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
~]# rpm -qa | grep virt
libvirt-daemon-qemu-0.10.2.3-1.fc18.x86_64
virt-manager-0.9.4-4.fc18.noarch
libvirt-daemon-driver-interface-0.10.2.3-1.fc18.x86_64
python-virtinst-0.600.3-2.fc18.noarch
libvirt-daemon-driver-storage-0.10.2.3-1.fc18.x86_64
libvirt-daemon-config-nwfilter-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-libxl-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-nodedev-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-qemu-0.10.2.3-1.fc18.x86_64
libvirt-daemon-0.10.2.3-1.fc18.x86_64
libvirt-client-0.10.2.3-1.fc18.x86_64
virt-manager-common-0.9.4-4.fc18.noarch
libvirt-daemon-kvm-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-nwfilter-0.10.2.3-1.fc18.x86_64
libvirt-python-0.10.2.3-1.fc18.x86_64
virt-viewer-0.5.4-3.fc18.x86_64
libvirt-daemon-driver-network-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-xen-0.10.2.3-1.fc18.x86_64
libvirt-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-uml-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-lxc-0.10.2.3-1.fc18.x86_64
libvirt-daemon-config-network-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-secret-0.10.2.3-1.fc18.x86_64
cat default.xml <snipped>
<network>
<name>default</name>
<uuid>e5216e09-7d6d-7999-0327-67ca7ecc5c60</uuid>
<forward dev='eth1' mode='route'>
<interface dev='eth1'/>
</forward>
<bridge name='virbr0' stp='on' delay='0' />
<mac address='52:54:00:C6:4C:07'/>
<ip address='192.168.1.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.1.10' end='192.168.1.25' />
</dhcp>
</ip>
</network>
Booting F16-DVD in rescue mode on guest still no joy.
--
Regards,
Frank
http//www.frankly3d.com
11 years
Connection breaks for my macvtap
by Richa Marwaha
Hi
I am trying to run some KVM fuzz testing where I have a tool called scapy
running on my host and guest which changes the data in the IP header of the
packages and send it out to the host and vice versa. I have macvtap setup
on my host (have tried both VEPA and Bridge mode).
My ssh connection to my guest breaks down after having send just 22 packets
and also the gnome crashes. I see the following message in the dmesg
dbus[545]: [system] Rejected send message, 2 matched rules;
type="method_return", sender=":1.0" (uid=0 pid=499
comm="/usr/lib/systemd/systemd-logind ") interface="(unset)"
member="(unset)" error name="(unset)" requested_reply="0"
destination=":1.17" (uid=42 pid=658 comm="/usr/bin/gnome-session -f --debug
")
The connection to the guest restart but wanted to know what makes it
breakdown.
Regards,
Richa Marwaha
11 years
Re: [fedora-virt] F18 Host Only one Guest (currently) cannot connect to host, ping, web anything
by Frank Murphy
~]# firewall-cmd --get-active-zones
public: eth0 eth1 virbr0 (no ipv4 yet)
virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.1 netmask 255.255.255.0 broadcast
192.168.1.255 ether 52:54:00:c6:4c:07 txqueuelen 0 (Ethernet)
RX packets 196 bytes 23873 (23.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 67 bytes 14028 (13.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether fe:54:00:35:0e:16 txqueuelen 500 (Ethernet)
RX packets 83 bytes 9917 (9.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 299 bytes 19603 (19.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
--
Regards,
Frank
http//www.frankly3d.com
11 years
Fedora 18 host and two Centos-6.3 guest: how to shutdown guest?
by Dario Lesca
I have setup on a libvirtd Fedora 18 up to date two centos-6.3 server
(web and mail), but it seems that when I shutdown f18, the two hosts are
power off without shutdown.
How to ensure that the two guests are suspended, hibernate or shut down
properly? like Centos 6.3 host do?
I have missing some things?
Many thanks.
--
Dario Lesca - sip:dario@solinos.it
(Inviato dal mio Linux Fedora18+Gnome3)
11 years, 1 month