IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Do not use the model specified by the OS if it is "virtio-net" and
virtionet is not supported.
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1177113
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Try to use --boot uefi if the user hasn't already specified loader params,
or a kernel to boot. If we can't determine a UEFI setup, just print a
warning.
Introduced by f16dc4dd34
This will cause test case failure on different machines.
Use '/var' to replace it.
Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
Drop redundant tests, organize things better, add more tests where we
can stick new cli device options and view the output, since that's the
most common extension.
The value 4294967295 used in the testdriver for sheepdog volume is not
valid on 32bit systems as it won't fit in uid_t and libvirt will fail
parsing that.
Running "./setup.py test" then fails with:
raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: XML error: malformed owner element
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Handle type=network in devicedisk.py, and wire up all the network fields
for virt-install --disk. Right now it requires manually spelling out
all the protocol, name, host/port etc fields.
The one 'magic' bit is that VirtualDisk.path will be a pretty URL when
all those network fields are specified. This is keeps things mostly
working in various parts of the code where we expect 'path' to be an
identifier for a VirtualDisk.
And break about the vol_install vs local clone storage creators. And
just generally delete a lot of code. The commit aint pretty but it works
and deletes a ton of hacks
clitest.py used the value 100000000000 (100 PB) for memory size, which
was parsed as 0 by older libvirt. Latest release (1.2.10) has the
parsing fixed and properly reports an error on overflow. Changing the
memory size to 4000000 (4 TB) is still an overcommit, at least most
development machines and it works properly.
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
