[libvirt-users] Installation of libvirt on Ubuntu
by WANG Cheng D
Dear all,
I wonder if libvirt can work on Ubuntu.
As you know, it is very convenient to install libvirt on Fedora. I can download the libvirt packet from libvirt.org and install it using command ./configure, make and make install.
As I am going to install an open source simulation system named openairinterface, Ubuntu is the recommended OS, and I want to install the simulation system in libvirt lxc. (as you may know, there is another lxc user space tool on Ubuntu whose official website is "https://linuxcontainers.org", which I don't want to use).
My questions are:
1) Can I install libvirt on Ubuntu with the same installation steps as on Fedora (i.e., manually download the tar.gz packet and install it locally)? I found a link talking about installation libvirt on Ubuntu which installs something like "libvirt-bin" (https://help.ubuntu.com/lts/serverguide/libvirt.html). I am not sure if libvirt can be installed following this instruction?
2) How can I create the rootfs for a Ubuntu container if libvirt can be installed on Ubuntu? I create the rootfs for Fedora container using:
# yum --installroot=/root/fedora16linux container --releasever=19 install -y openssh, bridge-utils".
How can I achieve this on Ubuntu?
3) If libvirt can work on Ubuntu, Can a disk file on the host OS be exposed to a Ubuntu container just like on Fedora?
With my warmest regards,
Cheng Wang
10 years
Re: [libvirt-users] pty pairing host - guest
by Neel Basu
Getting no output on /dev/hvcNN
On Thu, Mar 19, 2015 at 3:15 PM, Daniel P. Berrange <berrange(a)redhat.com>
wrote:
> On Thu, Mar 19, 2015 at 01:29:37PM +0530, Neel Basu wrote:
> > HI!,
> >
> > I am using virt-manager GUI. There I can add a `Console Device` through
> > Add Hardware. I can add a virtio pty WITHOUT restarting the VM. also I
> get
> > a pty allocated to host machine say `/dev/pty/M`
> >
> > My expectation is this `host:/dev/pty/M` is connected with a
> > `guest:/dev/ttyN`. so If I open minicom or screen and write to
> > `host:/dev/pty/M` it will be propagated to 'guest:/dev/ttyN'. Is my
> > expectation correct ?
> >
> > If it is correct how will I know what is the guest tty allocated against
> > this host pty ?
>
> No, that's not how it works. The <console> devices are exposed to
> the guest as /dev/hvcNN devices. Starting with NN==0
>
> as per the dumpxml output
<console type='pty' tty='/dev/pts/1'>
<source path='/dev/pts/1'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
I expected host:/dev/pts/1 is paired with guest:/dev/hvc0
So I tried to communicate with minicom,echo,cat with these two but I saw no
output. what I echo on /dev/pts/1 doesn't pass to /dev/hvc0 or vice verse.
>
> > Similar to console device I can add a Serial device but that requires a
> > reboot of the guest VM. However I tried that though I prefer to do it
> > without a guest restart.
> >
> > <serial type='pty'>
> > <source path='/dev/pts/1'/>
> > <target port='0'/>
> > <alias name='serial0'/>
> > </serial>
> >
> > here also I expected host:/dev/pts/1 is paired with /dev/ttyS0 but
> couldn't
> > communicate.
>
> The serial port device supported is a 1990 era ISA bus serial port
> so there's no hotplug for that. Only the paravirt consoles can be
> hotplugged.
>
> Regards,
> Daniel
> --
> |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/
> :|
> |: http://libvirt.org -o- http://virt-manager.org
> :|
> |: http://autobuild.org -o- http://search.cpan.org/~danberr/
> :|
> |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc
> :|
>
10 years
Re: [libvirt-users] no luck with filesystem storage type [solved]
by Boylan, Ross
I needed one more option to make it work:
# mount -t 9p /mnt/SASInstaller /mnt/SASInstaller/
mount: wrong fs type, bad option, bad superblock on /mnt/SASInstaller,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
# mount -t 9p -o trans=virtio /mnt/SASInstaller /mnt/SASInstaller
The page you referenced also mentions using -oversion=9p2000.L. There is some additional info on the versions at
http://landley.net/kdocs/Documentation/filesystems/9p.txt; that page says .L is the default, while http://wiki.qemu.org/Documentation/9psetup#Starting_the_Guest_using_libvirt says it's .U. I don't know how to tell which I ended up with.
Thanks for the pointer.
Ross
________________________________________
From: Ján Tomko [jtomko(a)redhat.com]
Sent: Thursday, March 26, 2015 1:43 AM
To: Boylan, Ross
Cc: libvirt-users(a)redhat.com
Subject: Re: [libvirt-users] no luck with filesystem storage type
On Thu, Mar 26, 2015 at 01:37:06AM +0000, Boylan, Ross wrote:
> I have a directory on the host that I would like to be visible in the guest/domain. Using virt-manager I selected the directory, resulting in this configuration:
> <filesystem type='mount' accessmode='passthrough'>
> <source dir='/mnt/SASInstaller'/>
> <target dir='/mnt/SASInstaller'/>
> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
> </filesystem>
> I created the /mnt/SASInstaller manually in the VM.
>
> Nothing shows up. What am I missing? Do I need to run something in the VM (running Linux) to make it work?
You need to mount it:
mount -t 9p /mnt/SASInstaller /mnt/SASInstaller
The target 'dir' is not really a directory, it's just a mount tag.
See:
http://wiki.qemu.org/Documentation/9psetup#Starting_the_Guest_using_libvirt
Jan
10 years
[libvirt-users] no luck with filesystem storage type
by Boylan, Ross
I have a directory on the host that I would like to be visible in the guest/domain. Using virt-manager I selected the directory, resulting in this configuration:
<filesystem type='mount' accessmode='passthrough'>
<source dir='/mnt/SASInstaller'/>
<target dir='/mnt/SASInstaller'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</filesystem>
I created the /mnt/SASInstaller manually in the VM.
Nothing shows up. What am I missing? Do I need to run something in the VM (running Linux) to make it work?
Thanks.
Ross Boylan
10 years
[libvirt-users] libvirtd can't start
by 梅磊
Hi experts,
The libvirtd can’t start on my server after the server interruption
of power supply, the status is below:
[root@openstack3 libvirt]# service libvirtd status
Redirecting to /bin/systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
Active: failed (Result: signal) since Tue 2015-03-24 16:10:31 CST; 7min
ago
Process: 27372 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=killed,
signal=SEGV)
Main PID: 27372 (code=killed, signal=SEGV)
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000:
27383: debug : virFileClose:90 : Closed fd 22
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000:
27383: debug : virFileClose:90 : Closed fd 22
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000:
27383: debug : virFileClose:90 : Closed fd 22
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000:
27383: debug : virFileClose:90 : Closed fd 22
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.413+0000:
27383: debug : virFileClose:90 : Closed fd 22
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.413+0000:
27383: debug : virStateInitialize:847 : Running global init for netcf state
driver
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.413+0000:
27383: debug : virObjectNew:199 : OBJECT_NEW: obj=0x7f73f0080d00
classname=virNetcfDriverState
Mar 24 16:10:31 openstack3 libvirtd[27372]: ====== end of log =====
Mar 24 16:10:31 openstack3 systemd[1]: libvirtd.service: main process
exited, code=killed, status=11/SEGV
Mar 24 16:10:31 openstack3 systemd[1]: Unit libvirtd.service entered failed
state.
And the attachment is the log after restart the libvirtd.
After long time search on google, I didn’t get any useful information, so
anyone can give me some hint on this issue?
-BR,
Andy
10 years
[libvirt-users] machine='pc-q35-2.1' and sata controller
by Thomas Stein
Hello.
I'm not able to disable the sata controller on a machine='pc-q35-2.1' type VM.
Whenever i delete:
<controller type='sata' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x1f'
function='0x2'/>
</controller>
it gets added again when i close the editor.
The reason i would like to delete the sata controller is this error while
trying to migrate the machine:
2015-02-23 19:04:11.181+0000: 1972: error : qemuMonitorJSONCheckError:381 :
internal error: unable to execute QEMU command 'migrate': State blocked by
non-migratable device '0000:00:1f.2/ich9_ahci'
Someone has an idea to solve this?
thanks and cheers
t.
10 years
[libvirt-users] virsh dom state
by Fiorenza Meini
Hi there,
I'm running KVM under Openstack .
When I give virsh list command, I see some VM in NON persistent state.
What does it mean? How can I move it to a persisten state ?
I found that I cannot make a snapshot, from Openstack , of a machine
which is in a NON PERSISTENT state.
Regards
Fiorenza
--
Spazio Web S.r.l.
V. Dante, 10
13900 Biella
Tel.: +39 015 2431982
Fax.: +39 015 2522600
Numero d'Iscrizione al Registro Imprese presso CCIAA Biella, Cod.Fisc.e
P.Iva: 02414430021
Iscriz. REA: BI - 188936 Cap. Soc.: €. 30.000 i.v.
10 years
[libvirt-users] java binding in central maven repository
by Laszlo Hornyak
Hi,
The last libvirt artifact published to the maven central repository was
0.4.7 in 2011.
The libvirt.org/maven2 repository is updated, but
- sometimes the libvirt.org webserver is not responding and that breaks
the build.
- for similar reasons projects depending on other maven repositories can
not upload to central repository
Can we get back updates to maven central repo?
Best regards,
Laszlo
--
EOF
10 years
