[libvirt-users] Virtualbox HOWTO?
by Dr. Boris Neubert
Hi,
I have the latest libvirt from the git repo successfully compiled and up
and running under CentOS 6.5. I can connect to the daemon (started with
/usr/local/sbin/libvirtd -d --listen) both locally and remotely.
I cannot see my virtualbox virtual machines. They run as the user
"virtualbox". I connect with
virsh -c vbox+tcp://virtualbox@vmserver/session
and all
list --all
gets me is
Id Name State
----------------------------------------------------
I probably miss something elementary, especially because I am not asked
for a password for the virtualbox user and did not configure any
machines beforehand. But I did not find how do to the trick in the
documentation.
Anybody out there with a working Virtualbox setup can help me out?
Thanks and kind regards,
Boris
10 years, 4 months
[libvirt-users] newbee questions
by John Smith
Hi,
Im very new to virtualization on Linux, wanting to kick the tires
some, and am wondering where best to go next.
Right now, ive done the 'all in one install' of ovirt 3.4 on a single
fedora 19 machine. Its a desktop with a wifi network interface, and im
trying to set up the kvm hypervisor in combination with macvtap. Any
pointers to docs on what best to do next is appreciated. Im currently
trying to make sense of this:
http://www.ovirt.org/Quick_Start_Guide
Also, as far as I can tell, there seems to be an issue with the
detection of my wireless wifi network interface 'wlp2s0' as it doesnt
seem to show up anywhere in the interface. I can attach the
'ovirtmgmt' network to my standard wired ethernet interface 'p2p2',
but that device is not in use on the machine and it is disconnected
from the network.
Reading about linux virt and issues with bridging with wifi NIC's on
the web made me, perhaps incorrectly here, assume that a wifi nic
might be an issue, so thats where the idea to use macvtap came from.
Manual setup of macvtap seems to work, as i can do this without issues
on a root prompt on the same machine:
ip link add link wlp2s0 name macvtap0 type macvtap
ip link set macvtap0 address 1a:46:0b:ca:bc:7b up
ip link show macvtap0
But the wifi interface 'wlp2s0' does not seem to show up in the ovirt
web gui interface.
Im sorry if I sound confusing here, but that may be just because im
really still confused about ovirt.
;)
So any pointers on what to read up on or do next is appreciated,
Thanks,
Regards,
John Smith.
10 years, 4 months
[libvirt-users] Corrupt image?
by mattias
I took a gzipped qcow2 image
And do a gunzip on it
But what?
[root@mjw vm]# fdisk w.qcow2 -l
Disk w.qcow2: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
[root@mjw vm]#
The disc should not be 0 mb!!!
The disc worked before i gzipped it
10 years, 4 months
[libvirt-users] virsh update-device: need to clear network filters
by Oleg Bondarev
Hi,
Can anyone please help with the following: I have a running instance with
interface
<interface type='bridge'>
<mac address='fa:16:3e:ba:a4:67'/>
<source bridge='br100/>
<target dev='vnet0'/>
<model type='virtio'/>
<filterref filter='nova-instance-instance-00000001-fa163ebaa467'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</interface>
what I need is to clear network interface on the instance. I tried virsh
update-device with following xml:
<interface type='bridge'>
<mac address='fa:16:3e:ba:a4:67'/>
<source bridge='br100/>
<model type='virtio'/>
</interface>
but this results in the following error:
$ sudo virsh update-device 13 xml.xml --persistent --live --config
error: Failed to update device from xml.xml
error: End of file while reading data: Input/output error
error: Failed to reconnect to the hypervisor
and libvirt is restarted. Is it possible to clear nw filter at all?
Thanks,
Oleg
10 years, 4 months
[libvirt-users] Some odd quriks of libvirt and xen on fedora 20.
by Alvin Starr
for pv systems the vnc console display is on the correct port with the
following call do qeum-dm
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -domain-name
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: paravirt
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -vnc
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: 127.0.0.1:1
but for hv systems xl is being passed
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -domain-name
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: fullvirt
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -vnc
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: 127.0.0.1:0
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -vncunused
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -serial
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: pty
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -videoram
libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: 8
Where would I look to correct this?
--
Alvin Starr || voice: (905)513-7688
Netvel Inc. || Cell: (416)806-0133
alvin(a)netvel.net ||
10 years, 4 months
