[libvirt-users] So why does "destroy" not actually destroy?
by KARR, DAVID
I thought it odd that if I have a running VM and I do "virsh destroy" it results in a VM that is "shut off". To ACTUALLY destroy a VM, you have to follow that with "undefine". Could someone elaborate on how we ended up with these slightly confusing semantics?
9 years
[libvirt-users] Debug VM boot from ISO issues
by KARR, DAVID
I'm having trouble booting a VM from an ISO, but my problems may not be virtualization issues, just general confusion.
I'm running virt-manager on Ubuntu, but I need to boot a VM with an ISO that is based on CentOS. Is that possible?
How do I define the VM in virt-manager to boot from an ISO? I initially created the VM with virt-install, but I started over with virt-manager, and now I'm not sure how to specify the ISO to boot from.
9 years
[libvirt-users] IPMI in Libvirt
by Anderson Kaiser
Greetings all,
I am looking for a solution to use IPMI (BMC) in with LibVirt (Virt-Manager). Actually there is a Customer behind this request as well.
Trying to be short: We are looking for a Solution in OpenStack Environment. Customer wants to have the entire environment running in Virt-Manager (probably for a P.O.C or tests purposes). So here is what he is trying to do: http://red.ht/1HfNn9r
This template you can find in the Red Hat's OpenStack Install Guide. So far so good. But OpenStack works with High Availability and in some moment of the procedure you have to create an IPMI (BMC) interface in order to Fence the HA Nodes and Controllers.
(Just for curiosity in this first moment customer is setting the Nodes - Hypervisors - as Nested KVM - so he can use the VM as an Hypervisor as well).
That said the 3 VMs which are the controller, and also the 2 nodes, should have an IPMI Interface. Is it possible to have it in KVM? I mean, seems that in SeaBIOS we already have this support: http://www.seabios.org/pipermail/seabios/2012-August/004405.html
Also I found a Red Hat BugZilla regarding this request: https://bugzilla.redhat.com/show_bug.cgi?id=815136 . but it seems to be "abandoned" since the beginning.
So the point is:
- Is it possible to have a NIC or a Device emulating an IPMI (BMC) interface?
- If yes, how can we export it to the VM?
Maybe we can do a pass-trough if the hardware is available. But Lets think in a Notebook or a Desktop, for instance (we are working with a POC, remember?) and maybe the IPMI Interface could not be available or oesn't exist.
I thought if it was possible to have some kind of IPMI NIC emulated and also an "brdge" and then an additional virtual network for this bridge. Am I going to far? ;-)
Anderson Kaiser (RHCE, RHCVA)
Team Lead - Red Hat Global Support Services Latin America
Red Hat Inc,.
akaiser(a)redhat.com
Ph: +55 11 3529-6000
Red Hat Support: 0800-602-5222
9 years
Re: [libvirt-users] Migrate Win2k3 to KVM
by Pierre Schweitzer
On 07/13/2015 03:25 PM, Ruzsinszky Attila wrote:
> - - cd ControlSet001
>> - - cd Control
>> - - cd CriticalDeviceDatabase
>> - - Check you have the following keys: primary_ide_channel,
>> secondary_ide_channel, pci#ven_8086&dev_7010, pci#ven_8086&dev_7111
>> keys. Some will be missing (otherwise, you'd boot ;-)).
>>
> Here is my keys:
> ...
> <pci#cc_0600>
> <pci#cc_0604>
> <pci#ven_8086&dev_244e>
> <pci#ven_8086&dev_27b8>
> <pci#ven_8086&dev_27c0>
> <pci#ven_8086&dev_27d0>
> <pci#ven_8086&dev_27da>
> <pci#ven_8086&dev_27df>
> <pci#ven_8086&dev_27e0>
> <pci#ven_8086&dev_27e2>
> <pci#ven_9005&dev_0080&subsys_e2a09005>
> <primary_ide_channel>
> ...
>
> Can I remove them and add the new ones what you wrote me?
Let the one already in place, and just add the missing ones. Existing
ones won't cause troubles.
> Do I type in the registy entries under [1] and [2] exactly using copy paste?
Yup.
> I'll check those vendor IDs above.
>
> How can I check the ones what Qemu using? (IDE/SATA/SCSI/Virtio)
One easy way to find out is to use lspci -nn in a Linux host running
Qemu with your target configuration.
For instance, for the IDE bus, you'll get something like:
00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE
[Natoma/Triton II] [8086:7010]
--
Pierre Schweitzer <pierre(a)reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
9 years
Re: [libvirt-users] Migrate Win2k3 to KVM
by Pierre Schweitzer
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 07/13/2015 09:58 AM, Ruzsinszky Attila wrote:
>> Here is the first problem. I can't mount sdi1! sdi1 not
>> existent.
>>> :-(
>>
>> What if you partprobe /dev/sdi?
>>
> Nothing. Empty output.
When partprobe properly works (ie encounters no error), it doesn't
print anything to console, it just adds the appropriate entries in /dev.
(I guess some answers got lost on libvirt-users, sorry about that).
- --
Pierre Schweitzer <pierre(a)reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVo4GDAAoJEHVFVWw9WFsLEpAP/jXOTqFf+Uog9/J5iuBh9ktU
X4tEPEBa6j2V8Pkyv5YHKFe1T4JWvZw0AcbAuEQMS0glt3PUY7lsKFmqcYzJEukB
w95vqMbvtguRneMh1G9tbEdOk47/T0zEnDXBz6/wyHGxkz3xGNqkoD6gxL0w2gui
5WAAdv8CPKptUZKKWGxABdZBxMobUNwtowTL0/Ir5BEiMl9wCHbgq6NOrU4Aungm
kjLfR6BcecUkYh9lFeiyakYuENohNkZiP1f+zA8AlsZQDwAZP5Qe/J1vvfdawLiW
pmYOT8Cmb6lp+O9iZhIQCAcE8EgZ9I6O0+J1vbVESSb+s4V1p1/Psu5zNqYMHMZJ
3He9X1Jj8vD0qliPW/YpRVMyRde77H7NNHSuX9QU/3Z2RFMLLT5Hx0ywElDLYJI/
aYiQgD1+bEp8T6frpmaowj1jXt7OraLnblaa92md4vwMm0Bl/Oui7y+kr5XO1gjD
yri+YxAtptdge6nm2evLorQFrRi5DaVbjx0WPPHY2UJActo9lCHMciCyzAnUpsz3
c99Vlvk8jc2gTywst/rRgs7Ww9S+rxIRJZ6vck/lIjMjviIViH3aN0sQRB0cynLp
DPhkB/Yedmj8PpNQstl8srg1D34Itir80Ve/uk7/vdlZp1D1670r7nXN6p46IGh5
Fn3/SNUE5Hfa0DBSqo9o
=ovns
-----END PGP SIGNATURE-----
9 years
Re: [libvirt-users] Migrate Win2k3 to KVM
by Ruzsinszky Attila
Hi Vincent,
I can access to the source physical machine but it is an almost 24h running
machine.
I heard about VMware P2V program. I've never used it, yet.
I don't want to virtio. I want a booting W2k3. That's all. ;-)
TIA,
Ruzsi
9 years
[libvirt-users] Migrate Win2k3 to KVM
by Ruzsinszky Attila
Hi,
I made a disk image with CloneZilla from the original physical machine.
That image was restored on an iSCSI volume.
It isn't booting. I got BSOD.
I tried IDE, SATA, SCSI disk type without any success.
I tried to using virtio driver and if I use my image+W2k3 install CD+virtio
VFD the Windows repair console see the disk and I can use the repair
console with my image but the windows not start
(or not booting because the system disk can't be seen by original
"registry").
The drivers from virtio VFD image were copied to Windows' Driver directory
manually.
I tried to use virt-win-reg:
rattila@amd1:~$ virt-win-reg SJ-SIMISPC
/dev/disk/by-path/<iSCSI-path>:simispc-lun-2: Engedély megtagadva at
/usr/bin/virt-win-reg line 260.
(it means: Permission denied.)
What can I do changing the original driver to virtio (or IDE/SATA/SCSI in
KVM)?
I can't do anything with the physical machine so the only option is playing
with the disk image.
TIA,
Ruzsi
9 years
[libvirt-users] libvirt beginner needs to create and start VMs entirely on command line
by KARR, DAVID
I'm a beginner to libvirt and creating VMs, for that matter. I have a set of specifications for VMs I need to create and log into, but I have to create them on an Ubuntu box that I only have ssh access to. I won't have desktop GUI access, although I do have dynamic port forwarding, so I can access a browser GUI from my desktop.
Reading through the libvirt info, I see numerous mentions about using VNC to do additional work, but I won't be able to use VNC (not allowed within our firewall).
I could use some advice on how to move forward with this. I've started at https://help.ubuntu.com/lts/serverguide/libvirt.html for initial information.
I managed to create a disk image for my first VM, and I believe I created the first VM using an ISO (based on CentOS, I believe), but I'll probably have to rebuild that, because I think I have to configure networks on the VM, which I didn't do on initial creation. I was confused by the initial results from "virt-install", because it seemed to hang after a second or two (I posted this SO question about this: http://stackoverflow.com/questions/31302871/trouble-using-virt-install-on... ). The reply from this makes it seem like it was trying to present a GUI for next steps, but I of course never saw that. The VM appears to exist, but in a "shut off" state.
9 years
[libvirt-users] Fw: Error attaching tape drive device to KVM guest
by Jake Kugel
A quick follow-up in case anyone else is trying to use IBM tape device
within a KVM guest. I didn't get SCSI passthrough below working, but
there were two alternatives recommended to me:
(1) Use PCI passthrough to give the KVM guest dedicated access to the
Fibre Channel HBA PCI card. PCI passthrough seems to be more solid.
(2) Use ISCSI to share the tape devices and tape changer devices from
physical host, and use ISCSI client on KVM guest to access.
We were successful using option 2 even though there is performance penalty
for bridging with ISCSI. It gives us greater flexibility, we don't have
to dedicate a PCI card to the KVM guest.
----- Forwarded by jkugel us ibm com on 07/10/2015 01:50 PM -----
jkugel us ibm com wrote on 07/06/2015 10:23:45 AM:
> From: jkugel us ibm com
> To: libvirt-users(a)redhat.com
> Date: 07/06/2015 10:23 AM
> Subject: Error attaching tape drive device to KVM guest
>
> Hello,
>
> i'm trying to configure a host SCSI device (tape drive) so that it
> is available in a KVM guest VM, but am receiving an error when
> attempting to attach the device. My guest xml has the following
> scsi controller defined:
>
> <controller type='scsi' index='0' model='virtio-scsi'>
> <alias name='scsi0'/>
> <address type='pci' domain='0x0000' bus='0x00' slot='0x04'
> function='0x0'/>
> </controller>
>
> I created tapedrive.xml with following contents:
>
> <disk type='block' device='lun' sgio='unfiltered'>
> <driver name='qemu' type='raw' cache='none'/>
> <source dev='/dev/st0'/>
> <target dev='st0' bus='scsi'/>
> <address type='drive' controller='0' bus='0' target='0' unit='0'/>
> </disk>
>
> I then attempt to attach using following command, and receive this
error:
>
> # virsh attach-device instance-0000002d tapedrive.xml --config
> error: Failed to attach device from tapedrive.xml
> error: internal error: Invalid harddisk device name: st0
>
> Does anyone know cause of the error? In <address> section of tape
> drive definition I am using type='drive', I tried type='tape' also
> but same error. is there a different property value I should use
> here, or general advice for attaching tape drive to KVM guest? Thanks,
Jake
9 years