07-28-2014
KVM guests unique ID
Hi,
I wanted to know if there was a way to get a unique UUID for KVM guest from the guest OS which isn't easily modifiable. I have a software that I would like to run inside a KVM guest and want to do some license protection on it using a unique UUID. Does KVM allow multiple VMs on the same machine with same UUID. I mean if someone edits the configuration file of the VM manually from the host, would it still bring up the VM if the uuid was duplicated ? Also how can I get the uuid of a guest VM from the guest ?
Also if someone could throw some light on guest host communication channel. Is there an equivalent of Xenstore or guest property store in KVM ? Some mechanism to share small messages between the guest and the host.
Thanks
Shivani
5 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have an archive file that holds a batch of statements. I would like to be able to extract a certain statement based on the unique customer # (ie. 123456). The end for each statement is noted by "ENDSTM".
I can find the line number for the beginning of the statement section with sed.
... (5 Replies)
Discussion started by: andrewsc
5 Replies
2. Virtualization and Cloud Computing
Hi,
we try to export a Solaris installation from one laptop to another. I installed Solaris as 64 bit guest OS on my Mac in VirtualBox. After the transfer of the exported files to the other laptop (Dell Studio with T4300 Intel CPU) we try to start the guest in 64 bit mode but the guest only runs... (2 Replies)
Discussion started by: DukeNuke2
2 Replies
3. HP-UX
Hi All,
There are few threads regarding this subject of being unable to create more guests due to lack of RAM. So I am aware how the sum works.. add 8.5% to whatever is allocated, be that the host or guest. But I'm not sure if I have a hardware issue with memory or what I see is correct as I am... (3 Replies)
Discussion started by: EricF
3 Replies
4. Shell Programming and Scripting
I have 84 files with the following names splitseqs.1, spliseqs.2 etc.
and I want to change the .number to a unique filename.
E.g.
change splitseqs.1 into splitseqs.7114_1#24
and
change spliseqs.2 into splitseqs.7067_2#4
So all the current file names are unique, so are the new file names.... (1 Reply)
Discussion started by: avonm
1 Replies
5. UNIX for Dummies Questions & Answers
I would like to print unique lines without sort or unique. Unfortunately the server I am working on does not have sort or unique. I have not been able to contact the administrator of the server to ask him to add it for several weeks. (7 Replies)
Discussion started by: cokedude
7 Replies
LEARN ABOUT NETBSD
xbdback
XBDBACK(4) BSD/xen Kernel Interfaces Manual XBDBACK(4)
NAME
xbdback -- Xen backend paravirtualized block device interface
SYNOPSIS
pseudo-device xbdback
DESCRIPTION
The xbdback interface forms the backend part of the paravirtualized drivers used by Xen domains to offer a block device interface, similar to
a hard disk. xbdback interfaces are backed either by a physical device directly, or an image file mounted through vnd(4).
All xbdback interfaces follow the ``xbdbackXiY'' naming convention, where 'X' represents the guest domain identifier, and 'Y' an arbitrary
identifier. This identifier is usually associated to the device node as seen by the guest using major(3) and minor(3) numbers. For example,
identifier ``769'' (0x301) means major 3 and minor 1, identified as ``hda1'' under Linux convention. For NetBSD, the guest device name spec-
ified in the guest configuration file does not matter, and can be chosen arbitrarily.
A xbdback interface will appear as a xbd(4) block device inside a NetBSD guest domain. In the XenStore, xbd and xbdback are identified by
``vbd'' (virtual block device) entries.
DIAGNOSTICS
xbd backend: attach device %s (size %d) for domain %d Gives the device used as xbdback interface for the given guest domain, and its size,
in bytes.
xbd backend 0x%x for domain %d using event channel %d, protocol %s Gives the backend identifier, guest domain ID, event channel ID, and pro-
tocol used for block level communication.
xbdback %s: can't VOP_OPEN device 0x%x: %d When this message appears in the system message buffer with error 16 (EBUSY), the device is
likely to be already mounted. It must be unmounted first, as the system will refuse to open it a second time.
SEE ALSO
vnd(4), xbd(4), xenbus(4)
HISTORY
The xbdback driver first appeared in NetBSD 4.0.
AUTHORS
The xbdback driver was written by Manuel Bouyer <bouyer@NetBSD.org>.
BSD
June 7, 2011 BSD