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

VHM shutdown on iso installation process - copy files to disk #3508

Closed
virgileaime opened this Issue Jan 30, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@virgileaime

virgileaime commented Jan 30, 2018

Hello, i'm running 4.0 rc3.
I am trying to install both Kali and Windows 7 on a qube. The installation process works fine until shutting down abruptly in the middle of copying the files to the partition.

I have the same problem with kali, win7, win10 and most probably other ISOs as well.
The qube runs with sufficient RAM (6GB and more) and sufficient disk space ...

I am able to run Kali Live however.

Can somebody help ?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 30, 2018

Member

See /var/log/xen/console/guest-VMNAME-dm.log (replace VMNAME with actual name).
Have you created them as "StandaloneVM" (if using command line) or "Standalone qube not based on template" (if using GUI)?

Member

marmarek commented Jan 30, 2018

See /var/log/xen/console/guest-VMNAME-dm.log (replace VMNAME with actual name).
Have you created them as "StandaloneVM" (if using command line) or "Standalone qube not based on template" (if using GUI)?

@doug1

This comment has been minimized.

Show comment
Hide comment
@doug1

doug1 Jan 30, 2018

I had similar problem installing Win7 about a month ago and the fix was to disable memory balancing and set the memory and maxmem to the same number. If that works, it might provide a hint as to the cause.

doug1 commented Jan 30, 2018

I had similar problem installing Win7 about a month ago and the fix was to disable memory balancing and set the memory and maxmem to the same number. If that works, it might provide a hint as to the cause.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 31, 2018

Member

Ah, yes! Same here: #3432 (comment)

Member

marmarek commented Jan 31, 2018

Ah, yes! Same here: #3432 (comment)

@virgileaime

This comment has been minimized.

Show comment
Hide comment
@virgileaime

virgileaime Jan 31, 2018

It worked. Disabled memory balancing and set the memory at the same level.
Thanks

It worked. Disabled memory balancing and set the memory at the same level.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment