-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template creation errors #1157
Comments
same on fedora 26, kimchi 2.5.0, wok 2.5.0 |
I have same error code but a bit different message. I just installed wok and kimchi then i removed the default ISO store and added a new ISO store on different drive. So the drive where the ISOs is stored is not sda it's a btrfs raid 1 |
I don't have any Debian system to validate it. Debian is not usually tested by Kimchi community. Which OS are you seeing that? |
Hi @alinefm |
@shii1 It is an open source community in which people contribute thinking about their preferred OS. The file you mentioned is only an installation guide. Unfortunately, it does not mean the project is free of bugs. If I can reproduce the problem on Ubuntu 17.04 or Fedora 26, I will take a look to fix that. |
Hello
I use Ubuntu 17.10.
I tested and if I create a json file with URL to the iso under the
configuration directory, than I'm able to create a template.
But if I use the ISO from the data store then I get the error message.
Regards,
Fredrik
tis 25 juli 2017 kl. 20:17 skrev Aline Manera <notifications@github.com>:
… @shii1 <https://github.com/shii1> It is an open source community in which
people contribute thinking about their preferred OS.
Debian was already focus of some people before but today there is no one
working closely on it. Don't you want to be that person? :-)
The file you mentioned is only an installation guide. Unfortunately, it
does not mean the project is free of bugs.
If I can reproduce the problem on Ubuntu 17.04 or Fedora 26, I will take a
look to fix that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1157 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUTm5unaXP6a3UGvbFr7ef0wCsVNODUuks5sRjFOgaJpZM4OS-sn>
.
|
Thanks for the information, @Fredrik81 So you tried to create a Template from a predefined remote ISO (aka, from a URL) and it failed, right? |
Hello
No its a local BTRFS raid1 on same server as Kimchi.
ISO datastore is called "ISO" and path is //mnt/Kimchi/ISO
Regards,
Fredrik
tis 25 juli 2017 kl. 20:28 skrev Aline Manera <notifications@github.com>:
… Thanks for the information, @Fredrik81 <https://github.com/fredrik81>
So you tried to create a Template from a predefined remote ISO (aka, from
a URL) and it failed, right?
Just to make sure I will follow the same steps as yours.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1157 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUTm5n27nulSQ8wSFRFyhYUGNw2p5TrWks5sRjOwgaJpZM4OS-sn>
.
|
@alinefm |
@shii1 Did you get the same problem while using which type of ISO? A remote URL, from local dir pool? |
@alinefm |
Same issue for me, but on both Fedora 25 and Fedora 26.
What must I do to fix this issue? I can work around it for now, by using an existing built-in template such as the Fedora 24 one, and then just changing the .iso path before turning on the VM. But I'd really like to know if there's some commands I can run to fix it. |
Hi all, I was able to create a Template running Kimchi on Fedora 25 and using a Fedora 26 ISO image. I am still trying to reproduce that, but so far, it works for me. |
I just set up kimchi 2.5.0 and wok 2.5.0 on Fedora 26 and have this same issue. dunno if this helps:
{"info": {"status": 200, "zone": "PDT", "ip": "100.64.1.100", "app": "", "req": "POST", "user": "admin", "time": "22:33:10", "date": "2017-09-06"}, "message": {"code": "WOKROOT0001L", "params": {"username
": "admin"}}, "id": "fe8d84d2-e8cc-476b-aa74-3252b5022fdf", "error": null}
{"info": {"status": 200, "zone": "PDT", "ip": "", "app": "/plugins/kimchi", "req": "TASK", "user": "", "time": "22:33:37", "date": "2017-09-06"}, "message": {"code": "WOKASYNC0001L", "params": {"target_ur
i": "/plugins/kimchi/storagepools/kimchi_isos"}}, "id": "38d47e85-81e2-4b4b-a8cf-41e4af06fc1d", "error": null}
{"info": {"status": 500, "zone": "PDT", "ip": "100.64.1.100", "app": "/plugins/kimchi", "req": "POST", "user": "admin", "time": "22:34:00", "date": "2017-09-06"}, "message": {"code": "KCHTMPL0001L", "para
ms": {"os_distro": "ubuntu", "disks": "[{'base': '/var/lib/kimchi/isos/ubuntu-16.04.3-server-amd64.iso'}]", "name": "", "os_version": "16.04"}}, "id": "0780784f-77e6-4bc4-8de5-3d280ceeb0b0", "error": {"co
de": "KCHTMPL0020E", "params": {"err": "KCHIMG0001E: Error probing image OS information: part_list: parted print: /dev/sda: Warning: The driver descriptor says the physical block size is 2048 bytes, but L
inux says it is 512 bytes."}}} # uname --kernel-name --kernel-release --kernel-version
Linux 4.12.9-300.fc26.x86_64 #1 SMP Fri Aug 25 13:09:43 UTC 2017
# parted --list
Model: ATA SAMSUNG SSD SM87 (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 211MB 210MB fat16 EFI System Partition boot, esp
2 211MB 735MB 524MB ext2
3 735MB 512GB 511GB lvm |
I could reproduce that now. I am working on a patch to fix that. |
I, too, have just hit this on Debian 9.1 (along with the outstanding libvirt-bin situation). Pleased to see it's being worked on. If there's anything I can do to help @alinefm - please let me know as I have a client project stalled because of it. |
While creating a Template, the user can provide an ISO file or an Image file. Kimchi relies on python magic to get the file mime type and it was only considering ISO 9660 CD-ROM as valid for ISO images and it was fall backing to an Image file and failing . Add DOS/MBR as well to fix that problem. Signed-off-by: Aline Manera <aline.manera@gmail.com>
Sorry, forgot to restart wokd |
While creating a Template, the user can provide an ISO file or an Image file. Kimchi relies on python magic to get the file mime type and it was only considering ISO 9660 CD-ROM as valid for ISO images and it was fall backing to an Image file and failing . Add DOS/MBR as well to fix that problem. Signed-off-by: Aline Manera <aline.manera@gmail.com>
Hello, |
Even after deploying the patch it doesn't work. My LVM has
EDIT: I'm now using a workaround:
This adds a Ubuntu Server 18.04.1 image from the download-server. That way a template can be created and I can setup VMs. |
In case someone else has trouble finding the location of templates.py, here it is (Ubuntu 18): I manually applied the fix from 1ec059a, restarted wokd with |
While creating a Template, the user can provide an ISO file or an Image file. Kimchi relies on python magic to get the file mime type and it was only considering ISO 9660 CD-ROM as valid for ISO images and it was fall backing to an Image file and failing . Add DOS/MBR as well to fix that problem. Signed-off-by: Aline Manera <aline.manera@gmail.com>
Tried it, it doesn't appear on the list. Running ubuntu server 18.04 EDIT: it was because some links are 404. You may want to update your files. Thanks for the workaround btw. |
Here's the commands I used to get everything working from a fresh install - you do need to run it as root (
|
Hello,
I have just installed kimchi to give it another go, but I'm not able to get past template.
When I try to use preconfigured images, I get following error:
KCHVM0005E: Remote ISO image is not supported by this server.
Not sure how to verify it.
When I try to create a template using downloaded iso (debian 8 or 9):
KCHTMPL0020E: Unable to create template due error: KCHIMG0001E: Error probing image OS information: part_list: parted print: /dev/sda: Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes.
Debian GNU/Linux 9 (stretch) SMP Debian 4.9.30-2+deb9u2
libvirt 3.0.0-4
ii ginger 2.4.0
ii ginger-base 2.3.0
ii kimchi 2.5.0
ii wok 2.5.0
The text was updated successfully, but these errors were encountered: