/qubes-issues

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

No more qubes-manager after assigned peripherals #3131

Open
boistordu opened this Issue Sep 28, 2017 · 15 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 3.2 updates
4 participants
@boistordu @marmarek @vladimir-lu @andrewdavidwong
@boistordu

boistordu commented Sep 28, 2017

Qubes OS version (e.g., R3.2):

3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

Hvm of Ubuntu

Steps to reproduce the behavior:

I ve assigned the graphic Intel gpu from the laptop to the hvm

Expected behavior:

if the peripherals was not supposed to be assigned then why not throw an error message.

Actual behavior:

Black screen then reboot of the laptop-> no more qvm-manager, I can't launch it anymore

General notes:

i don't see how to restore the whole os. I can't do a thing because of that right now.

Related issues:
@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Sep 28, 2017

Of someone has a solution for me to restore my system it would be great.

boistordu commented Sep 28, 2017

Of someone has a solution for me to restore my system it would be great.
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Sep 28, 2017

Member

Try qvm-pci tool to detach device from the VM.
Member

marmarek commented Sep 28, 2017

Try qvm-pci tool to detach device from the VM.
@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Sep 28, 2017

boistordu commented Sep 28, 2017

@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Sep 28, 2017

It doesn't work. I'm going to send a link for a photo about the error

boistordu commented Sep 28, 2017

It doesn't work. I'm going to send a link for a photo about the error
@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Sep 28, 2017

image

boistordu commented Sep 28, 2017

image
@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Sep 28, 2017

Would be deleting the vm a good idea?
It s a basic vm so nothing important in there. But I don't know how to do it exactly?

boistordu commented Sep 28, 2017

Would be deleting the vm a good idea?
It s a basic vm so nothing important in there. But I don't know how to do it exactly?
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Sep 28, 2017

Member

Looks like /var/lib/qubes/qubes.xml file is broken (empty). If that's the case, restore it from latest backup in /var/lib/qubes/backup. Then check if all your VMs are there.
Member

marmarek commented Sep 28, 2017

Looks like /var/lib/qubes/qubes.xml file is broken (empty). If that's the case, restore it from latest backup in /var/lib/qubes/backup. Then check if all your VMs are there.
@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Sep 28, 2017

boistordu commented Sep 28, 2017

@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Sep 28, 2017

boistordu commented Sep 28, 2017

@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Sep 28, 2017

So just for more debugging for you.
The fs I ve partition for /var/lib/qubes was xfs. Since I ve red somewhere that xfs has better performance for vm disk file but could loose maybe small files from time to time, I guess so that's because maybe of that.

I've installed qubes 4 days ago only.
So it would be maybe a better idea to put a cron or to backups qubes.xml everytime a modification is made in place of each reboot...

boistordu commented Sep 28, 2017

So just for more debugging for you.
The fs I ve partition for /var/lib/qubes was xfs. Since I ve red somewhere that xfs has better performance for vm disk file but could loose maybe small files from time to time, I guess so that's because maybe of that.

I've installed qubes 4 days ago only.
So it would be maybe a better idea to put a cron or to backups qubes.xml everytime a modification is made in place of each reboot...
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Sep 28, 2017

Member

Well, if random filesystem corruption happens, it means that filesystem should be avoided... FWIW I had similar experience with xfs some years ago - it is no use for systems without very stable power supply (big UPS etc).
Making backups is a good thing anyway, we have qvm-backup (or GUI version in Qubes Manager) for that. I hope you didn't have anything unrecoverable there...
Yes, the easiest thing to do now is to reinstall - if one file got corrupted, there may be more affected.
Member

marmarek commented Sep 28, 2017

Well, if random filesystem corruption happens, it means that filesystem should be avoided... FWIW I had similar experience with xfs some years ago - it is no use for systems without very stable power supply (big UPS etc).
Making backups is a good thing anyway, we have qvm-backup (or GUI version in Qubes Manager) for that. I hope you didn't have anything unrecoverable there...
Yes, the easiest thing to do now is to reinstall - if one file got corrupted, there may be more affected.
@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Sep 28, 2017

boistordu commented Sep 28, 2017

@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Sep 28, 2017

No any advice?

By the way, this was not an electrical problem. But the system crashed pure and simple so even if you have no electrical problem, the problem could occur

boistordu commented Sep 28, 2017

No any advice?

By the way, this was not an electrical problem. But the system crashed pure and simple so even if you have no electrical problem, the problem could occur

@andrewdavidwong andrewdavidwong added bug C: qubes-manager labels Sep 29, 2017

@andrewdavidwong andrewdavidwong added this to the Release 3.2 updates milestone Sep 29, 2017

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Sep 29, 2017

Member

You can try btrfs. I haven't used it much personally, but people recommend it. In practice ext4 work really good on SSD too. You just need to remember to enable TRIM operation support: https://www.qubes-os.org/doc/disk-trim/
Member

marmarek commented Sep 29, 2017

You can try btrfs. I haven't used it much personally, but people recommend it. In practice ext4 work really good on SSD too. You just need to remember to enable TRIM operation support: https://www.qubes-os.org/doc/disk-trim/
@vladimir-lu

This comment has been minimized.

Show comment
Hide comment
@vladimir-lu

vladimir-lu Apr 7, 2018

I'm not sure this is the right issue for this, but I also had a blank qubes.xml with 4.0-RC5. dom0 filesystem is btrfs and it scrubs out OK, so corruption is probably not the cause. I saw in the backups directory that there was one more zero-size qubes.xml. It could be related to the previous shutdown where the dm filesystems were timing out and I just pressed the power button after 2 minutes though. Is qubes.xml written upon shutdown of qubesd by any chance?

vladimir-lu commented Apr 7, 2018

I'm not sure this is the right issue for this, but I also had a blank qubes.xml with 4.0-RC5. dom0 filesystem is btrfs and it scrubs out OK, so corruption is probably not the cause. I saw in the backups directory that there was one more zero-size qubes.xml. It could be related to the previous shutdown where the dm filesystems were timing out and I just pressed the power button after 2 minutes though. Is qubes.xml written upon shutdown of qubesd by any chance?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment