10 More Discussions You Might Find Interesting
1. Linux
Hello, I installed FreeBSD 10.3 on AQEMU. I can't connect to internet in none
of the modes of "Default, User-Mode Networking" and "TUN/TAP Networking".
I am able to ping my host in the TAP networking mode (192.168.1.33 which is my
IP addr in guest), but getting 'no route to host' for any... (1 Reply)
Discussion started by: temp-usr
1 Replies
2. Red Hat
Background : - Need to create addition 40G storage for VM guest.
1. I have created new KVM - VM guest on RHEL 5.8 server hosting server.
2. Hosting server has occupied all size with LV and there is not space to create new LV.
3. I tried to achieve this requirement by creating 40G file size and... (1 Reply)
Discussion started by: Nats
1 Replies
3. UNIX for Advanced & Expert Users
Im looking for the commands that can be executed to fetch the OS Version of the VMs running on the below Hypervisors.
Xen (Not the citrix Xen server, but the Xen Sever hosted on a ubuntu Machine)
KVM (0 Replies)
Discussion started by: ranvirsingh
0 Replies
4. UNIX for Dummies Questions & Answers
As the title suggests I ran into a little problem trying to create a virtual machine of Kali Linux usign Qemu inside OpenBSD. I edited the example Kali Linux gave on their website here to the following for BSD:
qemu-system-i386 -hda ./kali.qcow2 -boot d -cdrom ./kali-linux-1.0.5-i386.iso -m... (0 Replies)
Discussion started by: Azrael
0 Replies
5. UNIX for Advanced & Expert Users
Hi,
I have an problem with ACLs over NFS3. The Problem is, when i mount a nfsshare from an KVMguest, the UnixACLs were not mapped too. I don't know why. But this is only when i have the NFSshares on an virtulamachine. When i do the same with ein real machine, ACLs work well.
You can see that:... (4 Replies)
Discussion started by: darktux
4 Replies
6. UNIX for Advanced & Expert Users
Hi,
I've a CentOS Server and I need to create KVM guest machine without X.
/usr/sbin/virt-install --name server1 --ram 4000 --vcpus=8 --file=/srv/virtual/server1.img --file-size=20 --cdrom /tmp/server1.iso --mac=52:54:00:fd:48:7c
The iso was created with cobbler...
So, now the machine is... (5 Replies)
Discussion started by: hiddenshadow
5 Replies
7. Red Hat
I used the redhat RHEL6 boot with initrd but it failed, can sb help me
# /usr/libexec/qemu-kvm --enable-kvm -smp 8 -m 1024 -net nic,model=virtio -net tap,script=/etc/qemu-ifup -initrd /boot/initramfs-2.6.32-279.el6.x86_64.img -kernel /boot/vmlinuz-2.6.32-279.el6.x86_64 -append "root=/dev/ram... (4 Replies)
Discussion started by: yanglei_fage
4 Replies
8. Red Hat
Hi All,
I have RHEL 5u4 physical system with 2 Qlogic fc cards. It hosts 2 KVM virtual machines which are also running RHEL 5u4 OS. After all these I have created a virutal HBA (refered in google) successfully on the base OS. But the same is not visible to guest OS.
My question here is,
... (1 Reply)
Discussion started by: Vichu
1 Replies
9. Virtualization and Cloud Computing
Howdy
I am using Fedora12 with KVM, with XP64pro as a guest. Everything seems to be working just fine, BUT I can't Save. When I do instruction KVM to save, I get a continuing Saving display, but it continues for a long time until I finally terminate it due to boredom :) I have let it run for... (0 Replies)
Discussion started by: TJMan
0 Replies
10. Red Hat
Hello,
I have a KVM system running on RHEL 5.4. It hosts 4 guest VMs. One of the guest host fails to get back the mounted filesystems after the system reboots. Does anyone have any idea what the issue could be?
Regards,
Mahive. (1 Reply)
Discussion started by: mahive
1 Replies
VDEQ(1) General Commands Manual VDEQ(1)
NAME
vdeq - Virtual Distributed Ethernet wrapper for QEMU/KVM virtual machines
SYNOPSIS
vdeq qemu [ --mod octalmode ] QEMU_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] QEMU_OPTIONS
vdeq kvm [ --mod octalmode ] KVM_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] KVM_OPTIONS
vde{qemu_name} [ --mod octalmode ] QEMU_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] QEMU_OPTIONS
OLD SYNOPSIS
vdeq qemu [ --mod octalmode ] [ -sock socketpath [ ,socketpath [ ,... ] ] ] [ qemu_args ]
vde{qemu_name} [ -sock socketpath [ ,socketpath [ ,... ] ] ] [ qemu_args ]
DESCRIPTION
vdeq is a wrapper to start a QEMU/KVM virtual machine connected to a VDE network. It uses the qemu/kvm -tun-fd parameter to set up the
connection with a vde_switch.
The command
vdeq qemu -b c -hda=sampledisk
starts a qemu machine which boots from the sampledisk image and has a ne2000 ethernet interface connected to the standard vde_switch. The
command
vdeq kvm -b c -hda=sampledisk
starts a kvm machine which boots from the sampledisk image and has a ne2000 ethernet interface connected to the standard vde_switch.
It is also possible to create symbolic links to the vdeq executable to have a simpler command. If the link has a name that begins with vde
the remaining part of the name is taken as the qemu command. For example if vdeq is linked to vdeqemu:
vdeqemu -b c -hda=sampledisk
starts qemu as above. If vdeq is linked to vdekvm:
vdekvm -b c -hda=sampledisk
starts kvm with the same parameters.
The new syntax is consistent with the new Qemu 0.8.0 network parameters. Using vdeq is possible to specify a vde interface in the same way
as user,tap or socket interfaces. The sock= parameter can be used to use a specific socket. Please note that what qemu names as vlan is
not related to the 802.1q VLAN managed by the vde_switch. port= can be used to specify the port of the switch, otherwise the first allo-
catable port is assigned. The following command run a qemu VM with two ethernet interface connected to the standard switch and to the
switch with local socket "/tmp/my.ctl", port 10, respectively
vde qemu -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10
vdeqemu -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10
The following command run a kvm VM with two ethernet interface connected to the standard switch and to the switch with local socket
"/tmp/my.ctl", port 10, respectively
vde kvm -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10
vdekvm -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10
The old syntax can be used with Qemu 0.8.0 but all the vde interfaces are assigned to vlan 0.
vdeq qemu -sock /tmp/vde.ctl,/tmp/my.ctl -b c -hda=sampledisk
vdeqemu -sock /tmp/vde.ctl,/tmp/my.ctl -b c -hda=sampledisk
both start qemu with one ethernet interface connected both to the standard switch and to the switch with local socket "/tmp/my.ctl".
OPTIONS
--mod octalmode, specify the mode for comm socket.
-sock socketpath, specify the UNIX socket to be used by local programs for joining the VDE. The default value is "/tmp/vde.ctl" It is
also possible to indicate several socketpath (comma separated, no blanks): in this case several interfaces are defined. The first
socketpath is connected to the first ne2k interface and so on.
-h, -help, --help
print a Usage help.
NOTE
Qemu has changed its syntax for networking (cvs Nov.15 2005). As a temporary solution use vdeoq and vdeoqemu instead of vdeq and vdeqemu
if you are running a qemu with the old syntax.
By default qemu uses the same MAC address for every virtual machine, so if you plan to use several instances of qemu be sure to explicitly
set a different MAC address for each virtual machine. While generating your address beware to not use broadcast/multicast reserved MACs,
ethernet rules say: the multicast bit is the low-order bit of the first byte, which is "the first bit on the wire". For example
34:12:de:ad:be:ef is an unicast address, 35:12:de:ad:be:ef is a multicast address (see ETHERNET MULTICAST ADDRESSES section in
http://www.iana.org/assignments/ethernet-numbers for more informations).
NOTICE
Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik"
i.e. the German "Association for Electrical, Electronic & Information Technologies").
SEE ALSO
vde_switch(1), vde_plug(1), vde_plug2tap(1), dpipe(1).
AUTHOR
VDE is a project by Renzo Davoli <renzo@cs.unibo.it>
Virtual Distributed Ethernet December 6, 2006 VDEQ(1)